The Real-Time Fraud Detection and Blocking extension for WooCommerce stops credit card fraud and card testing bots before payment processing thereby protecting you from charge-backs, gateway fees, and reputational damage. It’s easy-to-use and has provided robust enterprise level anti-fraud protection since 2009.
New in version 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 columns on WooCommerce > Orders, with the full MaxMind response in the order notes. Block high-risk orders before billing, review orders yourself after billing, or both. See Choosing Your Approach.
- IP velocity protection measured in hours. Most card testing bots still fire rapidly, but a newer breed pauses a random 1 to 30 minutes between tests and rotates across hundreds of IP addresses. The time window now runs up to 24 hours and the block up to 72 hours to catch them.
- Google Storebot auto-whitelist, Screening statistics, and a setting for orders with no shopper present (phone orders, subscription renewals, integrations).
The following document provides all the information you need to get setup and effectively use this extension.
Want to get started fast? Then scroll down to our Quick Start Guide.
Requirements
↑ Back to top- WordPress: 5.8 or higher (tested up to 7.1)
- WooCommerce: 7.0 or higher (tested up to 11.3.0)
- PHP: 7.4 or higher
- MaxMind Account: Requires a MaxMind minFraud account โ a free trial with 1,000 risk score queries is currently available here.
- cURL: PHP cURL extension must be enabled (standard on most hosts). Used by WordPress to communicate with the MaxMind minFraud API over HTTPS.
- Outbound HTTPS: Server must be able to reach minfraud.maxmind.com on port 443
Installation
↑ Back to topTo start using a product from WooCommerce.com, you can use the โAdd to storeโ functionality on the order confirmation page or the My subscriptions section in your account.
- Navigate to My subscriptions.
- Find the Add to store button next to the product youโre planning to install.
- Follow the instructions on the screen, and the product will be automatically added to your store.
Alternative options and more information at:
Managing WooCommerce.com subscriptions.
Quick Start Guide
↑ Back to topGetting up and running takes just a few minutes:
- Open a minFraud account at MaxMind. A free trial with 1,000 risk score queries is currently available.
- Follow the links in your MaxMind account to generate a license key.
- Open the extension’s settings page โ WooCommerce > Fraud Detection/Blocking and open the Fraud screening setup accordion section. Enter your MaxMind Account ID and license key. If you plan to review orders yourself, choose Insights or Factors as the service tier โ a Score query returns the risk number and little else.
- Click the Test Connection button to verify your credentials are working. It uses one risk score query.
- Check Enable screening at the top of the settings page.
- Open the Risk thresholds accordion. The defaults should be fine. Email notification threshold is set to 0% so you’ll receive an email on every order screened. Decline threshold is set to 100% so no orders will be declined. As you gain experience and observe how MaxMind scores your customer base, lower the Decline threshold โ into the 90s if you’ll review orders yourself, or to 50%, then 40%, and eventually under 10% if you’d rather block automatically. In our experience most legitimate orders will have risk scores of under 3% โ but as they say ‘your mileage may vary’.
Note: MaxMind defines the risk score as the probability the order is fraudulent. - IP velocity protection โ leave it disabled for now. You can enable it later for automatic card testing bot blocking.
- Query caching โ enable it to minimize your MaxMind query consumption. The default settings – cache TTL of 10 minutes and use dedicated database table are fine.
- Notifications โ Check the email addresses. The defaults are usually OK, but make sure the “To” address is a valid email where you can receive the extension’s merchant notification emails.
- Network and proxy – if the two IP addresses shown are different check the Enable proxy detection box. A red warning at the top of the settings page also tells you when proxy headers arrive but proxy detection is off.
- Whitelisting โ enter your office IP address. No point in wasting queries on orders you enter manually. Don’t know your IP? Open the Network and proxy section again. It shows as Derived Client IP. Leave Orders with no shopper present on Whitelist this order. If you list products on Google Shopping or Google Merchant Center, check Automatically whitelist Google Storebot.
- Order notes, Logging and On processing error โ defaults are OK.
- Click Save Changes at the bottom left to save your settings.
What to expect โ you should receive a merchant notification email entitled Order Accepted for every order. This email will show the risk score, order details and MaxMind’s complete analysis response in a drop-down section. A sample of this email is shown below. Each order also shows its Risk Score and Screening Result on WooCommerce > Orders, and the Screening statistics panel at the top of the settings page starts counting.
Note: You will not receive an email on a order with contact and addresses details that match a previous order cached within the caching time period.
Next Steps
↑ Back to topAfter you’ve got the Real-Time Fraud Detection and Blocking for WooCommerce extension setup and working here are some of the next step you’ll want to take in order to get the full benefit.
- Choose your approach โ block before billing, review after billing, or both. See Choosing Your Approach below.
- IP velocity protection โ open this accordion and enable the feature. The default settings (5 Max attempts, 10 minute Time window, 30 minutes Block duration, destroy session and send email) are fine for most stores. This feature will protect you from credit card number testing bots by monitoring the number of order declines per IP address. Once an IP uses up its allowed declines, any further order attempts from that IP address are automatically blocked. If you’re hit by slow bots that pause between attempts, switch the window and block to hours. See below for more details on this feature.
- Lower the order decline risk score threshold. If you sell high margin inexpensive products you might use a higher decline threshold than a merchant selling low margin expensive products. Keep it below 100% so velocity protection has declines to count. See Tips and Best Practices below for some thoughts on the math for optimizing the risk score.
- Raise the email notification risk score threshold. No point in choking on excessive emails for known good orders. Raising this from 0% to 1 or 2% will eliminate most of the unnecessary notifications.
Choosing Your Approach
↑ Back to topEvery order that goes through shows its MaxMind risk score and screening result in two columns on WooCommerce > Orders, and the full MaxMind response is written to the order notes in plain, readable form. That gives you three ways to run fraud control:
- Block before billing. Set a decline threshold and let the extension stop high-risk orders at checkout, before your gateway is ever contacted. Nothing is captured and there is nothing to reverse.
- Review after billing. Let orders through, scan the Risk Score column, read MaxMind’s analysis on each order โ how far the customer’s IP is from the billing address, whether it’s a proxy, VPN or hosting provider, how long the email address has existed โ then ship, or cancel and refund the ones that don’t add up, before anything leaves your warehouse.
- The best of both. Auto-block the clear-cut fraud before billing and review only the gray-area middle after billing. Most merchants settle here.
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.
Keep the decline threshold below 100%. IP velocity protection stops card testing bots by counting declines โ at 100% 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.
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.
Configuration Guide
↑ Back to topNavigate to WooCommerce > Fraud Detection/Blocking. The page title shows the installed version. The settings page uses collapsible accordion sections. The first section โ Fraud Screening Setup โ is open by default.
Screening Statistics
↑ Back to topA collapsible panel above the settings counts screening activity for Today, Yesterday and All Time. Each checkout attempt is counted once, in one row, so the totals always add up: total screened = queries consumed + queries saved + not scored.
| Row | What it counts |
|---|---|
| Queries consumed | Orders scored by MaxMind: accepted and declined. |
| Queries saved | Checkouts handled without a MaxMind query: cache hits, whitelisted IPs, Google Storebot, velocity blocks, orders with no shopper present, and empty checkouts. |
| Not scored | Processing errors, split by the error disposition (accepted or declined). |
To start a new counting period, type reset and click Reset statistics; the panel shows the date counting began.
Fraud Screening Setup
↑ Back to top| Setting | Description | Default |
|---|---|---|
| Enable screening | Master switch for fraud screening. Requires MaxMind credentials configured below. | Off |
| MaxMind Account ID | Your numeric MaxMind account ID, found on the MaxMind dashboard under Account > Account Information. | โ |
| MaxMind License key | A license key generated in your MaxMind account under Account > Manage License Keys. | โ |
| minFraud Service tier | Score = basic risk score. Insights = score plus risk factors and IP data. Factors = full analysis with human-readable explanations. Higher tiers provide more information on the nature of the risk but cost more per query. Choose Insights or Factors if you will review orders after billing. | Score |
| MaxMind API URL | The MaxMind minFraud API URL. Change only if directed by MaxMind support. | https://minfraud.maxmind.com/minfraud/v2.0/ |
| Test MaxMind connection | Sends a test request to verify your credentials. Always uses one risk score query, whichever service tier is selected. |
Risk Thresholds
↑ Back to top| Setting | Description | Default |
|---|---|---|
| Email notification threshold | Send a fraud report email when the risk score is at or above this percentage. Set to 0 to receive emails for every screened order. | 0 |
| Decline threshold | Automatically decline orders at or above this risk score. Set to 100 to disable auto-decline while you calibrate. Changing it purges the query cache. | 100 |
| Decline message | Message shown to customers when their order is declined. Many merchants use it to invite the customer to call and place the order by phone. | (see below) |
Getting started: We recommend setting the decline threshold to 100 (no auto-decline) during your first week. Monitor the fraud report emails and the Risk Score column to understand the risk score distribution for your store’s orders. Then set the threshold for the approach you’ve chosen: in the 90s to review orders yourself, or a starting point of 30โ40% if you’d rather block automatically, gradually lowered as you gain confidence.
IP Velocity Protection
↑ Back to topDetects and blocks credit card testing bots by tracking declined checkout attempts per IP address. Most card testers try many card numbers in rapid succession; a newer breed pauses a random 1 to 30 minutes between tests and rotates across hundreds of IP addresses. Velocity protection counts only declined orders (not all attempts) and blocks the IP once it has used up its allowed declines.
| Setting | Description | Default |
|---|---|---|
| Enable velocity protection | Master switch for IP velocity tracking and blocking. | Off |
| Max attempts | Number of declines an IP is allowed before it is blocked. Range: 0โ50. With 5, the IP is blocked on its 6th decline; with 0, on its very first decline. | 5 |
| Time window | Declines are counted within this rolling window. Choose minutes (1โ60) or hours (1โ24) from the selector beside the field. Whole numbers only. | 10 minutes |
| Block duration | How long a blocked IP stays blocked. Choose minutes (1โ60) or hours (1โ72). The block timer resets on every subsequent attempt from the blocked IP (rolling block). | 30 minutes |
| Destroy session | Empty the shopping cart and destroy the WooCommerce session when an IP is blocked. This forces card testers to start over โ new session, re-add products, re-fill the checkout form. Does not affect the customerโs WordPress login. | On |
| Block message | Message shown to customers blocked by velocity protection. Supports [DURATION] (the block duration, for example 3 hours), [STORE_NAME] (your store name) and [MINUTES] (the block duration in minutes) tokens. | (see below) |
| Email notification | Send an email alert when a velocity block is triggered. | On |
| Velocity email subject | Subject line for velocity alert emails. The blocked IP is appended automatically. | Antifraud Velocity Alert |
How counting works: Only orders that are declined by MaxMind risk scoring (or by cache hit) count toward the velocity limit. Orders that pass screening, whitelisted orders, Google Storebot checkouts, and orders blocked by error disposition do not count. A single checkout that reaches the store through two checkout paths seconds apart counts once. This prevents false velocity blocks from legitimate customers who happen to retry checkout.
Upgrading from 8.2.x: Max attempts now means the number of declines allowed before the block. An existing setting of 1 or more allows one more decline than before โ lower it by one to keep the old behavior.
| Setting | Typical store | Under attack by slow, IP-rotating bots |
|---|---|---|
| Max attempts | 5 | 0 (block on the first decline) |
| Time window | 10 minutes | 24 hours |
| Block duration | 30 minutes | 72 hours |
Long blocks can occasionally catch a real customer who shares an IP with a bot (mobile carriers share addresses). The whitelist always overrides a block.
The admin page includes a View Velocity Table button showing all tracked IPs with their decline counts and block status, and a Clear Velocity Table button (two-click confirm) to reset all tracking data. A collapsible Velocity Protection Notes panel provides quick reference documentation.
Query Caching
↑ Back to top| Setting | Description | Default |
|---|---|---|
| Enable caching | Cache minFraud results for identical checkout data to reduce query charges and merchant emails. A cache hit keeps the original risk score and MaxMind response for the order. | On |
| Cache TTL | How long cached results remain valid, in minutes. Range: 1โ60. | 10 min |
| High-performance table | Create a dedicated database table for caching instead of using WordPress transients. Recommended for stores processing more than 50 orders per hour. Falls back to transients if the table can’t be created. | On |
Notifications
↑ Back to top| Setting | Description | Default |
|---|---|---|
| From address | The sender address for all fraud notification emails. | Store owner’s email |
| To address(es) | Recipient address(es). Separate multiple addresses with commas. | Admin email |
| Risk email subject | Subject prefix for fraud report emails. Risk % and disposition are appended automatically. | Antifraud Report – |
| Whitelist notifications | Send email when a whitelisted IP places an order. | On |
| Whitelist email subject | Subject line for whitelist notification emails. | Antifraud Report – IP Whitelisted |
| Error notifications | Send email when a processing error occurs during screening. | On |
| Error email subject | Subject line for error notification emails. | Antifraud Processing Error |
Network and Proxy
↑ Back to top| Setting | Description | Default |
|---|---|---|
| Behind proxy / CDN | Enable if your store is behind CloudFlare, a load balancer, CDN, or reverse proxy. When enabled, the extension reads the real client IP from X-Forwarded-For, CF-Connecting-IP, X-Real-IP, and True-Client-IP headers. | Off |
The section shows the 1st Hop IP, the Derived Client IP and the Proxy header the client IP came from. If the two IPs differ, enable proxy detection. If they match and a proxy header is listed, your server already restores the visitor’s IP and no change is needed. A red warning at the top of the settings page appears when proxy headers arrive but proxy detection is off.
Whitelisting
↑ Back to top| Setting | Description | Default |
|---|---|---|
| IP whitelist | Comma-separated list of IPv4/IPv6 addresses and CIDR ranges. Whitelisted IPs bypass fraud screening entirely without consuming a minFraud query. This is especially useful for whitelisting your office IP so that staff can place manual or test orders without triggering fraud screening. Examples: 192.168.1.100, 10.0.0.0/8, 2001:db8::/32 | โ |
| Orders with no shopper present | Applies to orders created manually in the admin (phone orders), scheduled orders such as subscription renewals, and orders pushed in through the WooCommerce REST API by an integration. The IP these orders carry belongs to a staff member or a server, not the customer. Whitelist this order (recommended), Screen without IP address or device information, or Screen normally (not recommended: the office or server IP produces inaccurate scores and can get velocity-blocked). Block checkout and WooPay always have a real shopper and are screened normally. | Whitelist |
Note: Changing the whitelist purges cached whitelist entries from the query cache.
Google Storebot
If you list products on Google Shopping or Google Merchant Center, Google’s Storebot crawler places test checkouts to verify your prices and availability. Without whitelisting, these tests use MaxMind queries and can be declined or velocity-blocked. Verified Storebot checkouts skip screening and velocity counting. A checkout is trusted only after its IP is verified โ against Google’s published IP ranges, a cache of addresses already verified, or a forward-confirmed reverse DNS lookup; the user agent alone is never trusted. Anything that fails verification is screened normally.
| Setting | Description | Default |
|---|---|---|
| Storebot whitelist | Automatically whitelist Google Storebot. | Off |
| Storebot notifications | One alert when Storebot activity begins each day, followed by a summary the next day. | On |
| Verification data | Shows the status of Google’s IP ranges, which are downloaded automatically on the first Storebot checkout and refreshed daily. A Troubleshooting link holds buttons to refresh the ranges and clear verified addresses. | โ |
Order Notes
↑ Back to top| Setting | Description | Default |
|---|---|---|
| Screening note | Add the screening result to the order’s notes. | On |
| Full response | Include the full MaxMind response in that note. The amount of detail depends on the service tier. The Risk Score and Screening Result columns on the Orders list are filled in either way. | On |
Note: Screening results for declined orders are available in the logs and alert emails only.
Logging
↑ Back to top| Setting | Description | Default |
|---|---|---|
| Enable logging | Log fraud analysis activity through WooCommerce’s built-in logging system. | On |
| Log level | All events (every screening, cache hit, API call), Warnings & errors (declines, velocity blocks, errors, emails) or Errors only. Start with All events during setup and switch to Warnings & errors once stable to reduce log volume on busy stores. | All events |
| View logs | Click the button to open WooCommerce > Status > Logs. Look for entries starting with real-time-fraud-blocking. | โ |
| Statistics on uninstall | Preserve screening statistics when the plugin is deleted. | On |
Log retention is managed through WooCommerce’s log settings at WooCommerce > Status > Logs > Settings.
On Processing Error
↑ Back to topControls what happens when MaxMind is unreachable, returns an error, or the extension encounters an unexpected exception during screening. The same disposition applies when an order can’t be scored meaningfully: a private or missing client IP (usually a proxy setting problem), or no email, billing country or postal code.
| Setting | Description | Default |
|---|---|---|
| Disposition | Accept order (recommended): allow the order so you don’t lose sales. A note is added to the order flagging it for manual review. Decline order: block checkout if screening fails. The customer sees the error decline message. | Accept |
| Error decline message | Message shown to customers when an order is declined due to a processing error. Only used when disposition is set to Decline. | (see below) |
Order notes: When disposition is set to Accept, orders that pass through without screening receive an order note: โFraud Detection โ Processing Error (Order Accepted)โ with the error details and a recommendation to review the order manually. Their Screening Result column shows Accepted under error policy for easy spotting.
How Screening Works
↑ Back to topThe extension intercepts checkout submissions across all WooCommerce checkout paths:
- Block Checkout โ via WooCommerce Store API hooks
- Classic Checkout โ via
woocommerce_checkout_processandwoocommerce_after_checkout_validation - WooPay โ via Store API (same as Block Checkout)
- PayPal โ screened before the redirect, with the result carried through the return from PayPal
Every checkout path follows the same screening flow:
- Customer clicks Place Order (or completes WooPay flow).
- Fraud Detection/Blocking intercepts the checkout submission before payment is captured.
- If screening is disabled, the order proceeds normally.
- Shopper present? โ admin, renewal and integration orders are handled according to your Orders with no shopper present setting.
- Google Storebot check โ if Storebot whitelisting is enabled and the checkout comes from a verified Google Storebot IP, the order proceeds without screening or velocity counting.
- IP whitelist check โ if the customerโs IP matches a whitelisted address or CIDR range, the order is allowed through without consuming a minFraud query. An optional notification email is sent.
- Velocity pre-check โ if IP velocity protection is enabled, the extension checks whether this IP is currently blocked. If blocked, the checkout is stopped immediately with the velocity block message. The block timer resets on every attempt (rolling block). No minFraud query is consumed.
- Cache check โ if caching is enabled and a cached result exists for this exact contact and address data, the cached decision (accept/decline) is used without consuming a minFraud query.
- Data check โ an empty checkout (no name, no email, $0) is declined without a query. An order with an unusable IP, or without email, billing country or postal code, follows the error disposition.
- minFraud query โ the extension sends order data (IP, hashed email and email domain, billing/shipping address and phone, order amount, currency, user agent, browser language, and a hashed session ID) to MaxMindโs minFraud API. Customer names are not sent.
- Error handling โ if the minFraud query fails (network error, invalid credentials, etc.), the error disposition setting determines whether the order is accepted or declined. Accepted orders receive an order note flagging them for manual review.
- Risk evaluation โ the returned risk score is compared against your thresholds. If it meets or exceeds the decline threshold, the order is declined. If it meets the email threshold, a notification is sent.
- Velocity recording โ if the order was declined by risk scoring, the decline is recorded against the customerโs IP for velocity tracking. If this decline uses up the IP’s allowed declines, the IP is blocked immediately, the session is destroyed and the cart emptied (if enabled), and a velocity alert email is sent.
- Record the outcome โ checkout proceeds (accepted) or the customer sees the appropriate decline message. Accepted orders get their Risk Score and Screening Result columns and the screening order note, and the statistics are updated.
Note: Because screening happens before payment, no credit card charge is made on declined orders. The customer sees your decline message and can modify their information or contact you.
Email Notifications
↑ Back to topThe extension sends detailed HTML email reports for eight screening outcomes. Each risk email includes customer details, IP address, risk score, order total, and the full MaxMind response data (varies by service tier).
| Email Type | When Sent | Default Subject |
|---|---|---|
| Fraud Report (accepted / declined) | Risk score meets or exceeds the email notification threshold. The report indicates whether the order was accepted or declined, depending on whether the score was above or below the decline threshold. | Antifraud Report – |
| Velocity Alert | An IP address has been blocked after using up its allowed declines within the time window. Includes the IP, email, decline count, block duration, and checkout source. | Antifraud Velocity Alert |
| Processing Error (accepted / declined) | MaxMind API returned an error or was unreachable. Sent regardless of the error disposition setting. | Antifraud Processing Error |
| Whitelist Notification | A whitelisted IP placed an order (if enabled). | Antifraud Report – IP Whitelisted |
| Google Storebot Alert | The first verified Storebot checkout of the day (if Storebot notifications are enabled). | Google Storebot Alert – Checkout testing underway |
| Google Storebot Summary | The next day: total Storebot checkouts, unique IPs, and how each was verified. | Google Storebot Summary (date) – counts appended |
Orders List and Order Notes
↑ Back to topOrders list: WooCommerce > Orders shows two columns after the order total, for both HPOS and legacy order storage:
| Column | Shows |
|---|---|
| Risk Score | The MaxMind risk score to two decimals, or a dash when the order wasn’t scored. |
| Screening Result | Screened, accepted, Served from cache, Whitelisted, Accepted under error policy, or Not screened. |
Declined orders are blocked before they exist, so they never appear in the Orders list; their results are in the logs and alert emails.
Order notes: Fraud Detection/Blocking adds notes to WooCommerce orders documenting the screening outcome. These appear in the Order Notes panel on the order detail page.
| Note Type | When Added | Contents |
|---|---|---|
| Screening Result | Every screened order that completes checkout (if the screening note is enabled). | Risk score, decline threshold, disposition, MaxMind transaction ID, customer IP and timestamp, followed by the full MaxMind response in readable plain text (if enabled). |
| Whitelisted | Order from a whitelisted IP. | Customer IP and the whitelist entry it matched. |
| Processing Error โ Accepted | Order accepted despite a screening failure (error disposition = Accept). | Error details, customer IP, and a recommendation to review the order manually for fraud risk. |
Tip: Orders accepted during a processing error show Accepted under error policy in the Screening Result column, so you can spot them in the Orders list and make sure they receive manual review.
Troubleshooting
↑ Back to topTest Connection fails with authentication error
Verify that your Account ID is the numeric ID (not your email address) and that the License Key has not been revoked. Generate a new license key in your MaxMind dashboard if needed.
Orders are not being screened
Confirm that “Enable screening” is checked and your MaxMind credentials are entered. Check WooCommerce > Status > Logs for entries starting with real-time-fraud-blocking. Also verify the plugin is active under Plugins > Installed Plugins.
All orders are being declined
Check your Decline Threshold. If set too low, even low-risk orders will be blocked. Set to 100 to disable auto-decline while you review the risk scores coming back in your email reports, then lower the threshold gradually.
Emails are not being received
Verify the From and To addresses in the Notifications section. Check that the From address is authorized to send mail on your domain (SPF/DKIM). Many hosting providers block outbound mail on port 25 or have server IPs that are flagged by major email providers. Installing an SMTP plugin (WP Mail SMTP, Post SMTP, or FluentSMTP) to authenticate through your mail server or a transactional email service (Gmail, SendGrid, Mailgun, Amazon SES) is strongly recommended. The plugin uses wp_mail(), so any SMTP plugin will automatically route all notifications through the configured mail server.
Wrong IP address detected (always 127.0.0.1 or server IP)
Enable “Behind proxy / CDN” in the Network and Proxy section. This tells the extension to read the real client IP from forwarded headers (X-Forwarded-For, CF-Connecting-IP, etc.) instead of the direct connection. The red warning at the top of the settings page points to this. Until it’s fixed, orders arriving from a private IP follow the error disposition rather than being scored on the wrong address.
Cache is not reducing minFraud queries
The cache only reuses results when the checkout identity data (IP, email, billing and shipping addresses) is identical. Changes to the cart contents or order amount do not affect the cache key โ so a customer adjusting their cart will still get a cached result. However, any change to the customer’s email or addresses generates a new cache key and requires a new query. Set a TTL of 10โ15 minutes for best results. The Screening statistics panel shows how many queries the cache saved.
Extension conflicts with another checkout extension
Fraud Detection/Blocking hooks into WooCommerce’s standard checkout pipeline. If another extension modifies the checkout flow (e.g., multi-step checkout, custom checkout pages), there may be conflicts. Check the logs for errors and contact support with details about the other extension.
Velocity protection is blocking legitimate customers
Increase the Max Attempts threshold or shorten the Time Window or Block Duration. Velocity only counts orders declined by MaxMind risk scoring, not payment gateway failures โ so a customer mistyping their card number won’t trigger a velocity block. However, a customer who enters an incorrect shipping zip code several times could trigger repeated MaxMind declines if the address mismatch pushes their risk score above your threshold. Long, hour-scale blocks are best kept for periods of bot attack. Start with 5 attempts in 10 minutes and adjust based on your storeโs checkout patterns. You can also use the View Velocity Table button to see which IPs are being tracked or blocked, and whitelist a customer’s IP to release them.
Velocity counters not incrementing
Velocity only counts declined orders. If the order is accepted, whitelisted, a verified Storebot checkout, or blocked by error disposition, it does not count toward velocity limits. Check that your decline threshold is below 100 so it can produce declines, and verify that velocity protection is enabled.
Google Merchant Center test orders are declined
Enable Automatically whitelist Google Storebot in the Whitelisting section. If Storebot checkouts are still screened, open the Troubleshooting link under Verification data and click Refresh Google IP ranges.
Tips & Best Practices
↑ Back to topGetting Started
Start with the decline threshold at 100 (no auto-decline) and the email threshold at 0 (email on every order). Run this way for a week to understand the risk score distribution for your store’s orders. Then decide whether you’ll block before billing, review after billing, or both (see Choosing Your Approach). For automatic blocking an interim setting of 30โ40% is common, then gradually lower the threshold as you gain confidence in the scoring for your particular customer base.
Understanding Risk Scores
MaxMind’s risk score is a percentage (0โ100) representing the probability that the transaction is fraudulent. A score of 25 means roughly a 25% chance of fraud based on the data sent. The score is not an absolute guarantee โ it is a probability based on patterns across MaxMind’s global network of merchants.
Calculating an Optimal Decline Threshold
Consider your profit margin and chargeback costs. The basic formula: if (profit ร (100 - riskScore)) > (fraudLoss ร riskScore), it may still be profitable to accept the order. For a product with a 30% margin and a $100 price, the breakeven risk score is roughly 23%. Many merchants start with a decline threshold of 30โ40% and adjust based on their chargeback rate.
Query Caching Tips
Caching saves money on retries. If a customer’s checkout fails (wrong CVV, expired card), they’ll retry with the same data. Without caching, each retry costs another query. With a 10-minute TTL, retries within that window are free. The high-performance database table is recommended for stores with more than 50 orders per hour to avoid bloating the WordPress options table.
Proxy / CDN Detection
If you use CloudFlare, AWS CloudFront, or any reverse proxy, you must enable proxy detection unless your server already restores the visitor’s IP. Without it, MaxMind sees your server’s IP instead of the customer’s, and every order will appear to come from the same location โ making the risk score meaningless. The settings page warns you when it detects this.
IP Velocity Protection
Most card testing bots fire dozens of checkout attempts in rapid succession from the same IP, each with a different stolen card number. Velocity protection catches this pattern by counting only declined orders. Start with 5 max attempts in a 10-minute window and a 30-minute block duration. The โdestroy sessionโ option is critical โ without it, bots retain their cart and session, making it trivial to retry. With session destruction, they must re-add products, re-fill the checkout form, and get a new session cookie on every block.
Slower bots pause a random 1 to 30 minutes between tests and rotate across hundreds of IP addresses, so no single IP looks busy in a ten-minute window. When you see that pattern, set Max attempts to 0, the time window to 24 hours and the block duration to 72 hours: each IP is blocked on its first decline, and any IP the bot returns to is already blocked, at no query cost.
The rolling block means every attempt from a blocked IP resets the block timer. A bot that keeps trying never gets unblocked. Legitimate customers who were caught by mistake simply wait for the block to expire, or you can whitelist their IP.
How to Uninstall
↑ Back to top- Go to Plugins > Installed Plugins.
- Deactivate Real-Time Fraud Detection and Blocking.
- Click Delete to remove the extension files.
When deleted, the extension automatically cleans up its database entries: settings, transients, the custom cache table, the velocity tracking table and the Google Storebot verification table are all removed. Screening statistics are kept so they survive a reinstall, unless you untick Preserve screening statistics when the plugin is deleted in the Logging section before deleting. No manual database cleanup is needed.
Screen Shots
↑ Back to topFraud Screening Setup – MaxMind Configuration

Risk Thresholds and IP Velocity Protection Configuration

Query Caching, Notifications and Network and Proxy Configuration

Whitelisting, Logging and On Processing Error Configuration

Logging – WooCommerce Logs

Logging – Fraud Detect/Block Log Detail

Order Decline Modal Message

Email Notification – Order Accept

Email Notification – Order Declined

FAQs
↑ Back to topHelp customers by answering commonly asked questions.
Question 1 – Can I review orders myself instead of having them blocked?
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 is detail to review.
Question 2 – What about card testing bots that slow down and rotate IP addresses?
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.
Question 3 – Does this work with my payment gateway?
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.
Question 4 – Will legitimate customers be affected?
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.
Question 5 – How much does MaxMind cost?
MaxMind currently offers a free trial with 1,000 risk score queries. After that, a Score query costs approximately half a cent, Insights about 1.5 cents and Factors about 2 cents. Smart query caching and IP velocity protection reduce costs further, and the Screening statistics panel shows exactly how many queries you used and saved.
Question 6 – Will this block Google Merchant Center's test orders?
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.
Question 7 – What about phone orders and subscription renewals?
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.
