Known Issues

The Credit Mutuel-CIC (CMCIC) gateway is returning

Response 150 General System Error

instead of

response 75 Number of Attempts Exceeded

.

Merchants using the CMCIC gateway.

None.

None.

Voided transactions performed soon after the batching time might still be batched, despite receiving confirmation that the void occurred in the API Response.

Merchants using Visa Platform Connect and GPX processors for payment transactions.

Merchants should see the error DNOTVOIDABLE rather than SOK when the void call was performed close to the daily set batching time.

Perform void calls before the set batching time setup for your merchant ID during the boarding of your account to prevent any overlap.

An intermittent DINVALIDATA error is sometimes returned in the

ics_bill

(settlement) call rather than during the

ics_auth

(authorization) call.

Merchants who use Visa Platform Connect for payment transactions.

None.

If this scenario occurs, perform an authorization reversal to remove the ring fencing of the funds induced by the generation of the authorization code by the issuer. Prompt your customer to enter a valid value based on our documented validations. The addition of restrictions in your checkout page will also assist in preventing this scenario.

A defect is causing the

consumerAuthenticationInformation.token

field to be returned in the

processorInformation

object instead of the

consumerAuthentication

object.

Merchants using the REST API.

None.

None.

When an invoice has been partially paid at least once, the remaining balance provided within the webhook response might not return a correct value.

Merchants using invoicing.

None.

Real-time data is available in the Business Center's Invoicing and Reporting pages to help you track the payment status of orders processed using invoicing.

Merchants using digital payments such as Apple Pay and Google Pay, in conjunction with Discover or Diners Club cards will see the following error:

DINVALIDDATA "Unsupported ECI type. e_commerce_indicator=DIPB"

.

Merchants processing Discover or Diners Club card transactions using Vantiv on Visa Platform Connect.

Our implementation with Vantiv is preventing the usage of the

e_commerce_indicator

value

dipb

, indicating the passing of a cryptogram from an authenticated transaction.

You can replace the value

dipb

with the value

internet

to bypass the current validation. However, you risk losing the liability shift and incurring increased rejections downstream.

The API testing trigger 5001.00, which tests AVS response codes, is not producing the correct responses for Discover cards.

Global.

The test amount of 5001.00 should trigger a processor response of

processorInformation.avs.code=Y

. Instead, it is returning

processorInformation.avs.code=A

.

None.

Some users logging into the Business Center's testing environment are not receiving the One-Time Password if it is sent using SMS.

Users of the Business Center's testing environment.

None.

You can use email instead of SMS.

When you use the REST API

GET reporting/v3/reports

request to query the

reportName

parameter, and the length of the report name is too long, the affected report is not returned in the response.

Users of the Reporting REST API.

None.

Merchants can omit the

reportName

query parameter in the API call or recreate the report with a shorter name.

Resellers are currently unable to enable Secure Acceptance for new merchant accounts.

Resellers.

None.

None.

An intermittent error sometimes prevents transactions from being recorded in the Business Center even though a response was received by the merchants. In some cases, this can result in the cardholder being charged twice.

Merchants using the Cielo and Rede processors in Latin America.

None.

None.

Some resellers are experiencing slow loading or timeouts in the Business Center's testing environment when using the Transaction Search and Transaction Details pages.

Resellers.

None.

None.