Predax Fraud Guard for WooCommerce -- WordPress 插件

开发者	ipsentry
更新时间	2026年9月23日 11:30
PHP版本:	7.4 及以上
WordPress版本:	7.1
版权:	GPLv2 or later
版权网址:	版权信息

Predax Fraud Guard is anti-fraud for WooCommerce: it stops fake orders, card testing and chargebacks before the order exists. Card testers and stolen-card fraudsters typically check out from behind a VPN, proxy, Tor or datacenter IP. Fraud Guard screens the customer's IP at checkout and scores its fraud risk from 0 to 100, and for each rule you choose what happens. Block refuses the checkout before payment is taken, so a blocked attempt never becomes a gateway fee or a chargeback. Hold lets the payment go through and keeps the order on hold for your review, so nothing ships until you decide. Or simply tag the order. Works with any payment gateway and with both the classic and block checkout. See what Predax knows about your own IP — free, no signup. Off by default. A fresh install sends nothing anywhere. Connect your Predax key and choose a protection mode; until then the plugin does nothing. What it stops

Card testing — bots running stolen card numbers through your checkout in bulk
Orders from VPNs, proxies, Tor and datacenter IPs
Too many orders, too fast — velocity rules catch rapid repeat attempts
Billing country that doesn't match the customer's real location
Disposable email addresses at checkout

Start in tag-only mode The default once configured is Tag + note: flagged orders get a "Predax: Medium / High / Critical Risk" tag and an order note, and nothing is blocked. Watch what the rules would have done, then turn on Block high risk or Block critical only when you're confident. Optionally send high-risk orders to On Hold for review instead of rejecting them: the payment is taken and the order waits for you before anything ships, so you can refund a fraudulent one instead of sending the goods. Safe for real customers and search traffic

Verified search engines are never blocked by your VPN, datacenter, country or risk rules.
Every decision is on the record. The Events Log shows which orders were tagged, held or blocked, and why — so a too-strict rule shows up in the log, not in falling sales.
One-click allow-listing from the Events Log lets a good customer check out again immediately.

Also included Risk score, threat flags and country saved on every order for reporting · Refund/chargeback feedback that adds the IP to your deny list · IP and CIDR allow/deny lists · Optional Community Threat Network sharing Free plan Click Connect with Predax in the setup wizard and your free account and API key are created for you — nothing to copy or paste. The free plan includes 5,000 IP checks a month with full VPN, proxy, Tor and datacenter detection and risk scoring. No credit card. Checkouts are only checked when they happen and results are cached, so it covers a small store comfortably; busier stores can move to a paid plan — same plugin, same settings, same key.

From your WordPress dashboard (recommended)

Make sure WooCommerce is installed and activated.
Go to Plugins → Add New Plugin in your WordPress admin.
Search for "Predax Fraud Guard".
Click Install Now, then Activate.
The Setup Wizard launches on first activation. Either click Connect with Predax for OAuth one-click connection, or enter your API key manually.
Pick a protection preset (Recommended / Strict / Monitor Only). This is the step where you opt in — IP lookups begin after this point.
Fine-tune individual rules at Fraud Guard → Settings any time.

Manual installation

Download the plugin ZIP from this page and upload it via Plugins → Add New Plugin → Upload Plugin (or extract the predax-fraud-guard-for-woocommerce folder to /wp-content/plugins/).
Activate the plugin through the Plugins menu and follow the Setup Wizard.

1.12.4

New: Clock & Country is now a choice of three - Off, Hold or Block. Block refuses the checkout before the card is charged, so there is no gateway fee and no chargeback. Hold lets the payment go through and keeps the order on hold for your review. Off only tags the order. If you saved the 1.12.3 switch, "on" becomes Hold and "off" stays Off.
Fixed: an order held by Clock & Country was listed in the Events Log as "flagged" with a generic reason. It now shows as held, with the reason "tz_country_mismatch", and blocked attempts are logged the same way.
Changed: the description now says plainly which actions happen before payment. Blocking stops the card being charged; holding does not - a held order has been paid for and waits for your review before anything ships.
The Recommended preset uses Hold for Clock & Country, Strict uses Block and Monitor leaves it off.

1.12.3

Fixed: orders put on hold by Predax were released again as soon as a card payment went through. WooCommerce runs the fraud check before the payment gateway charges the card, and the gateway then moved the order straight on to processing - so for card payments, Auto Hold and the clock-and-country hold did not actually hold anything. Held orders now stay on hold until you release them. The payment is still recorded as normal, and orders held by other plugins are not affected.
Changed: the clock-and-country hold now has its own switch, "Clock & Country Hold", under Order Actions. It works on its own and no longer needs Auto Hold switched on. Until you change it, it follows your Auto Hold setting, so updating does not start or stop holding orders on your store.
Fixed: the clock-and-country check only ran when the separate Billing Country Mismatch rule was switched on, and that rule is off by default - so on most stores it did nothing. It now works whatever that rule is set to, and the rule itself behaves exactly as before.

1.12.2

New: an order is now held for review when the billing country, the country the order came from, and the customer's browser clock all disagree. Each of those on its own has an innocent explanation - people travel, and a VPN moves the apparent location - so none of them holds an order by itself. Together they are the pattern of a card being used from somewhere the cardholder is not. Held orders are tagged "Predax: Clock & Country Mismatch" and the order note names both countries.
Note: this holds the order even when the risk score is low, because the score describes the connection, not the disagreement between three claims of location. A stolen card used over an ordinary home broadband connection scores near zero and is exactly the order worth a second look. It respects your Auto-hold setting: if you have Auto-hold switched off, nothing is ever held - the order is tagged instead.
Fixed: the browser timezone your store already collects at checkout never reached the check that uses it, so the "Predax: TZ Mismatch" tag could not appear on any order. It works now.
Improved: a timezone is now judged by the actual clock difference rather than the zone name, and only counts from three hours apart. A shopper in Paris buying from a German address is no longer a mismatch, and neither is a customer in California on a US address - both were flagged before.
Removed: the "Timezone mismatch" slider under Custom Scoring. It never affected any score, so it was a control that did nothing. The timezone is still used, as evidence, in the rule above.

1.12.1

Changed: the plugin now lists itself under its full name on the Plugins screen, so it matches the name shown on WordPress.org.
Fixed: the bundled Predax icon was a 1024x1024 photo-format file displayed at 28 pixels. It is now a correctly sized 256x256 icon, making the download about 220 KB smaller.
Fixed: the "What's new" panel inside the plugin listed the previous release's changes under the current version number.
Maintenance release only - no change to screening, scoring, rules or any stored setting.

1.12.0

New: a Help page, in the Fraud Guard menu. Plain-English explanation of every setting and what to choose, stored in the plugin so it works offline.
Fixed: Apple Private Relay and Cloudflare WARP are no longer treated as datacenter connections at checkout, so iPhone customers are not refused. Applies to both the classic checkout and the newer block-based checkout.
New: a warning when your object cache is silently failing to store results. Screening stays correct, but every checkout re-checks the same shopper and your plan allowance is spent several times faster than it should be.
Improved: the plugin is now fully translatable. The bundled translation template was previously almost empty.

1.11.0

New: the Disposable Email rule now checks a continuously updated list of thousands of throwaway providers instead of the short built-in list. Only the DOMAIN part of the customer's address is checked (for example "gmail.com") - the address itself, and everything before the @, never leaves your store. The built-in list is still consulted first and still applies if the API is unreachable, so no store loses a block it had before.
New: orders from a domain that cannot receive mail, or with a machine-generated mailbox name, are noted on the order. Both are record-only signals - they never block a checkout, place an order on hold, or count towards the tag threshold.
Fixed: order flags were discarded when the Predax API was briefly unreachable, so a flagged order could go untagged and unlogged. Fixed on both the classic and the Blocks checkout.
Fixed: a malformed billing email domain could previously cause repeated API errors that temporarily paused IP screening at checkout. Malformed domains are now rejected on your own server and never sent.
Note: email-domain lookups count towards your Predax plan allowance. Results are cached for six hours per domain.

1.10.0 Setup wizard

The Community Threat Network opt-in is now offered as an explicit, unticked checkbox in the setup wizard, with a plain-English description of exactly what is shared. It stays off by default and can be changed any time on the Advanced settings tab. Housekeeping
The plugin now identifies itself and its version in its API requests, which helps support diagnose issues faster.
Fix: screening results written by this plugin now carry the same crawler-identity fields as Predax Security. A store running both plugins shares one cached verdict per visitor, and the missing fields could stop Security's crawler policy from applying to a visitor whose verdict was cached at checkout.
Corrected in this readme: cached screening results last between 5 minutes and 1 hour per IP (the lifetime the API recommends), not a fixed 5 minutes.
Corrected in this readme: the "will this block real customers" answer described dashboard features belonging to the Predax Security plugin rather than this one.

1.9.0 Checkout accuracy

Fixed one shopper's screening result being reused for a different shopper behind the same network. The cached result was keyed on the IP alone, but the result also depends on the browser's timezone - which the Blocks checkout and the classic checkout send differently - so a timezone mismatch could be inherited by the next genuine customer and get their order tagged or held.
An allow-listed IP no longer has its order tagged from a screening result recorded before it was allow-listed.
If the Predax API cannot be reached during checkout, any earlier screening result is now discarded rather than being applied to the new order. Previously a customer could be held on a verdict from a previous attempt, possibly from before they turned a VPN off. Events Log
"Filter by reason" now works on the Flagged tab. Flagged and held orders were saved without a reason, so the filter returned nothing whatever you chose.
Flagged orders now record the rule that actually fired - order velocity, disposable email, billing mismatch or the risk threshold - instead of always claiming the risk threshold was crossed.
The chosen reason filter is no longer lost when you move to the next page of results. Community Threat Network
The Blocks checkout now contributes to the Community Threat Network. Only the classic checkout did, so stores using the default Blocks checkout received other stores' data without contributing any of their own. Other fixes
Risk labels on orders now match the bands the Predax API actually issues; an order scoring 75 previously showed a different level to the one the API reported.
Importing a settings file can no longer redirect the plugin to a different address - the API key is sent to that address, so this is now restricted to http and https as the settings form already was.
Uninstall now removes leftover lookup locks and the shared verdict cache. Efficiency
Predax Fraud Guard and Predax Security now share one cached verdict per visitor, so a store running both no longer spends two checks on the same person.
Cached verdicts now follow the lifetime the API recommends (up to an hour) instead of a fixed five minutes.
Tested up to WordPress 7.1.

1.8.4

Fix: hitting your plan's DAILY check limit no longer reports it as the monthly limit. The notice used to say checkout screening was paused "until your quota resets on the 1st" when it actually resumes at midnight UTC the same day. It now names the right limit and tells you the exact time screening resumes.
Improved: fewer API checks are used for the same shopper. Checkout pages make several parallel requests, and each one used to trigger its own lookup; the plugin now performs a single lookup and shares the result.

1.8.3

Fix: re-running the Setup Wizard and choosing "Monitor Only" now also switches off known-malicious IP blocking. Previously that one rule stayed on if a stricter preset had enabled it, so a preset promising to block nothing could still reject checkouts.
Fix: Fraud Guard admin notices no longer appear on Predax Security plugin pages when both plugins are installed - they now show only on Fraud Guard's own screens.

1.8.2

New: an invitation to join the Community Threat Network now appears on the Predax screens, with a one-click opt-in. Stores in the network warn each other, so a card tester blocked at another store is already known to yours. It remains entirely opt-in and was previously easy to miss.

1.8.1

Fix: shoppers on a VPN or proxy set to "Monitor" were still rejected when datacenter blocking was on, because VPN servers run in datacenters. Monitoring now means monitoring.
Fix: stores in the Community Threat Network were reporting every shopper as having no VPN/proxy/Tor/datacenter signal, so shared intelligence was based on incomplete data.

1.8.0

Fix: verified search engines are no longer caught by category rules, on both the classic and block-based checkout.
New: allow any IP directly from the Events Log.
New: tell us why you're deactivating, so we can fix it.

1.7.4

Fix: turning OFF both "Block VPN" and "Monitor VPN" now genuinely ignores VPN shoppers. Previously the order fell through to the risk-score check and was blocked anyway, logged as "high risk" with no mention of VPN. Same fix for the proxy toggles, on both the classic checkout and the Store API (block-based checkout) paths.

1.7.3

Fix: known-malicious IP blocking (introduced in 1.7.2) now correctly reads the malicious signal from the Predax API — a normalization gap meant it never actually triggered a block.
New: the Events Log now shows the specific reason for a malicious-IP flag (botnet C2 vs. hijacked network range) instead of a generic "malicious" tag.
New: the API key field is now masked (with a Show/Hide toggle) instead of shown in plain text — both on the Fraud Rules tab and in the Setup Wizard's manual-entry step — and is excluded from Settings Export/Import so it can never leave the site in a shared file.

1.7.2

New: known-malicious IP blocking — a dedicated category (separate from your general risk mode) for botnet C2 and hijacked-netblock IPs. Off by default; enable it via the Setup Wizard's Recommended/Strict presets, the Fraud Rules tab, or the one-click "Enable malicious-IP blocking" notice.
New: filter the Events Log by reason — narrow the log to just one block category instead of scrolling the full list.

1.7.1

New: live API usage meter on the Fraud Guard settings page — shows your monthly IP-check usage against your plan's quota (fetched hourly), with an upgrade link when you're above 80%.
New: quota notice — if your plan's monthly IP checks run out (checkout screening pauses and orders are allowed through until the quota resets), the plugin now tells you on its admin pages instead of failing silently. Dismissible per month.
New: API circuit-breaker — if the Predax API becomes slow or unreachable, checkouts now fail open instantly after a few consecutive failures instead of each waiting on the timeout, and the settings page shows an "API degraded" indicator. The API request timeout was lowered from 8s to 3.5s, so even a first failure delays a checkout far less.
Privacy: customer emails in the Events Log are now masked before storage ("bi***@example.com"). Enough to recognise a repeat customer; the linked order still holds the full email. Existing rows are untouched and age out via the log retention setting.
Performance: the IP allow/deny list options no longer autoload on every page request (the deny list can grow via the chargeback auto-append). A one-time migration updates existing installs.
Docs: installation instructions rewritten for installing from the WordPress.org plugin directory; added a section on free vs paid plan limits.

1.7.0

Rebrand: IPSentry is now Predax. This is the first WordPress.org release of the WooCommerce plugin. The plugin name, admin menu, and links now use Predax (predax.io). Your existing settings, API key, and order data are preserved — internal option names are unchanged, so nothing needs reconfiguring.
Admin menu moved to a lower position so it no longer sits among the core WordPress menu items.
Compliance: the OAuth-callback exit page now registers and prints its CSS/JS through the WordPress script API (wp_register_style/wp_register_script + wp_print_styles/wp_print_scripts) instead of hand-written tags. The WooCommerce settings save and checkout timezone read run inside WooCommerce's own nonce-verified flows and carry inline justifications for the static analyser.
Compatibility: declared WooCommerce High-Performance Order Storage (HPOS) compatibility.
Fix: the order-velocity time window now uses a timestamp-based date query (the previous datetime-string form could be misread by WooCommerce and count orders outside the window).
Hardening: checkout error notices are HTML-escaped before being added; the settings-import upload is capped at 512 KB with bounded JSON depth; the API base URL accepts http/https only; the timezone cookie is marked Secure on HTTPS stores; the Store API block path gained an explicit return after blocking.
Clarity: Refund / Chargeback Feedback labels and docs now state that "Log" reports go through the Community Threat Network opt-in; the readme documents exact API endpoints and the full telemetry data list.
New: IP allow-list (never block trusted IPs) and a managed deny-list, both supporting single IPs and CIDR ranges (IPv4 + IPv6), editable from the settings page and the WooCommerce → Predax tab.
New: the Community Threat Network opt-in is now a settings toggle (still off by default) instead of import/export only.
New: Events Log retention setting (default 90 days; 0 = keep forever) with automatic daily cleanup, plus a 7-day/all-time stats summary, CSV export, and a Clear Log button.
New: "Behind a proxy / CDN" setting (off by default). Enable it when your store is behind Cloudflare, a CDN, or a reverse proxy so the real customer IP is read from forwarded headers; when off, only the direct connection IP is used, so the customer IP cannot be spoofed to bypass fraud checks.
Security: the Events Log CSV export now neutralises spreadsheet formula-injection — a billing email such as "=...@example.com" can no longer execute as a formula when the export is opened in Excel/Sheets.
Fix: the "Flag for review" action on the velocity, disposable-email, and billing-country-mismatch rules now reliably tags the order, adds the order note, and writes the Events Log entry (previously these markers could be dropped on processed orders).
Fix: a critically-risky IP (risk score 90+) is now always blocked while a blocking mode is active, even when its VPN/proxy category is set to Monitor.
Fix: the WooCommerce → Predax settings tab now saves correctly (removed an invalid nested import form; import is now on the Fraud Guard → Developer page).
Hardening: /0 (match-all) entries are rejected in the IP allow/deny lists, and uninstall now cleans every site on a multisite network.
No change to the opt-in model — the plugin still makes zero outbound requests until you enter an API key and save a protection mode.

1.6.2

Compliance: community-feedback telemetry is now explicitly opt-in (off by default) behind a new ipsentry_woo_community_enabled option. Existing installs stop sending telemetry until they flip this on.
Compliance: all phoning-home defaults flipped to off — block_proxy, block_tor, and monitor_vpn default to 'no' on fresh installs.
Compliance: removed the self-hosted plugin updater class per WP.org Guideline 8.
Compliance: extracted every inline <script> / <style> block to enqueued asset files. OAuth-callback exit page now references an external CSS/JS pair.
Compliance: Privacy Policy content hook (wp_add_privacy_policy_content) so admins can pull suggested text from Tools → Privacy.
Compliance: Setup-wizard privacy-disclosure boxes added above OAuth button, manual API-key field, and preset-picker cards.
Compliance: nonce-before-cap order fixed on every admin-post and AJAX handler.
Compliance: input sanitisation tightened on every $_GET / $_POST / $_FILES read; imported settings values now validated per option type.
Compliance: Test-mode admin notice now scoped to Predax pages only (not global).
Added: uninstall.php drops the events-log table and deletes every ipsentry_woo_* option on plugin deletion.
Added: Domain Path: /languages header + minimal .pot translation template.
Added: .distignore excluding dev artefacts from the WP.org zip.
No behaviour change for existing installs other than the community-feedback gate — core IP checking still works as before.

1.6.1

Improved: OAuth connect popup now auto-closes reliably after authorization.
Improved: Per-user OAuth transients prevent conflicts on multi-admin sites.

1.6.0

New: Setup Wizard — guided 3-step setup on first activation with fraud protection presets (Recommended, Strict, Monitor Only).
New: One-Click Connect — click "Connect with Predax" in the setup wizard to link your store via OAuth. No API key to copy or paste.
New: "Run Setup Wizard" link in Developer tab to re-run the wizard at any time.

1.5.0

New: Events Log admin page (Predax → Events Log) — two tabs showing blocked checkout attempts and flagged/held orders with IP, risk score, flags, reason, and order links.
New: Predax risk column on WooCommerce → Orders list — shows colour-coded score badge and top threat flag.
Improvement: Orders now store a combined _ipsentry_flags meta key for quick flag lookup.

1.4.3

New: Dedicated settings page under Predax → Fraud Guard in the WordPress admin left nav — same tabbed UI as the Security plugin.

1.4.2

New: Settings import/export — back up your configuration or copy it between sites.
New: Support Email field — if set, checkout block error messages include a "Contact us at…" line.

1.4.1

Fix: VPN/proxy customers set to Monitor mode were incorrectly blocked by the risk threshold.

1.4.0

New: Automatic order hold, order velocity rules, billing country vs IP mismatch, disposable email detection, refund/chargeback feedback, test IP override.

1.3.0

New: Off/Monitor/Block radio groups for VPN, proxy, and Tor.
New: Custom risk scoring weights — adjust per-signal contribution to the final risk score.

1.2.0

New: Country-based blocking at checkout. Whitelist support. API timeout handling.

1.1.0

New: Configurable risk threshold. Order meta. Detailed order notes.

1.0.0

Initial release. Tag-only fraud screening at checkout. VPN / proxy / Tor / datacenter detection.

Predax Fraud Guard for WooCommerce – Anti-Fraud, Fake Order & Card Testing Protection

标签

下载

详情介绍:

安装:

屏幕截图:

升级注意事项:

常见问题:

更新日志: