Razorpay Test Card Number for Sandbox Payments

Answer first: the card most developers use for a successful Razorpay test payment is 4111 1111 1111 1111, a Visa sandbox number Razorpay documents for test mode. Enter any future expiry date and any three-digit CVV, and make sure you are using test API keys rather than live ones. Three criteria decide which test card you should pick: the outcome you need to simulate (success, decline, or 3D Secure challenge), the card network you want to exercise, and whether the number still appears in the gateway's current published list. Test cards are sandbox credentials, not real cardholder data, and they only behave as documented while your account is in test mode.

What a Razorpay test card actually is

A test card number is a published placeholder that routes to a simulated banking response inside the gateway's sandbox. No money moves, no issuer is contacted, and no real account is touched. Razorpay, like other gateways, maintains a short list of these numbers and ties each one to a fixed outcome so your integration can branch on success, failure, and authentication flows without waiting on a real bank.

• Pros: deterministic outcomes, instant results, repeatable test runs, no exposure of customer data.
• Cons: sandbox behavior is an approximation of production, so issuer declines, bank downtime, and network-specific quirks still have to be tested separately.

The important boundary: a real card number is never a test card. Feeding live cardholder data into a sandbox breaches card network rules and PCI DSS requirements, and it puts you in the position of storing data you are not allowed to store.

The default success card

Start here for happy-path testing. The Visa success number 4111 1111 1111 1111 is the one Razorpay's documentation leads with, and it is the number most tutorials and Stack Overflow answers reference.

Pros

• Works for standard payment, order, and capture flows.
• Recognized as a Visa card, so network-specific validation logic runs.
• Zero setup: paste it, add any future expiry, add any CVV.

Cons

• Only proves the success path, which is the least interesting path to debug.
• Tells you nothing about how your UI handles declines or authentication.

Use it when you are wiring up the payment call for the first time and just need a green result to confirm keys, order creation, and signature verification are correct.

Other networks worth keeping on hand

Razorpay's sandbox also lists Mastercard and American Express style numbers, commonly cited as 5267 3181 8797 5449 for Mastercard. If your checkout renders different forms or brand icons per network, you need at least one card per network to confirm the branch logic.

• Pros: catches brand-detection bugs, CVV length differences, and layout issues early.
• Cons: keeping a mental list of numbers is fragile, since gateways add, change, and retire test cards.

Use it when your integration displays a network logo, adjusts card field length, or validates card type before submission.

Failure and authentication scenarios

The most valuable test cards are the ones that fail. Razorpay's documentation includes numbers that reliably produce a declined payment and numbers that trigger a 3D Secure challenge, so you can build your error states, retry logic, and webhook handling against something reproducible. Always pull the current list from the dashboard or the live docs before you hardcode anything into a test suite, because these numbers change.

• Pros: lets you verify failure messaging, retry flows, and webhook signature handling without engineering a real failure.
• Cons: a declined sandbox card does not reproduce the specific reason codes a real issuer would return.

Use it when you are testing order state transitions, webhook consumers, or user-facing error copy.

How to enter the details correctly

1. Switch your dashboard to test mode and copy the test key ID and secret.
2. Load the checkout with those test credentials, not the live ones.
3. Enter the card number with or without spaces; the field strips them.
4. Use any future expiry date and any CVV of the correct length.
5. Confirm the response in the dashboard's test payments list, then check that your webhook received the matching event.

Mistakes that waste debugging time

• Mixing a live key with a test card, or the reverse, which produces an authentication error rather than a card error.
• Assuming an expired test expiry date is fine. Use a future date.
• Testing only the success card and shipping without a decline path.
• Hardcoding test numbers into production configuration files.
• Treating the sandbox as a safe place for real cardholder data.

Recommendation by use case

Building the integration from scratch: use the Visa success card. Testing brand rendering and input validation: add a Mastercard number. Testing error handling, webhooks, and retries: use a documented decline card. Testing the authentication step: use a card flagged for 3D Secure. In every case, verify the number against the current Razorpay documentation on the day you run the tests, and keep real card numbers and CVVs out of your test environment entirely.