Known Issues

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.