Known Issues

Security Keys
| EPS-33083

Description
Users who have custom roles that include key management permissions might not be able to download an Apple Pay Certificate Signing Request, even though the Business Center says it was successfully downloaded.
Audience
Users of the Business Center.
Technical Details
None.
Workaround
None.

Decision Manager Reports and Profile Statistics
| EPS-33856

Description
When users of Decision Manager's Case Management page compare the cases for a particular time period with the cases showing in the Profile Statistics dashboard for the same time period, the numbers might not match. For example, Case Management might show 100 Accept and 50 Reject cases, while Profile Statistics might show 95 Accept and 60 Reject cases.
Audience
Merchants using Decision Manager and Profile Statistics.
Technical Details
None.
Workaround
None.

Pay By Link
| EPS-34132

Description
When the customer views the receipt URL link for a transaction processed using Pay by Link, they might see a blank page with the following message:
'Error: Unexpected server error'
.
Additionally, the merchant might also encounter a red banner error in the Business Center when attempting to view the Settings page for Pay by Link.
Audience
Merchants and customers using Pay by Link.
Technical Details
None.
Workaround
None.

Unified Checkout
| EPS-34183

Description
When merchants use
billingType=NONE
in the capture context, in conjunction with Payer Authentication, the transaction sometimes fails with error message
DMISSINGFIELD RC 101
, related to the Billing Address Information.
Audience
Merchants using Unified Checkout.
Technical Details
None.
Workaround
None.

Payment Processing
|
EPS-34267

Description
This defect occurs when merchants process authorization transactions through the Barclays processor during network connectivity issues. From the merchant's perspective, they receive a response saying "Request has timed out, transaction not sent to Processor" with reason code 150 (ESYSTEM), leading them to believe the transaction failed. However, the acquirer (Barclays) actually processes the authorization and issues an authorization code, resulting in customer funds being held.
The merchant experiences this issue through both API responses and the Business Center interface, where they see failed transactions that actually succeeded on the processor side. This creates a mismatch between what the merchant sees in their reports versus what actually happened with the customer's payment method, leading to customer complaints about unexpected holds on their funds.
Audience
Merchants in the EU and UK who use Barclays as an acquirer and processor.
Technical Details
Workaround
  • Check directly with Barclays to confirm transaction status before retrying.
  • For payouts specifically, verify status with Barclays before attempting retries.
  • Use standalone transactions instead of retrying potentially successful ones.

Decision Manager
| EPS-34323

Description
Missing response for Apple Pay when Decision Manager returns the review status.
Audience
Merchants who use Decision Manager and Apple Pay.
Technical Details
None.
Workaround
None.

Portfolio Management
| EPS-34345

Description
Portfolio users in India cannot trigger user registration email to the merchants.
Audience
Portfolio users in India.
Technical Details
None.
Workaround
Use an administrator account.