Skip to main content
Welcome to the preview portal — This is an early release of the new Doc Hub experience, with more content coming soon.

May 2026


Production releases for the weeks ending May 1 to May 29, 2026: features, fixed issues, and known issues.

May 29, 2026

These release notes cover releases for the week ending May 29, 2026.

3-D Secure

Ticket: RM-44940

Description: This release adds support for 3-D Secure data-only transactions for Rede for Visa and Mastercard e-commerce transactions in Brazil. It enables merchants to submit enriched 3-D Secure data in the REST API without triggering cardholder authentication or challenge flows. This is an API-only enhancement; there are no changes in the .

Mandate: Does not apply.

Audience: This release affects merchants using Rede in Brazil, for Visa and Mastercard e-commerce transactions.

Benefit: This feature enables merchants to submit authorization requests with additional security-related data and checks in the background, without adding friction to the checkout experience. Because no cardholder challenge is triggered, merchants can provide more issuer-relevant transaction context while keeping the purchase flow unchanged for the customer.

By giving issuers more information during authorization, this enhancement can improve approval rates, reduce false declines, and decrease unnecessary authentication challenges. Liability remains with the merchant.

Technical Details: To implement this feature, merchants submit a standard authorization request with the following 3DS Data Only fields:

Required fields

consumerAuthenticationInformation.cavv consumerAuthenticationInformation.paSpecificationVersion consumerAuthenticationInformation.directoryServerTransactionId processingInformation.commerceIndicator

Optional field

consumerAuthenticationInformation.xid

Additional implementation requirements:

  • Submit the transaction as an e-commerce payment.
  • Submit the transaction in BRL.
  • Process the transaction as Visa or Mastercard through REDE.
  • No challenge is performed, no step-up authentication is expected, and the response follows the standard authorization response structure.

Request Example

{  "processingInformation": {    "commerceIndicator": "internet"  },  "paymentInformation": {    "card": {      "number": "4111111111111111",      "expirationMonth": "12",      "expirationYear": "2030",      "sourceAccountType": "C"    }  },  "consumerAuthenticationInformation": {    "cavv": "AAABBIIFmAAAAAAAAAAAAAAAAAA=",    "xid": "MDAwMDAwMDAwMDAwMDAwMzIyNzY=",    "paSpecificationVersion": "2.2.0",    "directoryServerTransactionId": "f3eecb72-31b3-4a62-b9af-8e6a8b7a0abc"  },  "orderInformation": {    "amountDetails": {      "totalAmount": "100.00",      "currency": "BRL"    },    "billTo": {      "firstName": "First",      "lastName": "Last",      "address1": "Av Paulista 123456",      "locality": "Sao Paulo",      "administrativeArea": "SP",      "postalCode": "01310-100",      "country": "BR",      "email": "[email protected]"    },    "shipTo": {      "firstName": "First",      "lastName": "Last",      "address1": "Av Paulista 123456",      "locality": "Sao Paulo",      "administrativeArea": "SP",      "postalCode": "01310-100",      "country": "BR"    }  }}

Response Example

{  "id": "6654706105956431203955",  "status": "AUTHORIZED",  "submitTimeUtc": "2026-04-21T14:22:10Z",  "processorInformation": {    "approvalCode": "831000",    "responseCode": "00",    "transactionId": "123456789012345"  },  "networkTransactionId": "987654321234567",  "reconciliationId": "6654706105956431203955"}

Important Dates: Released to production April 24, 2026.


Updates for FDC Nashville Global

Ticket: RM-44320

Description: These features are released for FDC Nashville Global:

Account Name Inquiry: Ensures compliance with network mandates and enhances fraud prevention by validating account holder names during account verification and 0 amount authorization transactions.

Extended Authorizations: Enables Extended Authorization capabilities, allowing merchants to hold approved authorizations for up to 30 calendar days for eligible Card Not Present transactions and customer-initiated transactions.

AFT Refund: AFT bitmap 43 Authorization/Credit Authorization changes and AFT Credit Authorization changes, disabling Credit Auth for FDC Nashville Global Visa AFT transactions, and updating bitmap 43 merchant name for all AFT transactions.

Mandate: Does not apply.

Audience: FDC Nashville Global merchants.

Benefit: This release enhances fraud prevention and allows merchants to hold approved authorizations for up to 30 calendar days.

Technical Details: None.

Important Dates: Released to production May 28, 2026.

Follow-On Credit Transactions

Ticket: RM-45829

Description: This release fixes an error in which some follow-on credit transactions for some payment gateways were failing with an ESYSTEM error, returning the message The follow-on credit cannot be processed because the capture transaction has not been processed yet.

Audience: All gateways that have enabled Auto Capture.

Technical Details: None.

Important Dates: Released to production May 22, 2026.

Ticket: EPS-37429

Description: After new transacting organizations are created, merchant-level organizations cannot see the transacting organization's transactions in the immediately. In some cases, it can take weeks for tansactions to appear.

Audience: Portfolio merchants.

Technical Details: None.

Workaround: Search for the transactions using a transacting MID user or a portfolio MID user.


Payer Authentication

Ticket: EPS-37750

Description: When portfolio accounts onboard merchants to 3-D Secure processing for Cartes Bancaires cards on the 's Payer Authentication Configuration screen for transacting accounts, the Acquirer ID is validated for 1-35 alphanumeric characters only. Accounts with space or hyphen characters in their names are not being accepted.

Audience: Portfolio merchants.

Technical Details: None.

Workaround: Contact support.

May 22, 2026

These release notes cover releases for the week ending May 22, 2026.

Merchant Descriptior Name

Ticket: RM-44633

Description: is updating validation for the merchantInformation.merchantDescriptor.name API field. Merchants can now submit merchant descriptor names that include either the asterisk (*) or hyphen (-) character. Transactions are no longer rejected solely because these characters are included in this descriptive field.

Mandate: Does not apply.

Audience: The updated validation is available to all merchants who use the merchantInformation.merchantDescriptor.name field.

Benefit: Improved merchant descriptor support.

Technical Details:

Example:

{  "merchantInformation": {    "merchantDescriptor": {      "name": "MERCHANT*STORE-NAME"    }  }}

Important Dates: Released to Production May 20, 2026.


New Features for Pisma

Ticket: RM-44633

Description: Merchants who use Prisma can now use 3-D Secure 2.x, Network Tokens, and MIT/COF framework data. These capabilities are available to Prisma merchants who are enabled. This update allows Prisma merchants to support tokenized and authenticated card-not-present payment flows and submit the required transaction framework data for eligible use cases.

Mandate: Does not apply.

Audience: Merchants processing in Argentina through the Prisma connection.

Benefit: Prisma merchants can support tokenized, authenticated, and credential-on-file card-not-present payment flows.

Technical Details: Supported 3-D Secure-related values include:

  • pa_specification_version
  • directory_server_transaction_id
  • cavv
  • ucaf_collection_indicator
  • ucaf_authentication_data

Supported MIT/COF-related values include:

  • subsequent_auth_first
  • subsequent_auth_reason
  • subsequent_auth
  • subsequent_auth_transaction_id

Supported Network Token-related value:

  • network_token_cryptogram

Important Dates: Released to Production May 20, 2026.

No customer-facing fixes were released this week.

Transaction Search in the

Ticket: EPS-37818

Description: For a similar search in the 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

Ticket: 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

Ticket: 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

Ticket: 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

Ticket: EPS-37838

Description: When a merchant uses the .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.

May 15, 2026

These release notes cover releases for the week ending May 15, 2026.

Partner Risk Controls (PaRC)

Ticket: RM-43752

Description: This release introduces new ECI (e-commerce indicator) controls in PaRC for e-commerce transactions, where the PaRC user can place rejected transactions in the new ECIs coming from the authentication.

Mandate: Does not apply.

Audience: Users of PaRC.

Benefit: Improved protection from unauthenticated transactions and blocking e-commerce transactions to prevent fraudulent merchants from performing riskier transactions.

Technical Details: The New ECIs are:

  • 07 (Data-only for VISA).
  • 04 and 06 (Data share program for Mastercard).
  • N0 and N2 for Mastercard (Non-financial transaction).

Important Dates: Released to production May 13, 2026.

Offline Transaction File Submission

Ticket: RM-45170

Description: This release fixes an issue that prevented links between credit transaction IDs and parent debit transaction IDs after execution of the scheduled completion job.

Audience: Merchants who use the FNBO/FNBOACH eCheck processor/gateway.

Technical Details: Searching for a debit request ID after a transaction is marked as Completed now accurately shows the parent debit and child credit transaction IDs on the same search result.

Important Dates: Released to production May 13, 2026.


Settlement

Ticket: RM-44760

Description: This release fixes an issue which caused incorrectly populated capture-sequence/count fields (pos 84/86) in settlement files for airline merchants, violating Worldpay requirements.

Audience: Airline merchants who use Worldpay.

Technical Details: None.

Important Dates: Released to production May 13, 2026.


Ticket: RM-45474

Description: This release resolves two bugs: one related to the page jumping to the top after each keystroke or click when re-entering credit card numbers, and another involving incorrect transaction amounts displayed on email receipts.

Audience: Global.

Technical Details: None.

Important Dates: Released to production May 13, 2026.

Response Code

Ticket: EPS-37597

Description: The Worldpay response code 149 (The transaction is not permitted, or the card is not available for use) is incorrectly mapped to response code 211 (Invalid CVN).

Audience: Merchants who use Worldpay.

Technical Details: None.

Workaround: None.


Apple Pay

Ticket: EPS-37644

Description: When an Apple Pay transaction is submitted through Worldpay and the customer's name in their Apple Wallet contains multi-byte UTF-8 characters, for example, Chinese, the transaction fails.

Audience: Users of Apple Pay and Worldpay.

Technical Details: The merchant receives the error Reason Code 233 (INVALID_FIELD_MAX_LENGTH).

Workaround: None.


Notifications

Ticket: EPS-37659

Description: Several types of notifications are not being delivered to some accounts in our testing environment, including:

  • Email
  • Webhooks
  • Invoicing
  • Pay by Link

Audience: Global.

Workaround: None.

May 8, 2026

These release notes cover releases for the week ending May 8, 2026.

Merchant-Initiated Transactions

Ticket: RM-45052

Description: In the Transit - Deferred Aggregated Model, riders can tap with either a physical card or a digital wallet. When a physical card is used, the transaction is performed using the card’s Funding Primary Account Number (FPAN). When a digital wallet (for example, Apple Pay or Google Pay) is used, the transit tap generates a Device Primary Account Number (DPAN). If an aggregated or end-of-day transit transaction is declined, an outstanding debt is created and might be recovered through a Merchant-Initiated Transaction (MIT) debt recovery flow, using the appropriate account number, in accordance with applicable card-scheme rules.

Key points:

  • Debt recovery might originate from transactions that initially used a DPAN or FPAN.
  • For the Mastercard transit program the MIT debt recovery requires the use of the FPAN also for the cases that DPAN was initially used.
  • Successful debt recovery enables removal of the card from the transit deny list.

Mandate: Does not apply.

Audience: Users of Merchant-Initiated Transactions.

Benefit: DPAN debt recoveries are now possible for Mastercard. This does not affect Visa DPAN debt recoveries.

Technical Details: None.

Important Dates: Released to production April 24, 2026.

Transaction Error Codes

Ticket: RM-44887

Description: This release fixes a mismapped error code that caused an incorrect transaction status.

When FDC Nashville Global or Chase Paymentech Solutions hard-declined an authorization due to an incorrect card verification value (CVV), our response mapped to a soft-decline (reason code 230). This placed the transaction in the status Authorizations Needing Review in the Transaction by Phase page of the . That enabled merchants to choose to reverse the authorization, leading to incorrect reason code 102 DINVALIDDATA.

These transactions are now correctly mapped to reason code 211 DCARDREFUSED, which is a hard-decline that cannot be reversed.

Audience: Users who process through FDC Nashville Global or Chase Paymentech Solutions.

Technical Details: None.

Important Dates: Released to Production May 6, 2026.


Transactions Through Cielo

Ticket: RM-45175

Description: This release fixes an issues in which authorization timeouts and processing errors from Cielo left transactions in an unknown state, leading merchants to retry them, which caused duplicate transactions. Now the authorization is reversed and the merchant is notified.

Audience: Users that process through Cielo.

Technical Details: None.

Important Dates: Released to production May 6, 2026.

Tax Calculation

Ticket: EPS-37002

Description: A mapping error is causing tax calculation requests that contain a data validation error to return reason code 150 instead of 102.

Audience: Users of tax calculation.

Technical Details: None.

Workaround: None.

May 1, 2026

These release notes cover releases for the week ending May 1, 2026.

Batch Processing Email

Ticket: RM-44485

Description: This release updates the email that is sent when batch processing is complete. The enhanced email now includes:

  • The number of successfully processed transactions.
  • The number of declined transactions.
  • The number of transactions with missing responses.

These totals align with the number of transactions submitted in the batch, providing merchants with a quick, high-level status overview.

Mandate: Does not apply.

Audience: All merchants who are not part of a portfolio. This release will be available to portfolio merchants in the coming months.

Benefit: The enhanced email provides an immediate, high-level overview of batch processing results, enabling faster decision-making and improved operational efficiency by quickly identifying the overall success rate and any issues that might require attention.

Technical Details: None.

Important Dates: Released to production April 26, 2026.


Batch Processing Report

Ticket: RM-44485

Description: A new report is generated for situations in which a transaction response was not received. Previously, when merchants uploaded batch files, two reports were generated: reply.all and reply.rejected. In some scenarios, such as response latency, internal exceptions, or timeouts, a transaction response might not be received. Previously, those cases were communicated manually, and merchants were asked to review the processing status in the before retrying the transactions.

To improve transparency and reduce manual follow-up, an additional report is now generated automatically for transactions for which no response was received. These are the new report details:

  • Title: reply.missing.csv.
  • Location: Located with reply.all and reply.rejected reports.
  • Report contents: The file will contain the fields merchantRefCode, merchantID, and requestID.

Mandate: Does not apply.

Audience: All merchants who are not part of a portfolio. This release will be available to portfolio merchants in the coming months.

Benefit: This new report enables merchants to easily identify transactions with missing responses.

Technical Details: Merchants are not required to take any additional actions when such transactions occur, and there are no changes to the existing reports.

Important Dates: Released to production April 26, 2026.

Oracle NetSuite Version 26.2.1

Description: This release fixes an issue that affected line item data handling within the Customer Payments workflow. Implementing this patch ensures that merchants maintain accurate and complete transaction records when processing customer payments, preventing potential discrepancies in financial reporting and order management workflows

Audience: Users of Oracle NetSuite.

Technical Details: None.

Important Dates: Released to production April 27, 2026.

Credit Transactions

Ticket: EPS-37416

Description: An intermittent issue is causing some follow-on credits that were processed in Latin America to fail.

Audience: Merchants in Latin America.

Technical Details: The reason code is 150: The follow-on credit cannot be processed because the capture transaction has not been processed yet.

Workaround: None.


Click to Pay

Ticket: EPS-37343

Description: For Romanian users of the Click to Pay Drop-In UI, the Phone Number field is being displayed as Platiti cu cardul instead of Număr de telefon.

Audience: Users of Click to Pay who use the Romanian translation.

Technical Details: None.

Workaround: None.

Last published: November 18, 2026

Not available for your audience

This page isn't available for your current audience selection.