{"title":"3D Secure 1 and 2 redirect authentication","category":"default","creationDate":1692966000,"content":"
\n

Adyen is no longer developing the Classic API integration<\/strong><\/p>\n

This page is for the Classic API (\/authorise<\/code>) integration, which we no longer accept new integrations with. <\/p>\n

We strongly recommend migrating to the newer 3D Secure redirect authentication on Checkout API<\/a> integration. To use this newer integration, you must also migrate to the Checkout API<\/a>.<\/p>\n<\/div><\/div>\n

3D Secure<\/a>\u00a0is a protocol\u00a0provided by credit card schemes. It is an additional authentication protocol that allows you to implement another layer of security on your Card-Not-Present<\/a> transactions.<\/p>\n

During a 3D Secure transaction, the shopper is redirected to a site controlled by the issuing bank\u00a0to answer additional security questions (usually a unique password or SMS verification).\u00a0This reduces the chance of a fraudulent transaction\u00a0occurring.<\/p>\n

When 3D Secure is used for personal cards, the\u00a0chargeback liability shifts to the issuing banks.<\/p>\n

\n

While this liability shift is appealing, there is a significant risk of a lower conversion rate when you use 3D Secure. This is because many shoppers are still not familiar with 3D Secure, so may not pass the verification process. Client-side technical errors may also occur when they are redirected.<\/p>\n

Adyen has developed a robust dynamic 3D Secure system. This lets you choose which transactions are sent for 3D Secure authentication, and which are processed without. For more information, read Dynamic 3D Secure<\/a>.<\/p>\n<\/div><\/div>\n

Managing PSD2 SCA compliance with 3D Secure<\/h2>\n

If you are implementing 3D Secure to handle PSD2 compliance, your options are to:<\/p>\n

    \n
  1. Let Adyen handle PSD2 compliance by default<\/a>.<\/li>\n
  2. Configure rules using Dynamic 3D Secure<\/a>.<\/li>\n
  3. Submit your preference for each transaction in your API request<\/a>.<\/li>\n<\/ol>\n

    In this integration guide, we talk about the steps on how you can submit 3D Secure requests for options 1 and 2.<\/p>\n

    If you want to use option 3 to send your preference for each transaction in your API request, you will need to submit additional fields<\/a>. However, note that option 3 overrides our default PSD2 compliance handling logic, including checking if the transaction is out of scope, determining the most suitable exemption type to request for, and evaluating whether to send the exemption in the authentication or authorisation request.<\/p>\n

    We recommend using option 3 only if you have an extensive knowledge of PSD2 SCA regulations and the 3D Secure protocol.<\/p>\n

    Requirements<\/h2>\n

    Before you begin to integrate, make sure you have followed the Get started with Adyen guide<\/a> to:<\/p>\n