Short answer
The phrase "stripe test card cvv v10" combines three items: a Stripe test card number, the CVC field on that card, and a version tag. Stripe publishes test card numbers. Stripe publishes no card series called "v10". The CVC on a test card is any 3 digits, or 4 for American Express, unless the documentation states a fixed value for a decline case.
What a test card does
A test card is a card number that Stripe accepts in test mode. Test mode runs on API keys that start with pk_test_ and sk_test_. A live key rejects these numbers. No money moves. No issuer is contacted.
Standard test numbers
- 4242 4242 4242 4242: Visa. Any future expiry date. Any 3-digit CVC. Any postal code.
- 4000 0025 0000 3155: triggers a 3D Secure authentication step.
- 4000 0000 0000 0002: generic decline.
- 4000 0000 0000 9995: decline, insufficient funds.
- 4000 0000 0000 0069: decline, expired card.
- 4000 0000 0000 0127: decline, incorrect CVC.
Each number returns a fixed result. Test the failure path with the same care as the success path.
CVC behavior in test mode
Stripe does not check the CVC on 4242 4242 4242 4242. Type 123 or 999. The result is the same. Cards built for a specific decline, such as 4000 0000 0000 0127, return that decline for any CVC value you enter.
About the v10 tag
I found no Stripe reference to a v10 card set. Stripe does not version its test card documentation by card series. Treat v10 as a label from a third-party page, not as a Stripe term.
What test cards cannot do
Test cards do not work in live mode. They do not validate a real account. They do not reproduce real issuer responses. For that, run a live-mode charge on your own card for a small amount.
Rules that apply to card data
PCI DSS forbids storing a card verification code after authorization. Using a card number that belongs to another person is fraud in the US and in most other jurisdictions. Test mode exists so that neither rule comes into play during development.