Card testing is a fraud procedure in which someone runs a batch of small charges against a payment gateway to learn which stolen card numbers still work. The tester reads the approvals and declines, then keeps or sells the live numbers. Merchants see it as clusters of tiny orders, a spike in declines, and a wave of chargebacks that lands weeks later.

more on this topic

How does the card testing procedure work?

The procedure is a filter. Someone holds a list of card numbers and needs to sort the live ones from the dead ones before selling them or cashing out.

credit card check protocol

The filter runs through a merchant's checkout. Small amounts, digital goods, fast delivery. Each attempt returns an answer from the gateway: approved or declined, often with a reason code attached.

credit card check protocol

What separates the card testing procedure from ordinary fraud is volume. One operator can push hundreds or thousands of attempts at a single store in an hour, and most of those attempts never turn into a real sale.

more on this topic

What does card testing look like from the merchant side?

Risk teams watch two layers: the transaction stream and the order data behind it. Both leave marks.

Signals in the transaction stream

  • Many attempts from one IP address or a small set of addresses within minutes.
  • Order totals that repeat at the same low amount, often under $5.
  • Decline rates that jump far above the store's normal baseline.
  • Card numbers that fail CVV or address checks yet still return a soft approval.
  • Traffic spikes at odd hours with no matching ad campaign or email send.

Signals in the order data

  • Email addresses built from random strings on free providers.
  • Several cards tried on one account in a short window.
  • Digital goods bought in bulk and delivered to a single address.
  • New accounts that place multiple orders before any browsing activity.

Which stores get targeted?

Low-value digital goods sit at the top of the list: gift cards, game credits, subscriptions, donation pages. They deliver fast, so a live card turns into value before the real cardholder checks a statement.

Stores with thin checkout friction get hit again. Attackers keep notes on sites that approve without a CVV check, and those sites stay on the list until someone closes the hole.

Small merchants matter here. A store processing a few hundred orders a day has no baseline for comparison, so a burst of 40 test charges looks like a good afternoon.

What does card testing cost a merchant?

The visible cost is interchange and gateway fees on attempts that never ship. The bigger cost arrives four to eight weeks later as chargebacks.

Each approved fraudulent order turns into a dispute. Once the chargeback ratio crosses the network thresholds, the account lands in a monitoring program with fines attached, and some processors drop the merchant outright.

There is a second bill too. Payment providers price in risk, so a store with a bad ratio pays more per transaction or gets moved to a rolling reserve.

How do merchants block card testing?

  1. Rate limit the checkout. Cap attempts per IP, per card, and per session.
  2. Turn on CVV and address verification, and make both hard fails instead of warnings.
  3. Add a challenge to low-value orders, such as a CAPTCHA or a 3-D Secure step.
  4. Block known bad IP ranges and disposable email domains at the form level.
  5. Alert on rapid changes in decline ratio for each checkout endpoint.
  6. Set a minimum order value for instant digital delivery, or require account age.

None of these steps stops every attempt. Together they raise the cost of each try, which is the point. A tester with 5,000 numbers moves on when 4,900 of them fail.

What should a merchant do after an attack?

  1. Pull gateway logs for the window and tag every attempt from the offending IPs and devices.
  2. Void or refund any order that shipped during the burst.
  3. Raise friction on the affected endpoint before opening it again.
  4. Report the incident to the payment processor, and to IC3 if money moved.

Is card testing illegal?

Yes. In the US, using stolen card numbers falls under wire fraud, access device fraud (18 U.S.C. § 1029), and identity theft statutes. Holding or selling card numbers is a separate offense on its own.

Testers leave a record. Gateways log IP addresses, device fingerprints, timing, and the cards tried, and processors keep those logs for years.

Frequently asked questions

How fast does card testing happen?

A single burst can run for minutes. Some campaigns spread attempts across days to stay under per-hour rate limits.

Can a store block card testing without hurting real customers?

In most cases, yes. Rate limits and CVV checks hit automated traffic far harder than they hit a person buying one item.

Does 3-D Secure stop card testing?

It removes most of it. The cardholder's bank gets a say in the decision, and a stolen number with no matching device tends to fail the challenge.

What is the difference between card testing and carding?

Carding is the broader crime of using stolen card data to buy goods or move money. Card testing is the check that runs first, to sort live numbers from dead ones.

Do testers target physical goods?

Rarely, because shipping creates a paper trail and a delay. When it happens, the orders tend to go to freight forwarders or vacant addresses.