Transaction with successful frictionless authentication
- The issuer has received a choice of "No
Preference" or "Challenge Requested". They assessed the transaction risk and decided that an authentication without interaction was sufficient.
- Overview :
The payment method is enrolled 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 Liability shift section is set to Yes. Thus, in the event of fraud, the merchant will not be charged.
- Authentification :
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 liability shift.
- 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: 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 data:
- Proof of authentication: sensitive data (CAVV, AEVV or AAV) that proves cardholder authentication by the ACS is present and masked.
- E-commerce indicator: 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 this example, 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.
- Overview :
- 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 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 Liability shift section is set to No. Thus, in the event of buyer fraud, the merchant will not be charged.
- Authentification :
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 has requested by the merchant and the request has been 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 liability shift.
- 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: 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 this example, 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 this example, 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.
- Overview:
- 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 (Strong Customer Authentication);
- Another exemption received from the DS.