Recurring Billing
| EPS-32204

Description
When these steps are performed in the Business Center, the Payment History section of the Subscription ID Detail Page is not displayed:
  1. Navigate to
    Virtual Terminal > Recurring Billing
    .
  2. Change the Subscription Scope from All Subscriptions to Subscription ID.
  3. Add a search filter for Subscription ID and enter an ID that has a processed payment associated with it.
  4. Open the ID details.
Audience
Merchants who use the Recurring Billing feature in the Business Center.
Technical Details
None.
Workaround
None.

Reporting
| EPS-32060

Description
An intermittent issue may cause the Exception Detail Report to generate an incorrect amount.
Audience
Merchants processing on TSYS/Vital.
Technical Details
An exponent discrepancy is generated in the Exception Detail Report by a factor of 100. For example,19.99 instead of 1999. This issue does not affect the Business Center, Processing, or Batching.
Workaround
None.

Payment Processing
| EPS-32199

Description
The Omnipay Reason Code 54 (Expired Card) is currently wrongly mapped to VAS Reason Code 102 DINVALIDDATA instead of 202 DCARDREFUSED.
Audience
Merchants who process on Lloyds-OmniPay.
Technical Details
None.
Workaround
None.

Batching
| EPS-31102

Description
Batch failures are not correctly added to the Transaction Exception Detail Report for American Express Direct.
Audience
Merchants who process on the American Express Direct gateway.
Technical Details
None.
Workaround
Merchants can review transaction in the transaction detail page to review their settlement status.

Payments
| EPS-31247

Description
When a merchant attempts to perform a full authorization reversal and settlement on the same transaction within a very short time frame (1-2 seconds apart), both operations are processed successfully. The settlement should fail because the authorization was reversed. In the Business Center, both the reversal and settlement appear as successful transactions.
Audience
Merchants in Central and Eastern Europe, the Middle East, and Africa.
Technical Details
None.
Workaround
None.

Payments
| EPS-31552

Description
Some issuers are overriding the customer-provided last name in Apple Pay transactions and populating the last name field with a slash (/) character. Consequently, those transactions are failing with Reason Code 102.
Audience
Merchants that accept Apple Pay.
Technical Details
None.
Workaround
None.

Reporting
| EPS-31952

Description
One-Time Reports are using GMT even if you have set up a different time zone.
Audience
Users of Reporting.
Technical Details
None.
Workaround
None.

Payments
| EPS-31987

Description
When a user in the Business Center processes a payment using a token from our legacy Secure Storage or Recurring billing systems, the following issues occur:
  • The client application displays
    SCMP API
    instead of
    LEGACY TOKEN PAYMENT
    .
  • The user who submitted the transaction is not shown in reports or the Transaction Details page.
Audience
Merchants who process payments using a token from our legacy Secure Storage or Recurring Billing systems.
Technical Details
None.
Workaround
None.

Payment Processing
| EPS-31570

Description
An intermittent issue is affecting the Elavon Americas gateway. Batching files for credit transactions sometimes omit the Transaction Reference Number.
Audience
Merchants who use the Elavon Americas gateway.
Technical Details
None.
Workaround
None.

Developer Center
| EPS-31591

Description
In the Developer Center, the request header
v-c-idempotency-id
is not yet supported for the Merchant Boarding API, although it is shown on the page.
Audience
Developers who test the Merchant Boarding API in the Devloper Center.
Technical Details
Sending the
v-c-idempotency-id
request header in the Merchant Boarding API request through the Developer Center, results in this error message:
Unexpected error occured while processing the request
.
Workaround
If you need to test the Merchant Boarding API, use your own testing tool instead of the Developer Center.

Merchant Management
| EPS-31808

Description
Users may experience an issue when attempting to view merchant details from the Manage Merchants page in the Portfolio Management section of the Business Center. The intermittent issue causes the page to turn blank and an error message appears before disappearing.
Audience
Users of Merchant Management.
Technical Details
None.
Workaround
None.

Decision Manager
| EPS-31837

Description
When adding the customer IP Address field to the negative list in the Business Center's Transactions Marking Tool, the field is not added to the list, although the action appears successful.
Audience
Users of Decision Manager.
Technical Details
None.
Workaround
None.

Reporting
| EPS-31140

Description
An intermittent issue sometimes causes missing data in the daily Transaction Request Report.
Audience
Users of Reporting.
Technical Details
None.
Workaround
Regenerate the report.

Webhooks
| EPS-31912

Description
A recent change to Invoicing webhooks added two new fields to the webhook payload. Some merchants are unable to process the new fields, causing errors with their integrations.
Audience
Merchants who use Invoicing webhooks.
Technical Details
None.
Workaround
None.

Batching
| EPS-31607

Description
When the transactions fail during batching, merchants are notified by email. In that email, there are three links to articles. Those links are not working because they are pointing to the wrong location.
Audience
Users of batching.
Technical Details
None.
Workaround
The correct links are:

Decision Manager
| EPS-31784

Description
An intermittent error sometimes causes inaccurate results when Case Management searches use Mark as Suspect as a criterion.
Audience
Users who process a large volume of transactions using Decision Manager.
Technical Details
None.
Workaround
Try using multiple searches, each covering a shorter time period.

Decision Manager
| EPS-31819

Description
A defect is causing the Business Center to generate a new authorization from an existing transaction. If the original transaction had a comma in the amount, the new authorization request results in an incorrect error message:
mitcofsubauthoriginalamount is invalid
.
Audience
Users of the Business Center.
Technical Details
None.
Workaround
None.