{"title":"Browser-based integration","category":"default","creationDate":1776961627,"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 Native 3D Secure 2 on Checkout API<\/a> integration. To use this newer integration, you must also migrate to the Checkout API<\/a>.<\/p>\n<\/div><\/div>\n

How it works<\/h2>\n

In a full implementation, a payment eligible for 3D Secure 2 can go through either a frictionless or a challenge authentication flow before the payment is authorised.\u00a0To support both flows, you need to\u00a0build your own client-side and server-side implementation, with the option of using our\u00a0helper functions<\/a>.<\/p>\n

If you only want to perform a 3D Secure 2 authentication and then authorise the payment later, see the Authentication-only<\/a> integration page.<\/p>\n

\n

The use of helper functions replaces the Web 3D Secure 2 SDK implementation. If you are currently using Web 3D Secure 2 SDK and require assistance, contact\u00a0Support Team<\/a>.<\/p>\n<\/div><\/div>\n

Here's a diagram for a 3D Secure 2 browser-based full implementation:<\/p>\n

\"\"<\/p>\n

    \n
  1. Submit a payment request<\/a>\u00a0with the required 3D Secure 2 objects to start the authentication process.\u00a0Build your implementation depending on the\u00a0resultCode<\/code>\u00a0returned in the response.<\/li>\n
  2. Get the 3D Secure device fingerprint<\/a>. If you receive an\u00a0IdentifyShopper<\/strong> resultCode<\/code>, you need to get the shopper's 3D Secure 2 device fingerprint. Create an iframe on the browser, send a device fingerprint request to the issuer, and then send the result to Adyen. If you get a response with an\u00a0Authorised<\/strong> resultCode<\/code>, this indicates that the\u00a03D Secure 2 authentication was frictionless, and the payment authorisation was successfully completed.<\/li>\n
  3. Present a challenge to the shopper<\/a>.\u00a0If you receive\u00a0ChallengeShopper<\/strong> resultCode<\/code>, this means that the issuer requires further shopper interaction. Depending on the logic on issuer's side, this result code can be returned after you submit a payment request or after you submit the device fingerprint result to Adyen.\u00a0To handle a challenge flow, create an iframe, send a challenge request to the issuer, and then submit the challenge result to Adyen.\u00a0<\/li>\n<\/ol>\n

    To optimize authorization rates, Adyen's Authentication Engine<\/a> routes each payment to either the 3D Secure 2 or the 3D Secure 1 flow, based on issuer performance. If you do not want to automatically fall back to 3D Secure 1, contact Support Team<\/a>.<\/p>\n

    For a complete list of\u00a0resultCode<\/code>\u00a0values and the actions that you need to take, see\u00a0Result codes<\/a>.<\/p>\n

    Before\u00a0you begin<\/h2>\n

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