Description
Running a WooCommerce store comes with fraud risks like fake registrations, suspicious transactions, chargebacks, and compliance issues. Traditional solutions rely on static rules and often fail to stop fraud. Sensfrx.ai (SFX) uses AI-powered fraud prevention to secure every step of the customer journey and stop fraud effectively.
Why WooCommerce Store Owners Trust Sensfrx.ai (SFX):
- Over 2+ million fraudulent attempts blocked annually.
- Reduces false positives, ensuring real customers aren’t blocked.
- Seamless integration with WooCommerce without disrupting workflows.
- Ensures compliance with regulations like OFAC sanctions while securing your business.
Customer Feedback:
“Sensfrx.ai (SFX) has transformed the way we protect our store. Fraudulent orders and bots have dropped by 90%. It’s like having a fraud prevention team working 24/7.”
— Shohei Tanaka, WooCommerce Store Owner
Top Features
- Fully AI-driven risk rating with no need for manual intervention.
- Block fraudulent visitor behavior before checkout.
- Eliminate Captchas while effectively blocking bots.
- Identify and stop users behind proxies or risky devices.
- Flag unusual or repetitive transactions instantly.
- Block by IP, state, zip code, or email with tailored messages.
- Automatically block high-risk or sanctioned countries.
- Adapts to evolving fraud patterns for better protection.
Keynote: Frauds, Attacks, & Security Measures in Digital Commerce
Strengthening WooCommerce Security: Practical Steps for Fraud Prevention
Sensfrx.ai (SFX) How it works?
Privacy & External Services
Important: This plugin connects to Sensfrx.ai (SFX)’s external fraud detection API to provide real-time fraud analysis. When the plugin is active and configured with your API credentials, the following data may be transmitted to Sensfrx.ai servers for fraud detection purposes:
Data Transmitted:
- User IP addresses and device fingerprints
- Registration information (email addresses, usernames, registration timestamps)
- Login attempts, timestamps, and authentication events
- Transaction details (order amounts, product information, payment methods)
- User profile updates and password change events
- Billing and shipping addresses
- WooCommerce order metadata
External Services Used:
- Sensfrx.ai (SFX) API: https://sensfrx.ai
- Privacy Policy: https://sensfrx.ai/privacy-policy
- Terms of Service: https://sensfrx.ai/terms
- Trust & Security: https://sensfrx.ai/trust
User Consent & Configuration:
By activating this plugin and entering your Sensfrx.ai (SFX) Property ID and Property Secret (obtained from https://client.sensfrx.ai), you acknowledge that user data will be transmitted to Sensfrx.ai’s servers for fraud analysis. The plugin will not transmit any data until valid API credentials are configured.
Data Security:
Sensfrx.ai (SFX) is SOC 2 compliant and maintains strict data security standards. All data transmissions use HTTPS encryption. For complete details about data handling, retention policies, and your rights under GDPR and other privacy regulations, please review Sensfrx.ai’s Privacy Policy.
Required API Credentials:
To use this plugin, you must sign up for a Sensfrx.ai (SFX) account at https://client.sensfrx.ai/signup and obtain your unique Property ID and Property Secret. A free plan with 500 API credits per month is available.
Upgrade Your Store Security
Stop losing revenue to fraud and protect your WooCommerce store with AI-driven fraud detection today!
Support
Join our community for real-time support and fraud prevention insights:
- Discord: https://discord.gg/zGBGQdwT4r
- Documentation: Sensfrx WooCommerce Plugin Guide
Installation
- Sign Up for FREE
Create your account at Sensfrx.ai (SFX) Signup to access 500 FREE API credits. - Add Your Store as a Property
Register your WooCommerce store to receive your unique Property ID and Property Secret. - Install the Sensfrx.ai (SFX) Plugin
Download and install the Sensfrx.ai (SFX) plugin via your WordPress dashboard. - Activate and Configure
Paste your credentials into the plugin settings to enable fraud protection. - Stay Protected
Sensfrx.ai (SFX) starts working immediately, blocking suspicious users and keeping your store secure.
For a step-by-step installation guide, watch our video tutorial: How to Install WooCommerce AI-Powered Fraud Prevention Plugin.
FAQ
Is Sensfrx.ai (SFX) free to use?
Yes, Sensfrx.ai (SFX) provides free access for up to 500 monthly active users. For larger volumes, explore our flexible paid plans that scale with your business.
How do I get my Property ID and Property Secret?
Sign up at Sensfrx.ai (SFX) Signup, add your WooCommerce store, and generate your unique Property ID and Property Secret from the dashboard.
What data does the plugin send and receive?
Sensfrx.ai (SFX) processes minimal user data, such as IP addresses, devices, and transaction details, solely for fraud detection purposes. We maintain strict data security standards and are SOC 2 compliant. For more details, visit our Trust and Security Page or read our Privacy Policy.
Screenshots
Changelog
3.11.11
- Recheck the connection after saving a replacement Property Secret.
- Keep the latest settings when another save is still in progress, and ignore stale connection replies.
- Require store-management permission for settings autosave.
3.11.10
- Fixed: Overview and Fraud intelligence use the same inclusive UTC calendar ranges. Seven days now requests seven dates, rather than eight; the correction also applies to longer periods.
- Improved: filtered empty activity states describe the selected filters without implying the whole store has no risky activity.
3.11.9
- Fixed: fraud history requests preserve their date filters, restoring order records in Fraud intelligence.
- Fixed: unavailable activity feeds show a retryable error instead of missing orders, zero totals or sample fraud records. Stale responses and exports are guarded while loading.
- Fixed: order values retain their own currency and decimal precision; blocked totals stay separate by currency, and merchant reviews remain distinct from original risk.
3.11.8
- Fixed: activity badges use the recorded fraud decision, so email addresses and notification wording cannot turn ordinary activity into blocked orders. Held orders show Held for review.
- Fixed: email activity is excluded from order filters and counts.
- Improved: fraud intelligence table actions remain reachable at narrow widths and enlarged zoom; complete currency metrics remain readable.
3.11.7
- Added: automatic order reassessment after temporary security-service failures. Checkout stays available while unchecked fulfillment and downloads wait for a completed check or merchant review.
- Fixed: recovery respects merchant holds, existing approvals, closed orders and changes to order details.
- Fixed: retries and queue failures stay visible, and unconfirmed payment reversals remain unresolved. Cash-on-delivery recovery does not mark unpaid orders paid.
3.11.6
- Fixed: temporary service and network errors remain explicitly unchecked on the order screen, instead of appearing as completed low-risk assessments. Checkout remains available.
3.11.5
- Fixed: Overview statistics and filtered reviews load correctly on stores using WordPress plain permalinks.
- Fixed: approval counts refresh immediately after single or bulk order reviews.
- Fixed: closed orders leave the review queue and cannot report a new approval. Commerce status sync preserves original risk, retries temporary failures and shows unresolved sync problems.
- Fixed: approving an unpaid on-hold order requests payment instead of marking it paid, even after its old fraud hold was removed.
- Fixed: wrong sign-in codes no longer restart the ten-minute expiry. A code with an expired or unknown deadline requires a fresh sign-in.
3.11.4
- Improved: Overview refreshes approval counts after review and describes approvals without claiming completed sales.
- Fixed: repeated review approvals cannot mark an unpaid order as paid, revive closed orders or resend the same review email. Completed orders retain their status.
- Fixed: bulk review accepts the transaction format returned by the SDK.
- Fixed: background guest payment checks work without a shopper session.
- Fixed: background payment confirmations are assessed without requiring the shopper to return to the thank-you page, using the order owner rather than an active admin session.
- Fixed: bot requests are assessed even when browser device data is absent.
- Fixed: challenged comments are saved in moderation, and comment decisions apply even when their severity label differs.
- Fixed: a queued forced logout applies before page output and cannot show its blocked-account notice to another visitor.
-
Fixed: the order panel shows your approval or refusal while retaining the original risk details.
-
Fixed: WordPress password reset and registration confirmation messages remain visible.
- Fixed: custom order lines and orders with deleted products still receive fraud checks instead of crashing.
- Fixed: signed callbacks use the correct REST address on stores with plain permalinks. Existing callback registrations are repaired in the background without changing their signing secrets.
- Fixed: review and refusal decisions are enforced even when a custom rule produces a different risk severity.
- Fixed: an order awaiting security review cannot be paid from its payment link or retried checkout until the store approves it.
- Improved: orders stopped before payment show the saved decision and reasons on the order screen.
3.11.3
- Fixed: a customer you put on the allow list in Sensfrx could still be signed out, and sent a password reset, by the automated-browser check. That check now tells Sensfrx who is signed in, so your allow and block lists apply to it.
- Fixed: a new Sensfrx account created from the plugin now uses your store’s time zone instead of India time.
3.11.2
- Fixed: “Orders blocked” on the dashboard counted refused sign-ins and sign-ups as orders.
- Fixed: order amounts in Fraud intelligence now show each order’s own currency. Totals add up orders in your store’s currency and count the others separately.
- Fixed: the “Connect email” step showed as done on every WooCommerce store, even with no email setup.
- Fixed: customer account alerts no longer show internal labels such as “Incident Triggered!” or “User Account Compromised”.
- Fixed: the average risk score can no longer show above 100, guest order checks are logged as “before payment”, and the Fraud review message reads “Blocked”.
- Changed: the Customer emails setting says plainly that these emails go out from your store’s own address.
3.11.1
- Fixed: guest orders placed through the block checkout now send the shopper’s email, name and billing address to Sensfrx. Before, only the shipping address was sent, so email checks did not run on those orders and your dashboard showed the customer as Anonymous.
- Fixed: the order amount sent to Sensfrx is now correct in every currency. Stores in euros, pounds, rupees and other currencies whose symbol is not “$” sent a wrong or empty amount for guest orders.
- Fixed: connecting with your WordPress administrator email now sends a verification code, as for any other email. Before, it stopped with “The API did not respond correctly”.
3.11.0
- New: each sign-in tells Sensfrx how the customer signed in (password, social sign-in such as Nextend Social Login, XML-RPC, or another method), so your Sensfrx dashboard shows it on logins and you can filter by it. Only whether a field was sent is checked, never its value. Sites with another sign-in plugin (passkeys, email links, single sign-on) can report it with the sensfrx_login_method filter.
3.10.1
- Fixed: MailPoet could unsubscribe an existing subscriber whose address was kept out of email marketing, the next time their account was saved. Only new subscribers are now affected, and existing subscriptions are never changed.
- Fixed: an address that belongs to an account on your store is never kept out because of a refused order, a refused checkout or a failed sign-up (anyone can type someone else’s address into a guest checkout).
- Fixed: an order Sensfrx refused counts only once it is actually cancelled or failed, so nothing happens in shadow mode, for whitelisted customers, or while you keep the order open.
- Checkouts refused during a card-testing attack are kept out for a week, each stored on its own, so an attack does not rewrite the list on every request.
- Only rules with real weight count, and browser-integrity checks that privacy browsers trigger are no longer treated as signs of a fake account.
3.10.0
- New: addresses Sensfrx judged fake stay out of your email marketing, so you are not billed for bot contacts and welcome and abandoned-cart emails do not go to junk addresses. This covers sign-ups Sensfrx allowed but that showed signs of a bot or a fake identity (for example a disposable address), orders Sensfrx refused, and checkouts refused during a card-testing attack. Such an address is saved as unsubscribed in MailPoet; Mailchimp for WooCommerce does not get its newsletter tick or the refused order; Klaviyo and Omnisend do not get the order or customer; Cart Abandonment Recovery (CartFlows) and Abandoned Cart Lite send it no abandoned-cart email. Nothing is deleted, nobody is emailed, and each new account kept out is listed in Activity. It lasts 90 days.
- Developers can turn it off with the sensfrx_email_guard_enabled filter.
- Sign-up checks now come with their reasons, as order checks do.
3.9.1
- Fixed: the dispute evidence report no longer lists other guest customers’ orders as the customer’s own, and no longer counts shared or unknown IP addresses (fixed on the Sensfrx side; this release updates the order screen to match).
- The dispute date is kept only when the payment provider supplies it (WooCommerce Stripe Gateway). A chargeback you report by hand no longer sets it, so the report counts card-network time limits conservatively instead of from the day you reported.
- The report page runs in a sandbox in your browser.
3.9.0
- New: dispute evidence. When a customer disputes an order as fraud, open “Dispute evidence” in the Sensfrx box on the order. It lists the customer’s earlier orders from your store that match this one (same account, device, IP address or delivery address) and were not disputed, and says whether they meet the card networks’ rules: Visa Compelling Evidence 3.0, Mastercard and American Express. Print it or save it as PDF and upload it with your reply to the payment provider.
- The Sensfrx box now also appears on orders Sensfrx checked before version 3.7.0, with the dispute evidence link.
- When a fraud dispute arrives through the WooCommerce Stripe Gateway, or you report one from the order page, its date is kept so the report counts earlier orders back from the day of the dispute.
3.8.1
- Improved: card-testing protection is harder to get around and gentler on real customers.
- Attack mode now starts only when most declined payments come from new visitors, so a payment-provider outage does not trigger it. New visitors share a limited allowance for at most two hours of an attack, and browsers first seen shortly before an attack count as new.
- A delivery address is refused only when declines come from more than one browser or network, both address lines are used, and returning customers with a completed order are not affected.
- Stores behind a CDN or proxy the plugin does not recognise are no longer treated as one visitor.
- The pay-for-order page no longer counts a card form the payment method rejects before trying the card, and orders a shop manager marks as failed are not counted.
- New: at most five “add payment method” attempts an hour per account, browser and network.
- Declined payments are reported at the end of the request, with a limit per visitor; visitor hashes are removed from orders once they are settled.
3.8.0
- New: protection against card testing (bots that run stolen card numbers through your checkout). After repeated declined payments from one browser or network, further attempts are refused before an order or payment is made, so no fee is paid on them. Declined payments to one delivery address under several different email addresses are stopped the same way.
- New: when declined payments arrive from several visitors at once, checkout asks for a browser that has opened your cart or checkout page, which stops scripts that call the checkout directly. Returning customers are not affected.
- New: declined payments are reported to Sensfrx, so an order placed out of a run of declines is held or refused.
- Covers the classic checkout, the block checkout and the pay-for-order page. Shop managers are never limited. It follows the main “Fraud protection for this store” switch, and writes a line to the activity log when it acts.
3.7.1
- Improved: when a customer finishes a sign-in with the emailed code, Sensfrx now learns that the device is theirs, so the same device is not asked for a code again for the same reason.
- Improved: the plugin tells Sensfrx which version it is running, so support can see whether a store has the latest protections.
3.7.0
- New: a Sensfrx box on the order screen. It shows what Sensfrx recommends for the order, what raised the risk in plain words, and anything that speaks for the shopper. It appears only on orders Sensfrx checked.
- New: when Sensfrx holds or refuses an order, the order gets a private note that says why.
- Improved: every reason in the review list has a plain name and a short explanation in place of a code.
3.6.5
- Privacy: the one-way code sent in place of a typed username is now made with a random key that is created on your site and never leaves it, so nobody outside your store, Sensfrx included, can work out what was typed.
- Fixed: the daily limit on emails to a customer now holds even when two requests arrive at the same instant.
3.6.4
- Fixed: a customer could be unable to finish a sign-in for a day if their sign-in codes did not arrive, or if other emails to their address had used up the daily limit. Sign-in codes, confirmation links and your decisions on held orders are no longer held back by the daily limit, and a password reset makes new sign-in codes available straight away.
- Fixed: if the store cannot send a sign-in code, the customer is told so instead of being asked for a code that never arrives, and the failure shows in the email log and setup notice.
- Fixed: each held order now gets its own “approved” or “cancelled” email, even when one customer has two on the same day.
- Improved: Sensfrx’s own refusals and sign-in code requests are no longer counted as failed passwords, and the activity log no longer records what was typed into the username box.
3.6.3
- New: the setup checklist has a “Send customer emails from your store” step. It is ticked automatically when an SMTP plugin sends your store’s mail.
- New: if WordPress cannot send Sensfrx’s emails to your customers (sign-in codes, order notices), Sensfrx shows one notice on its own screens and lets you know by email, at most once a week and only while emails are actually failing. It stops as soon as your mail works.
3.6.2
- Improved: fewer emails to your customers. Sensfrx emails go out through your store’s own mail, so every unnecessary one costs your store’s sending reputation. Each customer now gets at most one email of the same kind a day (for example one “sign-in blocked” notice, however many attempts were blocked), at most three sign-in codes a day, and at most four Sensfrx emails a day in all.
- Improved: a blocked sign-in sends the customer one email with a reset-password button, not two.
- Changed: the emails for activity that was allowed (“a login, order or sign-up looked slightly unusual”) are now off. They asked the customer to do nothing. You can switch them back on under Email notifications.
- Security: someone who has a customer’s password can no longer make your store email that customer a code on every attempt, and the blocked-sign-in message no longer tells them an email was sent.
3.6.1
- Improved: password-guessing and credential-stuffing protection now counts every failed sign-in correctly. Attempts on made-up usernames count as separate accounts, and a block for guessing one account now takes effect before the password is checked.
- Privacy: on a failed sign-in the plugin no longer sends the username that was typed. It sends a one-way code made with your store’s secret key, so Sensfrx can count attempts without seeing what was typed (people sometimes type a password into the username box).
3.6.0
- New: AI agents that prove who they are (for example Google’s shopping agent, by signing its requests) are recognised and shown in Fraud review as “Verified AI agent”. This is a label only: the agent is not trusted more, and every other check still runs.
- New: requests that pretend to be a known AI agent (such as ChatGPT or Google’s agent) but fail the proof are flagged as “AI Agent Impersonation”.
- The plugin forwards the agent’s signature headers to Sensfrx for checking. They are public values; no personal data is added.
3.5.0
- New: the card issuer’s address and security-code checks (AVS / CVV) now help score each order. They are read from the payment gateway after payment: Stripe (official and Payment Plugins), Authorize.Net CIM, Braintree, Square, PayPal advanced card processing, Elavon, Chase Paymentech, CyberSource and other gateways that record them on the order. No card data is sent; only whether each check matched.
- Improved: shipping to a different address no longer counts against an order on its own (gifts, work and family addresses are normal). Sensfrx now looks at whether the buyer is where the card is, and learns which countries are normal for your store.
- Fixed: digital products (tickets, courses, downloads) were treated as if they shipped somewhere.
3.4.0
- Security: password guessing and credential stuffing are now stopped in real time. After repeated failed sign-ins from one network or device (or on one account), further attempts are refused before the password is accepted, with the same message whether the password was right or not. An attacker blocked at two stores is blocked at every Sensfrx store for an hour.
- Security: a sign-in Sensfrx denies is refused before the session is created (it used to sign the visitor in and then out again). The account owner still gets a password reset email.
- New: a sign-in Sensfrx challenges now asks for a 6-digit code emailed to the account owner before signing in (it used to let the visitor in and only send an email). Works on wp-login.php and the WooCommerce My Account form.
- Shadow (monitoring) mode, the admin allow list and API timeouts keep the old behaviour: nothing is blocked.
3.3.0
- Security: signed webhooks with replay protection, REST nonce checks, webhook secret rotation, credentials no longer written to a public debug log
- New: Fraud intelligence shows why each event was scored, order number and amount, and links held orders straight to Fraud review; filters built for thousands of events
- New: Fraud review shows why each order was held and handles large queues (priority sort, filters, paging, bulk actions)
- New: plan usage shows the checks Sensfrx actually counts this month
- New: block/allow list values are checked before saving (IP, range, email, domain, username)
- New: Blocks checkout orders are now scored; historical orders sync
- Improved: redesigned admin (Dashboard, Settings, Privacy & GDPR, Validation rules, Fraud protection, Activity log); in-page confirmations instead of browser pop-ups
- Improved: self-hosted fonts, admin assets loaded only on Sensfrx screens, API timeout filter
- Fixed: risk colours used the wrong thresholds; dates shifted by a day in some time zones; Free-plan rule changes showed errors instead of plan options
- New: when you refund an order with a reason that mentions fraud, a chargeback or a dispute, it is reported to Sensfrx automatically so future scoring learns from it
- Fixed: on stores using WooCommerce’s high-performance order storage (HPOS), an order was sent to Sensfrx under two different transaction ids before and after payment
- Removed: 7,971 lines of unreachable code
3.2.3
- Security: Sensfrx webhooks are accepted only with a valid per-store signature
- Security: plugin admin API requests require a WordPress REST nonce
- Security: removed a diagnostic log file and rotate webhook signing secrets on upgrade
- Security: UCP request detection now applies only to the request that carries the UCP headers
3.2.2
- Enhanced subscription and revenue-limit handling
- Added inactive protection status handling with clear upgrade messaging
- Improved customer, subscription, and property validation
- Updated dashboard protection status UI for Active/Monitoring/Inactive states
- Improved existing customer and plan-selection flow
- Enhanced API error handling and debugging across Core API, Customer Dashboard, and WooCommerce plugin
3.2.1
- MCP support enabled
3.2.0
- Added Privacy & GDPR tools for shopper data export and deletion via Sensfrx cloud APIs
- Integrated WordPress Tools → Export/Erase Personal Data with Sensfrx local and cloud data
- Added consent modes for device fingerprinting (legitimate interest, require CMP, or disabled)
- Added optional transaction data minimization and local activity log retention controls
- Added merchant privacy contact sync and privacy policy suggested text for WordPress
3.1.3
- Hotfix for editor role redirect issue
3.1.2
- Added email notification support for promotion abuse detection
- Prevented duplicate activity log entries within a configurable time window
- Improved promotion abuse handling and logging
- Minor bug fixes and code improvements
3.1.1
- WordPress 7.1 compatibility and plugin directory compliance fixes
- Aligned plugin name between readme and plugin header
- Replaced debug print_r() calls in plugin activation handler
- Tested up to WooCommerce 10.9.1
3.1.0
- EDD support added in the plugin
3.0.10
- Bug fixes to improve stability of the plugin
3.0.9
- UI fixes on fraud protection page
3.0.8
- Urgent hotfix for redeclare error on checkout page
3.0.7
- Comma separated values support added for blacklist and whitelist feature
3.0.6
- CSS Scripts leakage to admin UI fixed
3.0.5
- Bug fixes related to onboarding issues and email alerts
3.0.4
- Major bug fixes related to redeclaration classes and guest checkout data mising issues
3.0.3
- Major bug fixes: Activation, Settings Page Accordion, Checkout Page
3.0.2
- Uninstall DROP table query fixed
3.0.1
- Admin email address related bug fixed
3.0.0
- Major overhaul of the entire plugin architecture
- Completely revamped UI for a cleaner and more modern experience
- Improved overall stability and robustness
- Fixed multiple critical bugs and performance issues
2.0.20
- Undefined variables and null array offset bugs fixed
2.0.19
- oAuth OTP moved from store email to Sensfrx API email
2.0.18
- Quick bug fix in SDK
2.0.17
- Shipping Address related bug fixes
2.0.16
- Fraud Cases Enable/Disable Feature is implemented
2.0.15
- Code Optimization
- oAuth Signup Feature & Verify API Integration
- UI Fixes
2.0.14
- Error reporting turned off
2.0.13
- PHP 8.2 compatibility bugs fixed
- Manual review events approve/deny javascript bug fixed
2.0.12
- Login Failed – Issue resolved; API now triggers only when the username is incorrect.
- Order Update fraud check event added.
- Add to Cart fraud check event added.
- Remove from Cart fraud check event added.
2.0.11
- Password reset now only triggers from WordPress, not from WooCommerce – fixed
- Password reset activity entry was missing in the Activity tab – fixed
- Bot Fraud check applied for Post comments
- Fraud Protection settings page implemented
2.0.10
- Post Payment Notifications: Admin approval now triggers an email notification to the user.
- JavaScript Loader Improvements: Added validation checks for pid and skey. JS files and pixel scripts will load only after these credentials are entered.
- PHP Warning Handling: Implemented exception handling to suppress and manage PHP warnings gracefully.
- Activity Tab Updates: Added loader for improved user experience while fetching latest activities. Resolved pagination issues.
- Core API Improvements: Under-the-hood enhancements made to the Core API, resulting in improved overall functionality.
2.0.9
- Fixed bug related to some data discrepancies.
2.0.8
- Fixed bug where Order ID was not received during pre-payment attempts.
- Review logs are now also recorded under the Activity tab.
- Manual Review implemented for Pre-Payment Attempts.
- For Pre-Payment Manual Reviews: Users will receive a payment link only after admin approval.
- Fixed PHP warnings related to user_id variable and severity key access.
- Added support for Item Type and Shipping method in transaction data.
2.0.7
- Activity logs time zone issues are fixed
- UI bug fixes
- Add the entries into activity logs when policies are disabled
2.0.6
- Export Activity bug fixed
- Email Customization Feature bug fixed
2.0.5
- UI Fixes
- Email Customization Feature added
2.0.4
- UI Fixes
- Dashboard Stats added
- AppSumo new plans added
- Activity Tab with export feature
2.0.3
- Activity logs tracking added
2.0.2
- Critical bugs related to account review fixed
2.0.1
- Login pages device fingerprinting bug fixed
2.0.0
- New UI for the plugin with many new features developed
1.0.15
- Bug fixes
1.0.14
- Bug fixes
1.0.13
- Bug fixes
1.0.12
- Bug fixes
1.0.11
- Guest checkout review added
- Bug fixes
1.0.10
- Bug fixes
1.0.9
- Order Review Feature added
- Bug fixes
1.0.8
- Admin role users whitelisting feature
- Shadow mode performance improved
- Bug fixes in cron jobs
1.0.7
- Custom rules support added for tags and custom fields
1.0.6
- Bug fixed
1.0.5
- Activity logs feature bugs fixed
- Fixed product category information sent with transaction data
1.0.4
- Added activity logs feature
1.0.3
- Fixed bugs on deny signal handling on registrations
1.0.2
- Fixed handling of deny signal on registrations
1.0.1
- Added support for manual review
- Fixed Transaction attempt data discrepencies
1.0.0
- SensFRX first version, in this version we have developed an easy-to-install and configure SDK of SensFRX for WordPress users.
- Account takeover, new account, transaction fraud, and profile update fraud protection.





