A test transaction card is a synthetic card number issued by a payment processor for use in a sandbox or staging environment. It behaves like a real card at checkout - the same number format and the same expiry, security-code, and billing-address fields - but no money moves and no bank account is ever involved. Developers rely on these cards to confirm that an integration handles approvals, declines, refunds, and error states correctly before a store goes live.

Key Features

• Processor-issued numbers that mirror real Visa, Mastercard, and Amex formats
• Predictable response codes for approvals, declines, and specific failure conditions
• No funds attached, so no charge can ever reach a real consumer account
• Compatible with hosted checkout pages, mobile SDKs, and direct API calls
• Supports testing of 3-D Secure challenges, AVS checks, and CVV verification flows
• Reusable across an unlimited number of sandbox transactions
• Available in several currencies and card brands for regional testing
• Documented alongside each processor's API reference and sample code

Materials and specifications

A test transaction card is data rather than plastic. Each published entry usually lists a card number, an expiry date, a security code, and sometimes a suggested postal code or ZIP used to trigger a particular address-verification result. Processors document which number produces which outcome, so a developer can deliberately simulate a successful authorization, an insufficient-funds decline, an expired-card error, or a failed security-code check. Because the numbers are public and inert, they carry no cardholder data and cannot be used against a live account.

Delivery, support, and returns

These credentials are digital and are released through your payment provider's developer dashboard and documentation, so there is no physical shipment and no tracking to wait on. Access is immediate once your sandbox account is created, and any question about a specific number's behavior is answered by the processor's own developer support team, which also maintains the lists as APIs change.

What is a test transaction card used for?

It is used to test payment integrations end to end: checkout forms, tokenization, subscriptions, refunds, and webhook handling. Testing with these numbers lets you catch logic errors without ever touching a real card.

Can a test card be used on a live site?

No. Sandbox cards only work against a provider's test mode. A live payment account rejects them, and using real card numbers in a test environment is a serious compliance violation.

Where do test transaction cards come from?

They are published free of charge by payment processors such as Stripe, PayPal, Adyen, and Braintree in their developer documentation. They are not a product anyone sells, and a legitimate one never includes real account data.