Checkout.com sandbox accepts any well-formed CVV with its standard test card numbers. Use a 3-digit value such as 100 or 123 for Visa, Mastercard, and Discover test cards, and a 4-digit CID such as 1000 for American Express. The sandbox never contacts an issuer, so the CVV check passes unless you deliberately use a test card built to simulate a decline.
What CVV value should I use with a Checkout.com test card?
Any 3-digit number works for most test PANs. Common picks in developer guides are 100, 123, and 999.
Checkout.com lists its test card numbers in the sandbox test card reference. The CVV field only has to match the format for that card type, not a stored value on file.
Do Checkout.com test cards require a specific CVC?
Standard test cards do not. The cards that simulate fixed responses are the exception.
- Standard test PANs: any valid-format CVV returns an approved CVV check.
- Simulation test PANs: documented values trigger declines, AVS mismatches, or CVV failures.
- Recurring and merchant-initiated flows: CVV is often omitted, which the sandbox also permits.
What about American Express test cards?
Amex uses a 4-digit card identification number instead of a 3-digit CVV. Enter a 4-digit value such as 1000 alongside the Amex test PAN.
How do I test a CVV mismatch or a decline?
Use the simulation cards listed in the Checkout.com test card reference. Each one returns a fixed response code so you can verify your error handling.
Confirm your integration surfaces the decline reason and does not retry the same card in a loop.
Is it legal to test with real card numbers?
No. PCI DSS forbids using live cardholder data in test environments, and CVV data must never be stored after authorization.
Only use the official test card numbers published by your payment provider.