What is a 3D Secure test card v6?

A 3D Secure test card is a sandbox card number published by a payment provider so developers can trigger a 3DS authentication result without touching a real account. The "v6" label is not an official EMVCo version. It is an internal index that a provider, plugin, or test-card list uses to tell one simulated card apart from another.

3d secure test card v5

In other words, v6 describes a slot in a test tool, not a protocol or a card product. The authentication logic behind it still follows the 3D Secure 2 specification.

3D Secure Test Card V9

Why does "v6" show up on some test card lists?

Providers often group sandbox cards by the outcome they produce: frictionless approval, challenge required, challenge failed, or issuer unavailable. A list may number those entries for versioning, so v1 through v6 can simply be the sixth variant on that list.

3D Secure Test Card v8: What It Is and How to Use It Safely

Because the numbering is not standardized, the same v6 value at two different providers can behave differently. Always confirm against the documentation of the processor you are integrated with.

3d secure test card v2

How do you run a 3DS test flow step by step?

1. Switch your integration to the provider's sandbox or test environment.
2. Create a payment intent or transaction using the published test card number and any required test expiry and CVC.
3. Watch for the authentication step. A challenge card opens a simulated issuer page, and a frictionless card returns an authentication result without user input.
4. Submit the simulated one-time code or select the approve or decline option on the challenge page.
5. Verify that your system stores the correct authentication outcome and handles both approval and failure paths.

Which authentication outcomes can you simulate?

• Successful authentication: the transaction proceeds with a liability shift flag set.
• Failed authentication: the issuer declines and your code must route to a retry or error state.
• Challenge abandoned: the user closes the authentication window before responding.
• Attempted authentication: data is submitted but the issuer does not authenticate, which matters for exemption logic.
• Authentication unavailable: a timeout that tests your fallback behavior.

What rules apply to 3DS test cards?

Test card numbers only function inside a sandbox. They are published openly and carry no value outside that environment.

Real account credentials should never be entered into a test flow, and test cards should never be used to probe a live system. Production traffic requires genuine authentication through the cardholder's own bank.

Frequently asked questions

Is a 3D Secure test card v6 valid in production?

No. Sandbox numbers are blocked in live mode by design. A live payment needs a real card and a genuine authentication step from the issuing bank.

Do all processors use a v6 naming scheme?

No. Most providers label test cards by behavior instead of by number, so always read the documentation for your specific integration.

Where do official 3DS test cards come from?

They are published in the developer documentation of payment service providers and card networks. That documentation is the only reliable source for current values.