3D Secure Mobile SDKs
3D Secure Mobile SDKs allow you to securely collect and tokenize sensitive card data (card number and CVV code) in your native iOS or Android app while authenticating the cardholder via 3D Secure at the same time. Completely outsource your tokenizaton and authentication processes to our libraries and benefit from features such as:
- 3D Secure / SCA Ready: The SDK takes over the complexity of the 3DS process
- Smart, secure, and state of the art UI components
- Card brand identification and input validation
- Card scanner
- Store payment information for later use and fast checkout. Delegate the token selection to the library
- Theme support: Style various items according to your CI / Dark mode support
Please note that it's currently not possible to use this API while sending the 3D Acquiring data dynamically. We're expecting to release this feature later this year.
Access the latest version of our SDKs by following the links below and linking the latest release to your app projects.
To start a 3D Secure Mobile SDK tokenization you have to call our init API from your server. The response returns a
mobileToken which is required to initialize the libraries.post
https://api.sandbox.datatrans.com
/v1/transactions
Init API
Request
Response
curl -L -X POST 'https://api.sandbox.datatrans.com/v1/transactions' \
-H 'Authorization: Basic MTEwMDAxNzc4OTpNQUd6UUVEbkVxd001d0Vr' \
-H 'Content-Type: application/json' \
--data-raw '{
"amount": 1000,
"currency": "EUR",
"refno": "SDK 3D_test",
"paymentMethods": [
"ECA", "VIS"
],
"card": {
"createAliasCVV": true
},
"option": {
"authenticationOnly": true,
"createAlias": true,
"returnMobileToken": true
}
}'
{
"mobileToken": "cca3f978017a694e11e92c10d78e71f302eb982819eaa857"
}
Now that you have retrieved a
mobileToken, you can continue with the initialization of our iOS or Android SDK. Make sure to call the library with your mobile token to start a transaction. Below is an example of the suggested minimum options to start a transaction with iOS (Swift, Objective-C) and Android (Kotlin, Java). Please read our detailed classes description for iOS and Android to discover more initialization options.Java
Swift
Objective-C
Kotlin
Transaction transaction = new Transaction(mobileToken, aliasPaymentMethods);
transaction.setListener(this);
transaction.getOptions().setAppCallbackScheme("your_scheme");
transaction.getOptions().setTesting(true);
transaction.getOptions().setUseCertificatePinning(true);
TransactionRegistry.INSTANCE.startTransaction(this, transaction);
let transaction = Transaction(mobileToken: mobile, aliasPaymentMethods: aliasPaymentMethods)
transaction.delegate = self
transaction.options.appCallbackScheme = "your_scheme"
transaction.options.testing = true
transaction.options.useCertificatePinning = true
transaction.start(presentingController: navigationController)
DTTransaction* transaction = [[DTTransaction alloc] initWithMobileToken:mobileToken aliasPaymentMethods:aliasPaymentMethods];
transaction.delegate = self;
transaction.options.appCallbackScheme = @"your_scheme";
transaction.options.testing = YES;
transaction.options.useCertificatePinning = YES;
[transaction startWithPresentingController:self.navigationController];
val transaction = Transaction(mobileToken, aliasPaymentMethods)
transaction.listener = this
transaction.options.appCallbackScheme = "your_scheme"
transaction.options.isTesting = true
transaction.options.useCertificatePinning = true
TransactionRegistry.startTransaction(this, transaction)
Once the card details have been collected, the 3D process will be started automatically. If required, the cardholder will be redirected to the website or the banking app of the card issuer to complete a challenge.
After the transaction has been completed, you can refer to the class
TransactionSuccess that will return the details of the transaction. If the transaction failed, you will have to refer to the class transactionError for further details instead. You may also implement TransactionDelegate (iOS) and TransactionListener (Android) to be notified when a transaction is successfully finalized, encounters an error, or is canceled by the user. For the card scanner to work, a usage description for the camera use will be required in your .plist file. If you do not provide a description for the camera use, the app will crash when starting the card scanner.
.plist File
Key : Privacy - Camera Usage Description
Value : $(PRODUCT_NAME) requires camera access to scan cards.
To obtain the tokens as well as the authentication result, you first need to submit the
transactionId returned by the SDK to your server. Subsequently, call the GET Status API from your server together with the
transactionId to obtain a token for the card number and the CVV code. Additionally, the API returns an 3D object which contains information about the result of the authentication process. The service requires HTTP basic authentication. The required credentials can be found in our dashboard. Please refer to API authentication data for more information.
get
https://api.sandbox.datatrans.com
/v1/transactions/{transactionId}
Status API
Request
Response
curl -X GET \
https://api.sandbox.datatrans.com/v1/transactions/190906151210861442 \
-H 'Authorization: Basic MTEwMDAxNzY3NTpTejdodE5uSjdNM05YQ0lT' \
{
"transactionId": "210609101239797372",
"type": "payment",
"status": "authenticated",
"currency": "EUR",
"refno": "SDK 3D_test",
"paymentMethod": "ECA",
"detail": {
"authorize": {
"amount": 1000
}
},
"card": {
"alias": "AAABee_Un5_ssdexyrAAAXULTeyzAAe1",
"fingerprint": "F-c6FruvXTy36oJPosQUsRCf",
"masked": "540400xxxxxx0001",
"aliasCVV" : "HemcmX8TTB6Lipr_uF5IwG9M",
"expiryMonth": "06",
"expiryYear": "25",
"3D": {
"eci": "02",
"xid": "MDAyMTA2MDkxMDEyMzk3OTczNzI=",
"cavv": "OTkyMTA2MDkxMDEyNDkwOTc0MDY=",
"threeDSVersion": "1.0.2",
"cavvAlgorithm": "1",
"directoryResponse": "Y",
"authenticationResponse": "Y"
}
},
"history": [
{
"action": "authenticate",
"amount": 1000,
"source": "api",
"date": "2021-06-09T08:12:49Z",
"success": true,
"ip": "178.238.172.18"
}
]
}
You can style various options in our Mobile SDKs. Refer to the class
ThemeConfiguration to adapt various colours to your corporate identity.Our iOS and Android Mobile SDK integrations are currently translated and supported in the following languages:
- English
en - German
de - French
fr - Italian
it
Please get in touch should you need an additional language to be added for your checkout or if you find a translation error.
Last modified 1yr ago