November 2026
Production releases for the weeks ending November 6 to November 13, 2026: features, fixed issues, and known issues.
November 13, 2026
These release notes cover releases for the week ending November 13, 2026.
SAP Commerce Cloud MLE Support
Description: The SAP Commerce Cloud integration now supports Message-Level Encryption (MLE) for REST APIs.
MLE enables application-level encryption and decryption of sensitive REST API payloads, helping protect payment data beyond standard transport-layer security. The enhancement supports both encrypted requests and encrypted responses, enabling end-to-end protection of sensitive transaction data.
Mandate: Does not apply.
Audience: Tech Partners
Benefit: Merchants will be able to:
- Enable Message-Level Encryption for supported REST API transactions.
- Configure the certificates, keys, and Key IDs required for request and response encryption.
- Continue using existing non-MLE REST processing where encryption is not required.
Technical Details: This enhancement will provide:
- Enhanced security through application-level encryption of sensitive REST API payloads.
- Support for response encryption, enabling secure handling of transaction data returned by the platform.
- Improved compliance readiness for merchants processing sensitive payment information.
Important Dates: November 12, 2026
PaRC On-Us BIN Management Update
Description: We implemented a change that standardizes how debit card types are specified. This update aligns the behavior across UI and bulk-upload flows.
We previously provided DR as a temporary workaround for bulk uploads because the system was not accepting files that used DB.
Now, you use DB for both individual/manual BIN entries through the PaRC UI and bulk On-Us BIN uploads using the CSV template. We validated the fix successfully using DB after deployment.
Important Dates: November 4, 2026
Fixed BEPG Transaction Failures Caused by Orchestrator Field-Length Validation
Ticket: RM-49232
Description: Fixed an issue that caused production transactions for REST merchants using the BEPG integration to fail with an INVALID_REQUEST or INVALID_DATA error due to the field length value for the consumerAuthenticationInformation.authenticationTransactionId field.
Audience: REST Merchants with the BEPG integration with RuPay
Technical Details: The fix raises the maxLength for the consumerAuthenticationInformation.authenticationTransactionId field from 26 to 36 characters.
Important Dates: November 11, 2026
There are no known issues this week.
These updates to the documentation site are part of this release.
Merchant Guides
These entries describe the updates to merchant guides.
| Product | Page | Description |
|---|---|---|
| Payments | Anticipated Amount Verification | New page. Include an anticipated transaction amount in an account verification request and receive a funds availability signal in the response, without placing a hold on cardholder funds. |
| Unified Checkout | Test Cards | Updated the test card lists. A Passkey Service Test Cards section replaces the 3-D Secure Frictionless Test Cards section. |
| Click to Pay Drop-In UI | Test Your Click to Pay Drop-In UI Configuration | Updated the test cards. |
| Click to Pay Drop-In UI | Get Started with Click to Pay Drop-In UI | Updated the merchant boarding instructions for the Boarding Registration Service (BRS) API. |
| Unified Checkout | Get Started with Unified Checkout | Updated the merchant boarding instructions. |
| Airline | Airline | Added REST content for airline processors that were previously documented only for the Simple Order API. Added processor-specific required fields for American Express Direct, Lloyds-OmniPay, OmniPay Direct, Streamline, TSYS Acquiring Solutions, and UATP. Updated the ancillary purchases fields. |
| BIN Lookup Service | BIN Lookup Service | Moved from Post-Transaction Processing to Accept Payments. The page URLs changed. |
| Transaction Search | Transaction Search Endpoints | Added the production endpoint for Saudi Arabia. |
| Unified Checkout | PayPal and Venmo | Renamed from Alternative Payment Wallets. Updated the required and optional fields for PayPal capture context requests. |
| Unified Checkout | Security Recommendations | Added URLs to the Content Security Policy (CSP) directive table. |
| Microform Integration | Transient Tokens for Accepting Card Information | Added an Endpoint section with the production and test URLs. |
| Microform Integration | Transient Tokens for Accepting Card Information | Added the production and test endpoints for Saudi Arabia. |
| Token Management Service | Network Tokens | Reorganized the network token workflows into Tokenization and Tokenization with Payments sections for customer-initiated (CIT) and merchant-initiated (MIT) transactions. |
| Token Management Service | Get Started with TMS for Merchants | Added a step to the vault settings procedure and updated the network tokenization configuration steps. |
| Token Management Service | Delete a Network Token | Updated the endpoint and example for deleting a network token. |
| Token Management Service | Test Network Tokens | New section. Test network tokens with the Token Management Service (TMS) simulator and the Network Sandbox. |
| Release Notes | Release Notes | New section. Weekly production release notes, organized by month, plus an Announcements page. |
Technology Partner Guides
These entries describe the updates to technology partner guides and e-commerce plugins.
| Product | Page | Description |
|---|---|---|
| E-Commerce Plugins | Plugins for E-Commerce | Shortened the Overview and Get Started labels in the plugin guide sidebars and updated the guide descriptions. |
| Partner Program | Get Started as a Technology Partner | Moved to the technology partner section, which now has its own navigation. The page URLs changed. |
| OAuth 2.0 | OAuth 2.0 | New guide. Delegate limited API access between clients with secure tokens instead of shared API keys, and compare the On-Behalf-Of, Machine-to-Machine, and OpenID Connect integration methods. |
| Partner Solution Key | Partner Solution Key | New guide. How a partner solution key lets your solution process payments on behalf of a portfolio of merchants, and when to use it instead of OAuth 2.0. |
| Adobe Commerce Magento | Adobe Commerce Magento Overview | New guide. |
| BigCommerce | BigCommerce Overview | New guide. |
| Oracle NetSuite | Oracle NetSuite Overview | New guide. |
| Salesforce B2C Commerce | Salesforce B2C Commerce Overview | New guide. |
| Partner Program | Partner Program | New landing page for technology partners. |
November 6, 2026
These release notes cover releases for the week ending November 6, 2026.
No customer-facing features were released this week.
Automated Clearing House (ACH) eCheck Follow-On Credit Eligibility Restored
Ticket: RM-49229
Description: This release corrects a defect affecting Automated Clearing House (ACH) eCheck transactions. Sometimes, follow-on credits were incorrectly unavailable because the system could not accurately calculate transaction age when processing request IDs longer than 26 characters. Following this release, merchants can perform eligible follow-on credits for ACH eCheck transactions for up to 180 days after the original debit transaction, consistent with the intended processor rules.
Mandate: Does not apply.
Audience: Some merchants processing eCheck transactions through an ACH processor.
Technical Details: No API changes are required, and no merchant configuration changes are necessary to use this correction.
Important Dates: Released on November 4, 2026.
SDK Upgrade Breaks Some .NET SOAP Requests
Ticket: EPS-44622
Description: Applications using sign-only message security cannot submit Simple Order API requests after upgrading the .NET SOAP SDK from version 1.4.10 to version 1.4.11. Affected requests fail with an identity-check error before they are sent.
Audience: Some merchants using version 1.4.11 of the .NET SOAP SDK for the Simple Order API with sign-only message security.
Technical Details: Version 1.4.11 incorrectly applies an identity-verification check to sign-only connections. As a result, the SDK can throw System.ServiceModel.Security.MessageSecurityException with an Identity check failed for outgoing message message before submitting the request.
Workaround: Continue using version 1.4.10 of the .NET SOAP SDK until a corrected version is available.
Some Transaction Details Pages Do Not Load
Ticket: EPS-46021
Description: Some transactions appear in Transaction Search, but their Transaction Details pages display Unable to Load Transaction Data. The transaction data remains available in the underlying system.
Audience: Some users viewing transactions with unusually large linked transaction histories.
Technical Details: The Transaction Details page can time out while retrieving and assembling a transaction history containing an exceptionally large number of related attempts. This issue does not indicate that the transaction data is missing.
Workaround: Use Transaction Search to view the available transaction summary. Contact Customer Support if the complete transaction history is required.
Some Successful Authorizations Return System Errors
Ticket: EPS-46070
Description: Some successful payment authorizations can return an HTTP 500 response with SYSTEM_ERROR. The authorization might still appear as successful in Transaction Management.
Audience: Some merchants submitting payment authorization requests through the REST API.
Technical Details: This issue occurs when the authorization succeeds but the returned decision code is not recognized during API response transformation. The successful backend result is then replaced with a system-error response.
Workaround: Before retrying an affected authorization, use Transaction Management or the Transaction Search API to verify whether the original request succeeded.
Some Payer Authentication Updates Appear Successful
Ticket: EPS-46075
Description: Some UnionPay Payer Authentication configuration updates can appear successful after an earlier update was rejected. A subsequent attempt can report that no changes were submitted even though the configuration was not accepted by the authentication service.
Audience: Some merchants configuring UnionPay Payer Authentication through or the Payer Authentication configuration API.
Technical Details: When an update to the default-currency configuration is rejected, the submitted acquirer information can still be stored in the local Payer Authentication profile. Retrying the same update can then return a successful No changes in request response without resubmitting the configuration for validation.
Workaround: No known workaround.
Some eCheck Billing States Are Incorrect
Ticket: EPS-46119
Description: Some eCheck transactions processed through Unified Checkout can contain an incorrect billing state when billing-address collection is disabled. For affected US addresses, Unified Checkout can replace the submitted state with AL.
Audience: Some US merchants accepting eCheck payments through Unified Checkout.
Technical Details: This issue occurs when Billing Address is disabled and the capture mandate does not require billing-address collection. Under these conditions, the submitted value in orderInformation.billTo.administrativeArea might not be preserved.
Workaround: In , enable Billing Address under Payment Configuration > Unified Checkout > Customer Information and Payment Flow, and select Zip only or Full address.
Some Authorizations Include Conflicting Exemptions
Ticket: EPS-46258
Description: Some authorization requests can be declined when a Payer Authentication outage occurs and another Strong Customer Authentication (SCA) exemption is already present. Affected requests return reason code 102 and indicate that only one SCA exemption can be submitted per authorization.
Audience: Some merchants using Payer Authentication and SCA exemptions in Europe.
Technical Details: During some directory-server outages, the Payer Authentication response can add an outage exemption without recognizing an existing exemption. The authorization request is then declined because it contains more than one SCA exemption.
Workaround: No known workaround.
Some Report Events Display in One Row
Ticket: EPS-46426
Description: Some Processor Events Detail Reports display multiple processor events as comma-separated values in a single report row. The underlying event records and amounts remain correct.
Audience: Some merchants using Processor Events Detail Reports.
Technical Details: This issue occurs when a transaction has more than one processor event in the selected report period. The report combines the events into one row instead of displaying each event separately.
Workaround: No known workaround.
Some PayPal References Are Not Preserved
Ticket: EPS-46577
Description: Some merchants submitting custom reconciliation references for PayPal order, capture, or session requests receive system-generated references instead. As a result, merchants might be unable to use their submitted values to reconcile affected PayPal transactions.
Audience: Some merchants using PayPal through alternative payments and submitting custom reconciliation references.
Technical Details: Values submitted in processingInformation.reconciliationId or orderInformation.invoiceDetails.invoiceNumber are not included in affected PayPal order, capture, and session requests. PayPal refund requests preserve the submitted reference correctly.
Workaround: No known workaround.
Some Payer Authentication Validations Fail
Ticket: EPS-46646
Description: Some merchants using hybrid Payer Authentication receive an authentication failure when validating successful 3-D Secure authentication results. Affected requests return reason code 479 and the message Unable to validate response access token.
Audience: Some merchants using hybrid Payer Authentication in Europe.
Technical Details: The affected validation flow does not recognize the JSON Web Token (JWT) issuer used for some migrated Payer Authentication sessions. As a result, a successful authentication result can fail validation when responseAccessToken is submitted.
Workaround: No known workaround.
Some Payer Authentication Activations Fail
Ticket: EPS-46739
Description: Some newly onboarded merchants cannot enable 3-D Secure Payer Authentication through or API Onboarding. Activation fails and can incorrectly indicate that the merchant has already been created.
Audience: Some newly onboarded merchants enabling 3-D Secure Payer Authentication through or API Onboarding.
Technical Details: A newly created Payer Authentication profile might not be available when the system immediately attempts to use it as the merchant's default profile. The activation request then fails even though the new profile was created successfully.
Workaround: Contact Customer Support to complete Payer Authentication profile generation and synchronization for the affected merchant.
Some E-Commerce Transactions Rejected during Clearing
Ticket: EPS-46911
Description: Some Mastercard e-commerce transactions using 3-D Secure authentication are incorrectly classified as manually entered transactions and rejected during clearing.
Audience: Some merchants processing Mastercard e-commerce transactions through an affected processing connection in the US.
Technical Details: Affected sale and credit authorization messages do not include the required e-commerce classification and authentication information in ISO Field 63. As a result, transactions can receive Mastercard International Payment Management rejection code 8679 during clearing even when authorization completes successfully.
Workaround: No known workaround.
Thanks for your feedback!
Last published: November 18, 2026