WooPayments card testing: the settings that help, and the gap they leave
A guide for store owners who take cards with WooPayments. Updated November 15, 2026.
Your store takes cards through WooPayments, WooCommerce's own payment service, and bots are running stolen cards through your checkout. WooPayments has some protection built in and some you can set. Its own card testing page is honest that it isn't the whole answer: it says store owners are responsible for their own fraud prevention. This guide covers what WooPayments does, what to set, and what's left. Everything about WooPayments here comes from WooCommerce's documents and WooPayments' code, read on November 15, 2026.
What WooPayments does on its own
- Stripe's Radar. WooPayments runs on Stripe, and its fraud prevention page says Radar screens payments and blocks the ones it judges likely to be fraud.
- Card checks on every card payment, such as the CVC check, according to the same page.
- Some card-testing measures of its own, which its card testing page mentions without listing.
The fraud protection rules worth setting
WooPayments' fraud protection rules are in Payments, Settings, in the Fraud Protection section. Basic gives the standard level. Advanced lets you set rules of your own, under Configure:
- Purchase Price Threshold: a lowest and highest order total. Card testing usually means many small purchases; WooPayments' card testing page shows a rule that blocks orders under $5 as an example.
- AVS Mismatch: the postal code the shopper typed doesn't match the one the card's bank has. Not every country or bank supports this check.
- International IP Address: the shopper's IP address is outside the countries you sell to. It isn't there if you sell to every country.
- IP Address Mismatch: the shopper's IP address is in a different country from their billing address.
- Address Mismatch: the billing and shipping countries differ.
- Order Items Threshold: a fewest and most items per order.
A blocked order is left in Pending payment, and the shopper sees a general payment error. During an attack, WooPayments' advice is to tighten the rules and keep an eye on them until it's over. If more than 20 or so orders went through before you noticed, its card testing page says to contact WooPayments support about refunding them in bulk.
WooCommerce's general card testing guide adds a few more steps: if bots are going for donation or name-your-price products, make them private for a while; turn off guest checkout; and add a CAPTCHA.
The gap the rules leave
Each of those rules looks at one order at a time. None of them counts how many times the same email address has failed, how many payments have failed across your store this hour, or whether the shopper ever opened your checkout page. Card-testing bots switch IP addresses and names between tries, so each order on its own can look fine.
Counting is the part that has to happen in your store:
- Count failed payments, per connection, per email address and across the whole store.
- Attack mode: when failed payments pile up across the store, only take payments from shoppers who opened your checkout page. Bots that send orders straight to checkout never do.
- Guard every way in: the classic checkout, the checkout block's Store API and pay-for-order pages. A CAPTCHA that only sits on the checkout page never runs for bots that skip it.
- WooCommerce's own checkout limit (free): Rate limit Checkout in WooCommerce, Settings, Advanced, Features. It's off by default; turned on, it allows 3 checkout tries a minute from each shopper. It slows a bot down; it doesn't stop one that switches addresses.
Being card-tested right now? Start with the free steps in the failed orders guide: find and refund any orders that went through, tighten the rules above, and contact WooPayments support.
How Ropeline Pro does it
Ropeline Pro is a WordPress plugin that watches your WooCommerce checkout and steps in on its own:
- 5 failed payments from one connection or one email address in an hour: that shopper's checkout pauses for an hour.
- More than 6 checkout tries from one connection in 10 minutes: they're asked to wait 10 minutes.
- 10 failed payments across your store in an hour: attack mode for 2 hours. Only shoppers who opened your real checkout page can pay, which stops bots that send orders straight to checkout, from any address. You get an email when it starts.
- Works with the classic checkout, the checkout block and pay-for-order pages.
What we've checked with WooPayments, and what we haven't: WooPayments' code marks a declined card's order as Failed, and failed orders are what Pro counts. Orders its own fraud rules block stay in Pending payment, so Pro doesn't count those (WooPayments already stopped them). We haven't run a real WooPayments decline through Pro yet, because WooPayments needs a WordPress.com connection our test stores don't have. Pro's checkout-tries limit doesn't depend on the payment provider at all.
Not ready for Pro? The free Ropeline plugin counts your failed orders. When 10 or more payments fail within 24 hours, it warns you on its Overview and in the WordPress Dashboard, with what to do next. And the free store check shows in 10 seconds whether your checkout takes orders straight from scripts.
Store plan: a free week, no card, then $15 a month for stores with up to 500 orders a month ($39 up to 3,000, $99 for any size).
Install in a few minutes: download, upload to WordPress, paste your key. Cancel anytime and your site keeps the free plugin.
Start a free week, no card Check my store freeQuestions
Should I set the fraud protection rules if I use Ropeline Pro?
Yes. They're free, and they stop single orders that look wrong. Pro adds the counting across orders that the rules don't do.
Why are my blocked orders in Pending payment, not Failed?
That's how WooPayments marks an order its fraud rules stopped. Your store's Retain pending orders setting, in WooCommerce, Settings, Accounts & Privacy, decides how long all pending orders are kept.
Will Ropeline Pro block my real customers?
It's built not to. A pause only follows repeated declines from the same connection or email. During attack mode, shoppers who go through your checkout page, as almost everyone does, can still pay. Logged-in customers who have paid before skip the checkout-tries limit and attack mode.
I use the Stripe plugin instead. Is that different?
Yes: its settings live in your Stripe Dashboard. See Stripe card testing on WooCommerce.