On This Page

Release Notes

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

Announcements

These are the announcements for
August 8, 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 will apply 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.

Features Introduced This Week

Payer Authentication
 | RM-37493

Description
Merchants will experience a new interface when they launch the Payer Authentication Configuration Application. This streamlined design offers the flexibility to choose between a simple configuration or a more advanced one, where multiple currencies can be enabled.
Audience
All merchants have enabled their 3-D Secure configuration in Payer Authentication.
Benefit
Reduced configuration effort.
Technical Details
None.
Important Dates
Released to production August 6, 2025.

Fixed Issues

No customer-facing fixes were released this week.

Known Issues

Token Management Service
 | EPS-33336

Description
An intermittent issue is affecting some portfolio users of TMS. Sometimes the TMS search filter is disabled for users of merchant-level organizations. They are unable to view the details of any tokens used by the transacting organizations beneath them in the organization hierarchy.
Audience
Users of merchant-level organizations.
Technical Details
None.
Workaround
Use a transacting organization to use token search.

Payments through VisaNet
 | EPS-30296

Description
Payment facilitator IDs are not being automatically populated when transactions are sent to VisaNet.
Audience
Merchants in the Asia-Pacific region, primarily India.
Technical Details
None.
Workaround
Include the payment facilitator ID in API requests by using the aggregator ID field.

Refunds through Prosa
 | EPS-32953

Description
Merchants who process payments through Prosa receive an error when they try to refund a captured transaction more than 60 days after the original authorization.
Audience
Merchants who process payments through Prosa.
Technical Details
The error is
Payment processor error (100004) General System Error
.
Workaround
Perform a standalone credit instead of a linked refund.

Merchant Boarding API
 | EPS-3311

Description
The Merchant Boarding API sometimes responds with an error during account registration. The API status is
PARTIAL
 and the message is
Unexpected error with Product Enablement and Config API
. If that happens, the merchant account can be found in Business Center with the warning,
This merchant account hasn't completed the boarding process
.
Audience
Users of the Merchant Boarding API.
Technical Details
None.
Workaround
Find the merchant account in the Business Center and choose
Complete Boarding
.

Token Management Service
 | EPS-33222

Description
Merchants cannot create tokens from the transaction details page. When they select
Actions > Create Token
, fill in all the required details, and click
Save
, they receive an error message.
Audience
Users of the Token Management Service.
Technical Details
None.
Workaround
Create the token from the Token Management page or by using the API.

Reporting
 | EPS-33290

Description
When merchants try to enable the Processor Events Detail Report from the Standard Report Subscriptions tab in the Business Center's Report Subscription Management page, they see a success message but the report remains in
Disabled
 status.
Audience
Users of the Processor Events Detail Report.
Technical Details
None.
Workaround
Merchants can copy the standard Processor Events Detail Report and save it as a custom report subscription instead. They must click the
Save
 button twice, as the first time will trigger this error.

Security Keys
 | EPS-32983

Description
When a merchant-level account with an underscore in the account name generates a P12 security keys in the Business Center's Key Management page, they receive the message
Error, an error occurred retrieving the keys
.
Audience
Business Center users.
Technical Details
None.
Workaround
Use a transacting account instead of a merchant account. Or if you plan to use the P12 key for multiple merchant accounts, generate a meta key.

Payments
 | EPS-33062

Description
The merchant advice code is not always returned for the Simple Order or SOAP Toolkit API implementation for some rejected authorization responses.
Audience
Users of the Simple Order API and the SOAP Toolkit API.
Technical Details
ccAuthReply_merchantAdviceCode
 and
ccAuthReply_merchantAdviceCodeRaw
 are not returned for some rejected authorization responses.
Workaround
You can retrieve complete response information by using the transaction search in either the Business Center or the Transaction Search API.

Decision Manager
| EPS-33117

Description
Some users receive a red banner error in the Business Center when they attempt to edit a Decision Manager queue.
Audience
Users of Decision Manager.
Technical Details
None.
Workaround
None.

Flex Microform Version 2
 | EPS-32476

Description
Merchants might experience transaction failures due to invalid card type errors when sending token creation requests using Flex Microform v2. This issue occurs when a reseller has Partner Risk Controls services enabled. In these cases, Flex does not include the card type in the initial request payload; instead, the card type is added later during the PaRC request process. This can result in validation errors and failed transactions for affected merchants.
Audience
Merchants integrating Flex Microform version 2, particularly those whose resellers have Partner Risk Controls services enabled. The issue does not impact all such merchants and might depend on account configuration.
Technical Details
Merchants received the error
102 The field is invalid: card_type
. The issue arises when the
card_type
 value is missing or does not meet the expected validation requirements in the transaction payload.
Workaround
To avoid validation errors, merchants can ensure the
card_type
 value is explicitly included in the transaction request payload.

Partner Risk Controls
 | EPS-32921

Description
Some transactions whose Electronic Commerce Indicator is set to
ECI=7
 were not blocked by Partner Risk Controls.
Audience
Users of Partner Risk Controls.
Technical Details
None.
Workaround
None.

Fraud Management Essentials
 | EPS-31123

Description
Users of Fraud Management Essentials who have signed up to receive SMS messages when a transaction is processed are not receiving SMS messages.
Audience
Users of Fraud Management Essentials.
Technical Details
None.
Workaround
Use email messsges instead of SMS until the problem is resolved.

Merchant Boarding Templates
 | EPS-32626

Description
Users might experience a persistent error message when applying a card processing template while boarding merchants in the Business Center.
Audience
This issue may impact merchants using the Boarding Template feature in the Business Center for card processing configuration.
Technical Details
The error message incorrectly indicates missing information when the card processing template application is processed, even if incomplete information was provided.
Workaround
If this error is encountered, users can switch to a different tab in the Business Center platform, then return to the original tab and click
Apply
 again. The form should then submit as expected.

Merchant Management
 | EPS-32722

Description
An intermittent issue is affecting users who edit merchant accounts on the Manage Merchants page. When a user edits only attributes in the Common Settings section and submits the changes, they might see a red banner that says
Error: An unknown error occurred. Try again later.
 However, the changes are successfully saved.
Audience
Users of Merchant Boarding.
Technical Details
None.
Workaround
You can ignore the error message.