Card testing on WooCommerce: how to spot it and what to switch on

If you run a WooCommerce store, one morning you may open your orders and find dozens of new ones from names you don't recognise. Most have failed. A few went through for a couple of dollars. Nobody has been in touch.

That pattern is usually card testing. It isn't aimed at your business in particular. Your checkout just happens to be a convenient place for someone to check whether a list of stolen card numbers still works.

What card testing is

WooCommerce's own guide to card testing describes it as fraud where someone with a large batch of stolen card details makes many small purchases, each with a different card, to find out which cards are valid. A card that works can then be sold on or used for bigger fraud somewhere else.

You don't lose stock, because the "customer" doesn't care about the product. The costs show up in other ways:

  • Transaction fees on attempts your payment provider processes.
  • Disputes and chargebacks when the real cardholders spot charges they didn't make.
  • Pressure from your payment provider if your store's failure or dispute rate climbs.
  • A messy order list that hides your real orders and skews your reports.

Signs it's happening

The usual giveaways:

  • Lots of failed or pending orders in a short window, often overnight.
  • Small amounts, frequently your cheapest product, a donation, or a "pay what you want" item.
  • Guest checkouts with odd or random-looking names and email addresses.
  • Billing details, emails and cards that change on every attempt.
  • A spike of declines in your payment provider's dashboard that doesn't match your normal sales.

One or two strange orders happen to everyone. Dozens in an hour is not a sale.

If it's happening right now

Do these first, in roughly this order:

  1. Refund anything that went through and looks fraudulent. WooCommerce's guide calls this the most important step, because it heads off disputes from the real cardholders. Do it the same day.
  2. Take the target away. If the attacks all hit one cheap product, a donation item or a pay-what-you-want product, make it private or unavailable for now.
  3. Consider turning off guest checkout temporarily, so a customer account is needed to buy.
  4. Talk to your payment provider. Tell them what you're seeing and ask what fraud settings they can tighten on their side.

None of this needs to be permanent. The aim is to stop the bleeding while you put better protection in place.

Settings worth switching on

Rate limiting for the block checkout

If your store uses the newer Checkout block, WooCommerce has a built-in option for this. Go to WooCommerce → Settings → Advanced → Features and turn on "Rate limiting Checkout block and Store API". According to the WooCommerce developer docs, this limits the place-order step to three requests per 60 seconds, which is plenty for a real customer and slows down a script considerably.

Two caveats. It applies to the Checkout block, so an older shortcode-based checkout needs a different approach. And if your site sits behind a proxy or CDN, the limit needs proxy support set up properly, otherwise every visitor can look like the same IP address. That second part is a developer job rather than a checkbox.

A bot check at checkout

Most card testing is automated, so a bot check on the checkout catches a lot of it. WooCommerce's guide mentions reCAPTCHA extensions and Cloudflare Turnstile, which is a lighter option that most real customers never notice. Whichever you use, place a test order afterwards on desktop and on a phone. A bot check that blocks real customers is worse than the problem it solves.

Fraud rules

Anti-fraud extensions add rules such as blocking repeated orders from the same buyer in a short window, capping failed payments, or flagging risky orders for review. They can work well, but WooCommerce's guide is blunt that a badly configured one offers little or no protection. Set the thresholds from what your normal customers actually do, and check the orders the rules catch for the first few weeks.

Fewer easy targets

Avoid donation or pay-what-you-want products with no minimum amount, since fraudsters like small charges a cardholder won't notice. If you sell very cheap items, it's worth knowing they're the likely target.

Make it part of normal upkeep

Card testing tends to come in waves, and online stores get more attention when traffic is high, so it's sensible to have the basics in place before a busy sales period. After that, it's a quick look during regular maintenance: are failed orders at a normal level, are the protections still active after plugin updates, and does checkout still work for a real person?

Where I fit in

I fix and maintain WordPress and WooCommerce sites for small NZ businesses, and checkout problems like this are part of that work. If your store is seeing a pile of odd failed orders, or you'd like the protections set up and tested before it happens, send me a short note with your store address and I'll take a look.