3DS2 SDK - Android & iOS
Use our native android SDK to improve issuer challenge display for 3DS2 and increase the chance of a frictionless authentication using mobile device data.
API version 3 required: New merchants boarded from May 2021 will have v3 of the API enabled against their account (enabling new test values with iOS/Android support on Try). Existing merchants will be gradually migrated - contact support to accelerate this if you require v3 for testing.
The Access 3DS API is periodically tested against the latest version of the Cardinal SDK. Current tested Cardinal SDK version:
- Android:
v2.2.6 - iOS:
v2.2.5
We strongly recommend signing up
Get started with our App SDK. Get a JWT to
initialize the SDK and perform device data collection .Submit order and risk data for
authentication. The 3DS flow ends here if no challenge is required (frictionless). Show the issuer
challenge display and retrieve the authentication details to form part of the payment authorize request. Test the integration on our Try environment using specific values (API v3 required).
Note: Native mobile support is a new feature of 3DS2, for responses that are 3DS1 a webview is required for the
Visualize our 3DS API and see the flow of a 3DS authentication.
| Flow | Diagram |
|---|---|
| Frictionless |  |
| 3DS2 Challenged If the issuers risk analysis decides the order is of sufficient risk then a |  |
| 3DS1 Challenged If no |  |
Next steps
