Known Issues

API requests that combine Payer Authentication with authorization and include relaxed AVS return a Billing Information error.

Users that send API requests combining Payer Authentication and Authorization with relaxed AVS.

None.

Send separate Payer Authentication and Authorization requests.

There is an intermittent issue that sometimes causes an HTTP 500 timeout response when you are using the REST API to download the Batch Upload report with a large number of transactions.

Merchants who download the Batch Upload report using the REST API.

None.

Download the report in the Business Center.

Wells Fargo users of portfolio accounts in the Business Center are unable to view merchant accounts that are configured to use Cardinal as a processor.

Wells Fargo portfolio users.

Attempting to view a MID configured for Cardinal results in the following error message:

Some of the processors configured on your account are not supported, hence the processor configuration is skipped on purpose. Please contact customer support to update your processor settings

.

None.

A merchant that had deleted their service account was affected by an issue that caused end users who attempt to pay an invoice to be shown the error message

Failed to retrieve invoice details

.

Users of Invoicing.

Deleting the service account triggered the defect.

Create a new merchant account until the defect is fixed.

When a merchant deleted the Secure Acceptance profile associated with their merchant accounts in the Business Center, the associated merchant accounts become unable to process invoice payments.

Users of Invoicing

None.

Create a new merchant accounts until the defect is fixed.

Portfolio accounts in India that use the legacy merchant boarding platform and use Payer Authentication are still required to enter the

-1000

suffix in the Acquirer ID field in the Payer Authentication Configuration page. If the suffix is not included, the following error message is shown:

Invalid Acquirer ID

. Users not in India and users of the new platform do not need to add the suffix.

Portfolios in India that use the legacy merchant boarding platform.

None.

Add the suffix.

When a user changes a merchant’s time zone in the Business Center's Merchant Details page by editing the Merchant Information section, the time zone appears to change but the time zone is not changed.

Users of Merchant Management.

None.

Call customer support and request that the time zone be updated.

When a merchant chooses the Settle option in the Orders Pending Review tab, the Accept Case Results dialog displays the message

No follow-on transaction requested

, and the settlement does not occur.

Users of Fraud Management Essentials in the Business Center

None.

Settle the transaction using the Settle option in the Order Search page.

MIT/COF transactions that use Discover or Diners card are returning a Network Trace ID containing letters. Subsequent transactions are then failing due to a front-end validation.

Merchants processing Diners or Discover MIT/COF transactions on Visa Platform Connect.

A 102 DINVALIDDATA error is returned that says

Field contains non numeric values : subsequent_auth_transaction_id

.

Manually stripping the initial four letters and the space will bypass our validation. However, some issuers will reject this workaround.

A small number of merchants are experiencing an intermittent issue that causes the Extended Settings page of Decision Manager to display without settings or display with settings that cannot be edited

A small number of merchants that use Decision Manager.

None.

None.

Merchants who attempt to create a report in the Business Center using the time zone “Asia/Rangoon - (GMT +06:30) Myanmar Standard Time” receive the error message “Error: Failed to create the Report” and the report is not created.

Users who create reports in the Business Center.

None.

None.

Transactions that included a company name with a single apostrophe were being approved for authorization and capture but not for follow-on credits.

Merchants whose company name includes a single apostrophe.

None.

None.

A possible defect caused a few transactions not to appear in the Payment Batch Detail Report (PBDR). The transactions were restored after reports were regenerated. We are investigating.

Only one merchant is known to have experienced this problem but it could affect others.

None.

Regenerate the PBDR or create a one-time report.

If the

jcn_gateway_credit

field is null, it defaults to

true

and initiates a credit authorization. However, credit authorization should only be initiated when the

jcn_gateway_credit

option is enabled.

Merchants that use the JCN gateway.

None.

None.

When a customer enters an incorrect PIN on a payment device that uses the REST API, the value of the

reason

field in the response says

UNAUTHORIZED_CARD

instead of

Incorrect PIN or PIN missing

.

Users of payment devices that use the REST API.

None.

The following support article lists the current issuer response codes that can be used as an alternative for mapping error response reasons for declined transactions: