End of Support for 3D Secure 1
Online payment card processing requirements have changed in the European Economic Area (EEA) and the UK. Now, EEA countries and the UK are enforcing the Strong Customer Authentication requirements of the Payment Services Directive (PSD2).
To comply with the Strong Customer Authentication requirements, first-generation 3D Secure technologies (3D Secure 1 or 3DS 1.x) are being replaced with newer technologies referred to as 3D Secure 2 (also known as 3DS 2.x, EMV 3-D Secure, and EMV 3DS).
Support for 3D Secure 1 ended on October 15, 2022. Continuing to rely on 3D Secure 1 for your Site Builder or SuiteCommerce web store can result in failed or declined payment card transactions. To minimize payment card transaction failures on your web store, use 3D Secure 2 instead of 3D Secure 1. See Migrating from 3D Secure 1 to 3D Secure 2.
To minimize declined transactions and to comply with the Strong Customer Authentication requirements, verify the following:
-
Your web store’s checkout or payment forms support 3D Secure 2 challenges.
-
Payment gateways and integrations between NetSuite and the gateway support the 3D Secure 2 cardholder challenge on your behalf.
If your payment gateway partner does not support 3D Secure 2, select a new partner. For a list of payment gateway partners who support 3D Secure 2, see Payment Gateway Support for 3D Secure 2.
To set up a new payment processing profile with your new payment gateway partner, 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 cannot migrate your website to SuiteCommerce or the latest version of SCA, take the following 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 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 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 the checkout version. You should 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 have not done do, 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. |
|
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. The Domain Bridging Update patch is required 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. Patches may be required to use native 3D Secure 2 with pre-2021.2 releases of SCA. 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: |