Blocklist Management & Matching

The central foundation of Veridis Fraud Guard Free is the merchant blocklist, managed under Fraud Guard → Blocklist.

Supported identifier types

Fraud Guard supports four specific identifier types, each targeted at stopping repeat abusive orders:

Identifier Type	Evaluated Checkout Field	Normalization & Matching Rules	Example
Email	Billing Email (billing_email)	Converted to lowercase, trimmed. Exact string match.	[email protected]
Phone	Billing Phone (billing_phone)	Strips spaces, dashes, parentheses, dots. Retains digits and leading +. Exact match.	+15551234567 or 0740123456
IP Address	Client IP (REMOTE_ADDR / proxy header)	Validated IPv4 or IPv6 address. Exact string match.	198.51.100.42
Domain	Domain part of Billing Email	Lowercased domain name. Matches any email ending in @domain.com.	mailinator.com

Adding rules manually

To add a new rule to your store’s blocklist:

1. In WordPress admin, navigate to WooCommerce → Fraud Guard → Blocklist.
2. Click Add New Entry.
3. Choose the Identifier Type (Email, Phone, IP, or Domain).
4. Enter the Value.
5. Add an optional internal Merchant Note (e.g., “Refused COD order #1042; parcel returned”).
6. Set the initial Status to Active.
7. Click Save Entry.

Merchant notes

Merchant notes are strictly internal and visible only to store administrators in wp-admin. They are never displayed to customers or included in public API outputs.

Active vs. inactive status

Every blocklist rule includes an active/inactive toggle. If you want to temporarily suspend a rule—such as when investigating a customer dispute or performing a test order—you can toggle the status to Inactive without deleting the record or losing historical context.

Inactive rules are completely bypassed during checkout evaluations.

Exact matching logic and normalization

Fraud Guard relies on deterministic exact matching rather than probabilistic scoring. This guarantees predictable results and eliminates false positives:

• Email addresses: Stored and queried in lowercase. Whitespace is stripped automatically. A rule for [email protected] matches [email protected].
• Phone numbers: Because customers format phone numbers inconsistently (e.g., (555) 123-4567, 555.123.4567, 555 123 4567), Fraud Guard sanitizes both the blocklist value and incoming checkout input to comparable normalized digits.
• IP addresses: Evaluates the client IP address reported during the checkout request. (If your store is behind Cloudflare or a reverse proxy, ensure standard WordPress headers are configured so REMOTE_ADDR reflects real client IPs).
• Domains: Extracts the host portion after the @ symbol in the customer’s billing email. A rule for tempmail.com matches any email address ending with @tempmail.com.

No wildcards or regular expressions

In Fraud Guard Free 1.0, matching is strictly deterministic. Wildcards (*@*.com) or arbitrary regex patterns are not supported to preserve fast database index lookups and avoid unintended checkout blocks.