Razorpay Test CVV: What to Enter in Test Mode

In Razorpay test mode the CVV field accepts any three-digit number. Most developers type 123 because it matches the documented test card 4111 1111 1111 1111. Test mode never reaches a real issuer, so the value is only checked by the Razorpay simulator and no real card is charged.

Standard test card values

• Card number: 4111 1111 1111 1111
• Expiry: any future date, for example 12/30
• CVV: 123
• Name on card: any text
• OTP at the 3DS step: use the test OTP published in your dashboard's test card list

Razorpay also publishes test cards for other networks and for failure scenarios. Each entry on that list comes with its own CVV, and the simulator accepts the listed value.

How to run a test payment

1. Sign in to the Razorpay Dashboard and switch the account to Test Mode.
2. Copy a test key ID and key secret from the API keys section, then confirm your integration uses those keys.
3. Open your checkout page and choose the card payment method.
4. Enter the test card number 4111 1111 1111 1111.
5. Enter any future expiry date.
6. Enter 123 in the CVV field.
7. Submit the form and complete the 3DS prompt with the test OTP.
8. Check the Dashboard payments list to confirm the result and inspect the response object your server received.

Why any CVV passes in test mode

Test mode routes every request to a local simulator instead of a card network. The simulator checks the card number and expiry against a fixed list, then returns a scripted response. Because no issuer is involved, the CVV comparison is not performed against a bank record, and a three-digit value such as 123 is accepted on every test card.

Rules that still apply to CVV data

• PCI DSS prohibits storing the CVV or CVC after an authorization request is processed.
• Never enter a real card number in test mode, even your own, because the test environment is not built to protect live cardholder data.
• Keep test keys and live keys in separate environments so a test CVV can never be submitted to a production endpoint.
• Log the response code, not the CVV, when you debug a failed transaction.

Common test mode errors

• Using live API keys while entering test card data, which returns an authentication or card declined error.
• Using an expired test expiry date, which the simulator rejects.
• Entering fewer than three digits in the CVV field, which fails client-side validation before the request is sent.
• Entering three digits on an American Express test card, which expects a four-digit verification value.

Testing failure paths

Razorpay's test list includes cards that trigger specific decline codes. Swap the successful test card for a failure card, keep the CVV as 123, and watch how your application handles the error response. Confirm that your code shows a readable message, leaves the order in a pending state, and does not mark the payment as captured. Repeat the run with a timeout card if one is listed so you can exercise retry logic.