Short answer
The Store API checkout, /wp-json/wc/store/v1/checkout, takes orders from any script, not only from the Checkout block, so bots can test cards without loading your site. WooCommerce can rate-limit it, but that is off by default: switch on “Rate limit Checkout” under Advanced → Features. Then add checks that tell a shopper from a script, because bots rotating IP addresses slip under rate limits.
Why the Store API is a target
The Checkout block places orders through the Store API, and the route is public by design. WooCommerce’s developer blog has reported card-testing attacks aimed at the Store API alone, even on stores that do not use the Checkout block.
You cannot simply switch the Store API off if you use the Cart or Checkout blocks, because they depend on it.
Switch on WooCommerce’s rate limiting
In WooCommerce 11.3 the switch is “Rate limit Checkout” under WooCommerce → Settings → Advanced → Features. With it on, the Store API checkout and the Checkout block’s Place order are limited to 3 requests per 60 seconds per shopper: logged-in shoppers by account, guests by IP address (November 2026).
For other limits, a developer can use the woocommerce_store_api_rate_limit_options filter. The documented defaults are 25 requests per 10 seconds, and only POST requests are limited.
Leave proxy support off unless the site sits behind a proxy or load balancer you control. With it on, the IP address is read from headers such as X-Forwarded-For, which a bot can set to anything.
add_filter( 'woocommerce_store_api_rate_limit_options', function () {
return array(
'enabled' => true, // Default: false
'proxy_support' => false, // Default: false
'limit' => 25, // Requests per time frame. Default: 25
'seconds' => 10, // Time frame in seconds. Default: 10
);
} );Why a rate limit is not enough on its own
Card-testing tools spread their attempts across many IP addresses, often home connections rented through proxy services, so each address stays under the limit. A rate limit slows a crude bot; it does not tell a shopper from a script. Stripe’s documentation makes the same point: filters based on a single signal such as IP address are usually not enough by themselves.
Steps with Brickmoat
Install the free plugin
Brickmoat checks the Store API checkout and its batch route before the order is created, as well as the classic checkout, pay-for-order and “Add payment method”.
Browser token on every order
Brickmoat adds a browser token to the Checkout block’s requests by itself. A request without one, from a script that never loaded a page, scores high on its own.
Counting beyond the IP address
Attempts and declines are counted per IP address, network range, email, device and billing address, so rotating one of them does not reset the count.
Lockdown during an attack
When declines spike, a missing token means a block, every guest is asked the “I’m human” question, and the store relaxes after 60 quiet minutes.
The plugin is free, with nothing to set up. Read the plugin guide or see what Pro adds.
Limits to know about
- Brickmoat does not replace a firewall or rate limits at your host; it works alongside them.
- A bot that drives a real browser can obtain the token. It is then caught by counting and lockdown, not by the token alone.
- If the plugin cannot complete a check, the order is allowed and the error is logged.
Related questions
Can I disable the WooCommerce Store API?
Not if you use the Cart or Checkout blocks, which rely on it. On a classic-checkout store a developer can restrict it, but test carefully, because themes and other plugins may use it too.
What happens when a shopper hits the rate limit?
WooCommerce refuses further checkout requests until the time frame has passed and sends headers saying when to retry. A real shopper rarely places three orders in one minute.
Do I need to change anything in the Checkout block for Brickmoat?
No. The plugin attaches its token to the Checkout block’s requests itself, and works with the classic checkout too.