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

\n
PSD2 compliance<\/h5>

If you are implementing 3D Secure to comply with PSD2 SCA, learn more from our comprehensive guide<\/a>.<\/p><\/div><\/div>\n\n

The Adyen 3DS2 Android SDK<\/a> gets the device fingerprint and presents the challenge to your shopper. From your server, you need to send a payment request, the encrypted device fingerprint, and the challenge result to Adyen.<\/p>\n

In a full 3D Secure 2 implementation, a payment can go through either a frictionless<\/a> or a challenge<\/a> authentication flow before it can be authorised.<\/p>\n

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

How it works<\/h3>\n

Here's how a 3D Secure 2 challenge authentication flow works:<\/p>\n

\n \"\"\n<\/a><\/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. If the transaction is exempted from 3D Secure, you might get an Authorised<\/strong> result code.<\/li>\n
  2. If you receive an IdentifyShopper<\/strong> resultCode<\/code>, get the 3D Secure 2 device fingerprint<\/a> and send the encrypted device fingerprint information to Adyen. After you send the device fingerprint, it is possible that you receive an Authorised<\/strong>resultCode<\/code> in the response. This means that the 3D Secure 2 authentication was frictionless, and the payment was authorised.<\/li>\n
  3. If you receive\u00a0ChallengeShopper<\/strong>resultCode<\/code>, this means that the issuer requires further shopper interaction and you need to present a challenge to the shopper<\/a>.<\/li>\n
  4. After the 3D Secure 2 flow is complete, whether the transaction is successful or not, close the transaction<\/a> and clean up the ThreeDS2Service.INSTANCE<\/code>.<\/li>\n<\/ol>\n

    The payment might also be routed to 3D Secure 1<\/a>, based on issuer performance. This is indicated by a\u00a0RedirectShopper<\/strong>\u00a0resultCode<\/code>. If you do not want to automatically fall back to 3D Secure 1, contact our Support Team<\/a>.<\/p>\n

    To test your integration, see\u00a0Testing 3D Secure 2<\/a>.<\/p>\n

    Before\u00a0you begin<\/h2>\n
    \n
    Adyen 3DS2 Android<\/h5>

    Subscribe to our GitHub repository<\/a> to get the latest updates and versions.<\/p><\/div><\/div>\n\n

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