Stripe test cards accept any 3-digit CVV, and any 4-digit CVV for American Express, as long as you are using test-mode API keys. The "v7" in stripe test card cvv v7 is not a Stripe API field and does not change the value you type: a card like 4242 4242 4242 4242 succeeds with 123, 000, or 999. In practice, "v7" is a version tag from third-party test-card spreadsheets, internal QA test matrices, or a release number in a test suite.

Stripe Test Card CVV Guide

Is there an official Stripe "CVV v7" value?

No. Stripe documents test card numbers, expiry dates, and CVC handling, but it does not publish a versioned CVV called v7. Card verification codes are always 3 digits for Visa, Mastercard, Discover, JCB, and Diners, and 4 digits for American Express.

Stripe Test Card CVV Explained: What "v10" Lists Get Wrong

When a team writes "cvv v7," they usually mean the seventh revision of a test-case sheet or the seventh version of a checkout test plan. Treat the label as documentation metadata, not as a card value.

read more

Which CVV should I enter with a Stripe test card?

Enter any 3-digit number when you test a non-Amex brand. Stripe's test mode does not validate the code against an issuer, so 123, 456, and 001 all behave the same way on a success card.

stripe test card cvv v6

  • Visa: 4242 4242 4242 4242, CVV 123, any future expiry, any postal code.
  • Mastercard: 5555 5555 5555 4444, CVV 123.
  • American Express: 3782 822463 10005, CVV 1234.
  • Discover: 6011 1111 1111 1117, CVV 123.
  • JCB: 3566 0020 2036 0505, CVV 123.

Use an expiry date in the future, such as 12/34. A past date can trigger an expired-card decline even when the card number itself is a success card.

How do I test a failed CVC check in Stripe?

Stripe triggers a CVC failure with a dedicated test card number, not with a special CVV. Charge 4000 0000 0000 0127 to return an incorrect CVC code, and 4000 0000 0000 0101 when you need the CVC check to fail without a hard decline.

This matters for QA scripts built around a "v7" revision: the CVV digits stay generic while the card number selects the response. Rewriting the CVV will not produce a new decline reason.

How do I test other declines and 3D Secure?

Stripe maps each test card number to one response so you can drive a specific branch of your checkout logic.

  • 4000 0000 0000 0002 returns a generic card decline.
  • 4000 0000 0000 9995 returns insufficient funds.
  • 4000 0000 0000 0069 returns an expired card.
  • 4000 0025 0000 3155 requires 3D Secure authentication.
  • 4000 0000 0000 3220 requires 3D Secure 2 authentication.

Server-side test tokens such as tok_visa and PaymentMethod IDs such as pm_card_visa skip raw card entry and still accept any CVC passed in the request.

Do test cards work with live keys?

No. Test card numbers are rejected when you use a live secret key, and real card numbers are rejected with test keys. Confirm the key prefix before you run a suite: sk_test_ and pk_test_ for test mode, sk_live_ and pk_live_ for production.

Mixing keys is the most common reason a valid test card suddenly returns a decline during a release check.

Can I use real card numbers in a test environment?

Never. Real card data belongs only in a PCI DSS compliant production flow, and test environments rarely meet those controls.

Keep a fixture file of published test numbers, rotate it with each test-plan revision, and label entries by expected response instead of by version number. That way a "v7" or "v8" label stays harmless metadata and the CVV stays a fixed, documented placeholder.