On This Page

Features Introduced This Week

Pay with Token Using Unified Checkout

Description: Use Token Management Service (TMS) tokens within Unified Checkout to show the chosen payment token within the UI alongside your other chosen payment methods.
Mandate: Does not apply
Audience: Unified Checkout users in the these regions: AP, CEMEA, EU, LAC, and NA.
Benefit: By combining tokenized credential management and checkout into a single integration, merchants can scale faster, improve customer experience, and future‑proof their e‑commerce payments strategy.
Technical Details: Merchants can present previously stored customer credentials directly within the Unified Checkout experience and enable returning customers to complete purchases faster and more securely. Merchants can re‑use tokens for the use with payment processing from within Unified Checkout.
Important Dates: Released to production on March 10, 2026.

Unified Checkout Version 1

Description: Unified Checkout Version 1 delivers a modern, low‑code digital payment acceptance experience that combines streamlined integration capabilities with intuitive merchant configuration screens in the Business Center. This release modernizes how merchants onboard, integrate, and manage checkout experiences by pairing updated APIs and SDKs with guided UI‑based configuration flows. Merchants can complete core setup steps, manage payment options, and control customer information requirements through Business Center screens, while developers benefit from consistent APIs, updated naming conventions, and AI‑generated sample code across five programming languages.
Mandate: Does not apply
Audience: Unified Checkout users in these regions: AP, CEMEA, EU, LAC, and NA.
Benefit: Unified Checkout v1 reduces both development and operational effort by unifying integration and configuration into a consistent, low‑code framework. Developers benefit from clearer naming conventions, updated URLs, and AI‑generated sample code that accelerates onboarding and evaluation. Merchants and operations teams gain the flexibility to manage payment methods, customer data collection, and checkout behavior directly through intuitive Business Center screens without requiring code changes. Together, these improvements lower onboarding friction, speed time to market, and provide a scalable foundation for future payment enhancements.
Technical Details: Merchants integrating or upgrading to Unified Checkout v1 will experience changes across both integration and operational workflows. On the integration side, API paths, JavaScript file names, global objects, method names, and error labels have been updated. Any implementation referencing legacy identifiers (such as SecureAcceptance.js
, the
Accept
namespace, or URLs containing
up
) will require updates to align with Unified Checkout conventions. On the merchant operations side, configuration tasks that were previously handled through custom development or static integration decisions can now be managed directly within the Business Center. Merchants should review user roles and permissions to ensure appropriate access to Unified Checkout configuration screens.
Important Dates: Released to production on March 13, 2026.