Introducing 3D Secure 2
Under no circumstances should merchants store or log any credit card details unless they are fully PCI-DSS compliant. This falls under your responsibility to ensure you do not produce code which circumvents our toolkits. We do not accept any liability for this.
3D Secure 2.0 (also known as EMV 3DS) is a new version of 3D Secure 1. 3D Secure 2.0 aiming to improve the security and consumer experience, including helping merchants achieve Strong Customer Authentication (SCA) compliance under PSD2.
The Payment Services Directive (PSD2), has introduced a new regulatory requirement: Strong Customer Authentication (SCA), with the aim to add an increased layer of security for card not present transactions, when making mobile and online payments.
What is Strong Customer Authentication?
For more information, see What is Strong Customer Authentication
3D Secure 2 Flow.
For more information, see 3D Secure 2 Payment Flow
Integration Steps.
For the integration steps, see Integration Steps.
NOTE! Use Judopay’s Web SDK for an even simpler integration.
Exemptions to SCA.
Merchants can request specific customer initiated transactions be exempt. For more information, see Exemptions to SCA
Liability Shift.
The 3D Secure liability shift is a rule protecting you from fraudulent transactions. For more information, see Liability Shift
3D Secure 2 Best Practices.
Read more on how to keep your online payments secure 3D Secure 2 Best Practices