Skip to content
Support

Troubleshooting & FAQ

Frequently asked questions, privacy details, uninstallation behavior, and troubleshooting steps for Veridis Fraud Guard Free.

Answers to common operational questions, privacy practices, and diagnostic steps for Veridis Fraud Guard Free.

Frequently asked questions

Section titled “Frequently asked questions”

Does Fraud Guard use artificial intelligence or risk scoring?

Section titled “Does Fraud Guard use artificial intelligence or risk scoring?”

No. Veridis Fraud Guard Free is strictly deterministic. It relies on direct matching against your store’s own merchant blocklist (email, phone, IP, and domain). It does not compute opaque risk scores, guess customer intent, or charge recurring fees for AI predictions.

Does Fraud Guard guarantee zero uncollected Cash on Delivery parcels?

Section titled “Does Fraud Guard guarantee zero uncollected Cash on Delivery parcels?”

No security or protection tool can guarantee 100% prevention of uncollected packages from previously unknown first-time buyers. Fraud Guard gives you deterministic control over repeat problematic customers, preventing buyers who have previously burned your store from repeatedly doing so.

Does Fraud Guard slow down the WooCommerce checkout?

Section titled “Does Fraud Guard slow down the WooCommerce checkout?”

No. Fraud Guard runs indexed SQL queries directly against your local MySQL database. Because it performs no external HTTP requests, API calls, or cloud scoring rounds, checkout evaluation occurs locally on your server using indexed database tables without waiting on external networks.

Does Hold mode block customers who pay with credit cards?

Section titled “Does Hold mode block customers who pay with credit cards?”

No. In Hold mode, prepaid orders (credit cards, digital wallets, bank transfers) complete payment normally without altering the order status. A private operational note is added to alert your team, ensuring you never inadvertently interrupt legitimate paying customers.

What happens if a customer formats their phone number differently?

Section titled “What happens if a customer formats their phone number differently?”

Fraud Guard normalizes phone numbers by stripping formatting characters (spaces, hyphens, parentheses, and dots) before comparing them. Whether the customer enters (555) 123-4567 or 5551234567, the normalized match evaluates successfully.

Data privacy and GDPR compliance

Section titled “Data privacy and GDPR compliance”

Veridis Fraud Guard Free is built around a local-first, privacy-conscious architecture:

  • Local data residency: All blocklist entries and activity logs reside exclusively within your WordPress database (wp_veridis_fraud_guard_blocklist and wp_veridis_fraud_guard_activity).
  • No external telemetry: Fraud Guard does not connect to Veridis servers, analytics beacons, or third-party cloud services.
  • Automated 90-day retention: Exact matched identifier values in checkout Activity logs expire and are automatically cleared after 90 days via scheduled WordPress tasks, while non-identifying operational records remain for reporting.
  • WordPress Privacy Tools: Implements native WordPress personal data exporter and eraser hooks, ensuring customer blocklist records and activity entries are included when handling GDPR customer data requests.

Uninstallation and data cleanup

Section titled “Uninstallation and data cleanup”

When you deactivate or delete the plugin:

  • Standard deactivation: Deactivating the plugin preserves your blocklist rules, settings, and historical logs so you do not lose data during temporary troubleshooting or site updates.
  • Plugin deletion: If you delete Fraud Guard via the WordPress administrative interface (Plugins → Installed Plugins → Delete), WordPress executes the plugin uninstaller:
    • Custom tables (wp_veridis_fraud_guard_blocklist and wp_veridis_fraud_guard_activity) are dropped.
    • Plugin options and settings in wp_options are removed.
    • Scheduled cron events (veridis_fraud_guard_purge_activity_identifiers) are cleared.
    • WooCommerce orders, order notes, and financial records are preserved.

Troubleshooting common issues

Section titled “Troubleshooting common issues”

Checkouts are not being evaluated or blocked

Section titled “Checkouts are not being evaluated or blocked”
  1. Verify Protection Mode: Navigate to WooCommerce → Fraud Guard → Settings and ensure the mode is set to Block or Hold (not Off or Warn).
  2. Verify Rule Status: In WooCommerce → Fraud Guard → Blocklist, confirm that the rule has its toggle set to Active.
  3. Verify Field Normalization: Check WooCommerce → Fraud Guard → Activity to see what value was received during checkout and ensure your blocklist entry matches that format.

Reverse proxies and Cloudflare IP detection

Section titled “Reverse proxies and Cloudflare IP detection”

If IP address rules are not matching on stores using Cloudflare, Fastly, or reverse proxies:

  • Ensure your web server or WordPress configuration (wp-config.php) restores the real client IP header (CF-Connecting-IP or X-Forwarded-For).
  • Test by checking the IP address recorded on standard WooCommerce orders in WooCommerce → Orders.

Scheduled cleanup cron is not running

Section titled “Scheduled cleanup cron is not running”

If activity logs older than 90 days are not being pruned:

  • Check that standard WordPress cron (wp-cron.php) is functioning on your host, or configure a system crontab (*/10 * * * * wp-cron.php).
  • You can inspect scheduled cron hooks using the WP-CLI command wp cron event list.