Reporting | EPS-32060
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
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
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
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
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
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
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 displaysSCMP APIinstead ofLEGACY 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
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
Developer Center
| EPS-31591- Description
- In the Developer Center, the request headerv-c-idempotency-idis 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 thev-c-idempotency-idrequest 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
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
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
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
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
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
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
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.
REST API | EPS-27519
REST API
| EPS-27519- Description
- Our REST API specification shows that the fieldmerchantInformation.merchantDescriptor.alternateNamehas a maximum character value of ≤ 13 characters. However, the validation is not working and allows more than 13 characters.
- Audience
- Developers using the REST API.
- Technical Details
- None.
- Workaround
- None.
Payer Authentication | EPS-30938
Payer Authentication
| EPS-30938- Description
- Optional text messages from issuers to cardholders in multibyte characters might not be displayed properly in Frictionless Payer Authentication Enrollment transaction responses for merchants. As a result, merchants might not be able to display the multibyte characters to cardholders on merchant sites in readable format.
- Audience
- Merchants who use Frictionless Payer Authentication Enrollment and cardholders with text information provided by the ACS/Issuer, which can include possible follow-up actions to be done for their authentication transactions.
- Technical Details
- None.
- Workaround
- None.
Token Management Service | EPS-31044
Token Management Service
| EPS-31044- Description
- An intermittent issue sometimes prevents Mastercard Token Requestor Identifier (TRID) enrollment from returning the TRID value in the Business Center, despite showing a success message.
- Audience
- Merchants who process network token transactions.
- Technical Details
- None.
- Workaround
- None.
Microform | EPS-31200
Microform
| EPS-31200- Description
- Microform transient tokens created using the version 2 JavaScript libraries are prevented from being authorized.
- Audience
- Merchants who use Microform version 2.
- Technical Details
- The error is generic due to a mapping issue.
- Workaround
- None.
Decision Manager Detail Report | EPS-31348
Decision Manager Detail Report
| EPS-31348- Description
- An intermittent issue in our testing environment sometimes causes the Decision Manager Detail Report to have two columns that have the same data, but with two different names. The names areDevice Fingerprint Date Device First SeenandDevice Fingerprint Device First Encounter.
- Audience
- Users of the Decision Manager Detail Report.
- Technical Details
- None.
- Workaround
- None. The report works correctly in the production environment.
Decision Manager Case Search | EPS-31428
Decision Manager Case Search
| EPS-31428- Description
- When a user performs a case search based on a particular Decision Manager profile, only a subset of the result is returned. However, a general case search based on a time period returns the full results. A free-text case management search also does not return the correct results.
- Audience
- Users of Decision Manager Case Results.
- Technical Details
- None.
- Workaround
- Use a general case search and filtering it according to your needs.
Token Management Service | EPS-31481
Token Management Service
| EPS-31481- Description
- Sometimes when a user deletes a token, it still appears active in the Business Center.
- Audience
- Users of the Token Management Service.
- Technical Details
- None.
- Workaround
- None.