Short answer
Only partly. A CAPTCHA stops bots that fill in your checkout page, but card-testing tools often post straight to the Store API, the classic checkout request or a payment plugin’s own request, where a CAPTCHA that only sits on the page is never checked. It has to be verified on the server for every route that can charge a card, and works far better alongside decline counting and lockdown.
Where a checkout CAPTCHA helps
Google reCAPTCHA, Cloudflare Turnstile and hCaptcha all raise the cost of filling in a form with a script, and stop simple bots that drive a browser through your checkout page.
Why it often fails against card testing
Stripe’s own advice for a CAPTCHA that has not stopped card testing is to make sure it is required on every request that can validate a card or take a payment, and that it is checked on the server. On WooCommerce stores, the usual gaps are:
- It is added to the classic checkout page but not to the Store API that the Checkout block uses
- It is shown in the browser but never verified on the server, so a script can leave it out
- A payment plugin’s own request, such as PayPal Payments’ create-order call, skips it
- Solving services pass many challenges for a fraction of a cent each
Keep it out of real shoppers’ way
A challenge on every checkout costs some genuine sales, especially on phones. Showing one only to checkouts that look risky, or to every guest only while an attack is running, means most shoppers never see one.
Steps with Brickmoat
Install the free plugin
Brickmoat quietly checks for a real browser on every checkout route, on your server, with nothing for shoppers to do.
Unsure cases get an “I’m human” check
A checkout that looks risky but not certain is asked a quick “I’m human” question instead of being blocked, and the order goes ahead once it is answered.
Every guest is asked during lockdown
When declines spike, lockdown asks every guest checkout the question until the store has been quiet for 60 minutes. Outside an attack, most shoppers never see it.
Optional: use Cloudflare Turnstile
Add your Cloudflare Turnstile keys in Brickmoat’s settings and the question becomes a Turnstile check, verified with Cloudflare from your server.
Watch the event log
Each challenge and block is listed with its reason, so you can see who was asked and why.
The plugin is free, with nothing to set up. Read the plugin guide or see what Pro adds.
Limits to know about
- No challenge stops every bot, because solving services exist. That is why Brickmoat also counts declines and locks down rather than relying on the challenge.
- Turnstile needs a free Cloudflare account and its two keys. Without them the plugin uses its own simple “I’m human” check.
- If Cloudflare cannot be reached to verify an answer, the shopper is let through rather than stuck at checkout.
Related questions
Is reCAPTCHA v3 enough for WooCommerce checkout?
It gives a score rather than a challenge, and how much it helps depends on the threshold you set and on it being checked for every checkout route. On its own it rarely stops a determined card tester.
What is a good reCAPTCHA alternative for WooCommerce?
Cloudflare Turnstile and hCaptcha work in a similar way. Which one matters less than whether it is verified on the server for every route that can charge a card.
Does a CAPTCHA lower conversions?
A visible challenge makes some shoppers give up, especially on phones. Show one only when a checkout looks risky or while an attack is running.