https://forum.whmcsservices.net/ Thu, 25 Jun 2026 08:05:02 +0000 MyBB https://forum.whmcsservices.net/showthread.php?tid=593 Sat, 06 Jun 2026 00:20:39 +0000 whmcsservices]]> https://forum.whmcsservices.net/showthread.php?tid=593 Version: 1.0.0 Released (20/10/2026)
Stable

New Initial Release]]> Version: 1.0.0 Released (20/10/2026)
Stable

New Initial Release]]> https://forum.whmcsservices.net/showthread.php?tid=592 Sat, 06 Jun 2026 00:20:08 +0000 whmcsservices]]> https://forum.whmcsservices.net/showthread.php?tid=592
1. Back up your WHMCS files and database.
2. Upload the package contents to your WHMCS root.
3. Go to `System Settings > Addon Modules`.
4. Activate `FraudRecord System`.
5. Configure Access Control and `Delete Data on Deactivate` only if needed.
6. Go to `Addons > FraudRecord System > Settings` and enter the FraudRecord API Key.
7. Go to `System Settings > Fraud Protection`, activate `FraudRecord System`, and configure its separate Order Screening API Key and screening settings.

Testing

FraudRecord warns not to use realistic real-person data during tests. Use unrealistic dummy data only.

Suggested test steps:

1. Open `Addons > FraudRecord System > Settings` and save the FraudRecord API Key.
2. Run a manual lookup with dummy data.
3. Activate FraudRecord System under `System Settings > Fraud Protection`.
4. Save the fraud module's separate Order Screening API Key and rejection thresholds.
5. Create a dummy order and run a fraud check.
6. Confirm rejected results appear in `Addons > FraudRecord System > Flagged Orders`.
7. Confirm the client-profile FraudRecord tab can bypass future screening and remove or apply the client-area ordering restriction while the fraud module is active.]]>
1. Back up your WHMCS files and database.
2. Upload the package contents to your WHMCS root.
3. Go to `System Settings > Addon Modules`.
4. Activate `FraudRecord System`.
5. Configure Access Control and `Delete Data on Deactivate` only if needed.
6. Go to `Addons > FraudRecord System > Settings` and enter the FraudRecord API Key.
7. Go to `System Settings > Fraud Protection`, activate `FraudRecord System`, and configure its separate Order Screening API Key and screening settings.

Testing

FraudRecord warns not to use realistic real-person data during tests. Use unrealistic dummy data only.

Suggested test steps:

1. Open `Addons > FraudRecord System > Settings` and save the FraudRecord API Key.
2. Run a manual lookup with dummy data.
3. Activate FraudRecord System under `System Settings > Fraud Protection`.
4. Save the fraud module's separate Order Screening API Key and rejection thresholds.
5. Create a dummy order and run a fraud check.
6. Confirm rejected results appear in `Addons > FraudRecord System > Flagged Orders`.
7. Confirm the client-profile FraudRecord tab can bypass future screening and remove or apply the client-area ordering restriction while the fraud module is active.]]> https://forum.whmcsservices.net/showthread.php?tid=591 Sat, 06 Jun 2026 00:19:19 +0000 whmcsservices]]> https://forum.whmcsservices.net/showthread.php?tid=591
ThemeMetro (Latest Version) Click Here
Impressive Themes (Latest Version) Click Here
SwiftModders (Latest Version) Click Here
ThemeLooks (Latest Version) Click Here
RS Studio (Latest Version) Click Here
AA Layer (Latest Version) Click Here
Lara, WHMCS Admin (Latest Version) Click Here

Other Themes are not fully tested yet, so I am not sure if they work or not. You can contact me first. Click Here

I can not guarantee that MG Multibrand will work with my module.]]>
ThemeMetro (Latest Version) Click Here
Impressive Themes (Latest Version) Click Here
SwiftModders (Latest Version) Click Here
ThemeLooks (Latest Version) Click Here
RS Studio (Latest Version) Click Here
AA Layer (Latest Version) Click Here
Lara, WHMCS Admin (Latest Version) Click Here

Other Themes are not fully tested yet, so I am not sure if they work or not. You can contact me first. Click Here

I can not guarantee that MG Multibrand will work with my module.]]>