Looking for a better shopper experience?
Instead of redirecting shoppers, you can alternatively perform native 3D Secure 2 authentication within your website or mobile app.
To complete a card payment with 3D Secure authentication, the shopper needs to verify the payment with their bank. For 3D Secure 1, this usually involves entering a unique password or SMS code on their bank's website. For 3D Secure 2, the shopper's identity may be verified using a passive, biometric, or two-factor authentication approach.
This section explains how to implement both versions of 3D Secure using a redirect. We will check which version the issuer supports, and provide a redirect URL where your shopper can complete either the 3D Secure 1 or the 3D Secure 2 authentication, depending on which version the issuer supports.
Which platform are you integrating?
Web
Support cards with 3D Secure authentication through a redirect on your website.
iOS
Support cards with 3D Secure authentication through a redirect in your iOS app.
Android
Support cards with 3D Secure authentication through a redirect in your Android app.
API only
Use our APIs to accept cards with 3D Secure authentication through a redirect on your website, or in your iOS or Android app.