• France
status page
demonstrations
assistance
FAQContact support
Search
Categories
Tags
English
French
English
Homepage
Use cases
Create a payment
Create an installment payment
Create a multi-card (split) payment
Create a payment by Alias (Token)
Create a payment link
Create a recurring payment
Manage subscriptions
Manage your transactions (refund, cancel...)
Analyze your reports
API docs
Embedded Form
REST API
Hosted payment
Mobile payment
File exchange
Snippets
Payment methods
Plugins
Guides
Merchant Back Office
Functional guides

Transmitting merchant preferences

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: The choice of the preference is transferred to the card issuer (No Preference).
1 Deprecated.
2
  • 3DS1: Disabled 3DS1 authentication. Depreciated

    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 issuer. If the frictionless request is accepted, the transaction does not benefit from liability shift in case of chargeback.
    • For payments made in euro, if the amount is higher than €30, the value transmitted by the merchant is ignored and the choice of the preference is transferred to the card issuer (No Preference).
    • For payments made in a currency other than euro, a request for frictionless is transmitted to the issuer. If the frictionless request is accepted, the transaction does not benefit from liability shift in case of chargeback.

    If the store does not have the “Frictionless 3DS2” option, the choice of the preference is transferred to the card issuer (No Preference).

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.
© 2025 {'|'} All rights reserved to Sogecommerce
25.18-1.11