Card test mode is a sandbox environment that lets you run a checkout, subscription, or refund flow with simulated card numbers instead of a real funding source. It is the standard way to confirm that an integration handles approvals, declines, and edge cases before you switch to live credentials. Every major processor ships one, and the numbers it accepts are published for testing only.
Key Features
- Predefined test card numbers for Visa, Mastercard, American Express, and Discover that return predictable results.
- Simulated responses for declines, expired cards, insufficient funds, and mismatched CVC or postal code.
- 3-D Secure and SCA challenge simulation, including both authentication success and failure paths.
- Separate test API keys and webhook endpoints so sandbox events never reach production systems.
- Support for tokenization, recurring billing, partial refunds, and dispute workflows.
- Authorize-only and capture-later modes for testing delayed settlement logic.
- Error injection and configurable response delays to exercise timeout and retry handling.
- No real funds move and no genuine cardholder data is stored or transmitted.
Materials and Specifications
Test mode is delivered through the same REST and GraphQL APIs, hosted checkout pages, and mobile SDKs as the live environment, so code written against it carries over with only a credential change. Environments are isolated per merchant account, test data can be purged on request, and working with simulated values keeps PCI scope unchanged because no real account numbers are involved. Many processors also provide a browser dashboard for replaying transactions and inspecting raw payloads.
Delivery and Returns
Access is digital: credentials appear in your account dashboard or arrive by email shortly after purchase, and there is nothing to ship or return physically. If activation fails or the environment cannot be provisioned, support will issue a full refund within the stated window, and unused subscriptions can be cancelled at any time.
What is card test mode used for?
It is used to build and debug payment flows such as checkouts, refunds, subscriptions, and webhooks without moving real money. Developers verify that each response type is handled correctly before going live.
Does test mode cover refunds and subscriptions?
Yes. Most processors let you create a test charge, refund it in full or in part, and run recurring billing cycles on an accelerated schedule. Dispute and chargeback simulations are usually available as well.
Can test cards be used on a live site?
No. Test numbers are rejected by production endpoints, and using them outside a sandbox breaks processor terms. Test mode exists strictly for integration work on non-production systems.