Find BIN attacks in card authorisations
Drop in card authorisations with their time and card number. See every burst on one BIN, which bursts look like card testing, and the velocity rule that would have stopped each one.
Card authorisations file
24,850 authorisations on 40 BINs were read, and 0 rows without a readable time or card number were left out.
The file is read in this browser and never uploaded, and counts are emailed only if you request the result.
A burst starts when this many attempts on the same BIN fall inside the window. The result also shows what this count would have stopped.
These are 24,000 made-up authorisations at one online shop over 14 days, with a flash sale and four attacks planted on four BINs. One attack is slow and only shows with the 1 hour window.
Likely BIN attacks
3 bursts on 3 BINs look like a BIN attack, with 670 attempts. A velocity rule of 20 attempts on one BIN within 10 minutes would have stopped 613 of them and 230 other authorisations.
Authorisations over time
Each bar is one hour of authorisations, or one day when the file is long. An attack shows as a spike on one BIN, and a sale lifts every BIN at once.
Bursts on one BIN
| BIN | Start | Length | Attempts | Approved | Declined | Signs | Verdict | Velocity rule | Stopped |
|---|---|---|---|---|---|---|---|---|---|
| 464056 | 2026-09-03 02:10 | 35 min | 420 | 49 | 88.3% | Mostly declined, Small amounts, Different cards | Likely attack | 3 attempts within 1 minute | 418 (99.5%) |
| 453047 | 2026-09-07 14:00 | 12 min | 160 | 27 | 83.1% | Mostly declined, Small amounts, Expiry dates | Likely attack | 3 attempts within 1 minute | 158 (98.8%) |
| 429139 | 2026-09-12 09:30 | 6 min | 90 | 27 | 70.0% | Mostly declined, Small amounts, CVV failures | Likely attack | 4 attempts within 1 minute | 87 (96.7%) |
| 555795 | 2026-09-06 18:58 | 63 min | 231 | 216 | 6.5% | Different cards | Busy traffic | – | – |
| 558706 | 2026-09-06 19:29 | 29 min | 57 | 57 | 0.0% | Different cards | Busy traffic | – | – |
| 558706 | 2026-09-06 19:11 | 10 min | 20 | 19 | 5.0% | Different cards | Busy traffic | – | – |
Get the result by email
Run the same velocity counts on each BIN for every authorisation, so the burst is stopped as it happens. Start your trial
How bursts are found
Count = Attempts on this BIN within the window up to this one Burst = Attempts in a row while the count holds: Count ≥ Attempts on one BIN Mostly declined: Declined ≥ 50% Small amounts: Share at small amounts ≥ 50% Different cards: Different cards ÷ Attempts ≥ 80% Expiry dates: Share tried with multiple expiry dates ≥ 20% CVV failures: Share of CVV checks that failed ≥ 30% Likely attack = Two or more signs, or all available signs Velocity rule = Most attempts outside attacks + 1
Attempts are replayed in time order, so the rule sees only earlier attempts, as it would in live use. For each BIN, the rule sits just above its busiest normal traffic in this file, so it stops no normal authorisations here but may do so on another day. A burst gives you a reason to look, and the signs show what to check next.
Find BIN attacks in authorisations
A BIN attack appears as many attempts on one BIN in a short time, mostly declined and often for small amounts. This tool groups attempts into bursts and checks each burst for signs of card testing in the file.
The result shows which bursts look like a BIN attack and the velocity rule on that BIN that would have stopped each one. Use the burst and its signs as a reason to look more closely at the authorisations.
BIN attack questions
What is a BIN attack?
A fraudster tries different card numbers that share one BIN, often using different expiry dates or CVVs. The attempts can reveal which cards work.
How can you detect a BIN attack in authorisations?
Look for a burst of attempts on one BIN, with signs such as mostly declined attempts, small amounts, or repeated expiry date and CVV attempts. This tool checks each burst for the signs available in the file.
What is card testing?
Card testing uses small attempts to find card details that work. A burst with signs of card testing looks like a BIN attack and is a reason to look more closely.
How does a BIN attack work on credit cards?
Attempts are sent using different card numbers that share one BIN. Most may be declined, while approved attempts identify cards that work.
What velocity rule would stop a BIN attack?
A velocity rule counts attempts on one BIN within a chosen window. This tool shows a rule for each burst, set just above that BIN’s busiest normal traffic in the file.