Short answer
Confirm it in the Stripe Dashboard: a spike of failed or blocked payments for small amounts with nonsense names. Refund any test payments that succeeded, so they do not turn into disputes. Then stop the attack at your WooCommerce checkout, because Stripe only sees each attempt after your store has sent it: guard every checkout route, count declines and lock down while the attack lasts.
How to confirm it in Stripe
Stripe’s documentation says most attacks are obvious in the Dashboard. Look for:
- A spike in failed or blocked payments on the Dashboard home page and the payments list
- Payments marked “Blocked by Stripe”
- A spike of card errors in the Developers logs, often with the decline code generic_decline
- Small payments with nonsense customer names and emails
Why it matters even when Stripe blocks it
Stripe lists the costs: test charges that succeed turn into early fraud warnings and disputes; a high decline rate can make card issuers treat your genuine payments as riskier, even after the attack; some pricing plans add authorisation fees; and heavy card testing can put the account into a card-network monitoring programme.
Visa’s acquirer monitoring programme, VAMP, also counts card-testing (“enumeration”) activity, which is one more reason payment providers act quickly on it.
Refund what got through
Stripe recommends refunding fraudulent payments that succeeded, to head off disputes. Do it before anything ships, and cancel the matching WooCommerce orders.
Steps with Brickmoat
Install the free plugin
Brickmoat checks every WooCommerce checkout route before the order reaches Stripe, so blocked attempts never become Stripe payments at all.
Start lockdown if it is still going
Press “Start lockdown” on the Overview to tighten every check straight away for 24 hours. Otherwise lockdown starts by itself when declines spike.
Clean up the failed orders
The Cleanup screen moves the attack’s failed and unpaid orders to Trash, with undo. Refund successful test charges in Stripe yourself.
Optional: send Stripe a report
Pro ($19 per month, or $149 a year) builds a report of each attack, with its times, attempts, declines and what was switched on, as a web page and PDF you can send Stripe.
The plugin is free, with nothing to set up. Read the plugin guide or see what Pro adds.
Limits to know about
- Brickmoat guards WooCommerce’s checkout routes and the PayPal Payments button. Requests the Stripe plugin makes on its own, such as saving a card through Stripe’s fields, are left to Stripe’s protections.
- It does not refund or cancel payments in Stripe; that stays in your Stripe Dashboard.
- A bot that imitates a real browser can get a few attempts through before declines trigger lockdown.
Related questions
Does Stripe Radar stop card testing on WooCommerce?
It helps: Stripe’s card-testing protection and Radar block many attempts. But each attempt still reaches Stripe from your store, and declines still count against you, so stopping bots before Stripe is contacted reduces the damage.
Will Stripe close my account because of card testing?
Stripe says card testing is shared responsibility between merchants, card networks and Stripe. Fixing it quickly and refunding what got through is what they expect; heavy or repeated attacks can lead to card-network monitoring.
Do I pay Stripe for declined card-testing attempts?
That depends on your Stripe pricing. Stripe’s documentation mentions authorisation fees on custom pricing plans and dispute fees for test charges that succeed.