Founding offerThe first 10 online stores pay $9 a month instead of $15, for as long as they stay.Founding offer: $9 a month instead of $15 for the first 10 stores.Claim yours
Ropeline Try Pro free

Stripe card testing on WooCommerce: what Stripe stops, and what it can't

A guide for store owners who take cards with Stripe. Updated November 15, 2026.

Your WooCommerce store takes cards through Stripe, and bots are putting stolen cards through your checkout to see which ones work. Stripe does a lot against this already. This guide sets out what Stripe and its free WooCommerce plugin do on their own, what's worth turning on, and the part that has to happen in your store. Everything about Stripe here comes from Stripe's and WooCommerce's own documents and the Stripe plugin's code, read on November 15, 2026.

What Stripe already does

Stripe's guide is also clear about where its help stops. It suggests your own rate limits and login requirements on top, and says that on a plugin or platform, those usually take changes to code. On WooCommerce, that means a plugin.

What to turn on in your Stripe Dashboard

  1. Block payments that fail the CVC or postal code check. Open Radar, then its rules. Stripe lists both among Radar's built-in rules.
  2. Look at what Radar blocked. If you see a run of blocked or declined payments with different names and cards, you're being tested.
  3. If your Radar plan has custom rules, you can write your own on top. Which rules you get depends on your Radar plan: Stripe's pricing page has the details.

Radar's pricing changes on January 22, 2027, and Stripe doesn't say whether its cheapest plan keeps the CVC and postal code rules. What that means for your store is in the Black Friday checklist.

What the Stripe plugin limits on its own

Card testers don't only use your checkout. A bot logged in to a customer account can test cards under My Account, Payment methods, Add payment method, with no order at all, so nothing shows up in your order list. Two limits slow that down:

Both count per customer account. They slow one account down. They don't notice the same thing happening across many accounts, or across your whole store.

The gap that's left

Stripe sees each payment once it's sent. What it doesn't see is your store: who opened your checkout page, how many times the same email address has failed at your checkout, how many accounts are saving cards, how many payments have failed across the store this hour. Card-testing bots also switch IP addresses between tries, so a limit per address only goes so far.

That's the part that has to happen in WooCommerce, before the card reaches Stripe:

  1. Count failed payments, per connection, per email address and across the whole store.
  2. 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.
  3. Guard every way in: the classic checkout, the checkout block's Store API, pay-for-order pages and Add payment method.
  4. 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, turn on the Radar rules above, and tell Stripe.

How Ropeline Pro does it

Ropeline Pro is a WordPress plugin that watches your WooCommerce checkout and steps in on its own, next to Stripe and Radar:

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 free

Or 14 days free with a card

Questions

Doesn't Radar already stop card testing?

It stops a lot of it, and it's worth keeping. Radar judges each payment after the bot has reached your checkout. Counting failures across your store and turning on attack mode stops the bot before its next card gets to Stripe.

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 WooPayments, not the Stripe plugin. Is that different?

WooPayments runs on Stripe too, but its settings live in WooCommerce. See card testing with WooPayments.