The Razorpay CVV test API is simply Razorpay test mode, where CVV verification is switched off. Any three-digit CVV works, any future expiry date works, and the API response depends on the test card number you send. No real card is charged and no network authorization runs.

razorpay cvv validation test

What does Razorpay do with CVV in test mode?

Test mode skips the card network. Because no issuing bank is contacted, CVV and address checks never run. The gateway checks one thing only: that a 3-digit value arrived in the CVV field.

razorpay cvv test

The value 123 and the value 999 behave the same way. There is no shortlist of approved test CVVs to memorize and no registration step.

more on this topic

• CVV: any 3 digits for Visa and Mastercard test cards
• Expiry: any date in the future
• Name on card: any string
• 3D Secure: simulated by specific test cards in the docs

Which test card numbers work with any CVV?

Razorpay publishes a small set of test cards. The two used most are 4111 1111 1111 1111 (Visa) and 5267 3181 8797 5449 (Mastercard). Both return a successful payment when you pair them with a random CVV.

razorpay cvv test integration

The docs also list cards that trigger a failed payment or a 3D Secure challenge. Treat that list as a moving target, since Razorpay adds and retires simulations over time.

• 4111 1111 1111 1111, Visa, success path
• 5267 3181 8797 5449, Mastercard, success path
• Other documented cards, failure and 3DS paths

Test keys vs live keys

Every Razorpay account ships two key pairs. A Key ID starting with rzp_test_ hits the sandbox and accepts test cards with any CVV. A Key ID starting with rzp_live_ hits the card networks and will reject every test card.

Mixing them is the top cause of a "card declined" error during development. Check the key prefix before you debug anything else.

How do you run a test payment through the API?

1. Open the Razorpay Dashboard and switch the toggle to Test Mode.
2. Copy the Key ID and Key Secret from Settings, then API Keys.
3. Create an order with POST /v1/orders using the test key pair.
4. Send the test card number, any CVV, and a future expiry to your payment call.
5. Confirm the payment status in the dashboard or with a payments fetch.

Test payments sit in the Test Mode ledger and can be refunded like live ones. They never touch a bank account and no fee applies.

Why does a test payment fail even with a valid CVV?

CVV is almost never the reason. In test mode the common culprits are a live key, an expired order, or a card number stored as a string with spaces.

• Wrong key prefix, live instead of test
• Expiry date in the past
• Amount below the minimum for the currency
• Card number not stripped of dashes before the request

A 401 response points at the key secret. A 400 response points at the request body. A captured payment with the wrong status points at the card number itself.

What happens to CVV data in production?

In live mode the CVV travels to the issuer for verification and is never stored. PCI DSS Requirement 3.2 bans keeping sensitive authentication data after authorization, and that rule covers CVV, full track data, and PIN blocks.

If you use Razorpay's hosted checkout, the CVV field never reaches your server. If you build a custom form, your server sees the value for the length of the request, so keep it out of logs, queues, and databases.

Test mode vs live mode at a glance

• Card network: test mode skips it, live mode uses it
• CVV: test mode accepts any 3 digits, live mode checks the issuer record
• Money: test mode moves none, live mode settles to your account
• Keys: rzp_test_ against rzp_live_
• Fees: none in test mode

Can you buy a CVV for testing?

No. CVVs are not a product and no legitimate vendor sells them. Test CVVs come from the gateway's own documentation and work in the sandbox only.

Sites that advertise CVVs for sale are trading stolen card data. That activity falls under 18 U.S.C. 1029, the US access device fraud statute, and carries prison time. Razorpay test mode is the legal way to exercise CVV fields in code.

Checklist before you move to live keys

• Confirm every test case passes with rzp_test_ keys
• Rotate the secret and store it in a vault, not in source control
• Strip CVV from your logs and error trackers
• Handle the failure and 3DS test cases in your UI
• Re-run the same flows with rzp_live_ keys and a small real amount

Frequently asked questions

Does Razorpay validate CVV in test mode?

No. Test mode accepts any 3-digit CVV and never contacts the issuer.

What CVV should I use with 4111 1111 1111 1111?

Any 3 digits, such as 123 or 456. The result depends on the card number, not the CVV.

Can I test 3D Secure without a real card?

Yes. Razorpay lists test cards that trigger a 3DS challenge, and the docs show the password to type on the simulated page.

Are test mode payments free?

Yes. No money moves in test mode, so no fees apply and nothing settles.

Why does my test key return a 401 error?

The key secret is wrong, or the key ID and secret got swapped. Generate a new pair in the dashboard if you are unsure.

Do test payments show up in reports?

They appear in the Test Mode ledger only. Live reports and settlements stay clean.