What is 3D Security?
3D authentication is a protocol used for online card payments that provides an extra layer of security. It requires cardholders to enter an additional password or authentication code before their payment can be processed. By using 3D authentication with Total Processing, you can offer your customers a secure and seamless payment experience, ensuring that their transactions are safe and fraud-free. Get an in-depth understanding of 3D authentication below!
Using your own external MPI? Reach out to support@totalprocessing.com to get this set up!
3D version 2.0 authentication Most recent
3D Secure version 2 (3DS2) is the latest version of the 3D Secure protocol, offering a more secure and seamless payment experience for both customers and merchants. 3DS2 uses advanced authentication methods, such as biometric data, and allows for seamless integration with merchants' systems, making it future-proof and scalable to new payment technologies.
I'm operating in a non-3DS2 required country. Why should I use 3DV2?
In addition to increased security, implementing 3D version 2.0 methods also allows for 'Liability Shift'. Liability shift is a way for merchants to protect themselves from being held responsible for a fraudulent transaction made with a stolen credit or debit card.
3D version 1.0 Outdated
The first version of the 3D Secure protocol, 3DV1, required customers to verify their identity using a password or other authentication method before completing a transaction. However, 3DV1 has been discontinued in favor of newer, more secure protocols such as 3DV2, which uses more advanced authentication methods, like biometric data, and allows for seamless integration with merchants' systems.
How do they compare?
Feature | 3DS2 | 3DS1 |
---|---|---|
Authentication methods | Multiple authentication methods such as biometric, one-time passcode and FIDO. | Only static password or PIN |
Frictionless authentication | Supports risk-based authentication for seamless checkout experiences. | Not available |
Scalability | Designed to be future-proof and scalable to new payment technologies such as mobile wallets and IoT devices. | Not scalable to new payment technologies |
Support for merchants | Designed to provide additional data to merchants for better fraud prevention and risk management. | Not designed for merchant support |
Flexibility | Offers more customisation options to merchants, including different authentication flows based on risk levels and transaction values. | Less flexible in terms of customisation |
PSD2 & Strong Customer Authentication
3DS2 works alongside Strong Customer Authentication (SCA), a requirement under the European Union's Second Payment Services Directive (PSD2) for certain online payment transactions. SCA requires that customers provide two or more independent authentication factors when making a payment online, such as something they know, have and are.
3DS2 and SCA provide a robust and secure system for online payment transactions, ensuring that customer payment information is protected, reducing the risk of fraud. By adopting 3DS2 and SCA, merchants and financial institutions can provide a seamless and secure payment experience for their customers.
3D version 2.0 mandated countries
Country | 3D version 2 required |
---|---|
Poland | Yes |
Malta | Yes |
Romania | Yes |
Portugal | Yes |
Luxembourg | Yes |
Lithuania | Yes |
Liechtenstein | Yes |
Slovenia | Yes |
Slovakia | Yes |
Latvia | Yes |
Ireland | Yes |
Iceland | Yes |
France | Yes |
Germany | Yes |
Italy | Yes |
Hungary | Yes |
Spain | Yes |
Croatia | Yes |
Republic of Cyprus | Yes |
Bulgaria | Yes |
Czech Republic | Yes |
United Kingdom | Yes |
Monaco | Yes |
Finland | Yes |
Norway | Yes |
Estonia | Yes |
Sweden | Yes |
Denmark | Yes |
Austria | Yes |
Belgium | Yes |
Netherlands | Yes |