Selective 3D Secure and 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:

Value Description
missing or empty or 0
  • 3DS1: Forced 3DS1 authentication.
  • 3DS2: Strong authentication (Challenge) is requested.
1 Deprecated.
2
  • 3DS1: Disabled 3DS1 authentication. Requires the “Selective 3DS1” option.

    By using this value, you expose yourself to “Soft decline” refusals.

    If the store does not have the “Selective 3DS1” function, 3DS1 authentication is forced.

  • 3DS2: Allows to request authentication without interaction (frictionless). Requires the “Frictionless 3DS2” option.
    • For payments made in euro, if the amount is lower than €30, a request for frictionless is transmitted to the DS. If the frictionless request is accepted by the issuer, the merchant loses the payment guarantee.

    • For payments made in euros, if the amount is greater than €30, the value transmitted by the merchant is ignored and strong authentication (Challenge) is requested.

    • For payments made in a currency other than euro, a request for frictionless is transmitted to the DS.

    If the store does not have the "Frictionless 3DS2” option, strong authentication (Challenge) is requested.

3
  • 3DS1: Forced 3DS1 authentication.
  • 3DS2: CHALLENGE REQUESTED: 3DS Requestor Preference Allows to request strong authentication for the transaction.
4
  • 3DS1: Forced 3DS1 authentication.
  • 3DS2: CHALLENGE REQUESTED: mandate Allows to indicate that, due to regulatory reasons, strong authentication is required for the transaction.
5
  • 3DS1: Forced 3DS1 authentication.
  • 3DS2: NO PREFERENCE: 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.