A test credit card is a card number that a payment processor publishes for use only in its sandbox or test mode. It passes the same format checks as a real card, so a developer can run charges, declines, refunds, and authentication flows without moving live money. Test cards do not work in production, cannot be used to buy anything, and are not tied to any person's account.

fake credit card

What a test credit card actually is

A test credit card looks like an ordinary card number: 16 digits for Visa and Mastercard, 15 for American Express, plus an expiry date and a card verification value. The difference is where it lives. Test numbers exist inside a gateway's sandbox environment, which is a separate copy of the payment system that talks to simulated banks instead of real ones.

credit card tester

The most widely known example is 4242 4242 4242 4242, a Visa test number that appears in the documentation of several major gateways. Similar numbers cover Mastercard, American Express, and Discover, plus regional card schemes.

fake credit card

Why payment processors publish test cards

Every payment integration has failure paths, and those paths are hard to exercise with a real card. Test cards let a developer choose the outcome on purpose:

read more

• Approval: a card that always authorizes, so the happy path can be verified end to end.
• Decline: a card that always returns a generic decline, useful for error messaging.
• Specific errors: cards mapped to insufficient funds, expired card, incorrect CVC, or processing failure.
• Authentication: cards that trigger a 3D Secure challenge, so the redirect and return flow can be tested.
• Refunds and partial captures: transactions that behave like live ones once they are created.

Any card number that passes the Luhn checksum and falls inside a recognized issuer range will survive basic client-side validation, which is exactly why test numbers are built that way.

How test card numbers differ from real ones

Three differences matter in practice.

1. They are not linked to an account. No bank issued them and no balance backs them.
2. They only respond in test mode. Sent to a live endpoint, they are rejected.
3. Their CVC and expiry are usually arbitrary. A sandbox may accept any valid-format CVC, or it may require a specific value.

Because of this, a test credit card cannot be used to purchase goods, and a real card number cannot be substituted into a sandbox to simulate one.

Common test scenarios you can trigger

Most gateways document a table that maps each test number to a result. Typical entries include an always-approved card, a card that fails authentication, a card that returns a hard decline, and a card that succeeds only after a challenge. Some gateways also provide test cards for wallet flows and for installment or recurring billing.

Always read the documentation for the specific processor and account region you are integrating. Test numbers are not portable between gateways, and a number that approves in one sandbox may return an unknown-card error in another.

Using test cards without breaking rules

• Keep test credentials out of production code and production keys out of test code.
• Never enter a real card number into a sandbox, and never enter a test number into a live checkout.
• Store test data separately so it does not mix with customer records.
• Review local rules on payment testing if you handle card data at all.

Buying, selling, or using real card numbers that belong to someone else is illegal in the United States and most other countries. Test cards exist so that no real card is needed during development, which is the entire point of keeping them in a sandbox.