The short answer

You do not buy a CVV for a Razorpay test integration, and you cannot. Test mode ships with the answers built in: generate a test key pair from your Razorpay dashboard, use one of the published test card numbers, type any 3 digit value (4 digits for American Express) into the CVV field, and the sandbox will authorize the payment. No money moves, no cardholder data is touched, and nothing needs to be sourced from a third party. Anyone offering to sell you live CVV data is selling stolen payment credentials, which is a federal offense in the United States and most other jurisdictions, and using one against a live gateway ties your account to that crime.

razorpay cvv test integration

What test mode really does

Razorpay runs two separate environments behind the same API surface. Live keys move real money and validate real cardholder data. Test keys route every request to a simulator that answers with canned outcomes. The simulator reads the card number you send, matches it against a table of test PANs, and returns a success or a specific failure based on which number you chose. The CVV is accepted as long as it is the right length, because in test mode there is no issuer to check it against.

razorpay cvv validation test

Setting up a test integration

1. Switch the dashboard to Test Mode and copy the key ID (it starts with rzp_test_) and the key secret.
2. Keep the key secret on your server only. Never ship it to a browser or a mobile bundle.
3. Create an order server side with the amount as an integer in the smallest currency unit, for example paise when the currency is INR.
4. Pass the order ID into Razorpay Checkout along with the public key ID.
5. Verify the returned signature on your server using an HMAC SHA256 digest of order_id, a pipe character, and payment_id, keyed with your key secret.
6. Handle the payment.captured and payment.failed webhooks so your order state does not depend on the browser staying open.

Where the CVV sits in the flow

Checkout collects the card number, expiry, and CVV in an iframe that Razorpay controls. The CVV travels to the gateway as part of the authorization request and is discarded after the response. Your server should never see it, log it, or store it. That rule comes from PCI DSS and it applies in test mode as well, because code written against a test build is the code that ships.

Razorpay CVV Test Tool

Parameter bands worth knowing

• CVV length: 3 digits for Visa, Mastercard, and Discover. 4 digits for American Express.
• Expiry: any future MM/YY in test mode, though the published test cards usually list a fixed date.
• Amount: integer, smallest currency unit, no decimal point. A decimal here is the most common cause of a 400 response.
• Currency: INR for domestic Indian accounts, with others available depending on your account configuration.
• Signature: 64 character lowercase hex string from HMAC SHA256.

Pitfalls

• Mixing keys. A test key ID with a live key secret fails in ways that look like a CVV problem but are not.
• Assuming a test CVV maps to a live one. It does not. Every sandbox value is inert.
• Storing the CVV in your database, even in a test table, because that code path tends to survive into production.
• Skipping server side signature verification and trusting the client callback.
• Treating a green test run as proof that production will behave the same. Issuer declines, 3D Secure, and risk rules only exist in live mode.

FAQ

Can I buy a CVV to run a Razorpay test?

No. There is no legitimate market for CVV values, and test mode does not require one. Use 123.

Razorpay Credit Card CVV Validation Test: Guide

Which test card should I start with?

Use the Visa test PAN listed in the Razorpay dashboard, 4111 1111 1111 1111, with any future expiry. Swap in the other listed numbers to trigger specific failure codes.

Do test transactions cost anything?

No. Test mode settles nothing and moves no funds.