Black Friday card testing checklist for WooCommerce
A guide for store owners. Updated November 6, 2026.
Black Friday is November 27 and Cyber Monday is November 30. Card testing is when bots run stolen card numbers through your checkout to see which ones work. A sale makes it harder to deal with: failed orders are easier to miss among real ones, and a fix made in a hurry can stop real buyers on your busiest day. So make your changes now, while a mistake costs little.
This week: close the easy doors
- Run the free store check. It shows in 10 seconds whether your checkout takes orders straight from scripts.
- Turn on WooCommerce's own checkout limit (free). It's the Rate limit Checkout switch in WooCommerce, Settings, Advanced, Features, on recent WooCommerce versions, and it's off by default. It allows 3 checkout tries a minute from each shopper. It slows a bot down; it doesn't stop one that switches addresses.
- Look at your payment provider's fraud settings. In Stripe, that's Radar: see the January change below. PayPal and others have their own settings.
- Make sure failed orders reach a person. Check that the Failed order email in WooCommerce, Settings, Emails is on, and goes to an inbox someone will read during the sale.
By November 20: test it like a buyer
- Buy something from your own store in a private browser window. Try each way to pay: card, PayPal, Apple Pay or Google Pay, and buttons on the product page if you have them.
- Do it again as a new customer and as a returning one. Security tools and new checkout settings can treat them differently.
- Stop adding things after that. Every change after your last test is one you haven't tried on a real order. If you do have to change something, buy again afterwards.
On the day: know your first hour
- Learn the signs. Failed orders in a burst, small amounts, different names and addresses, often for the same cheap product. The failed orders guide shows what to look for.
- Keep your provider's support contact handy. Tell them early if you're being tested. Some providers restrict accounts after an attack.
- Keep the under-attack page open in a tab. It has the steps in order, and a person answers if you email.
If you use Stripe: Radar's pricing changes on January 22, 2027
This doesn't change anything on Black Friday, but it's worth knowing before you touch your Radar settings. All of this is from Stripe's notice and its pricing page, read on November 6, 2026.
- There are now four tiers: Lite, Standard, Plus and Pro.
- If you used Radar on Stripe's standard pricing before July 29, 2026, you've been on a free trial of Standard since that date. If you do nothing, you stay on Standard and Stripe starts charging for it on January 22, 2027.
- Lite costs nothing extra on standard payments pricing, and you can switch to it from your Stripe Dashboard. Stripe says it protects against card testing and covers card payments.
- Standard starts at $10 monthly, or pay as you go. It adds all payment methods, fraud analytics, and default allowlists and blocklists.
- Custom rules need Plus or Pro, which start at $14 and $20 monthly.
What we'd do: nothing before the sale, because the trial runs past it. In December, look at how much Radar has blocked for you (Stripe shows this in your Dashboard) and decide before January 22.
Before you move to Lite, check that you keep what you use. Stripe's docs list blocking payments that fail the CVC or postal code check among Radar's built-in rules, but its pricing table doesn't say whether Lite has them. Your Dashboard will show you.
Where Ropeline fits next to Radar
Ropeline doesn't replace Radar. Radar judges each payment, after the bot has already reached your checkout. Ropeline Pro is a WordPress plugin that watches your WooCommerce checkout, and counts failed payments per connection, per email address and across the whole store:
- 5 failed payments from one connection or one email address in an hour: that shopper's checkout pauses for an hour.
- 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.
- Logged-in customers who have paid before skip attack mode.
- It works on payment gateways that mark a declined payment as failed.
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.
When to install
Ropeline's first 7 days only watch, apart from attack mode, which works from the first attack. So install by November 20 if you want that week over before the sale. You can also turn learning mode off in the settings.
The free week lasts 7 days, so one started on November 20 ends on Black Friday. To stay covered through the weekend, the 14-day trial started that day runs to December 4. Cancel before day 15 and you pay nothing.
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 freeRather not set it up alone? Start a free week and tick "Set it up with me". The person who builds Ropeline emails you to set a time, then sets up Ropeline Pro with you on a free 20-minute screen-share.
You share your screen and do the clicks: we never ask for your password or a login to your store. If card testing is happening right now, tick that too and your call comes first. There are 10 of these calls, first come, first served.
Start a free week, set it up with meQuestions
Will this block real buyers during the sale?
It's built not to. A pause only follows repeated declines from the same connection or email. In attack mode, shoppers who go through your checkout page, as almost everyone does, can still pay. Still, test your own checkout before the sale, whatever you run.
Should I add a CAPTCHA to checkout for the sale?
Only if you can test it first. A CAPTCHA that sits on the checkout page never runs for bots that skip the page, so it also has to guard ?wc-ajax=checkout and the Store API. See WooCommerce bot protection, door by door.
Do declined cards cost me money?
It depends on your payment plan: on some, a declined card adds a fee. Check your provider's pricing. Stripe's Radar pages don't say whether blocked attempts are charged, so we won't guess.