What is a test credit card?
A test credit card is a fake card number that a payment processor publishes for use in its sandbox or test mode. It follows the same numbering format as a real card, passes checksum validation, and returns a simulated result instead of charging anyone. No money moves and no real account is involved.
How do test card numbers work?
Test numbers exist only inside a processor's test environment. When you send one through a test API key, the gateway matches the number to a predefined outcome such as approved, declined, or expired card.
Because the sandbox never touches the card networks, you can run the same transaction thousands of times. Switching to a live API key sends the same request to the real network, where a test number fails immediately.
What is the Luhn algorithm?
The Luhn algorithm is a checksum that catches typos in card numbers before a request reaches the network. Published test numbers are built to satisfy it, which is why a random 16 digit string usually fails at the form level.
Do test cards come with a CVV and expiry date?
Yes. Processors publish a matching CVV and a future expiry date for each test number. You can also swap those values to force specific errors, such as a CVV mismatch or an expired card response.
Common test card numbers by network
Most processors publish a short list covering the major card brands. The exact digits vary by provider, but the pattern is consistent across gateways.
- Visa: 4242 4242 4242 4242
- Mastercard: 5555 5555 5555 4444
- American Express: 3782 822463 10005
- Discover: 6011 1111 1111 1117
Confirm the current list in your own processor's documentation, since numbers and their mapped responses change over time.
What should you test in a payment flow?
Test cards are most useful for exercising the branches your code will hit in production. A short checklist covers most of the risk.
- Successful authorization and capture with a standard approval number.
- Soft and hard declines, including insufficient funds and do-not-honor responses.
- CVV mismatch and postal code mismatch errors.
- Expired card and invalid number errors.
- 3D Secure challenge flows and authentication failures.
- Refunds, partial refunds, and voids.
- Webhook delivery, retries, and idempotency on duplicate events.
- Currency conversion and recurring billing cycles.
Are test credit cards legal to use?
Yes, inside a sandbox and for software testing purposes. They are not valid for real purchases and any live payment network will reject them.
Using a real card number that does not belong to you, in a test environment or anywhere else, is card fraud and is illegal in the United States and most other countries. PCI DSS also requires that live cardholder data never be copied into test or development systems.
Test cards compared with real card validation
Test numbers verify that your integration handles each response correctly. They cannot tell you whether a real card is valid, funded, or authorized, and they should never be used to probe live accounts.
When you need production-like data, use tokenized records or synthetic data sets approved by your compliance team.