Security · Guide
How to Stop Card Testing Attacks on WooCommerce
Short answer
To stop card testing attacks on WooCommerce, add a bot check such as Cloudflare Turnstile to checkout, set order-attempt and failed-payment limits, and use your payment gateway fraud rules. Turn on 3D Secure for risky payments and rate limit checkout traffic at the edge. Check failed orders daily until the spike ends.
Key takeaways
- Card testing uses many small checkout attempts to find which stolen card numbers still work.
- Start an active attack with Checkout CAPTCHA, order-attempt limits and failed-payment caps, not lower fraud scores.
- WooCommerce Anti-Fraud Medium preset allows 5 orders in 24 hours and 3 failed payments.
- Stripe Radar can block more than 1 successful charge from one IP address in an hour.
- WooPayments supports 3D Secure on checkout and the Pay For Order page at no added fee, as of November 2026.
- Cloudflare rate limiting can challenge 4 failed requests in 1 minute and block 20 in 1 hour.
What is a card testing attack on WooCommerce?
A card testing attack is automated checkout abuse where stolen card numbers are tried in small orders to find which cards still work.
Attackers run many low-value attempts, often with changed emails, IP addresses and card details between tries. WooCommerce Anti-Fraud docs describe this pattern as repeated checkout attempts, rapid failed payments and large numbers of failed orders (Anti-Fraud for WooCommerce).
Each attempt can create a failed order, send admin email and use gateway resources.
How do you know your store is under a card testing attack?
You are likely under attack when failed low-value orders spike sharply from many new emails, cards or IP addresses in a short time.
Look in WooCommerce > Orders for a run of failed or pending orders with small totals. Check whether the billing names, emails and card types change often while the order value stays low.
WooCommerce Anti-Fraud docs list the same signs: repeated checkout attempts, rapid failed payments, large numbers of failed orders, and attackers changing email addresses, IP addresses, cards and other details (Anti-Fraud for WooCommerce).
Also check your gateway dashboard for a rise in declines. A sudden cluster of declines on low amounts is a stronger signal than one failed order. Note the start time, the common amounts and the payment method used.
Wordfence sends an “Increased Attack Rate” alert when its firewall records at least 100 blocks in 10 minutes, as of November 2026 (Basic Plugin Settings). That alert alone does not prove card testing, but it can confirm a wider automated attack.
What should you do first during an active attack?
During an active attack, turn on Checkout CAPTCHA first, then set order-attempt and failed-payment limits.
WooCommerce Anti-Fraud docs give this exact order: start with Checkout CAPTCHA, Order attempt limits and Cap failed payments per order, and do not begin by lowering every fraud-score threshold (Anti-Fraud for WooCommerce). Lowering scores first can block real customers and hide which rule actually helped.
Follow these steps in order:
- Enable a checkout bot check, such as Cloudflare Turnstile or Google reCAPTCHA v2, in WooCommerce > Settings > Anti-Fraud.
- Enable Limit orders per buyer and Cap failed payments per order under Card testing protection.
- Turn on Progressive checkout delay if it is available, so failed payments add waiting time.
- Check WooCommerce > Orders and note the failed orders from the attack period before you delete anything.
- Tell your payment gateway support that you see automated testing, and ask what fraud controls it can add.
Do not delete failed orders at once. WooCommerce docs warn that deleting an order does not remove data already sent to a payment provider, accounting platform or fulfilment tool (Anti-Fraud for WooCommerce).
How do you add a bot check to WooCommerce checkout?
Add Cloudflare Turnstile or Google reCAPTCHA v2 to checkout, and use only one bot check on that form.
WooCommerce Anti-Fraud supports Cloudflare Turnstile and Google reCAPTCHA v2 as Checkout CAPTCHA options. It does not support Google reCAPTCHA v3 for this use, because v3 uses a background score rather than the challenge flow this integration needs (Anti-Fraud for WooCommerce).
To set up Turnstile in WooCommerce, follow these steps:
- Create a free Cloudflare account and open Turnstile in the Cloudflare dashboard.
- Click Add widget, add your hostname, choose Managed mode, and copy the Site Key and Secret Key.
- In WordPress, go to WooCommerce > Settings > Accounts & Privacy > Customer Accounts and click Cloudflare Turnstile.
- Check Enable Cloudflare Turnstile, select Classic Checkout under Forms, paste both keys and click Save changes.
WooCommerce docs for Turnstile list the same path and note that you need a free Cloudflare account to get the keys (Configuring Cloudflare Turnstile). The same page says Turnstile runs a challenge invisibly in the background and only interrupts users when suspicious behaviour is detected.
Place a real test order after setup. Use a low-value product, complete checkout as a guest if your store allows it, and confirm the order reaches the expected status. For more detail, see how to add Cloudflare Turnstile to WordPress.
How do you set order and failed-payment limits in WooCommerce?
Set a limit on orders per buyer and a cap on failed payments per order, then pick a preset that matches your normal order volume.
Go to WooCommerce > Settings > Anti-Fraud and open Card testing protection. Enable Limit orders per buyer to cap how many orders a buyer can place inside the rolling window. Enable Cap failed payments per order to stop repeated declines against the same order and related failed orders (Anti-Fraud for WooCommerce).
Anti-Fraud scores checked orders from 0 to 100. Lower scores mean fewer risk signals, and higher scores mean more or stronger signals. The presets below are the starting values in the WooCommerce docs, as of November 2026.
| Preset | Medium / High threshold | Hold / Cancel score | Order-attempt limit | Failed-payment limit |
|---|---|---|---|---|
| Low | 40 / 85 | 85 / 95 | 8 orders / 24 hours | 5 |
| Medium | 25 / 75 | 70 / 90 | 5 orders / 24 hours | 3 |
| High | 20 / 60 | 55 / 85 | 3 orders / 24 hours | 2 |
Start with Medium for most stores. High uses Advanced counting, while Low and Medium use Orders only counting in the preset table. Advanced counting combines order and failed-payment signals and can use cart fingerprint and session data when attackers rotate details (Anti-Fraud for WooCommerce).
Enable Run check before payment only when you need to stop a high-risk checkout before payment completes. When it is on, a checkout that reaches the High Risk threshold can be blocked with the message set under Message for blocked checkouts.
Use at least 2 allowed attempts for Add payment method protection, so a single typo does not block a real customer. Version 8.0.7 of Anti-Fraud adds protection for My Account > Add payment method, including limits, a temporary lock and a minimum account age option.
How do you use Stripe Radar rules to block card testing?
Use Stripe Radar velocity rules to block repeated charges from one IP address or one card number in an hour.
Stripe Radar evaluates rules in a fixed order: Request 3DS first, then Allow, Block and Review. Once a rule matches, no later rule is checked.
Allow rules need care, because they override other rules except 3DS rules. Only merchants that have processed more than $100,000 can write allow rules (Radar for Fraud Teams: Rules 101).
Stripe lists these card-testing rules in its Radar guide:
Block if :total_charges_per_ip_address_hourly: > 1Block if :blocked_charges_per_ip_address_hourly: > 1Block if :total_charges_per_card_number_hourly: > 1Block if :address_zip_check: != 'pass'Block if :cvc_check: != 'pass'
The first rule blocks charges if one IP address was authorised more than once in the past hour. The second rule is a more aggressive companion to the first. The card-number rule blocks a card that was authorised more than once in the past hour (Radar for Fraud Teams: Rules 101).
The postcode and CVC rules only work if you collect those fields at checkout. Stripe notes that you must collect postcodes to use the postcode rule, and CVC to use the CVC rule.
Do not use a strict != 'pass' rule if many real customers use issuers that return unavailable or unchecked. Those payments would also be blocked.
Backtest a rule before you turn it on. Stripe says you can backtest combinations using transaction data from the last 6 months in the Radar Dashboard. Start with Review for a new rule, watch what it would have caught, then change it to Block.
How does 3D Secure help against card testing?
3D Secure helps because it asks the cardholder to complete an extra check with their bank, which automated card testing cannot complete.
3D Secure is also called 3DS or SCA. WooPayments supports it on both the checkout page and the Pay For Order page. In most cases, a customer using a protected payment method is prompted to pass an extra verification step to complete the transaction (Does WooPayments support 3D Secure?).
There is no additional fee for transactions that trigger 3DS authentication with WooPayments, as of November 2026. You can test the flow with a 3D Secure test card while WooPayments is in test mode.
Use 3D Secure for risky payments, not for every order. In Stripe Radar, you can request 3D Secure when the risk is high or when the card country differs from the IP country. That keeps friction low for normal local orders and adds a check where the risk is higher.
Learn what WooPayments includes in what is WooPayments. If your store uses Stripe directly, check the same 3DS settings in your Stripe dashboard and in your WooCommerce Stripe plugin settings.
How do you rate limit checkout traffic at the edge?
Rate limit checkout and login paths at the edge so repeated requests from one IP are challenged or blocked before they reach WordPress.
Cloudflare docs explain that Turnstile and rate limiting work best together. Turnstile challenges automated form submissions, while rate limiting catches high-volume attacks that bypass the form, such as direct POST requests to the endpoint (Stop malicious bots).
Cloudflare gives a tiered example for login endpoints that you can adapt for checkout:
- Short window: challenge an IP that sends 4 failed requests in 1 minute.
- Long window: block an IP that sends 20 failed requests in 1 hour, for 1 day.
The same Cloudflare guide gives a checkout example of 10 requests per 1 minute for a high-frequency path. Adjust the path, rate and action for your own checkout URL and traffic. Start with Managed Challenge, not Block, and review Security Events before you make a rule stricter.
Bot Fight Mode is included with Free Cloudflare plans. It identifies traffic that matches known bot patterns and issues a computational challenge, without requiring you to write rules (Stop malicious bots).
At the WordPress level, keep your firewall on and set to Extended Protection where possible. For Cloudflare setup, see Cloudflare WAF rules for WordPress.
Wordfence docs recommend Protection Level set to Extended Protection and Firewall Status set to Enabled and Protecting, once Learning Mode is not needed (Basic Plugin Settings). For WordPress setup, see how to set up the Wordfence firewall.
How do you protect the PayPal and Add payment method paths?
Protect every payment path, not only the main checkout form, because attackers use direct API paths that skip the checkout page.
WooCommerce velocity docs report a surge in card testing on stores using the PayPal Payments extension, version 3.1.2 and newer, with hundreds or thousands of fake transactions in minutes (Velocity Attacks). PayPal Advanced Card Processing can allow direct API-based payments that bypass reCAPTCHA and normal checkout validation.
For PayPal, WooCommerce docs list these steps:
- Go to WooCommerce > Settings > Payments > PayPal > Advanced Card Processing.
- Disable Enable Advanced Card Processing if direct card entry is being abused.
- Customers can still pay by card through the Debit/Credit Card option in the PayPal popup.
- Enable PayPal Card Attack Protection and fill in all three fields.
The recommended PayPal card attack values in the WooCommerce docs are a rolling window of 300 seconds, 3 to 5 attempts per window, and 10 attempts per hour (Velocity Attacks). If a field is left blank, checkout can fail with a too-many-attempts error or remain unprotected.
Also protect My Account > Add payment method. Anti-Fraud version 8.0.7 adds limits there, including a maximum number of attempts, a counting window, a temporary lock and a longer lock for repeat abuse. You can also require a minimum account age or a previous processing or completed order before a customer can add a payment method.
How do you check that the attack has stopped?
The attack has stopped when failed low-value orders fall back to normal levels for 24 to 48 hours and real checkouts still complete.
Check these items each day during recovery:
- WooCommerce > Orders: failed orders per day, by payment method and order total.
- Your gateway dashboard: declines per hour, and whether the same IP or card pattern has gone.
- Anti-Fraud matched rules: which rules fired, and whether real customers triggered them.
- Cloudflare Security Events: which rate limiting rules fired, and whether they caught only bot traffic.
- Wordfence Live Traffic or firewall logs: blocked checkout requests and any new IP ranges.
Keep the bot check and the limits on after the spike ends. Removing them at once invites a repeat attack from the same card list. Lower a limit only after a full day with normal failed-order counts and no new attack pattern.
Place test orders through each important checkout path. WooCommerce Anti-Fraud docs list this as a setup step: place test orders through every important checkout and payment path, then open the orders and confirm the expected risk score, matched rules and order status (Anti-Fraud for WooCommerce).
What mistakes should you avoid?
Avoid lowering fraud scores first, running two bot checks at once, and leaving a payment path unprotected.
These mistakes cause the most harm during card testing:
- Lowering Medium and High thresholds before you add CAPTCHA and limits, which blocks real customers.
- Running Turnstile and reCAPTCHA together on checkout, which can cause duplicate widgets and failed verification.
- Leaving PayPal Advanced Card Processing on while card testing hits its direct API path.
- Leaving a PayPal card attack field blank, so protection does not activate.
- Deleting failed orders before you review them, which removes the pattern you need to block.
- Turning off protection as soon as the spike pauses, instead of watching for 24 to 48 hours.
- Using a strict postcode or CVC block rule when many real customers have issuers that return unavailable.
Fix one layer at a time and test checkout after each change. If a real order is blocked, note the matched rule, the payment method and the order total before you change the rule. A narrow allow-list for a trusted customer is safer than weakening a rule for every customer.
Frequently asked questions
Will card testing attacks cost me money even if no order completes?
Yes, they can. Failed attempts still create failed orders, admin email and gateway traffic, and successful test charges can lead to disputes later. Check your gateway dashboard for declines and fees, and keep bot checks and velocity limits on after the spike ends so the same card list is not tried again.
Should I disable guest checkout to stop card testing?
Disabling guest checkout can slow an attack, because it forces account creation, but it also adds friction for real buyers. Try a bot check and order limits first. If attacks continue through guest checkout, require login only for your lowest-price products or for the payment path being abused, then watch conversion.
How long should I keep the extra limits in place?
Keep the bot check and the order and failed-payment limits on for at least 24 to 48 hours after failed orders return to normal. If the pattern stays gone for that period and real checkouts complete normally, you can loosen a limit one step at a time. Do not remove all protection at once.
Can I stop card testing with WooCommerce Anti-Fraud alone?
Anti-Fraud helps a lot, but it works best as one layer. Pair it with a checkout bot check, gateway fraud rules such as Stripe Radar, 3D Secure for risky payments, and rate limiting at the edge. Attackers often switch paths, so a single plugin rarely covers checkout, PayPal and Add payment method together.
What should I do if real customers are blocked after I add protection?
Find the blocked order and note which rule matched, the payment method and the order total. Raise the limit that caught the customer, or add a narrow allow-list for that trusted customer, instead of turning off all protection. Place a test order through the same path to confirm the fix before you loosen more rules.
Sources
- Anti-Fraud for WooCommerce WooCommerce
- Radar for Fraud Teams: Rules 101 Stripe
- Configuring Cloudflare Turnstile WooCommerce
- Velocity Attacks Documentation WooCommerce
- Does WooPayments support 3D Secure? WooCommerce
- Stop malicious bots while allowing legitimate traffic Cloudflare Developers
- Basic Plugin Settings Wordfence
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.
Thanks — we review requests within 3 business days.
