The 3DS V2 protocol supports 150 data points transmitted to the issuer. However, the processing of data by issuers may take time, so it is recommended to send some essential data to the issuer in order to benefit of frictionless payment.
In a payment request, the merchant must submit the following data:
To encourage frictionless payments, the merchant can :
Some additional data are strongly recommended to improve the issuer’s risk analysis of the transaction:
The following JSON objects may be added to requests for payment:
The recommended data are as follows:
Note: All data will be used to secure the on-line route with a view to combating fraud. Issuing banks are regulated on the management of these confidential data.
With or without these additionnal data, the payement request is flagged as 'no preference'. In this case, if the payment is frictionless, the liability shift to the issuing bank applies. For more details : Liability shift and 3DS Matrix |
The JSON object threeDSPolicy EN allows the merchant to indicate his request of a frictionless payment
The parameter challengePreference indicates the merchant’s preference for authentication:
In all cases, the final choice is defined by the issuing bank (cardholder's bank).
Example : Request frictionless payment
{ "challengePreference": "noChallenge" } |
The liability shift to the cardholder bank (issuer) is based on the card brand and the merchant request for the authentication mode. For more details : Liability shift and 3DS Matrix |
The JSON obect threeDSPolicy EN allows the merchant to request an exemption.
The parameter threeDSExemption – exemptionReason indicates the exemption wished by the merchant :
In all cases, the final choice is defined by the issuing bank (cardholder's bank).
Example: Low amount exemption
{ "threeDSExemption": { "exemptionReason": "lowValue" } } |
The liability shift to the cardholder bank (issuer) is based on the card brand and the merchant request for the authentication mode. For more details : Liability shift and 3DS Matrix |