Known Issues

An intermittent issue sometimes causes voided transactions that were sent through GPX or VPC to be submitted for clearing.

Merchants who use GPX or VPC.

None.

None.

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.

Merchants who process transactions through FDI Global.

None.

None.

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.

Merchants who use Elavon Americas as a payment processor.

Elavon is returning a three-digit card suffix instead of the expected four digits.

None. Elavon has been notified.

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.

Merchants who use the

Transactions by Phase - Settlements Pending Batch

report.

None.

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.

The refund and reversal amount shown in the Business Center for some transactions shows as $0.00 instead of the actual amount.

Global.

None.

None.

For some accounts that use Decision Manager Hierarchy, attempting to access order or product velocity resulted in an error.

Users of Decision Manager Hierarchy.

None.

None.

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.

Merchants who perform authorization and capture in separate transactions.

None.

None.

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.

Business Center administrators in India.

None.

None.

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.

Users who view the Business Center using one of the affected languages.

None.

Use a period instead of a comma to indicate the decimal value in the transaction amount until the issue is resolved.

An intermittent issue in Unified Checkout sometimes causes a 30 to 40-second lag while loading the payment options.

Unified Checkout merchants whose account configuration has disabled the Click to Pay feature.

None.

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.

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.

Worldpay VAP merchants.

None.

None.

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.

Merchants who use the

Transaction Search By Phase > Authorizations Ready to Settle

search filter.

None.

If there is only one search result, use the Transaction Details page to settle the transaction.