Plugins Plugin hub Backup SEO Caching Security Forms WooCommerce Images Best backup plugins
Hosting Hosting directory Shared Managed Cloud India
Themes & builders Compare Rank Math vs Yoast
Tools All tools Hosting finder Plugin stack builder Cost calculator Salt generator Theme detector Who is hosting this? Speed test Headline analyzer robots.txt generator Redirect generator Uptime calculator Blog name generator
Best lists Best backup plugins Deals
Guides All guides Speed up WordPress Choose hosting Back up WordPress
How we test

WooCommerce · Guide

How to Stop Fake and Fraud Orders in WooCommerce

Short answer

To stop fake orders in WooCommerce, turn on the built-in Rate limit Checkout setting, add a CAPTCHA to checkout, and switch on your payment gateway's fraud rules. Watch for a sudden rise in failed orders, which is the main sign of card testing. For repeat attacks, add the WooCommerce Anti-Fraud extension and hold high-risk orders for review before shipping.

Key takeaways

  • A sudden rise in Failed orders is the main sign of card testing, usually for small amounts.
  • Refund fraudulent payments first, then turn on the rate limit and a CAPTCHA.
  • WooCommerce's built-in rate limit allows 3 checkout requests per 60 seconds per visitor.
  • WooPayments fraud rules can block mismatched addresses, foreign IPs, and tiny orders.
  • Anti-Fraud scores orders from 0 to 100; start with the Medium preset and review real scores first.

What are fake orders, and how do you spot them?

Fake orders are orders placed by bots or stolen cards, not by real shoppers.

The most common form is card testing. Someone takes a list of stolen card numbers and runs them through a real checkout, usually with small purchases of the cheapest product, to learn which cards still work.

The main sign is a large increase in orders with the Failed status. WooCommerce's card testing guide names that jump as the clearest warning, and it usually arrives with odd names, throwaway email addresses, and many orders minutes apart.

Failed orders on their own cost you nothing. The cost comes when a stolen card does go through: the card owner disputes the charge, and your payment provider charges a dispute fee. Refunding the payment does not always refund the fee.

Check your orders list daily. Open WooCommerce > Orders, filter by Failed, and look for the pattern before it becomes a flood.

What should you do first during an attack?

Work in WooCommerce's own order: refund first, then contain, then harden.

  1. Review every payment made during the attack and refund the ones that look fraudulent. Do this urgently, since it limits disputes.
  2. Turn on Rate limit Checkout if your checkout uses the block editor, and add a CAPTCHA.
  3. Make cheap or donation-style products private for now, since card testers pick the lowest price.
  4. Turn off guest checkout while the attack runs, under WooCommerce > Settings > Accounts & Privacy.
  5. Contact your payment provider and ask them to review the anti-fraud measures on your account.

Do not start by deleting orders. Deleting a WooCommerce order does not remove data already sent to your payment provider, accounting tool, or fulfilment system, so review the affected orders first.

Our guide to stopping WooCommerce card testing attacks covers the same response in more depth.

How do you turn on WooCommerce's built-in rate limit?

The rate limit caps how many checkout attempts one visitor can make in a short window.

Go to WooCommerce > Settings > Advanced > Features and tick Rate limit Checkout, then save. The setting is off by default, and it first appeared in WooCommerce 9.6.

Once on, it allows 3 checkout requests per 60 seconds from one IP address for guests, or per account for logged-in customers. Extra requests are refused with an HTTP 429 response until the window passes.

Know its limits. The toggle protects the block checkout and its Store API endpoint only, so a classic shortcode checkout is not covered.

If your site sits behind a CDN or proxy, your host must pass the real visitor IP to WordPress. Otherwise every visitor looks like one address and shares the same limit.

The Advanced settings docs list the toggle among the stable feature controls. Developers can tune the numbers with the woocommerce_store_api_rate_limit_options filter.

How do you add a CAPTCHA to checkout?

A CAPTCHA asks for proof that a person is typing, and it stops most bots before an order is created.

WooCommerce has no CAPTCHA of its own, so you need a plugin. Two options appear in WooCommerce's own guidance: Google reCAPTCHA v2 and Cloudflare Turnstile. Turnstile is free to use with the Simple Cloudflare Turnstile plugin from WordPress.org.

For Turnstile, create a widget in your Cloudflare dashboard to get a site key and a secret key.

Cloudflare's Turnstile docs explain the two steps: a script runs a challenge in the visitor's browser and makes a token, then your server sends that token to Cloudflare to confirm it is valid.

For reCAPTCHA, create a v2 checkbox key in the Google admin console. Google's reCAPTCHA docs list four types, and the v2 checkbox is the one that shows the familiar “I'm not a robot” box.

Do not run two CAPTCHA plugins at once. Two widgets on the same checkout can produce duplicate tokens, missing tokens, or failed checks, and real shoppers get blocked along with the bots. Test a full purchase after you switch one on.

How do your payment gateway's fraud rules help?

The gateway checks the card, so its fraud rules are the last line of defence before money moves.

If you use WooPayments, open Payments > Settings > Fraud protection. The fraud protection docs describe two levels: Basic, which gives the base platform protection, and Advanced, which lets you set your own filters.

The Advanced filters are AVS Mismatch, International IP Address, IP Address Mismatch, Address Mismatch, Purchase Price Threshold, and Order Items Threshold. A useful first rule blocks orders under a small amount, since card testers usually pick your cheapest product.

WooPayments is built with Stripe and uses Stripe Radar for real-time fraud detection. Stripe's Radar rules docs explain how rules can request 3D Secure, allow, block, or send a payment for review, and that high-risk payments are blocked by default.

Also check card verification. WooPayments runs CVC and address checks on card payments, and a failed CVC check can block the payment when that filter is on. Find the result for any payment under Payments > Transactions.

If you use Stripe directly, the same Radar rules apply in your Stripe dashboard. Our comparison of WooCommerce Payments vs Stripe explains which setup fits which store.

Should you install the Anti-Fraud extension?

Install it when the free layers are not enough, or when fake orders keep coming back.

The WooCommerce Anti-Fraud extension scores each checked order from 0 to 100 and holds, cancels, or stops orders based on the score. Lower scores mean fewer risk signals, and higher scores mean more or stronger ones. Find it at WooCommerce > Settings > Anti-Fraud after install.

It ships with three presets that set the thresholds, order limits, and failed-payment limits. WooCommerce's Anti-Fraud docs list them as follows:

PresetMedium / High thresholdHold / Cancel scoreOrder-attempt limitFailed-payment limit
Low40 / 8585 / 958 orders per 24 hours5
Medium25 / 7570 / 905 orders per 24 hours3
High20 / 6055 / 853 orders per 24 hours2

Start with Medium and watch real order scores for a week before you turn on automatic holds or cancels. A preset is a starting point, not a finished setup: it does not set up CAPTCHA keys, enable the pre-payment check, or name your trusted customers.

Turn on Run check before payment when you need to stop a high-risk checkout before the card is charged. During an active attack, start with the CAPTCHA, order-attempt limits, and failed-payment caps, and do not lower every fraud-score threshold at once.

The extension also keeps allow lists and block lists for customers, emails, IPs, and phone numbers. Keep allow-list rules narrow, since a broad exception can bypass useful checks for more customers than you meant.

How do you clean up after an attack?

Contain first, then review, then clean.

  1. Confirm the attack has stopped by watching the Failed orders count fall back to normal.
  2. Open each suspicious order and check the payment status in your gateway dashboard.
  3. Refund every payment you believe is fraudulent, and note that the gateway fee may not come back.
  4. Use Order review & alerts > Failed orders & cleanup in the Anti-Fraud settings, or your gateway dashboard, to review failed orders from the affected period.
  5. Cancel or delete the junk orders only after you have reviewed them.
  6. Leave the rate limit, CAPTCHA, and gateway rules switched on.

Order Attribution can help with the review. It adds an Origin column to the orders list, showing where each order came from, on which device, and how many pages the shopper viewed.

If orders are stuck in a strange status after the attack, see our guide to orders stuck on pending payment.

What mistakes should you avoid?

Most stores that keep getting fake orders make one of these errors.

  • Leaving the built-in rate limit switched off, since it costs nothing and takes a minute to enable.
  • Lowering every fraud threshold during an attack, which blocks real shoppers and hides the real pattern.
  • Running two CAPTCHA plugins on the same checkout, which breaks verification for everyone.
  • Refunding without checking first, or deleting orders before reviewing them.
  • Turning the protections off once the attack fades. Card testers return to stores that drop their guard.
  • Assuming any system is perfect. WooCommerce's own docs say no fraud prevention system catches everything, so keep reviewing high-value and international orders by hand.

Layer the defences and keep them on. A rate limit, a CAPTCHA, gateway rules, and a weekly look at your Failed orders will stop most fake orders before they cost you money.

Frequently asked questions

What is card testing in WooCommerce?

Card testing is when someone runs many stolen card numbers through your checkout to find which ones still work. The main sign is a sudden rise in orders with the Failed status, often for small amounts and minutes apart. Refund any payments that went through, turn on the rate limit and a CAPTCHA, and contact your payment provider.

Can I stop fake orders in WooCommerce for free?

WooCommerce has no built-in fraud protection section, but it does have a free rate limit. Go to WooCommerce, Settings, Advanced, Features, and tick Rate limit Checkout. It allows 3 checkout requests per 60 seconds per visitor on the block checkout. Add a free CAPTCHA such as Cloudflare Turnstile for a second layer.

Is the built-in rate limit enough on its own?

A rate limit slows bots down, but it cannot tell a stolen card from a real one, and it only covers the block checkout. Your payment gateway's fraud rules check the card itself, which is why WooCommerce pairs the two. Use the rate limit and a CAPTCHA first, then gateway rules, then an anti-fraud extension if attacks continue.

Should I install the WooCommerce Anti-Fraud extension?

Yes, when it is set up with care. Anti-Fraud scores orders from 0 to 100 and can hold or cancel high-risk ones before you ship. Start with the Medium preset, watch real scores for a week, and only then turn on automatic actions. Keep allow-list rules narrow so trusted customers are not caught by mistake.

Why do I suddenly have many failed payments?

A sudden rise in failed payments usually means card testing, but it can also mean a gateway problem or a broken checkout. Check whether the failures share one cheap product, odd names, and rapid timing. If they do, follow the card testing steps. If they look like real customers, check your gateway and checkout first.

Sources

  1. How do I prevent and respond to card testing attacks? WooCommerce
  2. Anti-Fraud for WooCommerce WooCommerce
  3. WooPayments: Fraud Protection WooCommerce
  4. Advanced Settings WooCommerce
  5. Fraud prevention rules Stripe
  6. Get started with Cloudflare Turnstile Cloudflare
  7. Choosing the type of reCAPTCHA Google for Developers

Is your product missing, or something out of date?

Tell us what to add or correct. We read every note and reply when we need a source. A message does not buy a ranking.

About the editors

WPLegible editors

Researched from the primary sources listed above and checked against our editorial rules. About the site · How we test