3D Secure 2 — the most common questions
3D Secure 2.0 is the main online card payment authentication solution that will make you stay compliant with PSD2 requirements. If you’re still not sure how new requirements can impact your business or how to implement changes, here are the answers to the most frequently asked questions.
Do I have to add 3D Secure 2.0 to a payment process on my website?
Please note that strong customer authentication (SCA) is part of the PSD2 — the regulation that comes into effect on 14 September 2019. The 3D Secure 2 will make you stay compliant with the directive as it is considered the main method of authenticating online card payments.
This is why we strongly recommend enabling our non-invasive 3D Secure in order to stay compliant with new regulations. If you still don’t have 3DS enabled, please contact our support team.
What are the differences between 3DS 1.0 and 2.0?
- stronger authentication — static passwords will be replaced with tokens and biometric
- enhanced customer experience
- better conversion thanks to reducing friction in the transaction process
- support for mobile clients.
For more details on the differences read one of our past blog posts: 3D Secure 2.0 specifications in a nutshell.
What may happen if I don’t use 3D Secure authentication?
- transaction declines
- a massive drop in conversion
- checkout friction and poor customer experience
- increased risk of cart abandonment.
How does SecurionPay support 3DS2?
If any action is required, you will be notified immediately.
What should I do to activate 3D Secure 2?
If you don’t have our non-invasive 3D Secure implemented, follow the instructions.
If you’re using SecurionPay Checkout, you need to implement the 3D Secure method into your Checkout Request object. Find out more details in the documentation (threeDSecure object).
Do I have to apply 3DS 2.0 if my customers are not from the EU?
Will 3DS2 affect user experience on my website?
Do I have to apply 3DS to all my recurring payments?
As most subscription-based payments are perceived as merchant initiated, they are out of the SCA scope, but it’s still up to the bank whether the transaction needs to be authenticated or not.
Are there any exemptions from 3DS2?
Latest posts by Sandra Wróbel-Konior (see all)
- Dating Merchant Account and Payment Gateway — All You Need to Know - December 16, 2019
- High-Risk Merchant Account — What it is and How it Works - November 14, 2019
- Reasons why Customers File Chargebacks - October 23, 2019