Subscription includes
Support
Most fraud detection tools flag orders after payment has already been processed — leaving you with chargebacks, gateway fees, reputational damage and wasted time reversing transactions. Real-Time Fraud Detection and Blocking for WooCommerce takes a different approach.
When a customer clicks Place Order, this extension intercepts the checkout and screens the transaction through MaxMind’s minFraud risk detection network before your payment gateway is ever contacted, new in version 8.3.3, what you do with that score is your choice. Block high-risk orders instantly: no order is created, no payment is captured, and no chargeback is filed. Review the risk score and full MaxMind detail now recorded on every order after billing. Or combine both.
New in 8.3.3 — you choose how to fight fraud
Every order that goes through now shows its MaxMind risk score and screening result in two new columns on **WooCommerce > Orders**, and the full MaxMind response is written to the order notes in plain, readable form. Scan the Risk Score column straight down your Orders list, open any order to see why it scored the way it did, and run fraud control the way that fits your business:
This works because of when screening happens. Orders are screened before payment, so a declined order is never charged. An accepted order is charged — but the money is only truly lost once the goods ship. Until then you can cancel and refund: you may pay a processing fee, but you keep the stock and avoid the chargeback and its fee.
One caveat for review-only stores: keep your decline threshold below 100%. IP velocity protection stops card testing bots by counting declines — at a 100% threshold nothing is ever declined, so bots run unchecked and every attempt costs you a MaxMind query. A threshold in the 90s still sends virtually all real orders through for review while giving velocity protection the declines it needs to shut bots down.
Reviewing orders? Choose Insights or Factors. A Score query returns the risk number and little else. Insights and Factors return the IP, email, address and device detail you’ll want in front of you when you decide.
Most card testing bots still hammer a store in rapid bursts, and velocity protection shuts them down in minutes (see the case study below). But we’ve now met a newer breed: slow-rollers that pause a random 1 to 30 minutes between tests and roll across hundreds of IP addresses, so no single IP ever looks busy in a ten-minute window. We’ve extended the velocity system to catch them too.
Version 8.3.3 can now measure velocity in hours. Count declines per IP over a window of up to 24 hours, and block an offending IP for up to 72 hours. A bot that comes back to an IP twenty minutes — or six hours — later finds it already blocked, at no MaxMind query cost. Set Max attempts to 0 and an IP is blocked on its very first decline, so every address the bot burns is out of play for days and its pool shrinks with every attempt.
Blocked IPs are stopped before the MaxMind API is called, so no query credits are consumed. The shopping session is destroyed and the cart emptied, forcing the bot to start completely over. The block timer resets with each new attempt, so persistent bots stay locked out and give up.
A merchant’s store was hit by a card testing bot — 105 checkout attempts in under 20 minutes using randomized names, junk email addresses, and rotating IP addresses. Here’s what happened with velocity protection enabled:
Fraud attempts:Â 105
Reached payment: 0
Blocked by velocity: 92
Total cost to stop: $0.07
Every order scored 99% risk and was declined instantly before reaching the payment gateway. After 5 declines, velocity protection blocked the IP. The remaining 92 attempts consumed zero MaxMind queries. Destroying the session and emptying the cart forced the bot to rebuild its cart from scratch on every attempt.
When the bot rotated to a second IP, velocity caught it again. The bot gave up after about 20 minutes. Total cost: 13 MaxMind queries at approximately 7 cents.
That bot worked fast, as most still do. With velocity windows now also measured in hours, the same protection reaches the slow-rollers too.
Every checkout is screened through a multi-layer process designed to
maximize protection while minimizing query costs:
All of this happens in less than a tenth of a second. Legitimate customers experience no delay.
When a customer retries checkout with identical billing, shipping, and contact data — for example, after adding or removing a product to check shipping costs or sales tax — the extension serves the cached screening result instead of making another MaxMind API call. This can significantly reduce your query costs on stores with high retry rates.
The cache is automatically purged whenever you change your whitelist or risk thresholds, so cached decisions always reflect your current settings.
Getting up and running takes just a few minutes:
Real-Time Fraud Detection and Blocking for WooCommerce screens orders using MaxMind’s minFraud service. To perform this screening, checkout data is sent to MaxMind in real time: IP address, email domain, billing and shipping address and phone number, order amount, browser user agent and language, and a hashed shopping session ID. Email addresses are transmitted as MD5 hashes and session IDs as SHA-256 hashes, so neither reaches MaxMind in readable form. Customer names are not sent.
The risk score, screening result and MaxMind response for each order are saved with that order, where they remain for the life of the order record. Screening activity is recorded in WooCommerce’s logs to support fraud investigation and troubleshooting. The velocity protection, query cache and Storebot verification records are temporary and are cleared automatically. Screening statistics are daily counts only and contain no customer data.
No customer data is shared with any party other than MaxMind. If you turn on Google Storebot whitelisting, the extension also downloads Google’s published crawler IP ranges from Google, at most once a day; no customer data is sent with that request. Fraud prevention is recognized as a legitimate interest under GDPR and is explicitly permitted under the California Consumer Privacy Act (CCPA) as an activity that prevents security incidents and resists fraudulent or illegal activity. Merchants should include fraud screening in their store’s privacy policy, and merchants who keep MaxMind analysis on order records should account for that in their retention policy.
Yes — new in 8.3.3. Raise the decline threshold so only flagrant fraud and card testing bots are blocked, and every other order goes through with its MaxMind risk score in the Risk Score column of your Orders list and the full MaxMind response in the order notes. Review the high scores, then cancel and refund before you ship. Keep the decline threshold below 100% so IP velocity protection can still stop card testing bots, and choose Insights or Factors so there's detail to review.
Rapid-fire bots are caught within minutes. The slow-rollers pause a random 1 to 30 minutes between tests and move across hundreds of IP addresses. With the velocity window and block set in hours — up to 24 and 72 — any IP the bot returns to is already blocked, at no query cost. Set Max attempts to 0 and each IP is blocked on its first decline.
Yes. The extension screens orders before payment processing, so it works with all payment gateways — Stripe, PayPal, Authorize.net, and any other gateway that uses WooCommerce's standard checkout flow.
Screening happens in tenths of a second and is invisible to customers whose orders fall below your risk threshold. Only high-risk orders see a decline message, which you can customize — many merchants use it to invite the customer to call and place the order by phone, so even a mistaken decline need not cost the sale.
You control this. The extension lets you choose whether to accept or decline orders when MaxMind returns an error or is unreachable. An optional email notification alerts you when screening is skipped so you can review the order manually.
Not if you turn on Google Storebot whitelisting. Verified Storebot checkouts skip screening and velocity protection entirely, and you can get an email the first time Storebot shows up each day plus a summary the next day.
Orders with no shopper present — orders entered in the admin, scheduled renewals and orders from integrations — carry a staff or server IP address rather than the customer's. You choose how they're handled: whitelist them (recommended), screen them without IP or device data, or screen them normally.
Categories
Extension information
Quality Checks
Countries