A 3D Secure test card v5 is a sandbox card number taken from the fifth published revision of a payment provider's test card set. It lets a developer trigger specific 3DS authentication outcomes, such as a challenge or a frictionless approval, without touching a real account. Because each gateway publishes its own numbers, there is no universal v5 card: the correct value is whatever your provider lists on its current test card page.

3d secure test card v5

Why version numbers appear on test card lists

Payment providers revise test card sets when card network rules, 3DS2 field requirements, or their own sandbox behavior change. A list marked v5 is the fifth such revision, not a fifth generation of the 3D Secure protocol itself. The protocol version is tracked separately by EMVCo, which owns the 3DS specification and has moved through 3DS1 and 3DS2.x releases. Mixing the two numbering schemes is a common source of confusion.

3d secure test card v7

The practical effect: if a tutorial quotes a card from v3 of a provider's list, that number may still work, or it may no longer produce the behavior described. Check the version date shown on the provider's page.

3d secure test card v10

What a 3DS test card can simulate

• Frictionless flow: the issuer approves without showing a challenge screen.
• Challenge flow: a simulated authentication page appears and accepts a test password or code.
• Failed authentication: the challenge is rejected and the authorization is declined.
• Attempted or unavailable: authentication cannot complete, so the transaction falls back to a liability shift decision.
• Timeout or error: the authentication step returns an error state.

Providers assign one card number per outcome. That is why a 3DS test card list is long: each row maps to a single branch of your integration logic.

3d secure test card v10

How to run a 3DS test transaction

1. Switch your environment to sandbox or test mode and confirm the API keys belong to that mode.
2. Copy the card number, expiry, and CVC from your provider's current test card page rather than from a third party post.
3. Create a payment intent or equivalent object and pass the 3DS parameters your integration requires.
4. Complete the simulated challenge when it renders, using the test credentials your provider documents.
5. Compare the resulting status against the outcome you expected for that card.

Common reasons 3DS tests fail

• The card comes from an older revision of the test list and no longer maps to the documented outcome.
• Test mode is active but live keys are used, or the reverse.
• The browser blocks the challenge iframe, so the flow never returns a result.
• The account is not enabled for the 3DS product you are testing.
• Webhook or return URL handling is misconfigured, so a successful authentication looks like a failure.

Keep test credentials separate from real credentials

Test card numbers are public by design and safe to paste into documentation, tickets, and shared notes. Real card data is not, and using it in a sandbox breaks card network rules and your processing agreement. If you are debugging a live issue, use your provider's test suite or request a tokenized reference from your own acquirer instead of handling card numbers directly.