Known Issues {#rn-known-issues} =============================== **Payment Clearing** \| EPS-30773 --------------------------------- Description : An intermittent issue sometimes causes voided transactions that were sent through GPX or VPC to be submitted for clearing. Audience : Merchants who use GPX or VPC. Technical Details : None. Workaround : None. **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} **Transaction Details** ----------------------- Description : The refund and reversal amount shown in the Business Center for some transactions shows as $0.00 instead of the actual amount. Audience : Global. Technical Details : None. Workaround : None. **Decision Manager Hierarchy** \| EPS-33543 ------------------------------------------- Description : For some accounts that use Decision Manager Hierarchy, attempting to access order or product velocity resulted in an error. Audience : Users of Decision Manager Hierarchy. Technical Details : None. Workaround : None. **Merchant-Defined Data** \| EPS-33367 -------------------------------------- Description : 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. Audience : Merchants who perform authorization and capture in separate transactions. Technical Details : None. Workaround : None. **Business Center in India** \| EPS-33419 ----------------------------------------- Description : 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. Audience : Business Center administrators in India. Technical Details : None. Workaround : None. **Transaction Details** \| EPS-33508 ------------------------------------ Description : 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. Audience : Users who view the Business Center using one of the affected languages. Technical Details : None. Workaround : Use a period instead of a comma to indicate the decimal value in the transaction amount until the issue is resolved. **Unified Checkout** \| EPS-33641 --------------------------------- Description : An intermittent issue in Unified Checkout sometimes causes a 30 to 40-second lag while loading the payment options. Audience : Unified Checkout merchants whose account configuration has disabled the Click to Pay feature. Technical Details : None. Workaround : 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. **Worldpay VAP Error Code** \| EPS-33667 ---------------------------------------- Description : 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.* Audience : Worldpay VAP merchants. Technical Details : None. Workaround : None. **Transaction Search** \| EPS-33684 ----------------------------------- Description : 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. Audience : Merchants who use the **Transaction Search By Phase \> Authorizations Ready to Settle** search filter. Technical Details : None. Workaround : If there is only one search result, use the Transaction Details page to settle the transaction.