Enter any 3-digit CVV, such as 123, on a 2Checkout test card and the sandbox will accept it. Test mode checks the length and format of the code, not whether it matches a real card, so no real CVV is needed. American Express test cards take a 4-digit code in the same field.

related article

What CVV do you enter on a 2Checkout test card?

2Checkout (now part of Verifone) never sends a test order to the card issuer. The CVV field is validated at the form and gateway layer only, then the sandbox returns whatever outcome your account is set to produce. Any digits of the right length pass.

2checkout cvv test card

• Visa, Mastercard, Discover, JCB: 3 digits, for example 123, 456, or 000.
• American Express: 4 digits, for example 1234.
• Wrong length: 2 digits or 5 digits fail form validation before the order is created.

Use 123 by default. It is the value most gateway documentation uses, and support teams recognize it on sight when you send a screenshot of a failed test.

2Checkout CVV Test Card: The Ultimate Guide

Which test card numbers work in the 2Checkout sandbox?

Verifone publishes the current test card list inside the merchant control panel. The numbers below are the standard public test numbers used across payment gateways and make a sensible starting point.

2checkout cvv test

• Visa: 4111 1111 1111 1111
• Mastercard: 5555 5555 5555 4444
• American Express: 3782 822463 10005
• Discover: 6011 1111 1111 1117
• JCB: 3566 0020 2036 0505

Pair each number with any future expiry date and a CVV of the right length. Check the list against the current Verifone docs before you hard-code anything into a test suite, because card portfolios get retired.

Does the 2Checkout sandbox check CVV and AVS?

What happens to the CVV value in test mode?

The gateway runs format validation, then returns the result configured in your sandbox settings. That is why 123, 999, and 000 all pass on the same test card. Nothing about the code is checked against cardholder data.

How does AVS behave in test mode?

Address Verification System results come from the street number and ZIP you type into the billing form. Some sandbox setups let you pick the AVS response code outright. Others return a match when the address is well formed, so enter a complete US billing address with a real-format ZIP such as 90210 if your integration insists on a match.

What does the CVV field do on a live order?

On a real transaction the issuer compares the code to the one on file for that card and returns a match, no-match, or not-processed response. Merchants see that result as part of the authorization response, not as a stored value. The code itself is never written to your database.

• Match: authorization proceeds.
• No match: the issuer declines or flags the order, depending on your rules.
• Not processed: the issuer did not check, common with some card types and regions.

This is the behavior your sandbox tests are meant to imitate, which is why a test CVV only needs to look right.

How do you force a decline in the 2Checkout sandbox?

Use the sandbox decline triggers instead of hunting for a magic card number. 2Checkout exposes order outcomes in the test settings, and several gateways accept amount-based triggers as well.

• Set the order total to the decline amount listed in your control panel.
• Switch the test outcome to declined for the next order.
• Enter a 2-digit CVV to test rejection at the form level.
• Enter an expired date to test the date check.
• Use a card type you have disabled in account settings to test the routing fallback.

Why is my 2Checkout test card rejected?

Most failures come from configuration, not from the card number. Work down this list before you file a ticket.

• Test mode is off and the request is hitting the live gateway.
• The expiry date is in the past, or the year format does not match the field.
• The card brand is switched off for your account.
• The billing country does not match the order currency.
• 3D Secure is required and the test card is not enrolled.
• The billing address has no ZIP and your AVS rule needs one.
• You reused an order reference that already completed.

Can you use a real card CVV for sandbox testing?

No. Real card numbers and CVVs are not test data, and pushing a live card through a sandbox breaks card network rules. In the US, using card details you do not own is fraud under federal law and state statutes. Keep test traffic on the published sandbox numbers.

How do you build a CVV test matrix?

A short matrix catches the failures that matter without turning testing into a project. Cover one pass case per card brand plus the format edges, then stop.

• Visa test card, CVV 123, future expiry: expect approval.
• Amex test card, CVV 1234: expect approval.
• Visa test card, CVV 12: expect form-level rejection.
• Visa test card, expired date, CVV 123: expect date rejection.
• Decline amount, CVV 123: expect the configured decline message.

FAQ

Is 123 a valid test CVV for 2Checkout?

Yes. Any 3-digit value works in test mode, and 123 is the most common choice. Amex test cards need 4 digits.

Does 2Checkout keep the CVV from a test order?

No. The code is not stored after authorization, and PCI rules forbid keeping it in any case. Your order logs show the result, not the digits you typed.

Do I need 3D Secure for test orders?

Only if your account is set to require it. Most sandbox accounts ship with 3DS off, so a test card plus a 3-digit CVV completes the order.

Why does my test order stay pending?

A pending status often means manual capture is on or the test amount tripped a fraud rule. Check the order detail page in the control panel for the reason code.

Do test card numbers ever expire?

The numbers stay valid, but the issuer ranges behind them change. Recheck the list in your merchant panel once a year and after any platform migration.