What is 3DS?
Strong Customer Authentication (SCA) regulation in Europe requires the use of 3D Secure (3DS) for card payments.
3DS requires customers to complete an additional verification step with the card issuer when paying. If challenged, we direct the customer to an authentication page served by their bank, and they enter a password associated with the card or a code sent to their phone.
Configure 3D Secure for your Primer account
At Primer, we've decoupled 3D Secure from any underlying processor. Configure 3D Secure in your workflow, and Universal Checkout will handle the rest, presenting a fully in-context and optimized 3D Secure flow to your customer on web and mobile. Now you're SCA-ready with a unified checkout across all your payments services including 3D Secure 2.0.
Primer supports Dynamic 3DS to improve conversion, enabling you to present 3D Secure to customers only when it's absolutely required.
If your card processor does not support third-party 3D Secure, Primer seamlessly redirects the user to the processor's 3DS challenge page instead.
Set up the workflow for 3D Secure
Configuring 3DS settings for your payments takes place within the "Authorize payment" Action. Learn more here about how to set up a workflow to process payments.
In the configuration panel, you need to choose which 3DS option you want for all payments processed by this Action block:
No 3DS
3D Secure will not be used for any payments processed by this block. Payments will be declined when the Issuer requires authentication.
Adaptive 3DS
Use Primer’s proprietary Adaptive 3DS which will only carry out 3DS authentication if the payment would be declined without it.
Primer 3DS
3D Secure authentication will be handled by Primer's agnostic 3D Secure solution for payments processed by this block. This could either be a challenge or frictionless.
Processor 3DS
Your processor will present a 3DS challenge according to their configuration. This isn't compatible with Fallbacks as Primer is not involved in the flow.
Configure your Client Session
To improve 3DS success rates, it is recommended to pass the following elements in the Client Session:
Field | Description |
---|---|
The customer's email address | |
The customer's billing address |
In Sandbox, the email address and billing address must be provided to trigger 3DS.
Handle 3D Secure in Universal Checkout
Install 3DS SDK
3D Secure on Android requires the addition of the io.primer:3ds-android
library to your project. This library is currently held on Primer’s private artifactory.
- 1
Add the URL to our artifactory to your
gradle.properties
1
PRIMER_ANDROID_ARTIFACTORY_URL=https://primer.jfrog.io/artifactory/primer-android/
bashcopy - 2
Amend the repositories section of your app's
build.gradle
to include our Artifactory1234567
repositories { /* Other repositories... */ maven { url "${PRIMER_ANDROID_ARTIFACTORY_URL}" }}
bashcopy - 3
Finally, amend the dependencies section of your app's
build.gradle
to include the3ds-android
library. Paste this code, make sure to replacesupported-3ds-sdk-version
with the right value. See the table below to get the correct one:12345
dependencies { /* Other dependencies... */ implementation "io.primer:3ds-android:{supported-3ds-sdk-version}"}
bashcopy
Interoperability matrix
Primer SDK internally uses Primer 3DS SDK as a compile
time dependency. In order for the SDKs to work properly,
the versions used internally and the one imported to your code must match.
Here is a breakdown of supported interoperable versions:
Primer SDK version | Primer 3DS SDK version |
---|---|
2.16.0+ | 1.1.2 |
2.15.0 - 2.15.1 | 1.1.1 |
2.0.0 - 2.14.1 | 1.1.0 |
To validate that the 3DS SDK is imported correctly:
- 1Clean and sync your project
- 2Validate that library can be found in
External Libraries
section (if you use Android Studio)
Handle Out-of-Band (OOB) redirects (Optional)
Starting from 3D Secure protocol version 2.2.0, you can enhance the user experience by implementing an automatic redirect from another (authentication) application during an OOB challenge to your application once the challenge is successfully completed. This feature allows for a seamless transition and improved user flow.
If this feature is not implemented, the user will have to come back to your application manually to complete their payment, which adds significant friction.
To enable this feature, ensure that you include the threeDsAppRequestorUrl
parameter when configuring the PrimerThreeDsOptions
object.
Please note that the threeDsAppRequestorUrl
value must be a Android App Link.
Additionally, it is essential that your application is configured to handle the App Link properly in order to facilitate the redirection.
To configure the App Link correctly using Universal Checkout, follow these steps:
- 1
Add the following to your
AndroidManifest.xml
file:123456789101112131415161718
<activity android:name="io.primer.android.threeds.ui.ThreeDsActivity" android:exported="true" tools:node="merge"> <intent-filter android:autoVerify="true" tools:targetApi="m"> <action android:name="android.intent.action.VIEW" /> <category android:name="android.intent.category.DEFAULT" /> <category android:name="android.intent.category.BROWSABLE" /> <data android:host="{yourdomain.com}" android:pathPrefix="/3ds" android:scheme="https" /> </intent-filter></activity>
xmlcopy - 2
Replace the value of
android:host
with your web domain name, ensuring not to modify any other configuration - 3
Once you've made the necessary changes, verify the App Link configuration by following the guidelines provided in the Android documentation.
- 4
Pass your App Link (e.g.
https://{yourdomain.com}/3ds
) asthreeDsAppRequestorUrl
in thePrimerThreeDsOptions
object of your settings.1234567
val settings = PrimerSettings( // ... paymentMethodOptions = PrimerPaymentMethodOptions( threeDsOptions = PrimerThreeDsOptions("https://{yourdomain.com}/3ds") ) // ...)
kotlincopy
Execute 3D Secure
Universal Checkout drop-in and headless automatically render the 3DS challenge when required by your workflow.
If your application is not installed from a trusted source (e.g. a debug version, not installed from the store, or used on an emulator), try to set
PrimerDebugOptions.is3DSSanityCheckEnabled
to false
.
Otherwise 3D Secure library initialization will fail due to security checks being performed.
is3DSSanityCheckEnabled
flag should only be used in development mode, and not in production release of your app.
Test 3D Secure
Go Live
Before going live with 3D Secure, your account has to be configured for each of your processor.
To do so, please get in touch with your contact at Primer with the following information:
- Acquirer Merchant ID
- ARN (Acquirer reference number) - per card scheme
For Amex - this is referred to as the Amex SE number (Service entity) - Merchant Category Code