Answer
In the 2Checkout (now Verifone) sandbox, enter any three-digit value in the CVV field, such as 123, while using an official test card number from the developer portal. The sandbox does not validate the CVV against an issuer. Real CVV checks run only when you switch to live mode and process a real card.
Prerequisites
- A 2Checkout or Verifone sandbox merchant account with test mode enabled
- An official test card number published in the developer portal
- A test checkout page or API request you can submit
Steps
- Sign in to your sandbox merchant account.
- Confirm that test mode is active for the account or the specific checkout page.
- Open the test checkout form or prepare your API test request.
- Enter an official test card number from the developer portal.
- Enter any three-digit number in the CVV field, for example 123.
- Fill the remaining fields with test data, including a future expiry date and a test billing address.
- Submit the transaction.
- Read the response code and message in the sandbox dashboard or API reply.
Why any CVV works in the sandbox
Sandbox environments simulate payment responses. They do not send card data to a card network or an issuing bank. Because no issuer is involved, the gateway cannot check a CVV against a real card record. The field is still present so your integration can send the same request shape it will use in production.
When the CVV is validated
The CVV is validated only in live mode. At that point the gateway forwards the value to the issuer, and the issuer returns a match, no match, or not processed result. Use a real card only when you are authorized to test a live transaction, and never store the CVV after authorization.
Common sandbox errors
- Using a real card number in the sandbox instead of a published test card
- Leaving the CVV field empty when your request schema marks it as required
- Testing against a live endpoint while the account is still in test mode
- Assuming a declined sandbox response means the CVV value was wrong