Short answer
Card testers skip your shop pages and post stolen cards straight to WooCommerce’s checkout routes, so a CAPTCHA on the checkout page alone rarely stops them. Guard every route that can charge a card, count declines per address, network, email and device, challenge or block repeat offenders, and tighten every check when declines spike. Then clear out the failed orders the attack leaves behind.
What a card-testing attack looks like
A bot holding a list of stolen card numbers uses your checkout to find out which ones still work. It usually buys the cheapest product as a guest, with a different name, email and card each time, and runs through dozens or hundreds of attempts in minutes. You will usually see several of these at once:
- A burst of failed orders, or orders stuck at Pending payment
- The same low-priced product in most of them
- Billing names that have nothing to do with the email addresses
- Origin shown as Unknown in the orders list (WooCommerce 8.5 and later)
- A flood of failed-order emails, then a message from Stripe or PayPal about declines
Why a CAPTCHA on the checkout page is not enough
A bot does not need your checkout page. It can send orders straight to the routes behind it, and many card-testing tools do exactly that:
A check has to run on every one of these routes, on your own server, before the payment provider is contacted. A CAPTCHA that only appears on the page, or is not verified on every route, is simply skipped.
- The Store API checkout used by the Checkout block: /wp-json/wc/store/v1/checkout
- The classic checkout: /?wc-ajax=checkout
- Pay-for-order links and the “Add payment method” form in My Account
- A payment plugin’s own requests, such as PayPal Payments’ ppc-create-order
What WooCommerce and your payment provider give you
WooCommerce has a “Rate limit Checkout” feature under WooCommerce → Settings → Advanced → Features. When it is on, the Store API checkout and the Checkout block’s Place order button are limited to 3 requests per 60 seconds per shopper, counted by IP address for guests (November 2026). It is off by default.
Stripe and PayPal run their own fraud checks, and Stripe blocks some attempts itself. Every attempt still reaches them, though, and Stripe’s documentation warns that a high decline rate can make your genuine payments look riskier to card issuers, even after the attack has stopped.
It is getting more common. Signifyd’s State of Fraud Report 2026 reported card-testing attacks up 175% year on year across its network of online merchants.
Steps with Brickmoat
Install the free plugin
Upload and activate Brickmoat. Protection starts at once on the block checkout, the classic checkout, the Store API, pay-for-order, “Add payment method” and the PayPal Payments button. There is nothing to configure.
Pick how careful it should be
Choose Relaxed, Balanced or Strict, and where attack alerts are emailed. Balanced suits most stores.
Let it count and challenge
Each attempt is checked for signs of a script, such as never having loaded a page, and counted against its IP address, network, email and device. Repeat offenders are asked a quick “I’m human” question or blocked, and blocks expire on their own.
Lockdown during an attack
When declines spike, lockdown switches on by itself: guests answer the “I’m human” question, payments that did not come through your shop pages are stopped, and failed-order emails are paused. It ends after 60 quiet minutes.
Clean up afterwards
The Cleanup screen moves the attack’s failed and unpaid orders to Trash in one click, with undo. Paid orders and returning customers are never touched.
The plugin is free, with nothing to set up. Read the plugin guide or see what Pro adds.
Limits to know about
- A bot that imitates a real browser can get a few attempts through before declines trigger lockdown. The aim is to stop it long before it finds a working card.
- Brickmoat stops card testing at checkout. Whether a successful payment with a stolen card is fraud is still your payment provider’s screening.
- If anything inside the plugin fails, the order is allowed and the error is logged, so the plugin is never the reason a checkout breaks.
- It needs WordPress 6.5 or newer, WooCommerce 8.5 or newer, PHP 7.4 or newer.
Related questions
Why are card testers targeting my small store?
Small stores are often picked because they are small: fewer checks at checkout and nobody watching at three in the morning. The bot only needs a checkout that answers “approved” or “declined”; what you sell does not matter.
Should I turn off guest checkout?
It stops many attacks but costs real sales, so Brickmoat never does it for you. Lockdown asks guests to prove they are human instead, and only during an attack. Requiring accounts stays an option you can choose yourself.
What will my payment provider do about an attack?
Stripe, PayPal and others watch decline rates. They may contact you, ask what you have changed, or place the store in a card-network monitoring programme if attacks continue. Acting fast and keeping a record helps; Brickmoat Pro builds a report of each attack for them.