January 2026
Production releases for the weeks ending January 2 to January 30, 2026: features, fixed issues, and known issues.
January 30, 2026
These release notes cover releases for the week ending January 30, 2026.
New API Payment Methods for Thunes
Ticket: RM-41805
Description: This release introduces API support for several new alternative payment methods through the existing Thunes processor integration. Clients using Thunes will now be able to accept the following payment methods:
- PSE
- ANCV Connect
- MasterPass
- Gcash (Direct)
- RabbitLinePay (Direct)
There are no changes in the .
Mandate: Does not apply.
Audience: Merchants and partners integrated with Thunes who accept alternative payment methods.
Benefit:
- Provides more flexible and localized payment options to the end users.
- Improves customer experience by enabling popular alternative payment methods used in multiple regions.
- Enables merchants to expand acceptance capabilities without additional custom development.
Technical Details: The API fields for this update are already existing in the API. No change is required to use these fields through Thunes.
Important Dates: Released to production January 29, 2026.
Credit Reference Reconciliation Number
Ticket: RM-41881
Description: This feature will enable the credit reference reconciliation number as a response field for all credit transactions that do not have an authorization reference reconciliation number.
Mandate: Does not apply.
Audience: Payment Service Providers.
Benefit: The credit reference reconciliation number response enables you to:
- Track the refund.
- Preserve a consumer reference
- Reconcile payments across the payment flow, from the merchant to the Payment Service Provider to the acquirer.
Technical Details: The field name is processorInformation.retrievalReferenceNumber.
Important Dates: Released to production January 29, 2026.
Offline Transaction File Submission
Ticket: RM-41827
Description: This release fixes performance issues for the Offline Transaction File Submission (batch upload) service. The update enables batch processing to continue after there is a failure of one or more transactions, reducing the need for manual intervention during the reconciliation process.
Audience: Users of batch upload.
Technical Details: None.
Important Dates: This was released to production December 12, 2025, but was not documented at that time.
Credits and Refunds
Ticket: RM-41850
Description: This release fixes an issue that was experienced by merchants whose accounts are enabled for Purchase Return Authorization. When they sent a credit or refund transaction through the API and the response contained HTTP code 203 or 205, the status field contained the HTTP code instead of the text description.
Audience: Merchants whose accounts are enabled for Purchase Return Authorization.
Technical Details: None.
Important Dates: Released to production January 28, 2026.
Credit Transactions
Ticket: RM-41626
Description: This release resolves an issue that caused follow-on credit transactions (refunds) to fail when requested more than 180 days after the original transaction, in cases where the associated authorization included Dynamic Currency Conversion.
Audience: Merchants that process transactions through Visa Platform Connect.
Technical Details: None.
Important Dates: Released to production January 29, 2026.
Ticket: EPS-35950
Description: The Customer Support link in the One-Time-Password page of the login is broken.
Audience: Users of the .
Technical Details: None.
Workaround: Navigate to https://support.visaacceptance.com to use the Support Center.
Decision Manager
Ticket: EPS-35715
Description: When a user of Decision Manager in the attempts to edit a custom rule, sometimes they are redirected to a blank page. This occurs intermittently in the and does not affect the API.
Audience: Users of Decision Manager.
Technical Details: None.
Workaround: None.
Decision Manager
Ticket: EPS-35668
Description: If you perform a large Case Search in Decision Manager, a latency issue sometimes causes the search to time out.
Audience: Users of Decision Manager.
Technical Details: None.
Workaround: Until the issue is fixed, try using a smaller search.
January 23, 2026
These release notes cover releases for the week ending January 23, 2026.
Salesforce B2B 1.7.0
Description: This release adds support for these services:
- Token Management Service
- Order Management Lite
- D2C store integration
Mandate: Does not apply.
Audience: Mechants who use Salesforce B2B.
Benefit:
- Tokenization of payment data increases security.
- Order Management Lite enables you to manage your order within your B2B system.
- D2C store integration enables you to provide Direct to Consumer services.
Technical Details: None.
Important Dates: Released to production January 22, 2026.
Salesforce Order Management 2.8
Description: This release includes the following updates:
- Support for payment authorization or order creation using Salesforce Order On Behalf Of. This feature enables customer service representatives to place orders directly on behalf of a customer.
- Support for payment tokenization and the My Account page.
- Support for message-level encryption.
- Card BIN Exclusion in transient tokens.
- Upgrade to Salesforce API v63.0.
- Klarna capture support.
Mandate: Does not apply.
Audience: Users of Salesforce Order Management.
Benefit: Increased flexibility and security.
Technical Details: None.
Important Dates: Released to production January 22, 2026.
Salesforce REST 26.1.0
Description: This release adds support for a data-only 3-D Secure workflow for Payer Authentication.
Mandate: Does not apply.
Audience: Users of Salesforce REST 26.1.0
Benefit: Data-only 3-D Secure shares data that merchants collect during transactions with the issuer so that the issuers can make more informed authorization decisions for future transactions.
Technical Details: None.
Important Dates: Released to production January 22, 2026.
No customer-facing fixes were released this week.
Diners and Discover Transactions
Ticket: EPS-30491
Description: The e-commerce indicator DIPB for Diners and Discover cards is not recognised when processing through Vantiv on Visa Platform Connect. This leads to authorization failure when a Diners or Discover transaction is authenticated, either through Payer Authentication or Digital Payment.
Audience: Merchants who process Diners or Discover cards through Vantiv on Visa Platform Connect.
Technical Details: None.
Workaround: None.
January 16, 2026
These release notes cover releases for the week ending January 16, 2026.
Email Branding
Ticket: RM-41034
Description: If a portfolio has set a theme for a specific country, merchants whose addresses are linked to that country will receive branding emails with that country’s theme. If no country-specific theme is set, the default branding theme will be used.
Mandate: Does not apply.
Audience: Portfolio merchants who use country-specific branding, and the merchants in their portfolio.
Benefit: Consistent branding.
Technical Details: None.
Important Dates: None.
Adobe Commerce 25.2.0
Description: This release includes these updates:
- Message-Level Encryption is supported. This significantly reduces the risk of sensitive data exposure and helps merchants maintain compliance with the latest PCI DSS standards.
- Updates for for Payer Authentication in Google Pay to improve transaction accuracy and authentication reliability.
- API endpoints are updated to ensure continued compatibility.
- Jaywan is added as a card type to enable acceptance of regional card schemes.
- Subresource Integrity is implemented to protect against malicious script injection.
- Content Security Policy violation issues have been fixed.
- Country field value derived from store view configuration.
Mandate: Does not apply.
Audience: Users of Adobe Commerce 25.2.0.
Benefit: See the description above.
Technical Details: None.
Important Dates: None.
No customer-facing fixes were released this week.
Partner Risk Controls
Ticket: EPS-34973
Description: An issue with currency conversion sometimes causes conversions that use the Australian dollar to calculate slightly different values.
Audience: Users of Partner Risk Controls.
Technical Details: The issue is that the currency code AUD is sometimes incorrectly used as aud, resulting in value discrepancies. For example, 32680.00000 instead of 32500.6500000.
Workaround: None.
Transaction Details
Ticket: EPS-35538
Description: When a user on the 's Transaction Details page tries to settle an authorization and then clicks the Help link, they receive the error message internal server error.
Audience: Users of Transaction Details in the .
Technical Details: None.
Workaround: None.
Decision Manager
Ticket: EPS-35557
Description: In the Decision Manager Rule Builder page, when a velocity rule cannot reach the server, the payload still includes velocity information as an empty string instead of null.
Audience: Users of Decision Manager's Rule Builder.
Technical Details: None.
Workaround: Create a nested rule in which one of the velocity conditions is set to is present, and the other condition is set for the rule that user wants to create.
January 9, 2026
These release notes cover releases for the week ending January 9, 2026.
Unified Checkout
Ticket: RM-41346 and RM-41387
Description: This release in the allows portfolio accounts and transacting merchant accounts to be enabled for Unified Checkout and its features. Portfolio users can see additional features. This functionality was already available for the API.
Mandate: Does not apply.
Audience: Portfolio account users.
Benefit: Unified Checkout is a hosted payment solution that provides a single integrated interface for accepting a wide range of digital payments directly on a merchant's ecommerce page. It is designed to reduce checkout friction, enhance security, and increase sales conversions.
Technical Details: None.
Important Dates: Released to production January 6, 2026.
Merchant Boarding
Ticket: RM-40886
Description: This release enables Payouts as a card type on the merchant boarding template for merchants that process through VPC.
Mandate: Not applicable.
Audience: Portfolio users who board merchants with VPC as their processor.
Benefit: Enabling Payouts provides an additional payment option for merchants.
Technical Details: Enable Payouts at the portfolio level and check the Payouts box in the Processor section.
Important Dates: Released to production January 7, 2026.
Invoicing
Ticket: RM-40845
Description: This release enables merchants to use these optional capabilities:
- Set an expiration date when you create or edit invoices.
- Extend expiration dates on existing invoices.
When an invoice payment link expires, the status of the link does not automatically change from Active to Inactive. The link remains in its current state, but the expiration message appears when the expired link is accessed.
When a customer attempts to access an expired invoice payment link, they receive a message stating that the link is expired. The message also directs the customer to contact the business that issued the link.
When this feature is released, expiration dates will not be applied automatically to existing invoices. Merchants can manually update expiration dates on existing invoice payment links.
Mandate: Does not apply.
Audience: Merchants who use invoicing.
Benefit: Setting an expiration date for an invoice payment link can prevent unauthorized payments. Unauthorized payments can occur when a link remains accessible or relies on manual deactivation.
Technical Details: To configure an invoice payment link expiration date, go to the Pay by Link module in the , create a new link or edit an existing link, and configure the expiration date field. If a customer needs more time to complete a payment, the merchant can update expiration dates on the existing invoice payment link.
Important Dates: Released to production January 8, 2026.
Pay By Link
Ticket: RM-40845
Description: This release enables merchants to use these optional capabilities:
- Set an expiration date when you create or edit payment links.
- Extend expiration dates on existing payment links.
When a payment link expires, the status of the link does not automatically change from Active to Inactive. The link remains in its current state, but the expiration message appears when the expired link is accessed.
When a customer attempts to access an expired payment link, they receive a message stating that the link is expired. The message also directs the customer to contact the business that issued the link.
When this feature is released, expiration dates will not be applied automatically to existing payment links. Merchants can manually update expiration dates on existing payment links.
Mandate: Does not apply.
Audience: Merchants who use Pay By Link.
Benefit: Setting an expiration date for a payment link can prevent unauthorized payments. Unauthorized payments can occur when a link remains accessible or relies on manual deactivation.
Technical Details: To configure a payment link expiration date, go to the Pay by Link module in the , create a new link or edit an existing link, and configure the expiration date field. If a customer needs more time to complete a payment, the merchant can update expiration dates on the existing payment link.
Important Dates: Released to production January 5, 2026.
Webhooks
Ticket: RM-40845
Description: A webhook notification can be sent to merchants and independent software vendors when invoices or payment links are created in the .
Merchants must subscribe to an Invoicing or Pay by Link creation event to receive the Webhook notifications.
Mandate: Does not apply.
Audience:
Benefit: Merchants and independent software vendors can integrate the Invoicing or Pay by Link webhooks as a trigger that begins their business processes.
Technical Details: None.
Important Dates: Released to production January 5, 2026.
Salesforce Commerce Cloud
Description: This release adds Unified Checkout to Salesforce Commerce Cloud.
Mandate: Does not apply.
Audience: Users of Salesforce Commerce Cloud.
Benefit: Unified Checkout is a hosted payment solution that provides a single integrated interface for accepting a wide range of digital payments directly on a merchant's ecommerce page. It is designed to reduce checkout friction, enhance security, and increase sales conversions.
Technical Details: None.
Important Dates: Released to production January 6, 2026.
Merchant Boarding
Ticket: RM-39965
Description: Portfolio merchants who use Prisma and the Visa Acceptance Platform can now board merchants using the 's Merchant Management feature.
Mandate: Does not apply.
Audience: Portfolio merchants who use Prisma and the Visa Acceptance Platform.
Benefit: Merchant management enables partners and resellers to board and manage their merchant accounts in a streamlined online interface instead of using the API.
Technical Details: No action is required by merchants.
Important Dates: Released to production Janaury 5, 2026.
Merchant Boarding in Japan
Ticket: RM-40408
Description: This release enables portfolio merchants to enter a shop name during merchant boarding in three new languages: Japanese, Romaji, and Katakana, for portfolios that are enabled for CSKK.
Mandate: Does not apply.
Audience: Portfolios that are CSKK-enabled.
Benefit: Additional language enable additional flexibility in naming shops.
Technical Details: No action is required.
Important Dates: Released to production January 5, 2026.
Transaction Search
Ticket: RM-39799
Description: Searching by token ID will now show more API events related to that token, including creation, updates, retrievals, and deletions, in addition to the existing view of payments and other service requests made using the token.
Mandate: Does not apply.
Audience: Merchants who use the Token Management System.
Benefit: Additional details about token events.
Technical Details: None.
Important Dates: Released to production January 5, 2026.
No customer-facing fixes were released this week.
Transaction Search
Ticket: EPS-34742
Description: When merchants load a saved search that contains more than one filter, only one filter is shown. The other filters are blank or missing.
Audience: Merchants who use Transaction Search.
Technical Details: None.
Workaround: None.
Virtual Terminal
Ticket: EPS-35660
Description: If a merchant is generating reports by filtering Client Application with UBC Virtual Terminal or Legacy Virtual Terminal options, they will not see Virtual Terminal transactions in the reports.
Audience: Merchants who use the legacy Virtual Terminal for payment transactions.
Technical Details: The transactions use the value UBC Virtual Terminal, but the filter option in the report setting is Legacy Virtual Terminal. As a result, it falsely appears that transactions are missing in the reports.
Workaround: Until the issue is fixed, do not use the Legacy Virtual Terminal filter option in the report setting. Follow these steps:
- In report settings, set Client Application to All.
- Add the Source field to your report.
- After export, filter the Source column in Excel for UBC Virtual Terminal.
January 2, 2026
These release notes cover releases for the week ending January 2, 2026.
No customer-facing features were released this week.
No customer-facing fixes were released this week.
REST API
Ticket: EPS-35205
Description: The processingInformation.paymentSolution field submitted in a REST API authorization request is not returned in the response if a digital payment was used in the request and the merchant ID is not configured for the Token Management System.
Audience: Merchants who require processingInformation.paymentSolution in their REST API response payload.
Technical Details: None.
Workaround: Track the processingInformation.paymentSolution value from the authorization request instead of relying on the value returned in the response.
Partner Risk Controls
Ticket: EPS-33958
Description: The profile assignment feature cannot search for merchant accounts from the available merchant account list.
Audience: Resellers using Partner Risk Controls.
Technical Details: None.
Workaround: Use the file upload solution to assign profiles.
Invoicing
Ticket: EPS-34231
Description: If an invoicing transaction returns a soft decline, for example, 230 - CVV failure, and the merchant subsequently settles the transaction manually using the , the invoice remains in pending status indefinitely.
Audience: Merchants who use invoicing.
Technical Details: None.
Workaround: None.
Thanks for your feedback!
Last published: November 18, 2026