July 2026
Production releases for the weeks ending July 2 to July 31, 2026: features, fixed issues, and known issues.
July 31, 2026
These release notes cover releases for the week ending July 31, 2026.
No customer-facing features were released this week.
No customer-facing fixes were released this week.
There are no known issues this week.
July 24, 2026
These release notes cover releases for the week ending July 24, 2026.
Payments
Ticket: RM-40445
Description: This release adds the Mexican Peso (MXN, ISO 4217 code 484) as a supported currency for merchants processing through the FTT (First Tennessee/FTB) acquirer on the CTPv4 gateway. Merchants routed to FTT can now submit authorizations, captures, and related transactions in MXN through the existing CTPv4 API.
Mandate: Does not apply.
Audience: External merchants and partners processing on the CTPv4 gateway through FTT, primarily in Latin America.
Benefit: This update enables merchants to offer an additional currency to their customers.
Technical Details: Use information.amountDetails.currency = "MXN" in transactions routed to the FTT acquirer.
Important Dates: Released to production July 24, 2026.
Payments
Ticket: RM-46895
Description: Online Authorizations for credits or refunds are currently supported on Streamline and Omnipay processing connections. However, in the event that a refund is attempted on a card that has expired subsequent to a prior purchase, the card fails card validation checks, preventing the refund from being attempted. The expired card validation has been removed from the refund flow so that the decision on accepting the refund can be presented to issuer.
Mandate: Does not apply.
Audience: Merchants who perform refunds using Worldpay-Streamline, OmnipayDirect, and Cardnet.
Benefit: Merchants can present refunds on cards that have expired since an original purchase transaction so that issuers can decide and clearly indicate whether the refund will be accepted.
Technical Details: None.
Important Dates: July 22, 2026.
No customer-facing fixes were released this week.
Access
Ticket: EPS-41165
Description: An intermittent issue might prevent some users from logging in to the .
Audience: Users of the .
Technical Details: None.
Workaround: None.
July 17, 2026
These release notes cover releases for the week ending July 17, 2026.
No customer-facing features were released this week.
No customer-facing fixes were released this week.
Prosa Settlements
Ticket: EPS-38180
Description: An intermittent issue with Prosa settlements is preventing the status from updating to TRANSMITTED in the , making it appear as though the transactions were not processed.
Audience: Merchants who process transactions through Prosa.
Technical Details: None.
Workaround: Ignore the status until the problem is fixed.
Decision Manager
Ticket: EPS-39134
Description: An issue sometimes occurs in Case Management that prevents the Assign Owner function from working.
Audience: Users of Decision Manager.
Technical Details: None.
Workaround: None.
July 10, 2026
These release notes cover releases for the week ending July 10, 2026.
Salesforce Order Management
Description: This release introduces enhanced payment lifecycle capabilities by enabling Capture and Refund functionalities for both PayPal and Venmo transactions.
Mandate: Does not apply.
Audience: Users of Salesforce Order Management.
Benefit: This release enables merchants to efficiently complete payment settlements and process refunds directly in the platform, improving transaction management, operational flexibility, and overall customer experience.
Technical Details: None.
Important Dates: Released to production July 9, 2026.
Klarna Advantage
Ticket: RM-45665
Description: Clients using the Transaction Search page in the can use a new search filter in the Status filter drop-down menu. The new filter is called Step Up Required, and can be used to filter Klarna Advantage transactions. Users can select this status to find transactions in which the authorization response contains a STEP_UP_REQUIRED result. The status also displays in search results and on the Transaction Details page.
Mandate: Does not apply.
Audience: Users of Klarna Advantage.
Benefit: Clients can now quickly filter and identify Klarna Advantage transactions that triggered step-up authentication during authorization, reducing manual effort when reviewing or investigating those transactions.
Technical Details: None.
Important Dates: Released to production July 7, 2026.
Staged Digital Wallet
Ticket: RM-45223
Description: now supports Staged Digital Wallet transactions for merchants processing through Rede in Brazil. Merchants submit staged-wallet data in the standard REST payment-authorization request for these scenarios:
- Cash-In loads funds into a wallet from a registered card.
- Purchase uses a wallet to make a payment or to transfer funds between wallets.
Clients experience this in the API. There is no change in the and no new response fields. Consumer Bill Payment Service is not part of this release.
Mandate: Does not apply.
Audience: Merchants processing through Rede in Brazil using the API.
Benefit: Brazilian merchants and wallet operators can process wallet-based cash-in and purchase/transfer activity through Rede using their existing integration, extending supported payment experiences with no change to response handling.
Technical Details: Merchants include staged-wallet fields in the standard authorization request. Required field set:
Core wallet and transaction type
paymentInformation.customer.stagedDigitalWalletIdprocessingInformation.walletTransactionIntent:01= Purchase, including wallet-to-wallet transfer;02= Cash inprocessingInformation.destinationType:04= machine-to-machine, same owner;05= person-to-person, different holder;06/07= transfers;08= stored-value walletprocessingInformation.businessApplicationId:AA= same person (pair with04);PP= different people (pair with05)
Sub-merchant (aggregatorInformation.subMerchant): merchantCategoryCode, id, address1, country, postalCode, cardAcceptorId
Sender (senderInformation): firstName, lastName, address1, locality, countryCode, taxIdNumber
Recipient (recipientInformation): conditional, required for person -to-person: firstName, lastName, taxIdNumber, beneficiaryId
Merchant (merchantInformation): merchantDescriptor.name, taxId
Important Dates: Released to production July 2, 2026.
No customer-facing fixes were released this week.
Invoicing
Ticket: EPS-41011
Description: Some merchants might experience intermittent HTTP 500 errors when sending API POST requests to the /invoicing/v2/invoices endpoint.
Audience: API users of Invoicing.
Technical Details: None.
Workaround: None.
Decision Manager
Ticket: EPS-39533
Description: When creating a custom rule in the , selecting a comparison value also selects a corresponding custom field and vice versa. Deselecting either field causes both fields to be deselected.
Audience: Users of Decision Manager.
Technical Details: None.
Workaround: None.
July 2, 2026
These release notes cover releases for the week ending July 2, 2026.
Account Name Inquiry API
Ticket: RM-45612
Description: This release adds new field(s) to the Account Name Inquiry API response on the Transaction Details service. Clients using the Account Name Inquiry API will begin receiving additional account name data in the response payload. No action is required to receive the new fields, but clients that want to utilize them will need to update their parsing logic accordingly.
Mandate: Does not apply.
Audience: Global.
Technical Details: The new response fields are:
aniFullNameMatchCodeaniRawFullNameMatchCodeaniIndicator
Important Dates: Released to production June 30, 2026.
Transaction Details API
Ticket: RM-45650
Description: This release introduces new Merchant Advice Code fields to the Transaction Details API response. Clients consuming the Transaction Details API will receive additional Merchant Advice Code data in the response payload, enabling better visibility into transaction outcomes and decline reasons. No action is required to receive the new fields, however, clients should update their parsing logic accordingly.
Mandate: Does not apply.
Audience: Global. Particularly relevant to merchants and acquirers who rely on Merchant Advice Codes for retry logic and transaction management.
Benefit:
- More informed retry strategies.
- Improved decline handling.
- Better operational visibility at the merchant level.
Technical Details: Response field names:
MerchantAdviceCodeMerchantAdviceCodeRaw
Important Dates: Released to production June 30, 2026.
No customer-facing fixes were released this week.
Unified Checkout
Ticket: EPS-38342
Description: When a Unified Checkout user submits a transaction with payment type PAN entry, and the showConfirmationStep field is not added to the capture context with a value of false, the authorization fails with a MISSING_FIELD error.
Audience: Users of Unified Checkout.
Technical Details: None.
Workaround: Enable "showConfirmationStep": "false" in the capture context.
Account Updater
Ticket: EPS-39734
Description: An intermittent error causes some merchants who use Account Updater to retrieve a batch status using the REST API's /accountupdater/v1/batches/{BATCH_ID}/status endpoint might experience HTTP 403 errors.
Audience: Merchants who use Account Updater.
Technical Details: None.
Workaround: Try again.
Thanks for your feedback!
Last published: November 18, 2026