Release Notes {#rn-general}
===========================

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

Announcements {#rn-announce}
============================

These are the announcements for August 22, 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}
============================================

No customer-facing features were released this week.

Fixed Issues {#rn-fixed-issues}
===============================

**Shopify** \| RM-37903
-----------------------

Description
:
This release fixes a bug that prevented refunds on Shopify.

Audience
:
Shopify merchants.

Technical Details
:
None.

Important Dates
:

**Shopify** \| RM-37903
-----------------------

Description
:
This release fixes a bug that prevented Payer Authentication from retrying transactions.

Audience
:
Shopify merchants.

Technical Details
:
None.

Important Dates
:

Known Issues {#rn-known-issues}
===============================

**Recurring Billing** \| EPS-32922
----------------------------------

Description
:
An intermittent bug is affecting the legacy Recurring Billing service. When a merchant issues a follow-on credit for a settled transaction that was processed through recurring billing, they sometimes receive the error *Reason Code 102* (see technical details). This occurs even if the merchant's account is configured for 365 day credits.

Audience
:
Users of the legacy Recurring Billing service.

Technical Details
:
Reason Code 102: *There is a problem processing this request: The request id for the transaction is either invalid or missing.*

Workaround
:
Use a standalone credit instead of a follow-on credit.

**Tax Calculation** \| EPS-33141
--------------------------------

Description
:
A bug that affecting acquirers is preventing three tax fields from being populated in the TC33A file for authorizations and follow-on settlements. This is true even when the fileds were included in the payload. The fields are:

    * Local tax
    * Local Tax Included
    * Total Taxes Amount
    {#rn-known-issues_ul_prz_syy_jgc}

Audience
:
Acquirers who settle transactions that were performed using the Tax Calculation Service.

Technical Details
:
Local Tax: CP04 TCR0 Pos: 36-47, CP12 TCR1 Pos: 26-37  
Local Tax Included: CP04 TCR0 Pos: 48, CP12 TCR1 Pos: 38

    Total Taxes Amount: CP12 TCR1 Pos: 52-70

Workaround
:
None.

**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 that 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 \&gt; 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.
