Testing a credit card online means running a payment through a payment gateway's sandbox mode with a published test card number to confirm that your checkout form, decline handling, and 3D Secure flow work before real customers pay. Test numbers are issued by the processor itself, work only in test mode, and never touch a live bank account.
What is a test credit card number?
A test credit card number is a fake 16-digit PAN that a payment processor publishes for developer use. It follows the same format as a real card, including the ISO/IEC 7812 issuer prefix and the Luhn check digit, so your own validation code accepts it as well formed.
What Is a Credit Card Test? Card Testing Fraud Explained
In sandbox mode the expiry date can be any future month and the CVC can usually be any three digits. Some processors restrict those fields to specific values, so check the sandbox docs for your gateway.
credit card test for beginners
Where do you find test card numbers?
- Stripe: a documented list that covers Visa, Mastercard, American Express, Discover, and JCB.
- PayPal and Braintree: sandbox cards created in the developer dashboard.
- Adyen: a test card mapped to each possible result code.
- Square and Authorize.Net: sandbox credentials plus a short list of test PANs.
Every one of these numbers is public and safe to paste into a test environment. None of them can be charged for real money.
Credit Card Test for Beginners Guide
How do you run a test payment step by step?
- Switch your API keys from live mode to test or sandbox mode.
- Open your checkout page in a private browser window so no live session is cached.
- Enter a test PAN, a future expiry, and a CVC.
- Submit the order and read the response object, not just the screen message.
- Repeat with a decline card and a 3D Secure card to cover the failure paths.
Which test numbers produce which results?
- 4242 4242 4242 4242: successful Visa charge.
- 4000 0000 0000 0002: generic decline.
- 4000 0000 0000 9995: insufficient funds.
- 4000 0000 0000 3220: 3D Secure authentication required.
- 5555 5555 5555 4444: successful Mastercard charge.
- 3782 822463 10005: successful American Express charge.
These values come from public gateway documentation and are tied to sandbox behavior only. A processor may add or retire test numbers, so confirm against current docs before you rely on a result code.
Why does the Luhn check matter in testing?
The Luhn algorithm is the final check digit rule that catches most typos in a card number. If your form rejects 4242 4242 4242 4242, the bug is almost always in your own client-side validation rather than the gateway.
Testing a card with a deliberately broken check digit is a quick way to prove that your validation and error messaging work.
Why is my test card being declined?
Common causes are keys still in live mode, a test card used against a live endpoint, an expired test expiry date, or a gateway that expects a specific CVC value. Declines triggered by a decline test card are the expected result, not a bug.
If a real charge appears in your dashboard, you were not in sandbox mode at all.
Is a test card the same as a real card?
No. A test card number resolves only inside a sandbox and cannot authorize against a real account. Real card data belongs to its issuer and cardholder, and using numbers you do not own to check whether an account is live is carding, which is a federal crime in the United States under laws such as the Computer Fraud and Abuse Act.
Test cards exist so that developers can ship reliable checkout flows, and that is the only legitimate use for them.