Blog

Card testing prevention: a checklist for your payment page

Ten practical defences against card testing fraud, ordered from quickest to set up to most thorough, so you can close the gaps before testers find them.

Card testers go where it is easy. You do not need to be impossible to attack, just harder than the next site on their list. This checklist runs from the quickest wins to the deeper changes. If you are new to the topic, start with what card testing is and how it works.

Quick wins (an afternoon)

  1. Screen the connection before the payment call. Most testing traffic comes from hosting providers, proxies, VPNs and Tor. Checking the IP first and refusing or challenging those attempts stops the bulk of an attack before it costs you a fee.
  2. Rate limit the payment step. Limit attempts per IP, per network, per session and per account. A real buyer rarely needs more than three tries.
  3. Raise very low minimums. A $0.50 product or an open donation amount is exactly what testers search for. A floor of a few dollars removes much of the appeal.
  4. Make decline messages vague. "Your payment could not be completed" tells a real customer enough. "Incorrect security code" tells a tester which part to guess next.

Stronger defences (a few days)

  1. Count cards per network and per device. Several different cards from one network in a short time is the clearest sign of testing. Block or challenge after the second or third.
  2. Watch BIN patterns. Many cards with the same first six or eight digits in a row, or BINs in sequence, point to a BIN attack. Look up the BIN to see the issuing country and card type too.
  3. Compare card country with IP country. A mismatch alone is not fraud, but a foreign card on a datacenter IP is a strong combination.
  4. Challenge only when risk is high. Show a CAPTCHA or require 3-D Secure for risky attempts rather than for everyone, so real buyers never feel it.

Thorough (ongoing)

  1. Alert on decline rate. Set an alert for when the share of declined payments in the last hour jumps above normal. Card testing shows up here first, and the sooner you know, the less it costs.
  2. Protect every payment path. Testers find the weakest one: the old donation page, the "update card" form in account settings, the API your mobile app uses. Apply the same checks to all of them.

What not to do

Do not block whole countries or whole BINs as your main defence. It feels decisive, but it turns away real customers while testers simply switch to other cards. We explain why in what "BIN blacklisted" really means.

Where Fraudex fits

Steps 1, 5, 6 and 7 need two facts per attempt: what kind of network the visitor is on, and what the card's BIN says. Fraudex returns both from one API key in under a millisecond, so the check sits in front of your payment call without slowing down checkout.