How do I trigger 3DS2 In-app native flow for payments?

This page outlines the requirements to trigger the 3DS2 in-app native flow for in-app payments. If you’re experiencing a redirect flow instead of the native one, double-check if you’ve included the “sdkVersion” correctly in your API request to Checkout (/payments) or Classic Integration (/authorize).

If you are using Checkout (/payments)

Our platform expects merchants to pass “paymentMethod.threeDS2SdkVersion” in the /payments API request, as explained here for iOS and Android. Please follow the Adyen docs and perform the following two steps:

1. Get the threeSD2SdkVersion (iOS/Android).
2. Send it in the payment request to /payments.

If you are using Classic (/authorize)

Our platform expects merchants to pass “threeDS2RequestData.sdkVersion” in the /authorize API request as explained here for iOS and Android. Please follow the Adyen Docs and perform the following two steps:

1. Get the sdkVersion (iOS/Android).
2. Send it in the payment request to /authorize.

Additional notes / recommendations:

1. We strongly recommend dynamically passing the SDK version to our platform from the client or component side. Avoid hard-coding or sending dummy values, as you might break live transactions. 
2. Please ensure your SDK version meets the requirement as follows:
   1. Classic integration: iOS/Android v2.2.5
   2. Checkout integration: Android Component v4.5.0 and iOS Component v4.10.2

Our recommendation is to be the most updated 3DS2 SDK. Release notes:

• Checkout: Android / iOS
• Classic: Android / iOS

If you are correctly passing the SDK version in the API request but are still experiencing difficulties activating the in-app native flow, kindly consult the troubleshooting steps provided below: 

• iOS: Dropin | Component
• Android: Dropin | Component