On This Page
Known Issues
Transaction Search in the Business Center | EPS-37818
Transaction Search in the Business Center
| EPS-37818- Description
- For a similar search in the Business Center that has over 20 results (1 page), clicking the next page only shows 1 new result. Instead of returning results 21-40, results 2-21 are returned. When the user clicks page 3, results 3-22 are returned.
- Audience
- Global.
- Technical Details
- None.
- Workaround
- None.
Recurring Billing | EPS-37751
Recurring Billing
| EPS-37751- Description
- This issue affects subscriptions that fulfill these criteria:
- A recurring payment fails or is skipped for the month of February.
- The date of payment falls on the 29th - 31st of the month.
- The payment is subsequently retried successfully.
For these subscriptions, the billing cycle is incorrectly recalculated such that the date of payment falls on the 28th of the month instead of the original date (29, 30 or 31). - Audience
- Merchants who use Recurring Billing.
- Technical Details
- None.
- Workaround
- None.
Portfolio Management | EPS-37583
Portfolio Management
| EPS-37583- Description
- When a transacting organization is set to Inactive, it is still shown as a selectable option from its parent merchant organization.
- Audience
- Users of portfolio accounts.
- Technical Details
- None.
- Workaround
- None.
Virtual Terminal | EPS-37322
Virtual Terminal
| EPS-37322- Description
- The postal code cannot be set as Required for any country except the US and Canada.
- Audience
- Global.
- Technical Details
- None.
- Workaround
- Set the postal code manually.
SDK | EPS-37838
SDK
| EPS-37838- Description
- When a merchant uses the Cybersource .NET SDK (NuGet CyberSource.Rest.Client v0.0.1.62) to perform a GET request, the SDK incorrectly adds a digest header and includes the digest in the HTTP Signature's signed-headers list. Per the HTTP Message Signatures specification, Digest should only be signed for requests that have a body, for example, POST or PUT. Merchants might receive validation failures for signed requests.
- Audience
- Merchants using the SDK.
- Technical Details
- None.
- Workaround
- None.