August 2026
Production releases for the weeks ending August 14 to August 28, 2026: features, fixed issues, and known issues.
August 28, 2026
These release notes cover releases for the week ending August 28, 2026.
Login Page Enhancement: Improved Visibility of Forgot Password Link
Ticket: RM-44255
Description: This release repositions the Forgot Password link on the login page to improve visibility and align password recovery more closely with the login flow. This is a user interface change only. It does not affect authentication behavior or password reset functionality.
Mandate: Does not apply.
Audience: All clients.
Benefit: Clients can find the password recovery option more easily from the login page.
Technical Details: The Forgot Password link now appears in a different position on the login page. The Forgot Password link moved from the page footer to a position next to the Password field. No customer action is required.
Before:
After:
Important Dates: Released on August 24, 2026.
Merchant ID Dropdown Fix on Transactions through Merchant Management Service
Ticket: RM-48183
Description: The Merchant ID dropdown UI element on the Transactions page was producing an error that prevented users from fetching the merchant list. This fix resolves that
Audience: Merchants, Issuers, and Acquirers.
Technical Details: The Transaction Search merchant list dropdown UI can now be populated for accounts when account_id is greater than 30 characters.
Important Dates: Released on August 25, 2026
There are no known issues this week.
August 21, 2026
These release notes cover releases for the week ending August 21, 2026.
Restrict Wildcard Queries in Transaction Search
Ticket: RM-47629
Description: This release restricts wildcard query patterns for Transaction Search direct API users. Requests that use an unsupported wildcard pattern now receive an error response with guidance on proper query syntax.
Mandate: Does not apply.
Audience: Merchants who use the Transaction Search direct API endpoints. users are not affected.
Benefit: This change improves the performance and stability of transaction search.
Technical Details: Direct API requests that use an unsupported wildcard query pattern now receive an error response with guidance on proper query syntax.
Important Dates: Released on August 19, 2026.
No customer-facing fixes were released this week.
IUGU Settlements
Ticket: EPS-40848
Description: Some transactions processed through the IUGU gateway take up to 20 minutes to update to SETTLED status after a payment is processed, which might cause the transaction to time out on the merchant's system.
Audience: Some merchants who process transactions through the IUGU gateway.
Technical Details: A delay in persisting payment reference data causes the initial payment confirmation status update from IUGU to fail.
Workaround: None.
Invoicing
Ticket: EPS-41822
Description: A defect is causing some invoices to remain in PENDING status instead of transitioning to PAID status after the cardholder completes payment.
Audience: Some merchants who use Invoicing.
Technical Details: A higher transaction volume caused some transactions to be missed, leaving the corresponding invoices in PENDING status.
Workaround: is updating the affected invoices to show the correct status.
Unified Checkout and Decision Manager
Ticket: EPS-41981
Description: When a Unified Checkout customer enters a numeric-only first or last name during checkout, the authorization succeeds, but the post-authorization Decision Manager check fails, causing instant settlement to fail.
Audience: Merchants who use Unified Checkout together with Decision Manager, specifically when a numeric-only value is entered in the first or last name field.
Technical Details: Authorization succeeds because the numeric surname is accepted during authorization processing; the rejection occurs only in the post-authorization scoring, creating a mismatch between the authorization result and the DM result that causes instant settlement to fail despite a successful authorization.
Workaround: Ensure that customers do not enter a numeric-only value in the first or last name field, or disable the After Authorization Decision Manager scoring option.
Prosa Credits
Ticket: EPS-42197
Description: A defect is causing some settled Prosa transactions to be missing the Credit button in the , which prevents merchants from creating a credit for the transaction in the .
Audience: Some merchants using the Prosa gateway, primarily in Latin America and the Caribbean (LAC).
Technical Details: During certain Prosa payment flows, the transaction's BATCHED status does not persist to the database. Because the transaction is not identified as batched, the Credit button does not appear.
Workaround: Use the Virtual Terminal batch file upload feature to process the credit instead.
Authorization
Ticket: EPS-42267
Description: Some authorization requests sent to the /pts/v2/payment endpoint intermittently received 5xx errors during three brief intervals.
Audience: Some merchants who use Authorization.
Technical Details: A brief internal service error caused the failures.
Workaround: None.
August 14, 2026
These release notes cover releases for the week ending August 14, 2026.
Message-Level Encryption Support for TSS Endpoints
Ticket: RM-46978
Description: now supports optional message-level encryption (MLE) for selected Transaction Search Service (TSS) endpoints. Merchants enabled for MLE can receive encrypted response payloads from the affected TSS APIs. Merchants not using MLE can continue to use these endpoints without any changes to their integration.
Mandate: Does not apply.
Audience: Merchants who are enabled for MLE and use the TSS APIs.
Benefit: Merchants can adopt encrypted message handling for TSS API responses based on their security requirements, with no impact to existing non-MLE integrations.
Technical Details: These TSS endpoints now support optional MLE for response payloads:
GET /tss/v2/transactions/{id}/generalGET /tss/v2/transactions/{search-id}GET /tss/v2/transactions/{id}POST /tss/v2/searches
Existing request and response behavior remains unchanged for merchants who are not configured for MLE.
Important Dates: Released on August 11, 2026.
Unified Checkout Locale and Payment Enhancements
Ticket: RM-47302
Description: Unified Checkout now supports additional Latin America and Caribbean locales, gives merchants more control over which payment types display during checkout, supports a capture-only transaction mode, adds support for Unified Click to Pay (UCTP) v0.10 and Mastercard FIDO/Passkey authentication, and adds support for PayPal vaulting.
Mandate: Does not apply.
Technical Details:
- Unified Checkout supports additional locales
- Products: Unified Checkout, Click to Pay Drop-in UI
- Tech Details: Unified Checkout supports these additional locales:
- es-CR (Costa Rica)
- es-DO (Dominican Republic)
- es-GT (Guatemala)
- es-PA (Panama)
- es-PY (Paraguay)
- PayPal vaulting
- Products: Unified Checkout
- Tech Details: Support for PayPal vaulting enables merchants to securely store customer PayPal payment credentials for future transactions, supporting recurring payments and streamlined repeat purchases.
- FIDO/passkey support
- Products: Unified Click to Pay (UCTP)
- Tech Details: Support for UCTP v0.10 and Mastercard FIDO/Passkey authentication. Eligible Mastercard Click to Pay cardholders can authenticate using a registered passkey, such as Face ID or fingerprint recognition, enabling a faster, more seamless checkout experience with enhanced security.
- Allowed payment methods in checkout SDK
- Products: Unified Checkout
- Tech Details: Enables the multi-integration model where different parts of the page own different payment methods. For example, supporting checkout for Apple Pay or Google Pay in the same Unified Checkout session request while loading components for card and Click to Pay payment methods.
- Additional complete mandate function to fully suppress complete mandate
- Products: Unified Checkout
- Tech Details: Support for
completeMandate.suppressset totrueorfalse, which lets merchants fully suppress the complete mandate step where it is not required and offer a capture-only transaction mode.
Important Dates: Released on August 13, 2026.
No customer-facing fixes were released this week.
There are no known issues this week.
Thanks for your feedback!
Last published: November 18, 2026