How to Spot and Stop Card Testing Fraud

BinVerify · · 5 min read

What card testing is

Card testing is fraud in which criminals use automated scripts or software to find out which stolen or guessed card details work. Most attacks target online stores, where the attempts arrive as card-not-present payments. Visa describes two forms:

  • Enumeration: many attempts within one or a few BINs, trying combinations of card number, expiry date, CVV2 and postal code until the issuer approves one; also called a brute force attack.
  • Account testing: one or two low-amount payments to check whether a stolen card is still active.

The PCI Security Standards Council also calls it account testing, payment account enumeration or a BIN attack. Cards that pass are used for fraud or sold on criminal markets, and Visa put the fraud losses from enumeration at $1.1 billion in its 2023 fiscal year.

Warning signs in your data

Visa and the PCI Security Standards Council list these common signs:

  • A sudden spike in authorization attempts or declines, store-wide or for one BIN range.
  • Many small, identical or zero-amount attempts. Visa notes that attack transactions are often under $10.
  • Many card numbers from one BIN range, sometimes sequential, or one card tried again with a new expiry date, CVV2 or postal code.
  • Many cards from one IP address, device or email address; one card used from many IP addresses; or more different cardholder names than usual.
  • Approved authorizations that are reversed right away or not settled.
  • An IP address or device whose time zone or browser language does not fit the cardholder; Visa advises treating these as higher risk.

Visa also lists decline codes to watch, such as 14 (invalid account number), 54 (expired card), 59 (suspected fraud) and N7 (CVV2 failure). Depending on your acquirer, some can arrive as 05 (do not honor).

What it costs a merchant

  • Fees: if you pay per transaction, declined attempts cost money too; the PCI Security Standards Council warns of thousands of dollars in processing charges.
  • Chargebacks: the real cardholders can dispute the test payments that were approved.
  • Approval rates: a high rate of declines can make issuers and acquirers less willing to accept your legitimate payments.
  • Lost goods and time: orders paid with tested cards can mean lost inventory and wasted work.

Visa also monitors enumeration. Its Acquirer Monitoring Program (VAMP), which combines Visa's earlier fraud and dispute programs, took effect on 1 April 2025, with an advisory period until 30 September 2025. Each month Visa checks enumeration levels against two thresholds in its 2025 fact sheet: an enumeration ratio of 2,000 basis points (20% of authorizations) or more, and 300,000 or more enumerated transactions. Acquirers must take steps to keep their merchants below them, and entities identified as exceeding VAMP thresholds must put risk controls in place.

How to stop card testing

Visa and the PCI Security Standards Council recommend a layered defense. Their recommended layers include:

  • Bot protection, such as CAPTCHA, wherever a card can be checked or charged, plus a web application firewall that limits repeated submissions.
  • Velocity limits per IP address, device, email address, card and BIN; Visa's example is five authorizations from one IP address or card number in a set time.
  • Limits on how many cards one account or session can add and how many accounts one IP address can create.
  • Alerts on spikes in declines, reversals and attempts from one BIN range, monitored around the clock.
  • CVV2 and AVS checks, and 3-D Secure. Attackers also test cards through 3-D Secure, so watch authentication attempts for BIN spikes too.
  • A minimum amount on donation pages and other forms where the payer types the amount, which Visa says fraudsters have targeted.

Per-IP limits alone are not enough, as one attack can use many IP addresses; OWASP calls them coarse but useful as a floor. Add device fingerprinting, as Visa recommends, and per-network (ASN) limits where traffic from data centers is unexpected, as OWASP suggests.

If an attack is under way

  • Work with your acquirer or payment provider to stop the automated attempts.
  • Act quickly: tighten velocity limits, add a challenge to the payment form and put IP addresses with many failed payments on a block or review list.
  • If the attempts reach your payment API directly rather than the website form, roll (replace) your API keys.
  • Refund or void the fraudulent payments that were approved, to avoid disputes.

Visa monitors its network for enumeration. Its Visa Account Attack Intelligence (VAAI) Score rates card-not-present transactions from 01 to 99; a high score means the card details are likely being enumerated. Ask your acquirer whether you can use it.

Where BIN and IP checks fit

When you review payments from a suspected attack, two checks add context:

  • BIN Lookup shows the issuing bank, card type and issuing country from the first 6 or 8 digits, without the full card number. Use it to see which bank a targeted BIN belongs to and whether the issuing country matches the IP country.
  • VPN & Proxy Detection shows whether an IP address belongs to a VPN, a known proxy or a hosting company, with the provider, the ASN and the country.

Treat the results as reasons for review, not proof: a VPN, proxy or hosting result describes the address, not the person using it. For an IP address or device whose time zone or browser language does not fit the cardholder, Visa advises a stricter review.

Terms in this guide: Card-not-present (CNP) transaction, BIN (Bank Identification Number), CVV / CVC (card security code), Issuing bank (issuer), Acquirer (acquiring bank), Chargeback, AVS (Address Verification Service), 3-D Secure (3DS), ASN (Autonomous System Number), Data center IP address, VPN (virtual private network), Proxy

Sources

  1. Visa Guidance to Guard Against Enumeration Attacks and Account Testing Schemes (Visa Business News, 12 August 2021)
  2. Enumeration Mitigation and Considerations for Merchants, V1.3 (Visa, June 2026)
  3. Bulletin: The Threat of Account Testing to Payment Security (PCI Security Standards Council and NCFTA, October 2020)
  4. Introducing the Visa Acquirer Monitoring Program (Visa, 30 August 2024, update of 24 March 2025)
  5. Visa Acquirer Monitoring Program Overview, fact sheet (Visa, May 2025)
  6. Bot Management and Anti-Automation Cheat Sheet (OWASP Cheat Sheet Series)