- Get Started
- Guides
- Integrations
- References
- API Reference
- Basic Payment
- Forex
- Authentication
- Card Account
- Apple Pay
- Virtual Account
- Bank Account
- Token Account
- Customer
- Billing Address
- Merchant Billing Address
- Shipping Address
- Merchant Shipping Address
- Corporate
- Sender
- Recipient
- Merchant
- Marketplace & Cart
- Airline
- Lodging
- Passenger
- Tokenization
- Recurring Migration
- 3D Secure
- Custom Parameters
- Async Payments
- Webhook notifications
- Job
- Risk
- Point of Sale
- Response Parameters
- Card On File
- Chargeback
- Result Codes
- Payment Methods
- Transaction Flows
- Regression Testing
- Data Retention Policy
- Release Notes
- API Reference
- Support
3D Secure 2.x
Keep your transactions compliant with Strong Customer Authentication (SCA) requirements and bring more friendly user experience to your customers with a 3D Secure 2, also known as EMV 3D Secure. It's a brand new secure authentication protocol which supports app-based authentication. Mobile SDK makes it easy to integrate all new 3DS features into your e-commerce app.
App-based authentication
In the app-based flow, a cardholder initiates a transaction on a mobile device (Android or iOS) from a 3DS-enabled app. Mobile SDK collects as many data from the mobile device as possible and sends it to a cardholder's bank. The bank then can make decision if the data is enough to trust that the real cardholder is making the purchase or it needs further proof.
Frictionless flow
If bank verification is passed then the transaction goes through the “frictionless” flow and the authentication is completed without any additional input from the cardholder. The ability to share more data using 3D Secure 2 aims to increase the number of transactions that can be authenticated without further customer input.
Challenge flow
If the bank decides cardholder needs to pass further verification, the transaction is sent through the “challenge” flow and the customer is asked to provide additional input to authenticate the payment. Authentication is embedded directly into mobile checkout flow, no more redirects. It also might be implemented as authentication through the mobile banking app using fingerprint or even facial recognition (“out-of-band authentication”). Check Mobile SDK Advanced Options for more details.
New challenge flow aims to make authentication smoother and more reliable using latest techniques.
Integration types
1. Mobile SDK Ready-to-use UI and Custom UI integration
The Mobile SDK (MSDK) provides seamless integration with 3D Secure 2.x payments.
Integration steps differs depending on how MSDK is used in your app. In these guides we assume that you already integrated base MSDK to make payments with one of the following ways:
- MSDK + Ready-to-Use UI - using our checkouts screen;
- MSDK + Your Custom UI - using MSDK just for sending transactions.
Where do I start?
We recommend to get started with the Ready-to-Use UI integration. In case of using Ready-to-use screens everything works out of box. Just configure 3DS 2 in the Administration Portal for the card brands, and this info will be automatically fetched in the MSDK. Then import 3DS library to your project, and you are ready to run first 3DS 2 transaction.
FULL GUIDE >
Starting from version 4.0.0 Custom UI integration for 3D Secure 2 payments become easier and require only a few steps to enhance your payments with the new 3DS 2 verification. Check full integration guide below.
FULL GUIDE >
2. Standalone 3D Secure 2.x integration
If you are not going to implement payments through the Mobile SDK but would like to have 3DS-enabled app, you still can use MSDK as standalone solution. Refer to the following integration guide.