Merchant preference
The merchant can express their choice concerning strong buyer authentication using the vads_threeds_mpi 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:
| Use case | Values | Description |
|---|---|---|
| CHALLENGE: with cardholder interaction | 1 | Deprecated. |
| 3 | 3DS Requestor Preference: Allows to request strong authentication for the transaction. | |
| 4 | Challenge request mandate: Allows to indicate that, due to regulatory reasons, strong authentication is required for the transaction. | |
| No merchant preference | 0 or absent or empty | The choice of the preference is transferred to the card issuer. If the issuer decides to perform an authentication without interaction (frictionless), the payment will be guaranteed. |
| 5 |