End of Support for 3D Secure 1
Online payment card processing requirements have changed in the European Economic Area (EEA) and the UK. Now, these regions enforce Strong Customer Authentication requirements under the Payment Services Directive (PSD2).
To meet Strong Customer Authentication requirements, first-generation 3D Secure (3D Secure 1 or 3DS 1.x) is being replaced by newer 3D Secure 2 (also called 3DS 2.x, EMV 3-D Secure, or EMV 3DS).
Support for 3D Secure 1 ended on October 15, 2022. If you keep using 3D Secure 1 for your Site Builder or SuiteCommerce web store, your card payments may fail or get declined. To avoid this, switch to 3D Secure 2. See Migrating from 3D Secure 1 to 3D Secure 2.
To reduce declined transactions and comply with Strong Customer Authentication rules, make sure:
-
Your web store’s checkout or payment forms support 3D Secure 2 challenges.
-
Your payment gateways and NetSuite integrations handle the 3D Secure 2 cardholder challenge for you.
If your payment gateway partner doesn’t support 3D Secure 2, select a new partner. For a list of partners that do, see Payment Gateway Support for 3D Secure 2.
To set up a new payment processing profile for your new payment gateway, see the Order Management topic Creating Payment Processing Profiles.
-
The issuer of the payment card and the payment gateway both support 3D Secure 2.
Migrating from 3D Secure 1 to 3D Secure 2
Migrate your website to SuiteCommerce or the latest version of SuiteCommerce Advanced (SCA) and use a gateway that provides native 3D Secure 2 support. However, if you can’t migrate your website to SuiteCommerce or the latest SCA version, take these actions:
|
Product |
Version |
Native Support for 3D Secure 2 |
External Checkout Supported |
External Support for 3D Secure 2 |
Action You Should Take |
|---|---|---|---|---|---|
|
Site Builder |
All |
No |
No |
No |
Install SiteBuilder Extensions Kilimanjaro (bundle 194218) or SiteBuilder Extensions Premium Kilimanjaro (bundle 194219) and use the external checkout feature. See Installing a Bundle. The following patches are required for external checkout to work with SiteBuilder Extensions Kilimanjaro and SiteBuilder Extensions Premium Kilimanjaro:
Change your Proceed to Checkout touchpoint on your website setup record to point to the SiteBuilder Extensions SSP. See Select Supported Touch Points. Since this SSP replaces your website’s existing checkout, you’ll need to set up your new checkout to fit your business needs, and you might need a developer to transfer any code-level customizations from your old checkout. |
|
Site Builder with Reference Checkout |
All |
No |
No |
No |
Install SiteBuilder Extensions Kilimanjaro (bundle 194218) or SiteBuilder Extensions Premium Kilimanjaro (bundle 194219) and use the external checkout feature. See Installing a Bundle. The following patches are required for external checkout to work with SiteBuilder Extensions Kilimanjaro and SiteBuilder Extensions Premium Kilimanjaro:
Change the Proceed to Checkout touchpoint on your website setup record to point to the SiteBuilder Extensions SSP. See Select Supported Touch Points. Because this SSP replaces your website’s existing checkout, you need to follow procedures to set up your new checkout to meet your business’s requirements. You may also need a developer to transfer any code-level customizations that are being used in your old checkout. |
|
Site Builder with SiteBuilder Extensions |
All |
No |
Partial |
No |
Use the external checkout feature. 3D Secure 2 support depends on your checkout version. Install SiteBuilder Extensions Kilimanjaro (bundle 194218) or SiteBuilder Extensions Premium Kilimanjaro (bundle 194219). The following patches are required for external checkout to work with SiteBuilder Extensions Kilimanjaro and SiteBuilder Extensions Premium Kilimanjaro:
If you haven’t already, change your Proceed to Checkout touchpoint on your website setup record to point to the SiteBuilder Extensions SSP. See Select Supported Touch Points. Since this SSP replaces your website’s existing checkout, you’ll need to set up your new checkout to fit your business needs, and you might need a developer to transfer any code-level customizations from your old checkout. |
|
SuiteCommerce |
— |
Yes |
Yes |
Yes |
Use native 3D Secure or external checkout. |
|
SuiteCommerce MyAccount |
— |
Yes |
Yes, except for Windcave |
Yes |
Use native 3D Secure or external checkout. |
|
SCA— Includes My Account checkout |
Denali Mont Blanc |
No |
Partial |
Partial |
Use external checkout. Support for external checkout was introduced in the Mont Blanc release of SCA and a patch was developed to backport it to the Denali release. |
|
Vinson Elbrus |
No |
Yes |
Yes |
Use external checkout. The following patches are required for external checkout to work:
|
|
|
Kilimanjaro Aconcagua 2018.2 |
No |
Yes |
Yes |
Use external checkout. You'll need the Domain Bridging Update patch for external checkout to work on Kilimanjaro implementations. The following patches are required for external checkout to work with SCA Kilimanjaro and SCA 2018.2: |
|
|
2019.1 2019.2 |
No |
Yes |
Yes |
Use external checkout. |
|
|
2020.1 and later |
Yes |
Yes |
Yes |
Use native 3D Secure or external checkout. You might need patches to use native 3D Secure 2 with pre-2021.2 SCA releases. SCA 2020.1.8 and 2020.1.12 included minor fixes for 3D Secure 2. The following patches are required for external checkout to work with SCA 2020.1, SCA 2020.1.12, 2021.2, and SCA 2021.2.3: |