Key points
- Card testing is a bot trying stolen card numbers through your checkout. It shows up as a run of Failed or Pending payment orders, minutes apart, on one cheap product.
- WooCommerce’s Rate limit Checkout setting is off by default. On our lab it returned “Too many requests” on the fourth try in a minute, but it only guards the block checkout, not the classic one.
- None of WooCommerce, WooPayments, Stripe or PayPal Payments has a Turnstile option. PayPal Payments has reCAPTCHA built in; for Turnstile you need a third-party plugin.
- Clear the card-testing orders after the attack stops, not during. A cleaner removes orders; it does not block anything.
The problem: when the attack stops, every failed and pending order it placed is still sitting in your Orders screen.
Failed & Spam Order Cleaner previews them, then moves them to the trash in background batches: $39 a year for one site, 14-day refund. It cleans up, does not block: stopping the attack is a separate job.
Product page: Failed & Spam Order Cleaner for WooCommerce
Is this card testing, or something else?
It probably is if the Orders screen fills with Failed orders you never saw coming. Card testers use your checkout to learn which stolen cards still work, so the orders are small, fast and fake.
Check for these signs on WooCommerce » Orders with the Failed filter:
- dozens of orders placed minutes apart, often overnight,
- the same low-priced product on each one,
- a different name and email on almost every order,
- a handful of IP addresses and several countries behind them,
- an Origin of “Unknown” in the order attribution, which OOPSpam’s write-up (updated 22 Sep 2025, read 12 Oct 2026) treats as a strong sign.
We seeded an attack on our lab store to get the shots for this guide. It looked like this: 38 orders between 14:03 and 14:47, 31 Failed and 7 Pending payment, from 6 proxy IPs in 7 countries, with 34 different emails.

How do you stop WooCommerce card testing right now?
Slow the checkout down and tighten your gateway. These take minutes and cost nothing.
1. Turn on Rate limit Checkout (block checkout only)
Go to WooCommerce » Settings » Advanced » Features and tick Rate limit Checkout. The label reads “Enables rate limiting for Checkout place order and Store API /checkout endpoint.” It is off by default.

With it on, WooCommerce allows 3 checkout requests per 60 seconds from each IP address (or each user ID when someone is logged in).
We tested it on 12 Oct 2026. Requests one to three came back with a normal error for missing billing details. The fourth came back with a 429: “Too many requests. Please wait 60 seconds before trying again.”
In WooCommerce 11.2.1 the code only matches the Store API checkout route, /wc/store/v1/checkout, which the block checkout uses. The classic checkout (the [woocommerce_checkout] shortcode) is not rate-limited by this setting, whatever the label says. We read that in the source and did not test a classic checkout on the lab. If your checkout page uses the shortcode, this setting will not slow the attack.
2. Switch on your gateway’s fraud filters
Your payment plugin may already have a filter you have not turned on. We read these in each plugin’s code on 12 Oct 2026; we did not run an attack through them.
- WooPayments 11.2.0: Payments » Settings » Fraud protection. The level is Basic by default. Advanced adds filters for AVS mismatch, IP address mismatch, international IP address, address mismatch, a purchase price threshold and an order items threshold, each set to block the payment or hold it for review. WooPayments also adds a hidden card-testing token at checkout on its own, when its servers mark the account as eligible. There is no toggle for that.
- PayPal Payments 4.1.3: WooCommerce » Settings » Integration » “WooCommerce PayPal Payments reCAPTCHA”. Tick Enable reCAPTCHA protection and add both v3 and v2 keys. It is off by default, with a score threshold of 0.5 and “Guest Orders Only” on.
- Stripe 11.0.1: the plugin has no CAPTCHA or Turnstile setting. Stripe Radar lives in your Stripe Dashboard, outside the plugin, and we have not checked it.
WooCommerce’s own advice for an attack in progress is to refund any charges that went through and talk to your payment processor (WooCommerce docs, read 12 Oct 2026). Do that call today if any test charges succeeded.
3. Turn off guest checkout, only as a stopgap
WooCommerce » Settings » Accounts & Privacy » Checkout has “Enable guest checkout (recommended)”, and it is on by default. Unticking it makes every buyer create an account first.
That slows a bot, and it also slows every real customer who just wants to pay.

How do you stop it next time?
Add a challenge to the checkout and close the gaps the rate limit leaves. Start with the free layers.
Add a free Turnstile or CAPTCHA plugin
None of WooCommerce 11.2.1, WooPayments 11.2.0, Stripe 11.0.1 or PayPal Payments 4.1.3 has a Cloudflare Turnstile option. We searched all four codebases on 12 Oct 2026. If you want one on the checkout, it comes from a third-party plugin.
One free option is Simple Cloudflare Turnstile on WordPress.org (listing checked 12 Oct 2026). We have not tested its settings on our lab, so check its own docs for WooCommerce checkout support, and test a real order after you add it.
Rate-limit the whole Store API with code
The Store API has a wider rate limit with no admin screen. A developer can switch it on with the filter woocommerce_store_api_rate_limit_options. Its defaults in 11.2.1 are: off, proxy support off, 25 requests per 10 seconds. We have not run this filter on our lab.
Leave the payment method throttle alone
WooCommerce already waits 20 seconds between “add payment method” attempts from one user on My Account » Payment methods (filter woocommerce_payment_gateway_add_payment_method_delay). Stripe’s plugin adds its own 10 second delay after a failed attempt there. Both are on without you doing anything.
How do you clean up the orders the attack left?
Wait until the attack has stopped, then remove the fake orders without touching real ones. Our full walk-through is in how to clean up WooCommerce card-testing orders, and our comparison of failed-order cleanup tools covers the other options.
This is the part we build a tool for. Failed & Spam Order Cleaner for WooCommerce ($39 a year for one site) previews the matching Failed, Pending payment or On hold orders (plus Draft, the abandoned checkout status, when block checkout registers it), then moves them to the trash in the background. It does not block attacks. No rate limiting, CAPTCHA or IP blocklists. That is why the steps above come first.
On our lab, the preview showed 38 matching orders (31 Failed, 7 Pending payment) and changed nothing. One click by the admin moved all 38 to the trash with 0 errors. The 6 paid orders were left alone because they are Processing or Completed, statuses the run never selects (it examined 38 orders). The date range we set (11 Oct; the run itself was at 13:19 UTC on 12 Oct) explains only why #148 and #149 stayed.


FAQ
Does WooCommerce have card-testing protection built in?
Partly. The Rate limit Checkout setting is off by default and covers only the block checkout. WooPayments adds its own card-testing token when its servers decide the account needs it.
Will a CAPTCHA stop card testing on its own?
It adds a hurdle, but run it alongside your gateway’s fraud filters and a rate limit.
Should I delete the failed orders while the attack is still running?
No. Stop it first. The cleaner fixes its time window when Clean Up starts, so orders that arrive during the run are not swept in. Anything newer needs a second run.
Does the rate limit work on the classic checkout?
Not in WooCommerce 11.2.1. The code only matches the block checkout’s Store API route.
Sources
- WooCommerce 11.2.1 source,
src/Internal/Features/FeaturesController.php(Rate limit Checkout, off by default) andsrc/StoreApi/Authentication.php(3 requests per 60 s, Store API/checkoutroute only), read 12 Oct 2026. Lab test of the 429 response, 12 Oct 2026. - WooCommerce 11.2.1 source,
src/StoreApi/Utilities/RateLimits.php(woocommerce_store_api_rate_limit_optionsdefaults), read 12 Oct 2026. - WooCommerce 11.2.1 source,
includes/admin/settings/class-wc-settings-accounts.php(guest checkout on by default) andincludes/class-wc-form-handler.php(20 s payment method delay), read 12 Oct 2026. - WooPayments 11.2.0 source,
includes/fraud-prevention/class-fraud-risk-tools.phpandclass-fraud-prevention-service.php, read 12 Oct 2026. - PayPal Payments 4.1.3 source,
modules/ppcp-fraud-protection/src/Recaptcha/RecaptchaIntegration.php, read 12 Oct 2026. - Stripe for WooCommerce 11.0.1 source,
includes/class-wc-stripe-intent-controller.php, read 12 Oct 2026. - WooCommerce docs, How do I prevent and respond to card testing attacks?: https://woocommerce.com/document/how-do-i-prevent-and-respond-to-card-testing-attacks/ (read 12 Oct 2026).
- OOPSpam, How to Stop Failed Orders with Unknown Origin: https://www.oopspam.com/blog/how-to-stop-failed-orders-with-unknown-origin-in-woocommerce (updated 22 Sep 2025, read 12 Oct 2026).
- Simple Cloudflare Turnstile on WordPress.org: https://wordpress.org/plugins/simple-cloudflare-turnstile/ (listing checked 12 Oct 2026, not tested).
- Failed & Spam Order Cleaner 1.0.0 code and lab run on WordPress 7.1.2, WooCommerce 11.2.1, HPOS on (12 Oct 2026).
Still seeing failed orders after all this?
Tell us your gateway, whether your checkout is block or classic, and how many orders a night you are seeing, and we will tell you which layer is missing: ask about spam orders.
Failed & Spam Order Cleaner for WooCommerce. Clear the failed and pending orders a card-testing attack leaves behind, in the background, trash first, with a report on who sent them.
View the add-on