Transaction with successful frictionless authentication

Two cases for a transaction with successful frictionless authentication:
  1. The issuer has received a “No Preference” or “Challenge Requested” preference. However, they assessed the transaction risk and decided that an authentication without interaction was sufficient.
    • Overview

      The payment method is enrolled in 3D Secure and the buyer has authenticated him or herself correctly on his or her bank’s authentication page (ACS).

      The absence of a red exclamation mark in the various tabs indicates that the payment was successful.

      The Payment guarantee section is set to Yes. Thus, in the event of fraud, the merchant will not be charged.

    • Authentication

      The DS network responsible for the security is presented.

      The payment method BIN supports the v2 3D Secure protocol.

      The v2 3D Secure protocol is also supported by the acquirer.

      Authentication without cardholder interaction (frictionless) was granted by the bank but not requested by the merchant.

      The transaction benefits from payment guarantee.

    • Authentication data

      Proof of authentication: sensitive data (CAVV, AEVV or AAV) that proves cardholder authentication by the ACS is present and masked.

      E-commerce indicator: shows that the buyer has correctly authenticated him or herself. The 05 value indicates successful authentication for CB, VISA and AMEX. The 02 value indicates successful authentication for MasterCard.

      Merchant preference: the No preference value indicates that the merchant has not chosen the authentication method.

    • Authentication details

      Proof of authentication: sensitive data (CAVV, AEVV or AAV) that proves cardholder authentication by the ACS is present and masked.

      E-commerce indicator: shows that the buyer has correctly authenticated him or herself. The 05 value indicates successful authentication for CB, VISA and AMEX. The 02 value indicates successful authentication for MasterCard.

      Merchant preference: the No preference value indicates that the merchant has not chosen the authentication method.

      Reason for exemption: The reason for authentication without bearer interaction.

      In our case, the reason is transmitted by the issuer. View the exemption list.

    • Authentication details

      The detailed timeline of the events is displayed for better traceability in case technical assistance is required.

  2. The merchant has the “Frictionless 3DS2” option and has requested authentication without cardholder interaction. The card issuer has accepted the request.
    • Overview

      The payment method is enrolled in 3D Secure and the buyer has authenticated him or herself correctly on his or her bank’s authentication page (ACS).

      The absence of a red exclamation mark in the various tabs indicates that the payment was successful.

      The Payment guarantee section is set to No. Thus, in the event of buyer fraud, the merchant will not be charged.

    • Authentication

      The DS network responsible for the security is presented.

      The payment method BIN supports the v2 3D Secure protocol.

      The v2 3D Secure protocol is also supported by the acquirer.

      An authentication without cardholder interaction was requested by the merchant and the request was accepted by the bank. This authentication mode is valid in 3DS2 for an amount in euro lower than €30.

      The transaction does not benefit from payment guarantee.

    • Authentication data

      Proof of authentication: sensitive data (CAVV, AEVV or AAV) that proves cardholder authentication by the ACS is present and masked.

      E-commerce indicator: shows that the buyer has correctly authenticated him or herself. The 05 value indicates successful authentication for CB, VISA and AMEX. The 02 value indicates successful authentication for MasterCard.

      Merchant preference: In our case, the merchant requested authentication without interaction with the bearer. Based on the store’s options and the characteristics of the transaction, the gateway transmitted the request to the issuer.

      Reason for exemption: The reason for authentication without bearer interaction.

      In our case, the reason is transmitted by the payment gateway. View the exemption list.

    • Authentication details

      The detailed timeline of the events is displayed for better traceability in case technical assistance is required.

Exemption list:
  • Risk analysis by the issuer
  • Risk analysis by the acquirer
  • Strong authentication delegated to a third party
  • Low value transaction
  • Fixed recurring payments with a fixed term
  • The merchant participates in CB’s Low Risk Merchant Program
  • Other exemption cases
  • A technical error prevents cardholder authentication
  • Trusted beneficiaries
  • Payment devices
  • Payment by corporate card
  • Transaction not concerned by the SCA
  • Another exemption received from the DS