Test Credit Card Information: Sandbox Numbers for Developers

Test credit card information is fake sandbox data

Test credit card information consists of fictitious card numbers published by payment processors for use in sandbox or test mode. These numbers never connect to a real bank account. They exist so developers can check checkout forms, error handling, and settlement logic without moving real money. A test card number, a future expiry date, and any three or four digit code are enough to simulate a payment.

related article

Where test card numbers come from

Payment gateways publish their own sets of test card numbers. Stripe documents test numbers for Visa, Mastercard, and American Express, including specific numbers that trigger declines or require authentication. PayPal publishes sandbox test cards inside its developer dashboard. Adyen and other processors do the same. The values are public and safe to copy into a test environment.

Understanding Test Card Information

How to use test card information in a sandbox

1. Open your payment provider's test-mode dashboard and locate the test card section.
2. Copy one published test card number for the card brand you want to simulate.
3. Set the expiry date to any future month and year.
4. Enter any three or four digit code in the CVV field. The sandbox accepts any value.
5. Submit the test transaction and confirm the result in the provider's test event log.
6. Repeat with decline and authentication test numbers to cover failure paths.

What test card information is not

Test card information is not real card data. It does not include a real CVV, a real cardholder name, or a real billing address. Buying, selling, or trading real card numbers and CVVs is illegal in the United States and most other countries. Test numbers are published openly, so no one needs to buy them.

Credit Card Testing Data

Legal and compliance boundaries

Use test card numbers only in a sandbox that your payment processor provides. Never enter real card data into a test system. The PCI Security Standards Council forbids storing the CVV after authorization, even for real transactions. A developer who needs to test a production checkout should use the processor's official test mode, not live card data.