3DS2 Payments
Support 3D Secure 2 (3DS2) authentication for SCA-compliant card payments across NEXT's supported gateways, on storefront checkout and the Admin API.
3D Secure 2 Payments
3D-Secure v2 (3DS2) payments are fully supported in Next Commerce, both via the storefront checkout and for transactions created over the Admin API.
For EU-based merchants, or merchants selling to EU-based customers, Strong Customer Authentication (SCA) is mandated under the PSD2 directive for payment card transactions. 3DS2 offers a low or no-friction method to achieve SCA compliance on your store's transactions.
3DS2 authentication is supported on Next Commerce for the following gateways:
| Gateway | |
|---|---|
| NEXT Payments | Checkout.com |
| Adyen | NMI |
| Airwallex | Nuvei |
| BlueSnap | Stripe Payment Intents |
| Braintree | Test Gateway |
To support 3DS2 payments over the Admin API, see the Developers Guide
3DS Mode
Go to Settings > Payments, choose your gateway, and pick a 3DS Mode on the 3DS card.
| Mode | What it does |
|---|---|
| Off | Transactions are processed without 3DS. |
| Smart | Skips 3DS in the United States, Canada, Australia and New Zealand, unless the order is higher risk. All other orders use 3DS. |
| Always On | Every transaction uses 3DS. |
Smart Mode
Smart mode lets one gateway serve markets where 3DS is required and markets where it mostly adds friction. It decides per order from the billing address country.
| Billing country | Result |
|---|---|
| United States, Canada, Australia, New Zealand | Charged without 3DS. Orders above your risk tolerance are charged with 3DS and must complete the challenge, unless they score above 90, which are declined. |
| Any other country | Charged with 3DS, unless Optimized 3DS2 skips the challenge |
Smart mode uses the billing address country, not the card's issuing country. Orders charged without 3DS carry no liability shift.
3DS and Risk Screening
Risk Screening works with your 3DS Mode:
- Off: orders above your risk tolerance are declined.
- Smart or Always On: orders above your risk tolerance are charged with 3DS and must complete the challenge, unless they score above 90, which are declined.
- Orders that always use 3DS (every Always On order, and Smart orders outside the four countries above) are not risk screened unless Optimized 3DS2 is on. The 3DS challenge protects them instead.
3DS2 Merchant Profiles
Gateways that use a 3DS Merchant Profile need one before Smart or Always On can authenticate. NEXT Payments is configured for you, and Stripe Payment Intents uses Stripe's own 3DS, so neither needs one.
Enter the following values, most of which come from your processing provider or acquiring bank.
| Field | Description |
|---|---|
| Merchant Name | The merchant name assigned by your acquiring bank |
| Merchant Country | The country your business is registered in |
| Acquirer BIN | The acquiring BIN (ABIN) issued for that card network |
| Merchant ID (MID) | The merchant ID issued for that card network |
| MCC Code | Your merchant category code |
Acquirer BIN, Merchant ID, and MCC Code are entered per card network: Visa, Mastercard, AMEX, and Discover. Choose Save.
Each card network is optional. For example, entering Visa values but not Mastercard values applies 3DS to Visa transactions and processes Mastercard transactions without 3DS.
Optimized 3DS2
Choose Enable Optimized 3D Secure Transactions under Smart or Always On to skip 3DS challenges. When the card's issuing bank asks for a challenge, the transaction is charged without 3DS instead. Frictionless authentications still pass as 3DS.
Optimized 3DS2 needs a 3DS Merchant Profile and a merchant account that accepts both 3DS and non-3DS transactions. Higher risk orders always show the challenge.
Transactions charged without 3DS carry no liability shift, and card issuers in the EU and UK may decline them. With Smart mode you don't need Optimized 3DS2 to avoid 3DS in the United States, Canada, Australia and New Zealand.
Retry Non-3DS Enrolled Cards
You may optionally choose to automatically Retry Non-3DS Enrolled Cards as Standard Transaction to gracefully re-attempt any transactions on cardholders which do not support 3DS payments. Note that this setting should only be used with merchant accounts that support both 3DS and non-3DS transactions.