- Getting Started
- Tutorials
- Reference
- API Reference
- Basic Payment
- Authentication
- Card Account
- Virtual Account
- Bank Account
- Customer
- Billing Address
- Shipping Address
- Corporate
- Merchant
- Cart
- Airline
- Tokenization
- Recurring
- Recurring Migration
- 3D Secure
- Custom Parameters
- Async Payments
- Webhook notifications
- Risk
- Point of Sale
- Response Parameters
- Card On File
- Chargeback
- Result Codes
- Brands Reference
- API Reference
- FAQ
- Imprint

3DS SDK + MSDK + Ready-to-use UI
This guide describes how to use 3DS SDK in combination with the Mobile SDK (MSDK) and Ready-to-use UI. We assume that you already went through the base MSDK integration guide and can submit payments. If yes, proceed with the following instructions to enhance payments with the 3D Secure 2 verification.
NOTE: First of all, proper configuration in the Administration Portal should be done to enable 3DS 2 for the specific card brands.
Requirements
- MSDK 2.62.0 or higher
Import libraries
You can stop here, there are no more mandatory steps for this kind of integration. But we strongly recommend to look through the Customization guide to check advanced features of the 3DS SDK. Use OPPThreeDSService.sharedInstance.config
to apply customizations, note that it's still not mandatory to call initialization by yourself, everything else is implemented by MSDK.
[Optional] Initialize the 3DS service in advance
By default, initialization is started by MSDK while checkout is loading, but you may want to do it earlier, even on application start. Initialization phase includes fetching actual config info from the Server, collecting device data and performing security checks. All these actions are done in background thread, so start it whenever you want, it won't affect UI thread.