The top pick for almost every Stripe sandbox test is 4242 4242 4242 4242, paired with any future expiry date and any 3-digit CVC. That card is the one Stripe documents first, it runs the full authorization flow in test mode, and it has matching decline and 3D Secure variants in the same number family, which is the main thing to look for when you choose a test card. The "v10" in the query does not map to any test card in Stripe's documentation. It is a label that appears on third-party lists which repackage publicly published sandbox numbers, and treating it as a distinct card or a CVV format is the most common mistake in this search.
What "v10" actually refers to
Stripe publishes test card numbers as plain 16-digit PANs, with no version suffix. Version-style tags such as v10, v11 or v2 usually come from resellers or list sites that renumber the public set so it looks proprietary. If someone hands you a "v10 test card" with a specific CVV attached, the number underneath is almost certainly one of the standard Stripe sandbox cards, and the CVV is irrelevant because test mode accepts any 3-digit value.
- Pro: the underlying number still works in test mode if it is a real Stripe test PAN.
- Con: attached CVVs and expiry rules on those lists are invented, so a validator built around them fails against the real API.
The default success card and its CVV
For 4242 4242 4242 4242 you can enter any three digits, such as 123, and any expiry in the future. Stripe's test mode does not check the CVC value against anything. The same rule applies to the other brand cards used to confirm brand detection: 5555 5555 5555 4444 for Mastercard, 3782 822463 10005 for American Express (four-digit CVC), and 6011 1111 1111 1117 for Discover.
Stripe Test Card CVV: What to Enter and Which Numbers Behave How
- Pro: one card covers address checks, CVC field validation, and the happy-path charge.
- Con: it never produces a decline, so a test suite built only on this number proves very little.
Use it when you need a recommendation for a developer setting up a first checkout flow and nothing more.
Decline and error cards
Stripe documents dedicated decline numbers, including 4000 0000 0000 0002 for a generic decline, 4000 0000 0000 9995 for insufficient funds, and 4000 0000 0000 0127 for an incorrect CVC response. These matter because your error handling is the part of checkout that actually breaks in production.
- Pro: each number triggers a specific decline code you can assert against.
- Con: they still accept any CVC, so they cannot test a real CVC mismatch, only the simulated response.
Recommendation: wire at least one decline card into your integration tests before launch.
3D Secure test cards
Authentication flows need their own numbers. Stripe publishes cards that require 3D Secure authentication and cards that fail it, so you can exercise both branches of the challenge without touching a live account. Any CVC works here too.
- Pro: you can test the challenge, the success redirect, and the failure path in one sandbox.
- Con: behavior depends on your API version and account settings, so re-verify after any version upgrade.
Use these when your integration version changes or when you enable a new authentication rule.
Criteria for picking a test card
- It is published in Stripe's own documentation, not a repackaged list.
- It has sibling numbers for decline, insufficient funds, and expired card outcomes.
- It has a matching 3D Secure variant.
- It is clearly a sandbox number, so it can never be confused with live cardholder data.
Safety rules that apply to every test
Test mode keys are separate from live keys, and test mode never moves money. Never paste a real card number into a sandbox to "see what happens" and never store real cardholder data in a test database; PCI guidance treats any environment holding real account data as in scope. Keep test keys out of production builds and rotate them if they appear in a public repository. If a list offers a CVV plus expiry plus ZIP bundle labeled v10, treat it as noise and go back to the documented numbers.