On This Page

Release Notes

These release notes cover all releases to the production server for the week ending
September 19, 2025
.

Announcements

These are the announcements for
September 19, 2025
.

BIN Lookup Service 2.0

Products Included:
 BIN Lookup
Region/Country:
 Global
Expected Release Date:
 Currently in Limited Availability
The BIN Lookup Service 2.0 for the production environment is currently in Limited Availability.
Effective October 1, 2025
, network availability for BIN Lookup Service 2.0 will be restricted to
American Express
,
Discover
, and
Visa
. This restriction applies to all existing resellers and direct merchants using the service. BIN Lookup Service 2.0 with the current set of enabled networks will continue for existing clients until October 1, 2025, and there will be no immediate disruption in service. Our current focus is moving the service from Limited Availability to General Availability, and working on enhanced product features.
Any new resellers or direct merchants need to have an agreement and pricing in place to be enabled for the BIN Lookup Service. They can be enabled for American Express, Discover, and Visa along with certain regional networks.

Visa Acceptance Agent Toolkit

Products Included:
  • Visa Acceptance Agent Toolkit
  • Invoicing
  • Pay by Link
Region/Country:
 Global
Expected Release Date:
 Currently in Pilot Release
The Visa Acceptance Agent Toolkit pilot release is now available. Use the toolkit to simplify the process of integrating the Visa Acceptance Platform APIs into your agentic workflows.
The specialized tools in the toolkit currently enable your AI agents to use the Pay by Link and Invoicing APIs. This feature enables your agents to create and manage payment links and invoices. The toolkit is built in TypeScript, and you can integrate it with the Vercel AI SDK or use it to access a Model Context Protocol (MCP) server.
For more information, see the
Visa Acceptance Agent Toolkit Developer Guide
.

Webhooks Updates

We have added new validations for version 1 of webhooks:
  • Only alpha-numeric data and spaces are allowed in the name field of newly created or updated subscriptions. Existing version 1 subscriptions are not affected unless they are updated.
  • Most webhooks fields for newly created or modified subscriptions will not accept HTML tags. Existing version 1 subscriptions are not affected unless they are updated.
  • The
    securityType
     field in
    Create
     and
    Patch
     requests accepts only one of the following values:
    key
    ,
    oAuth
    , or
    oAuth_JWT
Version 1 will be decommissioned in April 2026. We recommend that you begin using webhooks version 2.

Features Introduced This Week

No customer-facing features were released this week.

Fixed Issues

Decision Manager
 | RM-39028

Description
This release fixes a defect in which transactions that were rejected in the early decision phase were rejected, but the final or profile decision was accepted. Now the final profile decision will also be rejected.
Audience
Users of Decision Manager.
Technical Details
Customers who previously implemented a workaround can now remove that workaround and restore the original functionality.
Important Dates
Released to production September 17, 2025.

Known Issues

Merchant Boarding API
 | EPS-33352

Description
The merchant address field in the merchant boarding API does not accept apostrophes, which is preventing clients from boarding merchant accounts with addresses that contain an apostrophe (').
Audience
Users of the merchant boarding API.
Technical Details
The field name of the merchant address field is
organizationInformation.businessInformation.address.address1
Workaround
None.

Flex Microform
 | EPS-33858

Description
When the microform is hosted within an iframe, trying to move from the microform to the parent page using the tab key results in a JavaScript error, which causes validation to not run for the last field in the microform. The cardholder would not be aware when there are problems with their input.
Audience
Merchants who use Flex Microform within an iframe.
Technical Details
The JavaScript error is
Uncaught TypeError: Cannot read properties of undefined
.
Workaround
None.

Business Center Refunds
 | EPS-33882

Description
This issue allows merchants to process two full refunds for the same transaction. Although the second refund fails, it appears successful in the Business Center. This occurs even though the refund limit is set to 100%.
Audience
Merchants using the Business Center to refund transactions.
Technical Details
Error code:
100073 Credit request declined as amount exceeds configured allowed value.
Workaround
None.

Merchant Boarding API
 | EPS-33892

Description
Sometimes, when the API is used to board a merchant account with TMS enabled, the account is registered but the product enablement fails. This defect leaves the merchant account with a status of PARTIAL.
Audience
Users of the merchant boarding API.
Technical Details
None.
Workaround
Use the Business Center to find the merchant account and complete its product enablement manually.

Payments through Rede
 | EPS-33931

Description
Network token cryptograms are missing from the authorization payload of transactions that are processed through Rede, resulting in issuer declines.
Audience
Merchants who process transactions through Rede.
Technical Details
None.
Workaround
None.

Payment Clearing
 | EPS-30773

Description
An intermittent issue sometimes causes voided transactions that were sent through GPX or VPC to be submitted for clearing.
Audience
Merchants who use GPX or VPC.
Technical Details
None.
Workaround
None.

Payment
 | EPS-33187

Description
FDC Nashville Global does not support currencies with more than two decimal places. For example, 1.999 uses three decimal places, which is not supported. Transactions with more than two decimal places appear successful during authorization but fail during settlement.
Audience
Merchants who process transactions through FDI Global.
Technical Details
None.
Workaround
None.

Decision Manager
 | EPS-33213

Description
When merchants who use Decision Manager send tokenized transactions through Elavon Americas, they sometimes receive the response code
102: invalid or missing card suffix
, even when the correct information was sent.
Audience
Merchants who use Elavon Americas as a payment processor.
Technical Details
Elavon is returning a three-digit card suffix instead of the expected four digits.
Workaround
None. Elavon has been notified.

Reporting
 | EPS-33455

Description
When a merchant exports the
Transactions by Phase - Settlements Pending Batch
 report to a CSV file while selecting the
Payment
 checkbox, some data rows will have an incorrect offset, meaning they will not correspond to the column they are in.
Audience
Merchants who use the
Transactions by Phase - Settlements Pending Batch
 report.
Technical Details
None.
Workaround
  • There is one extra field under the
    source
     column. This means that all the data from the column
    user
     to the column
    card_accountNumber
     (four columns) should be moved to the left by one column.
  • There are two extra fields under the
    card_accountNumber
     and
    card_expirationMonth
     columns. This means that all the data from the column
    card_expiration_year
     to the last column
    merchantDefinedDataField4
     should be moved to the left by two columns.

Transaction Details

Description
The refund and reversal amount shown in the Business Center for some transactions shows as $0.00 instead of the actual amount.
Audience
Global.
Technical Details
None.
Workaround
None.

Decision Manager Hierarchy
 | EPS-33543

Description
For some accounts that use Decision Manager Hierarchy, attempting to access order or product velocity resulted in an error.
Audience
Users of Decision Manager Hierarchy.
Technical Details
None.
Workaround
None.

Merchant-Defined Data
 | EPS-33367

Description
This is a display issue that can occur to merchants who perform authorization and capture in separate transactions. If the merchant performs a follow-on credit that references the capture transaction, the follow-on credit screen correctly displays the merchant-defined data from the capture transaction. However, after the credit is performed, the credit transaction instead displays merchant-defined data from the authorization transaction, which could be different.
Audience
Merchants who perform authorization and capture in separate transactions.
Technical Details
None.
Workaround
None.

Business Center in India
 | EPS-33419

Description
When a Business Center administrator creates a user in the Business Center in India, the registration email sent to the new user contains an incorrect link to activate the account.
Audience
Business Center administrators in India.
Technical Details
None.
Workaround
None.

Transaction Details
 | EPS-33508

Description
When merchants use the Business Center's Transaction Details page to perform a follow-on transaction, the amount of the transaction is already populated in the menu. However, when the language set in the Business Center uses a comma instead of a period to incidate decimal values in the amount, an error occurs.
Audience
Users who view the Business Center using one of the affected languages.
Technical Details
None.
Workaround
Use a period instead of a comma to indicate the decimal value in the transaction amount until the issue is resolved.

Unified Checkout
 | EPS-33641

Description
An intermittent issue in Unified Checkout sometimes causes a 30 to 40-second lag while loading the payment options.
Audience
Unified Checkout merchants whose account configuration has disabled the Click to Pay feature.
Technical Details
None.
Workaround
Merchants using Unified Checkout with Click To Pay disabled are advised to remove this option from their Capture Context request. It is also recommended that merchants use an updated client version of 0.28 or later.

Worldpay VAP Error Code
 | EPS-33667

Description
When Worldpay (
vantivcnp
) sends the error code for
invalid CVN
 to the Visa Acceptance Platform, the error code sent to the merchant incorrectly states
Card is Inactive or not authorized for card-not-present transactions.
Audience
Worldpay VAP merchants.
Technical Details
None.
Workaround
None.

Transaction Search
 | EPS-33684

Description
Merchants who perform transaction searches in the Business Center using the
Transaction Search By Phase > Authorizations Ready to Settle
 search filter receive an error if there is only one result. If there is more than one result, the error is not triggered.
Audience
Merchants who use the
Transaction Search By Phase > Authorizations Ready to Settle
 search filter.
Technical Details
None.
Workaround
If there is only one search result, use the Transaction Details page to settle the transaction.