card testing
automated scripts running large volumes of small transactions against stolen card numbers to find which are still active, before using the confirmed-live ones for bigger fraudulent purchases elsewhere.
how it plays out
- the fraudster gets a batch of card numbers.
from a breach, a card shop, or numbers generated from a known BIN.
- a script runs tiny charges on a site with light checkout controls.
donation pages and small digital goods are common picks.
- the approvals show which cards are live.
the declines are throwaways. the approvals are the product.
- the live cards get used or resold for bigger purchases somewhere else.
the tested site usually isn't where the real loss happens.
- the tested merchant is left with the cleanup.
auth fees, disputes on the small charges, and a decline spike their processor will notice.
why it's hard to catch
every attempt is tiny and looks like a normal small order on its own. it's the volume and the pattern that give it away.
what analysts look for
- a sudden spike in declines over a short window
- lots of different cards from one device, IP or session
- many small orders on cards that share a BIN
- billing details that change on every attempt
on Watch, month by month
items tagged card testing on Stingray Watch since aug 2026.
see the numbers
| month | items |
|---|---|
| aug 2026 | 1 |
| sep 2026 | 1 |
| oct 2026 | 1 |
| nov 2026 | 0 |
recent on Watch
see everything new on Stingray Watch
related terms
Stingray keeps the case, the pattern and what you figured out in one place, so the next analyst starts where you left off.