Answer
A card test transaction is an authorization request sent to a payment processor sandbox using a published test card number. It moves no real money. Version markers like v4 usually name an internal test suite revision, not a card feature.
Testing a real card number that belongs to someone else is fraud. In the US that falls under 18 U.S.C. 1029. Processors and card networks treat it as account takeover or carding, and they log the attempt.
Card Test Transaction v9: Meaning, Fraud Signals, and Legal Reality
What happens during a test authorization
- The client posts card number, expiry, CVV, and amount to the processor endpoint.
- The processor routes the request to a sandbox, not the card network.
- The sandbox returns a response code, an auth ID, and a timestamp.
- Your system stores the response and fires a webhook.
Sandbox responses are deterministic. A test card ending in 0002 always returns a decline. A card ending in 4242 returns an approval. Behavior is fixed by the processor, so results repeat.
Card Test Transaction V8: A Comprehensive Guide to Buying CVV
Where test numbers come from
Stripe, Adyen, Braintree, and authorizers such as Elavon publish test card tables in their developer docs. The numbers pass checksum checks so validation logic behaves the same as production. None of them map to a live account.
Amounts and voids
Test captures store a ledger entry inside the sandbox. Nothing settles to a bank. A void or refund in the sandbox reverses the entry. Run the full cycle: authorize, capture, refund, then confirm each state in your dashboard.
Response codes worth testing
- 05: do not honor
- 14: invalid card number
- 51: insufficient funds
- 54: expired card
- CVV mismatch
- AVS mismatch on street or ZIP
Map each code to a customer-facing message. Codes that reach production usually arrive with the same text a sandbox returns.
Version markers
Internal labels such as v4 do not change how a processor reads a request. Ask your team what the label covers. No public standard defines it.