The fastest route to a green checkmark in Razorpay test mode is the Visa success card, 4111 1111 1111 1111, paired with a test-mode key pair, an expiry date in the future, and a three digit CVV. It wins on the three criteria that decide every sandbox card: it clears the simulated bank step, it works with both the Orders API and the hosted checkout, and it needs nothing beyond a test key to start. What follows covers how the Razorpay test card set works, which numbers to reach for, and the setup errors that make a working card look broken.

What counts as a Razorpay test card

A Razorpay test card is a number Razorpay publishes for sandbox transactions. It routes through a simulated bank instead of a live one, so no money moves and no real account is touched. The set lives in Razorpay's documentation and changes only when the provider adds new scenarios.

Three properties apply to every number in the set:

• It works only while your integration runs on test keys. Live keys reject sandbox numbers.
• The expiry must be a future date. Razorpay validates the format, and an expired date can fail before the simulation starts.
• The CVV is a three digit value. Test mode does not check it against an issuer, so 123 is fine.

The cards cover domestic and international flows. If your checkout only offers one network, switching the network on the card is usually enough to reproduce the other path.

Visa success card

4111 1111 1111 1111

This is the number most Razorpay guides show first, and the one to try when you only need a single payment to succeed.

• Pros: clears the standard success flow and works with card, order, and payment link APIs.
• Pros: pairs with the simulated 3DS step, so you can exercise the OTP screen without hunting for another number.
• Cons: it never reproduces a decline, so failure testing needs a second card.
• Cons: it tells you nothing about network specific routing, such as Mastercard or Amex behavior.

Use it when you are wiring a new integration or confirming that a webhook fires on capture.

Mastercard success cards

Razorpay's list also carries Mastercard numbers for success, and 5267 3181 8797 5449 is among the entries developers cite most. Check the current official list before hardcoding anything, since test sets get revised and old numbers retire.

• Pros: confirms your checkout handles a second network without code changes.
• Pros: useful for regression runs after you touch validation logic.
• Cons: some Mastercard entries are reserved for specific scenarios, so a random pick may not behave like the Visa card.
• Cons: a success on one network does not guarantee the same result across every acquirer path.

Reach for these when your product supports more than one network and you want to prove that routing holds.

Failure and edge case flows

Success is the easy half. Declines, timeouts, and authentication failures are where integrations break in production.

• Razorpay documents test cards that return a decline, plus UPI test handles such as success@razorpay and failure@razorpay for the collect flow.
• For 3DS, the checkout shows an authentication screen. Razorpay's test mode guide names the OTP to enter, and the same code works on every simulated attempt.
• For webhooks, the failure path matters more than the success path. A captured payment event and a failed payment event carry different payloads, and both belong in your logs.

Test cards compared with live cards

The two are not interchangeable, and treating a sandbox pass as production proof is the most common error.

• What test cards do well: validate request shapes, response handling, retry logic, webhook parsing, and refund calls without touching real accounts.
• What they cannot do: simulate issuer risk rules, real settlement timing, chargeback handling, or the latency of a live bank.
• What changes at go live: key pair, endpoint behavior, and the compliance obligations that come with real card data.

Aim for a sandbox run that covers success, decline, and abandonment before you swap in live keys.

Setup checklist before you run a test payment

1. Flip the dashboard to test mode and copy the test key pair into your environment file.
2. Confirm your server calls the order creation endpoint with the test key before the checkout opens.
3. Disable any caching layer that could serve a stale checkout script.
4. Point your webhook endpoint at a tunnel or staging URL and log every event body.
5. Run one success, one decline, and one abandoned payment, then read the raw responses.

Mistakes that waste an afternoon

• Mixing a live key with a test card, which returns an authentication error that looks like a card failure.
• Reusing an old card number from a blog post that predates a docs revision.
• Testing only the happy path, then discovering on launch day that your decline handler throws.
• Ignoring the amount field, since some edge cases depend on the value you send.

Handling card data in a way that stays legal

Test numbers are safe to paste into tickets, chat, and code comments. Real card numbers are not. Buying, selling, or storing live card data you do not own is card fraud and carries criminal liability, and PCI DSS exists to keep genuine numbers inside a compliant environment. If you need realistic data for a demo, use the sandbox set and keep live numbers out of your fixtures, your logs, and your seed scripts.