What is a card testing attack?

In a card testing attack, a fraudster uses your checkout to find out which stolen card numbers still work, by making many small purchases or authorisations. Working cards are then used elsewhere or sold. The merchant is left with authorisation fees, declines, chargebacks and closer scrutiny from its payment provider.

The cards come from data breaches, phishing, malware on shops and devices, and markets where such data is traded. A list of stolen cards is of uncertain value, because many have been cancelled. Testing sorts the live cards from the dead ones, and a merchant's payment form is a convenient place to do it.

There are two variants. In the first, the attacker holds complete card details and submits each one to see whether it is approved. In the second, the attacker holds partial details, or generates card numbers within the range of a particular issuer, and submits many combinations of expiry date and security code until one succeeds. The second is sometimes called an enumeration attack and produces far more attempts per working card.

Operators choose targets that make testing cheap. Low-priced items, donation pages and digital goods allow small charges that a cardholder may not notice. Guest checkout removes the need for an account. Endpoints that validate a card without a purchase, such as adding a card to a wallet or a zero-value authorisation, are attractive for the same reason. Checkout APIs that can be called directly, without loading the page, let software run thousands of attempts.

For the merchant, the damage arrives in stages. Each attempt can carry an authorisation fee, whether approved or declined. The share of declined transactions rises, and payment providers and card schemes monitor that ratio. Approved test charges are later disputed by the cardholders, bringing chargebacks and their fees. A merchant whose decline or dispute levels pass the provider's thresholds can face higher costs, a reserve held on its funds or suspension of its account. Refunding the test charges takes staff time.

The signs are distinctive once you look for them. Declines rise suddenly, often within minutes. Many transactions are for the same small amount. Card numbers share their first digits and differ in the rest. Billing details do not match the card or are plainly invented. Attempts come from countries you do not sell to, or from one device behind many addresses. Orders are placed through guest checkout with no browsing beforehand.

Alert on changes in decline rate and document who investigates them; containment time depends on the attack and your available controls.

How Kairal helps

Kairal verifies suspicious requests on connected checkout and payment paths without a CAPTCHA puzzle. Compare Events and Sessions with payment outcomes in your back office. Payment authentication, card checks, prices and refunds remain with your application and payment provider.

Kairal Bot Protection