The module can deliver a clickable verification link or a code for the client to enter manually.
Configurable validity periods, reminders, account lifecycle actions, CAPTCHA protection, rate limiting and blocklist management give you greater control over client verification and help reduce fraudulent activity.

We will guide you step by step through the whole installation and configuration process.

The package contents should be uploaded without changing the provided directory structure.

Next, open the renamed file and enter your license key. The license key is available in our client area under 'My Products'.

Find 'Anti-Fraud And Email Verification' on the list and press 'Activate'.
Press 'Configure' , select the administrator role groups that should have access to the module, and save the changes.

The module is now available under 'Addons' → 'Secure Messages'.

In this guide, we will walk you through every section and option of the module in detail.

The 'Anti-Fraud Activity Summary' shows the numbers of failed verification attempts, rate-limited requests, automatic blocklist entries, failed CAPTCHA challenges and resent verification emails recorded today, during the last 7 days and during the last 30 days.

The 'Verifications Over Time' chart compares verified and unverified records from the last 30 days, helping you identify recent activity and trends.

Five counters provide a quick overview:

• Pending - verification has been initiated but not yet completed.
• Verified - the email address has been successfully verified.
• Rejected - the verification attempt has been rejected.
• Expired - the verification link or code is no longer valid.
• Total - the total number of verification records.

Press 'Show' on a counter to filter the table by the selected status.

• Email - the email address used for verification.
• Status - 'Pending', 'Verified', 'Rejected' or 'Expired'.
• Created At - when the verification was initiated.
• Verified At - when the email address was verified; 'Never' is shown if verification has not been completed.
• Expires At - when the verification link or code expires.

Use the search field to find a record. For records with 'Pending' status, the row actions allow you to manually approve or reject the verification. You can also return a record to 'Pending' status or delete it.

The record status will change to 'Verified', allowing the client to continue without completing the standard email verification process.

The record status will change to 'Rejected', and the client will not be considered verified.

Important: This changes the verification status only. It does not undo any order or account action already taken while the address was considered verified.

The related WHMCS client account and order, if any, remain unaffected. This action cannot be undone.

Entries may be added manually or created automatically after the configured number of failed attempts is reached.

• Type - email address, IP address or email domain.
• Value - the blocked value.
• Source - 'Manual' or 'Automatic'.
• Reason - an optional internal explanation.
• Expires At - the expiration date; 'Never' indicates a permanent block.
• Created At - when the entry was created.

Press the eye icon to view the complete reason when it is shortened in the table. Use the trash bin icon to delete an entry.

• Type - select 'Email', 'IP Address' or 'Email Domain'.
• Value - enter a value matching the selected type.
• Reason (Optional) - enter an internal note explaining the entry.
• Expires At (Optional) - select an expiration date or leave the field empty to create a permanent block.

Press 'Confirm' to add the entry.

The options are divided into four panels. Press 'Submit' to save the configuration.

• Verification Mode - choose where verification is required:
  • All Pages - locks the entire client area until verification is completed.
  • Checkout - prevents an unverified client from placing an order.
• Verification Delivery - choose 'Clickable Link' or 'Code To Type In'.
• Token Validity (Days) - define how long the generated verification link or code remains valid.

• Reminder After (Days) - send a reminder email after the client has remained unverified for the specified number of days. Enter 0 to disable reminders.
• Resend Cooldown (Minutes) - the minimum wait before another verification email can be requested.

• Auto-Inactivate After (Days) - set the client account to 'Inactive' after it has remained unverified for the specified number of days. Enter 0 to disable this action.
• Auto-Terminate After (Days) - permanently and irreversibly delete the client account and all of its WHMCS data after the specified number of unverified days. Enter 0 to disable this action.
• Auto-Delete Unverified Accounts - enable automatic cleanup of unverified accounts without active orders.
• Auto-Delete After (Days) - define the delay after Auto-Terminate before an eligible account is closed.
  
  

Important: Auto-Terminate actions are permanent and irreversible and may remove the client account together with all related WHMCS data. Review these settings carefully before enabling them in production.

• Rate Limit: Max Attempts - the maximum attempts allowed within the configured window.
• Rate Limit: Window (Minutes) - the rolling period used to count verification attempts.
• Auto-Ban After Failed Attempts - automatically block the related email address and IP address after this many failures. Enter 0 to disable it.
• Auto-Ban Window (Minutes) - the rolling period used to count failed attempts for automatic bans.
• Enable Captcha Verification - require a CAPTCHA challenge during email verification. The module uses the CAPTCHA type and credentials configured in WHMCS.
  
  

Before enabling this option, go to 'System Settings' → 'General Settings' → 'Security' in WHMCS and configure CAPTCHA.
Important: If CAPTCHA verification is enabled in the module but CAPTCHA has not been configured correctly in WHMCS, clients will encounter an error when attempting to complete verification.

• Clickable Link - open the link received in the verification email and complete any required CAPTCHA challenge.
• Code To Type In - enter the code received in the verification email in the form and press 'Verify'.

If 'Enable Captcha Verification' is active, the CAPTCHA configured in WHMCS is also displayed. After successful verification, the client can continue to the restricted page or complete checkout.

Create rules and assign them to selected administrators or administrator roles. For each rule, define the resources that should be available or restricted.

For detailed instructions, see the dedicated Access Control documentation.

For detailed guidance, check its dedicated article, available here.

Create a new theme or activate an existing one separately for each area. The module includes the officially supported 'Default' and 'Dark' themes.

Use a test account to check the selected delivery method, email content, CAPTCHA challenge and redirect behavior.

This gives legitimate clients additional time to complete verification and reduces the risk of unintended data loss.

These measures reduce repeated email requests while allowing legitimate clients to try again after a short wait.

Check automatically created entries and repeated failures before removing a block or changing the anti-fraud thresholds.

Go to 'System Settings' → 'Email Templates' in WHMCS and edit the 'Email Verification Link' template to adjust its subject and message content.
The template supports separate content for initial messages and reminders, as well as for code and clickable-link delivery.
When customizing it, retain the required Smarty conditions and variables, including {$is_reminder}, {$is_code_delivery}, {$code} and {$verify_url}.

Follow every step carefully to prevent data loss or other unexpected issues.

Choose the Open Source version of Anti-Fraud & Email Verification For WHMCS to receive these benefits together with prioritized support services.

Press 'Get Source Code' or 'Upgrade To Lifetime' on the product page in our client area to complete the upgrade, with a dedicated discount already applied.
Follow the comprehensive guide for the complete transition process.

Check the module and WHMCS mail logs, verify the mail configuration and ask the client to check the spam folder. Wait until the 'Resend Cooldown' ends before trying again.

The verification details may have expired, already been used or may not match the pending record. Request a new message and use the newest link or code within its validity period.

The resend cooldown or rate limit may have been reached. Wait until the relevant window ends or review the limits under 'Settings'.

The client's email address, domain or IP address may be on the blocklist. Review 'Blocklist' and 'Logs', then remove the entry only after confirming the request is legitimate.

Go to 'System Settings' → 'General Settings' → 'Security' and confirm that CAPTCHA has been configured correctly in WHMCS before enabling it in the module.