3D Secure test automation
Payments
3D Secure is the last step before the money moves. DoesQA proves every challenge, every frictionless pass and every failed authentication behaves before your customers hit it.
What we test on 3DS
3DS2 challenge flows: one-time passcodes, bank app approval and in-frame forms
Frictionless flows that authenticate with no challenge
Cardinal Commerce and other 3DS servers rendered in iframes and popups
Test your 3DS challenges end to end
What the customer sees next: confirmation, decline message or retry
How to test 3DS
Always use a test or sandbox checkout. Never use a live card. Your payment provider publishes 3DS test cards for a frictionless pass, a challenge you can complete, and a failed authentication. Start with frictionless, then a successful challenge, then a failure, and check what the shopper sees next: confirmation, decline or retry.
The challenge often loads in an iframe, sometimes nested. Some integrations redirect the whole page to the issuer and back. The test has to follow that frame or redirect, complete the published challenge details, and wait for the result. Run those cases on every release, and in every market where 3DS is on.
In DoesQA, Switch Frame steps into the challenge frames, Set value enters the published challenge details, and Switch to parent frame returns to checkout. Values keep each scenario's data out of the journey so one Flow covers challenge, frictionless and failure. Checks prove the confirmation or the decline. On Adyen checkouts, Adyen Widget fills the card form in one step before the challenge.
3DS test checklist
A frictionless payment that authenticates with no extra challenge.
A challenge you complete with the payment provider's published test details (and, for Adyen web challenges, the password Adyen publishes; see Getting started).
A failed authentication, with the decline or retry the customer should see.
The page the shopper lands on next: confirmation, decline message or retry.
Where 3DS tests usually break
The challenge sits in nested iframes.
A test that cannot leave the parent checkout page never sees the challenge form. The test has to step into those frames, complete the challenge, and prove the result, then return to the parent checkout. In DoesQA, Switch Frame steps into the challenge frames, Set value enters the published challenge details, and Switch to parent frame returns to checkout. On Adyen checkouts, Adyen Widget fills the card form in one step before the challenge.
Challenge, frictionless and failure need different data.
Hard-coding one card produces one path and hides the others. Keep a published test card for each outcome, and expect a different result for each. In DoesQA, drive the card and the expected outcome with Values so one Flow covers all three.
Some challenges leave the checkout page.
Some integrations redirect the whole page to the issuer and back. Follow the shopper and check where they land. In DoesQA, a redirect needs no extra step; if a challenge opens a new window, Switch Window moves into it and back.
What you need to get started
A checkout URL in a test or sandbox environment (for example Stripe test mode or an Adyen test account). Do not run 3DS tests against production with live cards.
The 3DS test cards and challenge outcomes published by your payment provider. Use the official lists. Stripe: Testing (3D Secure authentication and regulatory cards). Adyen: Test 3D Secure 2 authentication and Test card numbers (Adyen documents a web challenge password of "password"). PayPal: Test 3D Secure. Fetched 10 November 2026.
A separate test card for each scenario (challenge, frictionless, failure). In DoesQA, store those as Values so the Flow stays reusable. If the checkout uses Adyen's Drop-in or Component, Adyen Widget fills the card form in one step before the challenge.
Trusted by teams that ship every day
Our customers test 3D Secure with DoesQA on every release.



