Ravelin can provide an additional layer of fraud protection by performing 3D Secure (3DS) authentication.
3D Secure requires that customers perform an identity verification check with their card issuer.
With 3D Secure 2, frictionless authentication is possible. This means that the issuer trusts the customer based on the 3DS data provided, and therefore is not required to complete a challenge.
Ravelin’s 3DS Server supports 3D Secure 2 (3DS2) versions 2.2.0 and 2.1.0, and has fallback support for 3D Secure 1 (version 1.0.2) when 3DS2 is not available.
Ravelin’s 3DS Server is approved by EMVCo, is PCI 3DS compliant and is certified with 3DS implementations from all the major card schemes.
We can provide example browser and app 3DS checkout integrations to assist you in integrating with Ravelin’s 3DS Server.
A guide to performing 3DS authentication in a browser.
A guide to performing 3DS authentication in a mobile app.
A guide to performing merchant or PSP initiated 3DS authentication. Also known as 3DS Requestor Initiated (3RI) authentication.
A guide to performing 3DS 1 authentication.
A guide to using 3D Secure alongside Ravelin’s fraud scoring.
Test card numbers for testing your integration.
Ravelin’s 3D Secure API reference.
Details of Ravelin’s iOS 3DS SDK, required in a 3D Secure iOS app integration.
Details of Ravelin’s Android 3DS SDK, required in a 3D Secure Android app integration.