3D Secure authentication can follow different flows depending on the card issuer’s requirements. Use these test cards to verify each scenario works correctly on your site.
Understanding 3DS Flows
There are two primary 3DS flows, with optional fingerprinting in each:
Frictionless Flow
The issuing bank authenticates the cardholder silently without requiring any action from them. The payment completes seamlessly.
Test with: 4012000000020071 (Visa) or 5100270000000023 (Mastercard)
Challenge Flow
The issuing bank requires the cardholder to complete an authentication challenge. A popup or inline frame appears where the customer verifies their identity.
Test with: 4012000000020006 (Visa) or 5100270000000031 (Mastercard)
Enter password 3ds2 when prompted in the challenge window.
Fingerprinting
Some transactions include a fingerprinting step where the issuer collects device data before deciding on frictionless or challenge authentication. This happens invisibly to the customer.
Test with: 4012010000020070 (Visa frictionless + fingerprint) or
4012010000020005 (Visa challenge + fingerprint)
Testing Procedure
Test Frictionless Flow
- Add a product to cart and proceed to checkout
- Enter card number
4012000000020071 - Use any future expiry date and any CVV
- Complete the order
- Expected: Payment completes without any popup or challenge
Test Challenge Flow
- Add a product to cart and proceed to checkout
- Enter card number
4012000000020006 - Use any future expiry date and any CVV
- Complete the order
- Expected: A challenge window appears
- Enter password 3ds2
- Expected: Payment completes after authentication
Test 3DS Decline
- Add a product to cart and proceed to checkout
- Enter card number
4012000000020121 - Use any future expiry date and any CVV
- Complete the order
- Expected: Payment is declined with an authentication error
3DS Status Codes
| Status | Meaning | Payment Result |
|---|---|---|
| Y | Fully authenticated | Proceed with payment |
| A | Attempted authentication | Proceed with payment |
| N | Authentication failed | Payment declined |
| U | Authentication unavailable | May proceed (issuer dependent) |
| R | Authentication rejected | Payment declined |
Troubleshooting 3DS Tests
- Challenge window doesn’t appear: Check that popups are not blocked by your browser
- Challenge window is blank: Ensure your site is using HTTPS
- Authentication fails: Verify you’re entering the password 3ds2 correctly
- Unexpected behavior: Enable Debug Mode and check the logs