Important
We have released a new version. Documentation for our latest version can be found here.
Last Updated: 17 January 2024 | Change Log
3DS API
Verify your customer's identity simply and seamlessly to minimize fraud. Use our strong customer authentication to benefit from liability shift.
Important
Our 3DS2 offering will fallback to 3DS1 if not yet supported by the card issuer or the deviceData.collectionReference value is not included in the Authentication Request
Main steps:
| Steps | Description |
|---|---|
| Get started | Get started with our 3DS API by setting your headers and querying the 3DS root resource. |
| Device data initialization | Receive the form values required for the Device Data Collection form. This is used to fingerprint your customer's browser or device. |
| Device Data Collection (DDC) | Submit the DDC form to your customers card issuer. |
| Authentication | Order information and risk data is used to decide if a challenge is necessary. The 3DS flow ends here if no challenge is required (frictionless). |
| Challenge display | Display your customer's card issuers challenge page and perform an identity check on your customer. |
| Verification | Following a challenge, retrieve the authentication details, which must be used as part of your 3DS payment authorize request. |
| Testing | After you've finished your integration into our 3DS API, you must test your integration with the values provided. |
Next steps