Common Error Responses for Transactions without 3-D Secure {#googpay-auth-dw-no-3ds-errors}
===========================================================================================

This topic lists common error responses to transaction requests without 3-D Secure authentication.

3DS ECI provided for non-3DS transaction
:
Cause: Invalid e-commerce indicator for a transaction that does not use 3-D Secure.
:
Resolution: Make sure the processingInformation.commerceIndicator field is set to `internet` to indicate a transaction without 3-D Secure authentication. You could also omit the field from your request and let the gateway assign the value.

Authentication data present in non-3DS transaction
:
Cause: Conflicting authentication data.
:
Resolution: Remove the cardholder authentication data, which is used for transactions with 3-D Secure:

    * Remove the consumerAuthenticationInformation. cavv field (for Diners Club or Visa cards).
    * Remove the consumerAuthenticationInformation. ucafAuthenticationData field (for Mastercard only).

Digital wallet transaction missing required cryptogram
:
Cause: Missing or invalid cryptogram.
:
Resolution: Make sure the paymentInformation.tokenizedCard.cryptogram field is populated with the correct value.