Known Issues {#rn-known-issues} =============================== **Transaction History Might Not Display in Alternative Payments** \| EPS-42339 ------------------------------------------------------------------------------ Description : When merchants view the details of an authorization or captured payment transaction for Alternative Payments, the transaction history might not display any related credits that have been processed against the transaction. Additionally, the transaction history displays only the related capture and does not show associated transactions. Audience : Merchants who use Alternative Payments. Technical Details : None. Workaround : Use an alternative transaction identifier, such as the Merchant Reference Number (MRN), to find related transactions. **BIN Data Unavailable for Follow-On Transactions in Business Center Reporting** \| EPS-42464 --------------------------------------------------------------------------------------------- Description : Merchants are unable to view Bank Identification Number (BIN) data for follow-on transactions in Business Center Reports. In the Transaction Request Report (TRR) and Payment Batch Detail Report (PBDR), BIN data is not displayed for settlements, credits, and other follow-on transactions. Audience : Merchants who reference BIN number data in Business Center reports. Technical Details : Follow-on transactions do not store or carry card number information. As a result, BIN data is unavailable for these transactions. Workaround : No known workaround. **Some Account Updater Batches Remain in Processing State** \| EPS-42645 ------------------------------------------------------------------------ Description : For merchants using Account Updater, some batches submitted on August 20, 2026, might remain in a **Processing** state and not complete automatically. As a result, batch results might be delayed until someone manually intervenes. Audience : Merchants who use Account Updater. Technical Details : None. Workaround : No known workaround. **Transaction Search REST API Returns Empty `installmentInformation` Field** \| EPS-42700 ----------------------------------------------------------------------------------------- Description : When merchants use the Transaction Search REST API, the `installmentInformation` field is returned as empty, even when installment data exists for the transaction. As a result, merchants cannot retrieve installment information through Transaction Search. Audience : Merchants who use the Transaction Search REST API. Technical Details : The data source referenced by the Transaction Search REST API does not capture installment information. As a result, the `installmentInformation` field is always returned as empty. A change to the underlying data source is required in order to make this data available. Workaround : Use the Transaction Details REST API, which correctly returns `installmentInformation` data. **Incorrect Merchant Country in Checkout Sessions Might Affect Apple Pay Availability** \| EPS-42780 ---------------------------------------------------------------------------------------------------- Description : When a merchant uses Invoicing or Pay By Link with Unified Checkout, the checkout session is generated with the merchant country set to `US`, even when the merchant is located in another country. As a result, non-US merchants might experience missing or unavailable Apple Pay payment options during checkout. Audience : Non-US merchants who use Invoicing or Pay By Link with Unified Checkout. Technical Details : The Unified Checkout Capture Context generated through Invoicing or PayByLink always populates the merchant country as `US`. Workaround : Use a direct Unified Checkout (UC) or Flex session integration that supplies the correct merchant country when generating the session, rather than relying on the Invoicing or Pay By Link Capture Context generation path. **Acceptance Device List Cannot Be Exported to CSV** \| EPS-42803 ----------------------------------------------------------------- Description : When attempting to export the list of Acceptance Devices to a CSV file, merchants receive the error message *Error: CSV not available* and the export does not complete. Audience : Merchants that use Acceptance Devices. Technical Details : A front-end JavaScript issue prevents the CSV export from being generated successfully. Workaround : No known workaround. **Intermittent Tap-to-Phone Payments Might Fail Before Reaching Transaction Processing Systems** \| EPS-42847 ------------------------------------------------------------------------------------------------------------- Description : Some merchants located within the Democratic Republic of the Congo might experience intermittent Tap-to-Phone payment failures on their production Acceptance device fleets. Affected payments terminate before reaching Cybersource, the acquirer, or the issuer. As a result, the transaction is not processed and does not appear in Business Center for investigation or reconciliation. Audience : Merchants operating in the Democratic Republic of the Congo. Technical Details : None. Workaround : No known workaround. **Report Downloads API Returns Error When Using REST Client Java SDK v0.0.91 with P12 Certificates** \| EPS-43139 ----------------------------------------------------------------------------------------------------------------- Description : Merchants using JWT authentication with the `/reporting/v3/report-downloads GET` endpoint might receive a `401 UNAUTHORIZED_USER` response when using the REST Client Java SDK v0.0.91 with a P12 certificate. As a result, report downloads cannot be retrieved through the API. Audience : Merchants who upgrade to or use the REST Client Java SDK v0.0.91. Technical Details : The issue occurs when using JWT authentication with the `/reporting/v3/report-downloads GET` endpoint in the REST Client Java SDK v0.0.91 and a P12 certificate. Workaround : Revert to a previous version of the REST Client Java SDK. A fix is planned for a future release.