Selective 3D Secure and merchant preference
The merchant can express their choice concerning strong buyer authentication using the strongAuthentication field.
The value transmitted in the payment request has priority over the risk rules potentially defined by the merchant in their Merchant Back Office.
Here is how to use it:
|VALUE||3DS1 card||3DS2 card|
|ENABLED||Enables (if possible) strong authentication.||Deprecated. This value will be interpreted as CHALLENGE_REQUESTED.|
Disables (if possible) strong authentication. Requires the “Selective 3DS1” option.
The deactivation will not be taken into account if the payment method requires mandatory strong authentication. This is the case of MAESTRO cards.
Allows to request authentication without interaction (frictionless). Requires the “Frictionless 3DS2” option.
If the store does not have the “Frictionless 3DS2” option, strong authentication (Challenge) is requested.
|CHALLENGE_REQUESTED||Enables (if possible) strong authentication.||Allows to request strong authentication for the transaction.|
|CHALLENGE_MANDATE||Enables (if possible) strong authentication.||Allows to indicate that, due to regulatory reasons, strong authentication is required for the transaction.|
|NO_PREFERENCE||Enables (if possible) strong authentication.||Allows to indicate to the DS that the merchant does not have a preference. If the issuer decides to perform an authentication without interaction (frictionless), the payment will be guaranteed.|
|AUTO||Default value. Management of 3DS authentication delegated to the payment gateway (domain, provider, shop configuration).||Default value.
Strong authentication (Challenge) is requested.