The Checkout.com 3D Secure (3DS) mobile SDK allows you to provide a native 3DS2 experience in your mobile app, with visual styling that you can control.
The SDK handles the device data collection, communication with the card issuer, and presentation of 3D Secure challenges to the customer when required.
👉 See the Integration Guide with Code Examples
📚 Read the reference documentation
- Supports 3D Secure protocols 2.1.0 and 2.2.0.
- Presents native 3DS2 challenge screens to the user, with styling that you can customise to best fit your apps and branding.
- Optionally falls back to 3DS1 when 3DS2 is not available, returning the same authentication result to your app as for 3DS2. (This option can be configured by Checkout.com for your account.)
- Supports a range of local languages and accessibility needs, and allows you to set your own string translations.
- Meets requirements from EMVCo and the PCI Security Standards Council, specifically set for 3DS SDKs, so you can be sure it is interoperable with card issuers and that your customers’ sensitive data stays secure.
The 3DS SDK for Android supports apps targeting Android 5.0 (API level 21) and above.
First, integrate the 3DS SDK into your app.
Then, configure your app to:
- Initialize the SDK with your preferred user interface options.
- Configure the parameters for an authentication.
- Request authentication and handle the result to continue your payment flow.
👉 See the Integration Guide with Code Examples for full details.
📚 Read the reference documentation
The Android SDK depends on some external libraries:
- To help maintain security, we use SpongyCastle, Jose JWT, Jetpack Security and Certificate Transparency Android.
- To help provide support and monitor the performance of the SDK, we use our own Checkout Event Logger.
For help using the 3D Secure SDK, or to pass on your feedback, you can email our team at [email protected].
If you’ve found a bug, we encourage you to open an issue through GitHub. If your problem isn’t already listed, please detail the versions of the SDK and your development environment that you’re using, what you were hoping to accomplish, and what the actual result you observed was.
If you have an idea for a new feature, we’d also love to hear about it through GitHub. Please open an issue, detailing your idea and why it’s important for your project.
This software is released under license. See LICENSE for details.