How to use Fake cards for testing
- 1. Understand what “fake” means here. Public test numbers published by Stripe, Razorpay, and PayPal for developers.
- 2. Pick a processor. Use the sidebar — Stripe, Razorpay, or PayPal each has its own list.
- 3. Stay in test mode. Test keys and sandbox accounts only. Live gateways reject these numbers.
- 4. Do not fraud. Using test numbers on real merchants is not supported and may violate terms of service.
About this tool
Search queries like “fake credit card for testing” usually mean sandbox PANs, not generating random numbers to use on real sites. This page collects official test credentials and explains the legal and technical boundaries.
Official test numbers vs random Luhn cards
Processors publish specific PANs that their sandboxes recognize. A random Luhn-valid number is not a “fake credit card” that will authorize anywhere — use the Luhn tool only for format validation.
Legal and ethical use
Test PANs exist for integration development. Attempting to use them on live commerce, streaming trials, or verification bypass is fraud-adjacent. PureDevKit lists them for engineers building payment flows, not for circumventing paid services.
Code examples
Stripe Visa (success)
4242424242424242
Expiry: 12/34 CVV: 123 ZIP: 42424Razorpay domestic Visa
4111111111111111
Expiry: any future date CVV: any 3 digitsRazorpay UPI success
success@razorpayStripe PaymentIntent test JSON
{
"number": "4242424242424242",
"exp_month": 12,
"exp_year": 34,
"cvc": "123"
}