Find information on most frequently asked questions when authenticating with 3DS
- 3DS1 deprecation FAQ and deadlines
- Why is my transaction not going through 3DS2?
- How do I implement 3D Secure to comply with PSD2?
- Why is 3D Secure not triggered?
- How is it determined whether 3DS is triggered?
- How is it determined which 3D Secure version is used, 3D Secure 1 or 3D Secure 2?
3DS response codes
- What does the error code 701 with HTTP status 500 mean?
- Why are my 3DS payments not being completed?
- Why do I get an "Authentication required" response?
- Why a 3D Secure 2 payment was Authorised with transStatus: A : Attempted to Authenticate from the ARes and without a challenge?
- What does "Invalid paRes from issuer" mean?
- What does it mean if a payment is refused because 3d-secure: Authentication failed?
- Can I test 3D Secure 2 in Live?
- Which fields should I send in the payment request for 3D Secure 2?
- How do I test the different 3DS2 payment flows and response codes?
- How do I update my API version to support 3DS2?
- Can I still use my Dynamic 3DS rules with 3D Secure 2?
- Is my integration using 3D Secure?