Razorpay Test CVV: Which CVV Works in Test Mode

Short answer

In Razorpay test mode, use CVV 123 with the published test card numbers. The sandbox does not compare the three digits against the card, so any valid three digit value passes. The field still has to be filled because checkout validates the format before it sends the request. Test mode runs on a separate environment from live mode and never contacts a real issuing bank.

Check the current Razorpay test card page before you build a test suite. Card numbers and their assigned outcomes change, and a value that worked last quarter may behave differently now.

Test card numbers and their CVV

Razorpay keeps a small set of sandbox cards. Each card number is wired to a fixed result.

• 4111 1111 1111 1111 (Visa): payment succeeds. CVV 123.
• 5267 3181 8797 5449 (Mastercard): payment succeeds. CVV 123.
• 5104 0600 0000 0008 (Mastercard): payment succeeds. CVV 123.
• 4000 0000 0000 0002 (Visa): payment fails. CVV 123.
• 4000 0000 0000 3220 (Visa): triggers the 3DS challenge flow. CVV 123.

Pair each number with any future expiry date, such as 12/30, and any cardholder name. If the current documentation lists a card with a specific CVV, that number takes priority over 123.

How to run a test payment

1. Log in to the Razorpay Dashboard and move the mode toggle from Live to Test.
2. Open Settings, then API Keys, and copy the test mode Key ID.
3. Point your staging build at the test key instead of the live key.
4. Load checkout and enter one of the test card numbers above.
5. Type 123 in the CVV field.
6. Enter a future expiry date and any name.
7. Submit the payment and confirm the result under Payments in the Dashboard.

Why the CVV value rarely matters in test mode

CVV checks happen during authorization, when the acquirer asks the issuing bank to confirm the code matches the card. Test mode swaps the bank for a simulator. That simulator returns the outcome attached to the card number, so a card set to fail fails with any CVV and a card set to succeed succeeds with any CVV. The only rejection you will see from the CVV field itself is a format error.

Common test CVV problems

• A two digit or four digit entry on a Visa or Mastercard test card: the field blocks submission.
• An American Express test card: the four digit code belongs in the same CVV field.
• Live keys with test card numbers: the payment declines, because those numbers do not exist in production.
• An expiry date in the past: checkout stops the form before the request is sent.
• A blank CVV: checkout treats the field as required and will not submit.

CVV rules that carry into live mode

Once you move to live keys, CVV handling stops being a testing question. PCI DSS forbids storing the card verification value after authorization, and it must not appear in logs, databases, or support tickets. Razorpay checkout collects the CVV on its own page and hands your server a token, so the raw value never reaches your code. If you build a custom payment form, keep that boundary intact and confirm your setup with your acquirer before you accept real cards.