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.

March 2026


Production releases for the weeks ending March 6 to March 27, 2026: features, fixed issues, and known issues.

March 27, 2026

These release notes cover releases for the week ending March 27, 2026.

No customer-facing features were released this week.

No customer-facing fixes were released this week.

There are no known issues this week.

March 20, 2026

These release notes cover releases for the week ending March 20, 2026.

OptBlue Fields

Ticket: RM-42677

Description: This release adds optional American Express OptBlue Sub-Merchant fields to the Templates page in the , for all VPC processors. The new fields are controlled by a new OptBlue toggle that appears when American Express is selected. The new fields are:

  • ID
  • Phone
  • Email

Mandate: None.

Audience: Merchants who process transactions through VPC.

Benefit: These fields ensure required data is captured for settlement files and prevent American Express transaction rejections.

Technical Details: None.

Important Dates: Released to production March 19, 2026.


Ticket: RM-43157

Description: This release includes these updates:

  • We now send a specific developer ID in the payload for invoices coming from a standard invoice, simple invoice, and the Virtual Terminal's one-time-payment.
  • Two new drop-down menu options on the Manage Invoices dashboard to create two different invoices: standard invoice and simple invoice.
  • New filter options for My Invoices.

Mandate: None.

Audience: Users of Invoicing.

Benefit: Integration of Virtual Terminal with Pay by Link Invoicing streamlines the process and enhances customer experience.

Technical Details: None.

Important Dates: Released to production March 18, 2026.


Terminal Details

Ticket: RM-43720

Description: This release adds a new section called Additional Information to the Terminal Details page in the . This section contains terminal details, including:

  • Battery
  • Firmware
  • Connection status
  • Network
  • Time Zone
  • Last Access

Mandate: Does not apply.

Audience: Users of payment terminals.

Benefit: Increased visibility into the details of your terminal.

Technical Details: None.

Important Dates: Released to production March 17, 2026.


Recurring Billing Subscriptions

Ticket: RM-41823

Description: This feature gives users more control over their payments by displaying the next five upcoming scheduled payments and allowing them to be marked as Skipped. Users can also reverse this action, returning a payment to its Scheduled status.

To enhance visibility, the payments table pagination is updated to ten, to show all five upcoming payments along with up to five most recent past payments on the first page.

A Load More Scheduled button is introduced that allows users to load more upcoming scheduled payments and give the possibility to skip them.

Mandate: Does not apply.

Audience: Users of Recurring Billing.

Benefit: Users will be able to see their upcoming payments and skip or unskip them if needed.

Technical Details: None.

Important Dates: Released to production March 17, 2026.

Invoicing

Ticket: RM-44111

Description: Release fixes the following issues:

  • The Payment page sometimes did not load properly on mobile devices.
  • Amount-only invoices with zero-amount displayed the wrong message.
  • Emails were not working when the status was set to Created after creating an amount-only invoice.
  • Incorrect validation message when someone tried to create an amount-only invoice with a zero amount.
  • The amount field was displayed twice when the Custom Label object had a value, causing duplication of line items.

Audience: Users of Invoicing.

Technical Details: None.

Important Dates: Released to production March 20, 2026.

Unified Checkout and Token Management Service

Ticket: EPS-36831

Description: When Unified Checkout is disabled for a child account in , the Token Management Service is automatically disabled as well, causing tokens to become unavailable.

Audience: Users of Unified Checkout and Token Management Service.

Technical Details: None.

Workaround: Re-enabling Unified Checkout and the Token Management Service in the Unified Checkout settings restores Token Management Service functionality.


Search Export

Ticket: EPS-36827

Description: When a user in the searches for a merchant ID on the Designated Contacts page and clicks the Export button, the downloaded CSV file is empty.

Audience: Global.

Technical Details: None.

Workaround: None.


Transaction Details

Ticket: EPS-36741

Description: The Transaction Details page in the displays Token links with incorrect token IDs.

Audience: Users of the Token Management System.

Technical Details: None.

Workaround:

March 13, 2026

These release notes cover releases for the week ending March 13, 2026.

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 . 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 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 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 . 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.

No customer-facing fixes were released this week.

There are no known issues this week.

March 6, 2026

These release notes cover releases for the week ending March 6, 2026.

AFT and OCT Transactions

Ticket: RM-42567

Description: This release enhances the payment authorization API for Account Funding Transactions (AFTs) and Original Credit Transaction (OCTs). The response message contains the source of the funding in the payments.card.vpc-edqp-afs-enhancement field.

Mandate: Does not apply.

Audience: Merchants who accept AFT and OCT payments.

Benefit: The funding source is needed to support Visa Flexible Credential. This would help to apply credit card surcharges.

Technical Details: None.

Important Dates: Released to production March 4, 2026.

Vantiv Transactions

Ticket: RM-41337

Description: Transactions processed through Vantiv will now time out after 30 seconds.

Audience: Merchants who process transactions through Vantiv.

Technical Details: None.

Important Dates: March 4, 2026.

Ticket: EPS-36336

Description: Applications that are showing as Challenge or Not Run in Transaction Search will instead show as Failed in Similar Search.

Audience: Users of Similar Search in the .

Technical Details: None.

Workaround: No.


Visa Platform Connect Transactions

Ticket: EPS-36391

Description: All transactions using 3-digits exponent currency must be performed with the last digit as a zero. If a transaction is sent with different last digit (1-9), we will adjust the value to 0.

Audience: Merchants using 3-digits exponent currencies through Visa Platform Connect.

Technical Details: A discrepancy was found specifically for credit authorization transactions, where an initial authorization and settlement transaction performed without a 0 does not benefits from the same logic, leading to rejections from Visanet.

Workaround: Until further notice, consider performing an authorization and settlement transaction with the last digit set to zero, in case there is a possibly of future credits on your orders. If you are affected by this issue, consider performing a standalone credit.

Last published: November 18, 2026

Not available for your audience

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