Home / Fraud Library / Operational Techniques / BIN Attacks and Card Testing
Operational Techniques

BIN Attacks and Card Testing: How They Work and How to Stop Them

Operational Techniques ~6 min read The Fraud Practice Library

A BIN attack, also called an enumeration attack or card testing, is an automated attempt to find valid card details by trying many combinations against a merchant's checkout. In a classic BIN attack, the attacker targets one issuer's cards, runs thousands of low-value attempts, and keeps whatever the issuer approves. The merchant pays the cost: fees on every attempt, wrecked decline rates, issuer attention, and chargebacks later. Visa describes enumeration as a rapid, brute-force card testing attack at scale. This guide explains the signs and the defenses. For the basics, see the credit card BIN checks guide.

How a BIN attack works

In a classic BIN attack, bots submit many payment attempts that share the same BIN, varying the remaining details. Each approval confirms a working card; each decline is thrown away. The cards that pass are then used elsewhere or sold. They favor places where checking is cheap and friction is low:

  • Donation pages and other low-price checkouts.
  • Gift card and top-up purchases.
  • Free trials and $0 or $1 card authorizations.
  • "Add a card" screens on user accounts.

Two kinds of card testing

Not all card testing is guessing. A classic BIN attack generates candidate card numbers within a BIN range. List validation checks cards that are already stolen, from a breach, skimmer, malware or phishing kit, before anyone spends them, so the fraudster knows which ones still work. Both look like a run of small authorizations at your checkout, but the second changes how you should think about timing.

In a myNetWatchman analysis of 18.8 million tested cards (June 2023 to September 2026), 81.9% were tested on exactly one day and never seen again. A defense that waits for a second sighting never fires on most cards, so act on the first one where you can. The same research found testing concentrated on payment gateway APIs, donation pages, form builders, small merchant checkouts and purpose-built card checker services, which is why even a site with no obvious fraud problem can be used. Their data is a sample of global card testing rather than a census, and it may include some generated numbers alongside genuinely stolen ones.

  • Inventory every public form that takes a card (donations, registrations, renewals), assign an owner, and watch decline rates on each the way you watch your checkout.
  • Treat repeated attempts on one card number with varying expiry and CVV values as a distinct pattern: someone holding a partial card record and completing it.
  • Measure response in hours, not days, for your own alerts and for any intelligence feed you buy.

For the broader case that the testing stage is where intent is confirmed but the loss has not yet happened, see myNetWatchman's special report, The Economics of Card Testing (free, registration required). myNetWatchman is a card-intelligence vendor, so read its conclusions with that in mind.

Why it matters to your business

  • Cost per attempt: authorization and gateway fees on every try, approved or not.
  • Decline rates: a flood of declines can damage your standing with issuers and acquirers and lower approval rates for real customers.
  • Chargebacks: some tested cards will succeed and later come back as fraud disputes.
  • Network programs: Visa's VAMP includes enumeration criteria, so a card-testing spike can put your acquirer, and in turn you, under scrutiny long before chargebacks show up. See Visa's VAMP program.

Signs you're being tested

  • A sudden spike in payment attempts with no matching rise in traffic or marketing.
  • Average order value collapses toward near-zero as small test amounts flood in.
  • Decline rate jumps, often with decline reasons such as invalid card number, expiry or security code mismatch.
  • Many different cards from one device, IP address or session, sharing the same BIN.
  • Machine-like cadence: attempts seconds apart, little browsing before checkout, traffic from hosting or proxy networks.

Defenses that work

  1. Bot controls on the payment page. Rate limiting, a web application firewall and a challenge step (such as CAPTCHA) on payment and add-card forms.
  2. Velocity limits. Cap payment attempts per IP, device, session, account and BIN over short windows, and lock after repeated failures (velocity of use, device identification).
  3. Always collect CVV and address. Never skip CVV and AVS, and treat repeated mismatches as a risk signal.
  4. Don't expose cheap card checks. Protect $0 or $1 authorizations, require login to add a card, and consider a minimum order amount where it fits.
  5. Alert on the metrics. Watch attempts and decline rate in real time, overall and by BIN, with alerts that reach a person fast.
  6. Step up on risk. Add authentication such as 3-D Secure for suspicious traffic rather than for everyone.
  7. Work with your acquirer and gateway. They can see patterns across merchants and may offer blocking tools. Report the attack.

Prefer rate limits and challenges to permanently blocking a whole BIN range. Honest customers share those BINs, and attackers move to a new range quickly. For where BIN data fits in broader rules, see using BIN data in fraud rules.

After an attack

  • Review the orders and stored cards that did succeed and consider extra checks before they ship or renew.
  • Watch for chargebacks over the following weeks, and route them to the right team.
  • Tune the limits that would have stopped it earlier, and keep notes for your acquirer.

Learn to diagnose card testing from your data. Lesson 3 of our Advanced Chargeback Analytics course shows the signature of an enumeration attack in your transaction data and how to build a monitoring program around it.

Want a second pair of eyes on your BIN and card-testing controls? Talk to a senior consultant: vendor-neutral, no junior hand-offs. See our consulting services.