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

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

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

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

**Business Center** \| RM-38533
-------------------------------

Description
:
The following pages will display in the Payment Configuration section of the Business Center only if they are configured for the account:

    * Secure Acceptance
    * Digital Payments
    * Unified Checkout
    {#rn-features_ul_wvr_1fw_ngc}

Audience
:
Users of the three products listed above.

Benefit
:
This change creates a more streamlined and accurate view in the Business Center's Payment Configuration section.

Technical Details
:
None.

Important Dates
:
Released to production August 27, 2025.

**Oracle NetSuite 25.4.0**
--------------------------

Description
:
This release adds support for webhooks for invoice management.

Audience
:
Users of Oracle NetSuite 25.4.0.

Benefit
:
Webhooks provide additional insight into system events.

Technical Details
:
None.

Important Dates
:
Released August 29, 2025.

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

No customer-facing fixes were released this week.

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

**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.
{#rn-known-issues_ul_myt_k3w_ngc}