Short answer: A CVV test number is a dummy card verification value that a payment processor publishes for sandbox testing. It works only in test mode. It cannot authorize a real charge, and it has no value on a live payment network.
What a CVV test number is
Payment processors such as Stripe and PayPal provide test card numbers with matching test CVVs so developers can exercise checkout forms, tokenization, and error handling without touching real card data. A test CVV is typically three digits, such as 123, and is paired with a published test card number. The test environment accepts these values and returns simulated results. The production environment rejects them.
Where legitimate test numbers come from
Get test CVVs only from the official developer documentation or dashboard of a payment processor. Stripe publishes test card numbers, including 4242 4242 4242 4242, and accepts any three-digit CVV in test mode for many scenarios. PayPal's sandbox provides its own test card values. These sources are free, documented, and safe to use in development.
How to use a CVV test number in a payment test
- Open your payment processor's developer dashboard and switch the account or API keys to test mode.
- Copy a published test card number and its matching test CVV from the processor's official test documentation.
- Enter the test card number, a future expiry date, and the test CVV into your checkout form.
- Submit the payment and confirm that your integration returns the expected simulated result, such as a success code or a specific decline reason.
- Repeat the test with a decline test card to verify that your error messages and retry logic work.
- Switch back to live mode only after all test cases pass and you have removed test credentials from production code.
What not to do
Do not buy, sell, or use real CVV numbers. Real CVVs are sensitive authentication data. PCI DSS requires that they not be stored after authorization, and buying or selling stolen card data is illegal. A CVV test number is not a real card value, and no legitimate processor sells CVVs for live use. If a site offers to sell CVVs, treat it as a fraud risk and report it.
Prerequisites for safe payment testing
- A sandbox or test account with a payment processor.
- Access to the processor's official test card documentation.
- A staging checkout page that uses test API keys, not live keys.
- A written test plan that covers success, decline, and error cases.