Square card testing on WooCommerce: the Risk Manager rules to set, and what your orders hide
A guide for store owners who take payments with the WooCommerce Square plugin. Updated November 16, 2026.
Card testing is when bots run stolen card numbers through your checkout, one after another, to find the ones that still work. If your store takes cards through the WooCommerce Square plugin, those tries go to Square. Here's what Square gives you for free, what your order list will and won't show, and what else limits the bots. Everything about Square here comes from Square's own help pages on Risk Manager and 3D Secure, and from the WooCommerce Square plugin's code (version 5.5.3), read on November 16, 2026. We haven't run the Square plugin on our own test store.
Set up Square's Risk Manager (free)
Risk Manager is Square's own set of fraud rules for online payments. Square's 3D Secure page says it's free for payments taken through third-party integrations, which is what the WooCommerce Square plugin is.
- In your Square Dashboard, go to Payments & invoices, Risk Manager, click Get started and enroll.
- Under Rules, click Create rule for each of these:
- CVV invalid: decline. A real shopper who mistypes the security code can fix it and try again.
- Square's risk evaluation is high: require 3D Secure. The shopper's bank then asks them to confirm the payment, which a bot can't do. If you'd rather not add a step for anyone, choose decline instead.
- Postal code (AVS) mismatch: alert. Real shoppers mistype their postal code, so start with an alert, not a decline.
- Under Notifications, choose who gets Risk Manager's alerts.
Two things to know. Square describes Risk Manager's purchase limit as how many times a customer can complete a purchase in a day, so it's aimed at repeat purchases, not declined tries; it won't catch card testing on its own. And Square's 3D Secure page says some sellers need to update the integration on their website before 3D Secure rules work, and Risk Manager shows a banner if so. The WooCommerce Square plugin's code sends Square's buyer check along with the card when its checkout script makes one.
What your order list will and won't show
When Square declines a card at checkout, the WooCommerce Square plugin's code marks the order Failed, adds a note with Square's reason, and asks the shopper to try again. Two kinds of tries don't show as one failed order each:
- Card after card on the same order. WooCommerce reuses an unpaid order when the shopper tries again with the same cart. When that order is already Failed, the Square plugin adds another note instead of marking it Failed again. So one failed order can hold many declined cards: open it and count the payment-failed notes.
- Cards saved in My Account. If your store lets customers save a card under My Account, Payment methods, the Square plugin sends that card to Square with no WooCommerce order at all. A card declined there leaves nothing in your order list. WooCommerce makes each account wait 20 seconds between saved cards.
So check your Square Dashboard's payments, not only your WooCommerce orders, when you suspect card testing. What else helps:
- Turn off saving cards if your customers don't need it and your payment plugin lets you. WooCommerce's card testing page suggests turning off saved cards when your store is under attack but you don't see many failed orders, because bots can test cards by saving them to an account.
- 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.
- Count failed payments per shopper and across the store, not just failed orders, for the reason above.
Being card-tested right now? Start with the free steps in the failed orders guide, and tell Square.
How Ropeline Pro handles Square
Ropeline Pro is a WordPress plugin that watches your WooCommerce checkout and steps in on its own, next to Square's Risk Manager:
- 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.
- Every decline counts, even on the same order. When a shopper pays again for a failed order, Pro puts it back to Pending first, as a new order would be, so the next decline counts too.
- Saving a card in My Account is covered too. In the Square plugin's code, saving a card goes through WooCommerce's own Add payment method form, which Pro watches. Cards that fail to save there count like failed payments.
- Works with the classic checkout, the checkout block and pay-for-order pages.
We test these on our own test store with a payment method that always declines. We haven't run real Square declines.
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.
Taking cards with Stripe or PayPal as well? See Stripe card testing on WooCommerce and PayPal card testing on WooCommerce.
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
Will 3D Secure stop real customers?
It adds a step for the payments your rule picks: the shopper's bank asks them to confirm, often in their banking app. Square's page notes that banks can also decline more of those payments. That's why the rule above only asks for it when Square rates a payment high risk.
Does this apply to Square's own online store?
No. This guide is about WooCommerce stores that take payments through the WooCommerce Square plugin. Risk Manager's rules are set in your Square Dashboard either way.
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.