Release Notes {#rn-general} =========================== These release notes cover all releases to the production server for the week ending August 15, 2025. Announcements {#rn-announce} ============================ These are the announcements for August 15, 2025. BIN Lookup Service 2.0 {#announcement-binlookup-2} ================================================== **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. Features Introduced This Week {#rn-features} ============================================ **Reporting in the Busincess Center** \| RM-37514 ------------------------------------------------- Description : Previously, when generating a report in the Business Center, the Merchant ID (MID) drop-down menu displayed all MIDs in the portfolio, even the MIDs that are not associated with your merchant group. This configuration made it more difficult to find a specific MID. : With this release: : * If you are part of a merchant group, the MID drop-down menu displays only the MIDs that belong to your group. * This update applies to the report creation flow, which is accessed from Available Reports and Report Subscription Management in the Reporting module. {#rn-features_ul_esp_gry_hgc} : If you are not part of a merchant group, you will see no change --- the drop-down menu still diasplays all MIDs. Audience : Users of reporting who are part of a portfolio. Benefit : This enhancement ensures that only relevant MIDs display in a generated report, which reduces clutter and improves reporting experience. Technical Details : None. Important Dates : August 11, 2025. **RTSS** \| RM-37588 -------------------- Description : This release includes two changes related to RTSS: * We send an additional field-eligibility inquiry in follow-on RTSS events if it was sent in the original authorization. * If we encounter a failure in an authorization refresh that is related to split shipment, we send a new capture-failure RTSS event. {#rn-features_ul_a3q_fvy_hgc} Audience : Users of RTSS. Benefits : * The eligibility inquiry update enables the support of installment data transactions. * The new capture-failure event provides additional visibility to merchants about transaction events. {#rn-features_ul_n32_zmz_hgc} Technical Details : None. Important Dates : August 14, 2025. **Business Center Permissions** \| RM-35668 ------------------------------------------- Description : New permissions have been introduced in the Business Center for the following products: : * *Send Receipt* emails * *Transaction Search* emails * Batch Upload {#rn-features_ul_prb_mtz_hgc}If a user's role lacks the required permissions, the attempted action will return an *Access Forbidden* or similar message. We recommend reviewing your role configuration to ensure that the necessary access is granted. No product capabilities have been removed but the permission validation is more stringent. Audience : All merchants and partners who use the Business Center, particularly those who rely on *Send Receipt* emails *Transaction Search* emails, or Batch Upload. Benefit : Stronger permissions enforcement protects sensitive operations and ensures that only properly authorized personnel can perform them. Technical Details : None. Important Dates : Released to production June 30, 2025. **Payments** \| RM-36880 ------------------------ Description : Absa is added as an acquirer for China Union Pay. Audience : Users of China Union Pay. Benefit : The addition of new acquirer options provides flixibility to the merchant. Technical Details : None. Important Dates : Released to production August 14, 2025. Fixed Issues {#rn-fixed-issues} =============================== No customer-facing fixes were released this week. Known Issues {#rn-known-issues} =============================== **Virtual Terminal Email Receipts** \| **EPS-33298** ---------------------------------------------------- Description : When a user of Virtual Terminal has automatic email receipts enabled and they process a transaction, the email receipt states the amount is 0.00 instead of the amount of the transaction. Audience : Users of Virtual Terminal. Technical Details : None. Workaround : Generate a receipt manually in the Business Center. **Decision Manager** \| EPS-33012 --------------------------------- Description : When a user of Decision Manager tries to edit a queue that has *Move* in the policy, the result is a white screen. Audience : Users of Decision Manager. Technical Details : None. Workaround : None. **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 that are 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.