In the 2Checkout sandbox, the CVV on a test card is almost always any three digits. Type 123 and move on. Some accounts list a specific test value next to each test card number in the sandbox documentation, so if 123 gets rejected, that table is your first stop. There is no real CVV to match because no real bank is involved in the request.

2checkout cvv test card

What a test card actually is

A test card is a card number your payment processor publishes so developers can run charges without moving money. 2Checkout, now part of Verifone, has offered a sandbox environment for years for exactly this purpose. The numbers look like card numbers. The expiration dates are fake. The CVV field exists because the real checkout form has one, and the gateway still checks the format on the way in.

Test 2Checkout CVV

Which CVV value do you enter?

• Any three digits typically works. 123 is the default most people reach for first.
• For Amex-style test numbers, use four digits, since Amex CVVs are four digits long in production too.
• Some sandbox setups tie a specific CVV to a specific outcome, like a CVV mismatch decline. Check the test card table in your account.

If the sandbox rejects every CVV you try, the problem is usually the card number or the environment key, not the three digits.

2checkout cvv test card

Why your real card fails in sandbox

Sandbox endpoints do not talk to issuing banks. A live card number sent to a sandbox endpoint either gets declined or gets treated as a test number, depending on how the gateway is configured. The reverse holds too. Published test numbers get declined right away on the live endpoint, and forcing them through is a good way to get your merchant account flagged.

more on this topic

Reading the response you get back

Watch the response code, not the approval. Sandbox setups let you trigger specific outcomes: approved, declined, CVV failure, AVS failure. That is the whole point of the environment. You want to see how your code handles each one before a real customer touches the form.

About buying CVVs

Nobody needs to buy a CVV to test a payment integration. Test numbers are published by processors for free. Buying, selling, or using someone else's card data is card fraud in every U.S. state and in most countries, and the card networks treat CVV as sensitive authentication data that merchants are not allowed to store after authorization. If a site is selling CVV data, what it is selling was stolen, and the buyer ends up holding the liability.