The Blog

Card Testing Attacks: How High-Risk Merchants Stop Them

How card testing attacks work, the decline-data warning signs, and the layered controls high-risk merchants use to stop them.

Card Testing Attacks: How High-Risk Merchants Stop Them

What card testing attacks are and why fraudsters run them

Card testing attacks are one of the quietest threats to a high-risk merchant account, and often the first sign that something is wrong is a sudden wall of declines. Fraudsters push large batches of stolen or generated card numbers through your checkout to learn which ones still work, then spend the live cards elsewhere. By the time the real fraud shows up, your approval rates, your acquirer relationship and your monitoring status may already be taking the hit.

For merchants in iGaming, nutraceuticals, forex, adult, crypto, subscriptions and other high-risk verticals, the stakes are higher than for a mainstream retailer. Your traffic is already watched more closely, your reserves are already a sensitive subject, and a burst of abnormal authorisations can tip a healthy account into review. Understanding how these attacks work, and building defences before they arrive, is a core part of keeping your processing stable.

risk-monitor / card-testing
€0 to €1Typical test transaction amount
20%Visa VAMP enumeration ratio flag
300,000Enumerated transactions in a month threshold

A card testing attack is a probing exercise. Criminals hold a list of card numbers, some stolen in breaches, some generated by guessing the sequential digits that follow a known Bank Identification Number, and they need to know which of those cards are still live. The cheapest way to find out is to run many small or zero-value authorisations through a real merchant and watch the responses. An approval, or even a specific decline such as an incorrect CVV, tells them the account is active and worth keeping.

The tested cards rarely cause large losses on your site. That is the point. The fraudster wants a clean, confirmed list to use elsewhere, for bigger purchases, resale or account takeover, where the sums are worth the effort. Your checkout is simply a validation tool, which is why a BIN attack can pass almost unnoticed while it is happening. The damage lands later and lands on you.

Because the cards are often generated in sequence, an enumeration attack tends to leave a distinctive fingerprint: many attempts, closely spaced, sharing a BIN or a tight numeric range, all pushed through pages that accept payment with the least friction. Donation forms, free-trial sign-ups and low-price digital goods are favourite targets precisely because they are quick and cheap to probe.

How a card testing attack unfolds

Most attacks follow a recognisable arc, from quiet reconnaissance to full automation. Knowing the shape helps you spot it early.

  1. 01

    Sourcing the card list

    The attacker assembles numbers from data breaches, dark-web dumps or algorithmic generation around a target BIN. At this stage there is nothing visible on your side, but the raw material for the attack already exists.

  2. 02

    Finding a soft checkout

    They scout for a site that allows guest checkout, low or zero-value charges and little friction at payment. A page with no CAPTCHA, no 3DS and no velocity controls is ideal, so high-risk merchants with fast, conversion-optimised flows are attractive.

  3. 03

    Automated probing

    Bots submit a rapid stream of authorisations, often fractions of a euro, from one IP or a rotating pool. Responses are logged in real time: approvals and telling declines sort the live cards from the dead ones.

  4. 04

    Monetising the live cards

    The confirmed cards move to other targets for larger fraud. Weeks later, issuers report the activity through TC40 and SAFE data, and genuine cardholders raise disputes that surface on your account as chargebacks.

Warning signs in your payment data

You rarely get a warning from the attacker, but the attack writes itself into your transaction logs. These are the patterns worth alerting on.

DECLINE SPIKE

A sudden surge of declines

Clusters of "do not honour", invalid card, incorrect CVV and expired card responses appear far above your baseline, often within minutes.

SAME BIN

Sequential numbers, shared BIN

Many attempts use card numbers from the same BIN or a tight numeric range, the hallmark of a generated enumeration list.

VELOCITY

Many attempts from one source

A single IP, device fingerprint or email domain fires dozens or hundreds of tries, or a rotating pool of IPs repeats the same behaviour.

MICRO AMOUNT

Tiny or zero-value charges

Authorisations cluster at a few cents or a single euro, or lean on zero-value auth, far below your normal basket size.

GEO MISMATCH

Billing country versus IP

The billing address and the IP location disagree repeatedly, and traffic arrives at odd hours that do not match your customer base.

NEW ACCOUNTS

Fresh accounts and guest checkout

Bots favour newly created accounts or guest checkout on donation, trial and low-price pages, where identity checks are lightest.

Why card testing hurts high-risk merchants more

Every probe costs you. You usually pay an authorisation fee on each attempt, so a few thousand tries turn into a real bill even though not a single sale completes. Worse, the flood of failures drags down your approval ratio and inflates your decline rate, two numbers your acquirer watches closely. A deteriorating approval rate makes you look riskier than you are, and in high-risk payment processing that perception feeds straight into reviews, rolling reserve increases and, in the worst case, termination.

Then comes the delayed tail. The cards confirmed on your site get used elsewhere, issuers file TC40 and SAFE fraud reports, and the genuine cardholders dispute the later charges. Even when the fraud did not happen on your platform, the enumeration signal and the knock-on disputes can count against you and push you towards card scheme monitoring. For a merchant already operating under tighter thresholds, that extra scrutiny is exactly what you cannot afford.

Visa VAMP and enumeration

Visa's Acquirer Monitoring Program, in force since April 2025, also examines enumeration, that is card testing, on card-not-present traffic. Under the published rules a merchant can be flagged as excessive when its enumeration ratio reaches 20% or more and it records at least 300,000 enumerated transactions in a month. Thresholds and enforcement can change, so confirm the current figures and how they apply to your account with your acquirer, and read more about card scheme monitoring programmes such as VAMP.

The takeaway is not to panic over a single threshold, because few individual merchants reach 300,000 enumerated transactions in a month. It is that the schemes now treat card testing as a monitored metric in its own right, separate from chargebacks, and that your acquirer sees your enumeration behaviour whether or not you do. Measuring it yourself puts you on the same page as the people who review your account.

A layered defence against card testing fraud

No single control stops card testing fraud on its own. The aim is layered friction that stays invisible to genuine buyers while making automated probing slow, expensive and unrewarding.

LayerWhat it stopsWatch out for
Velocity limitsCaps attempts per IP, device, card, BIN and email over short windows, blunting rapid-fire probing.Set limits too tight and you block legitimate retries; tune them against your real traffic.
Bot protection and CAPTCHAChallenges automated scripts at checkout and account creation before they can submit payment.Invisible or risk-based challenges keep conversion intact; constant hard CAPTCHAs cost you sales.
Device fingerprintingSpots the same device behind rotating IPs and fresh accounts.Privacy tooling and shared networks can blur signals, so combine it with other checks.
3DS2 and SCAShifts liability and adds issuer-side checks, with risk-based exemptions for low-risk flows.Mandatory 3DS on every payment adds friction; apply it where risk scoring says it is needed.
AVS, CVV and amount rulesRejects mismatched billing data and enforces a minimum transaction amount, killing cent-level probes.Blocking zero-value auth is safe only where your flows genuinely do not need it.
Fraud scoring and routingMachine-learning scores and smart routing across MIDs isolate suspicious traffic before it burns one account.Models drift; review decline codes in real time and retrain as attack patterns change.

These layers work best together and tuned to your vertical. Strong authentication is central, and it is worth understanding how 3D Secure 2 can be applied selectively under PSD2 SCA so that you raise friction for risky sessions without taxing every customer. Spreading volume by routing across several MIDs also means that if one acquiring connection is targeted, a single MID is not left to absorb the whole attack. A capable high-risk payment gateway lets you set these rules centrally rather than reacting manually each time.

Quick self-check: how exposed is your checkout?

Tick what you already have in place and see how much of the stack is covered.

Tick the controls you already have.

What to do during an active attack

If the signs above are firing right now, speed and evidence matter. Work through these steps in order.

  1. Confirm the pattern. Read the decline data and verify you are seeing clustered declines, shared BINs, tiny amounts and repeated sources rather than a routine traffic bump.
  2. Tighten velocity and add friction. Turn on stricter velocity rules and enable CAPTCHA on checkout and account creation to break the automation immediately.
  3. Block the offenders temporarily. Put short-lived blocks on the offending IP ranges and BINs, and raise 3DS to mandatory for the affected flows while the attack is live.
  4. Tell your acquirer or ISO early. Flag the activity before it shows up in their monitoring, so your side of the story is on record and they can advise on thresholds.
  5. Reverse any approved tests. Refund or void any approved test transactions quickly to limit downstream chargebacks, and keep full logs as evidence. Standing chargeback alerts help you catch disputes before they escalate.
  6. Review and adjust. Once the attack subsides, loosen the temporary rules where safe, and fold what you learned into your permanent fraud scoring and velocity settings.

Frequently asked questions

Is a card testing attack the same as a BIN attack or an enumeration attack?

They describe the same behaviour from different angles. A BIN attack emphasises that the tested numbers share a Bank Identification Number, and an enumeration attack emphasises that the numbers are generated in sequence. Card testing is the broad term for running many small authorisations to find live cards.

Will 3DS2 alone stop card testing fraud?

It helps a great deal, because it adds issuer-side authentication and shifts liability, but it is not a complete answer on its own. Attackers target flows with exemptions or weak enforcement, so pair 3DS2 with velocity limits, bot protection and real-time monitoring for proper coverage.

Do the tiny test charges really matter if no real sale happens?

Yes. You usually pay an authorisation fee on every attempt, the declines drag down your approval ratio, and the cards confirmed on your site cause fraud and chargebacks elsewhere that can be traced back to you. The absence of a completed sale does not make the attack harmless.

Could I breach the Visa VAMP enumeration thresholds by accident?

The published flag combines a 20% or higher enumeration ratio with at least 300,000 enumerated transactions in a month, so most single merchants stay well under the volume figure. The important point is that enumeration is now monitored on its own, so measure it and confirm the current rules with your acquirer.

How quickly should I react once I spot the pattern?

Within minutes if you can. Enabling stricter velocity rules and CAPTCHA and blocking offending sources early limits the authorisation fees, protects your approval rate and reduces the later chargeback tail. Speed and good logs are your best tools during a live attack.

Harden your checkout against card testing

NextGen Payment works with high-risk merchants on fraud and chargeback prevention, with multiple acquiring connections and configurable gateway rules tuned to your traffic. Every account is different, so we start from your traffic and help you build the layered defences that make card testing far less rewarding.

Talk to our risk team
NextGen Payment logo
NextGen Payment provides secure transactions, fraud prevention, and banking solutions for high-risk businesses worldwide.
© 2026 NextGen Payment
Developed With  ❤️  BY
WebFactory