MySagePay
Login >
 
0191 313 0300

3D Secure v2 - What Do Customers Need to Do?

The first thing is to ensure your ecommerce payments have 3D Secure activated within MySagePay (if not already activated). You can find out how to do this on page 8 of our MySagePay User Guide 

Depending on which payment integration your site uses with Opayo you may have to make some changes to the integration, so it is important to flag with your developer/IT that you may need to make some development changes ahead of time to ensure they will be ready to act for you.  

Opayo has minimised the impact that this mandated change will have on you and your customers, keeping your business compliant for ecommerce transactions within the EEA. We recommend you update to Protocol 4. Below you can find out if you need to make any changes to your integration:

  1. Form integration – There will be no mandatory changes to your current integration. Simply activate 3D Secure within MySagePay. To do this click on the Settings tab, followed by 3D secure. You will then be able to activate the 3D secure scheme. If you are using Custom Templates you will need to update your templates to take advantage of 3DSv2 - kits can be downloaded here

  2. Server integration – There will be no mandatory changes to your current integration. Simply activate 3D Secure within MySagePay. To do this click on the Settings tab, followed by 3D secure. You will then be able to activate the 3D secure scheme. If you are using Custom Templates you will need to update your templates to take advantage of 3DSv2 - kits can be downloaded here

  3. Direct integration – Minimal impact, the 3DSv2 flow will be the same as the current 3DSv1 flow, however, an additional 9 fields will be required. Please refer to the parameters in the table you can find here.

  4. Pi integration - Minimal impact, the 3DSv2 flow will be the same as the current 3DSv1 flow, however, an additional 8 fields will be required. Please refer to the parameters in the table you can find here.

All Integrations - Since 3DSv2 is mandated, you will no longer be able to bypass the checks by submitting the ‘Apply3DSecure’ field with a value of ‘2’ for Form, Server or Direct. You will need to change this value to ‘0’ or use one of the other permitted values (1 or 3). This is only likely if you have a bespoke Opayo integration with your website, but your web developer will be able to tell you if this is the case. If you have integrated using Pi, you will need to pass ‘UseMSPSetting‘ or one of the other permitted values (‘Force‘ or ‘ForceIgnoringRules‘).

If you don’t know which integration your website uses, you can find this in MySagePay by clicking on any successful payment, then choose ‘Additional Details’ from the left menu. You will see the integration in the ‘System Used’ field.

Next Steps

  1. Enrolment - Opayo will enrol your MID/Merchant Number for both 3DSv1 and 3DSv2 if not already done. 

  2. Activation- You will need to activate 3D Secure from within MySagePay. If you have not already activated 3D Secure, please find the instructions to do so here. If you are using our PI or Direct integration you will also need to include the 3D Secure steps of the integration.

  3. Enablement- We will check all accounts and enable 3D Secure shortly before the deadline on September 14th 2021. If 3D Secure is not already enabled, we will email you to let you know and then we will activate 3D Secure automatically. To avoid disruption to your payment processing we strongly recommend you activate 3D Secure within My Sage Pay before September, the sooner the better.

  4. Technical Update – If you use our Direct integration - then you’ll need to undertake some additional development and upgrade to Protocol 4.00 before activating 3D Secure. Direct Documentation is available here If you use our Pi integration – then you’ll need to undertake additional work to your Pi integration. Pi Documentation is available here.

  5. Test your Changes - Our 3DSv2 test and live environments are available to developers and merchants to begin testing their integration and optimising 3DSv2 checkout flows