The Product Fraud Override Addon module requires a precise combination of system components, PHP versions, and extensions to operate without errors. Our developers have tested it exclusively under the conditions detailed below; these are mandatory. Failure to satisfy any requirement can produce fatal PHP errors, module loading failures, blank admin pages, or broken fraud override logic during order processing.

The module is delivered ionCube-encoded, depends on secure outbound connections, and uses modern PHP constructs. A working knowledge of WHMCS is therefore a prerequisite: administrators must be comfortable uploading files to the modules directory, activating the addon via the configuration interface, setting up hooks if needed, and troubleshooting gateway or order-flow integrations.

#System Requirements

  • Working knowledge of WHMCS, installing and configuring addons, gateways etc.
  • PHP 5.4 or higher for WHMCS 6.x
  • PHP 5.6 or higher for WHMCS 7.x
  • WHMCS 6.x or 7.x
  • OpenSSL w/ TLS 1.1+ support

#PHP Extension Requirements

  • cURL w/ TLS 1.1+ support
  • Ioncube Loader v5.0.21 or higher for WHMCS 6.x
  • Ioncube Loader v6.0.2 or higher for WHMCS 7.x

#Using the Requirements Test Script

We supply a compact PHP diagnostic script that inspects your live environment and flags every unmet requirement in a single report. It verifies the PHP version in use, confirms that the correct Ioncube Loader is resident and capable of decoding protected files, checks OpenSSL and cURL TLS protocol support, and cross-references your WHMCS version. Download the script directly from https://billing.aspnix.com/dl.php?type=d&id=138.

Upload the file to the root of your WHMCS installation, then call it from a browser. The output lists each checked item with a clear pass/fail status. Run the script after any PHP or extension upgrades to confirm compatibility before deploying the addon. This prevents the common scenario of uploading an encoded module only to discover that the loader version is insufficient.

#Common Pitfalls and Troubleshooting

The most frequent causes of failure are an Ioncube Loader older than the required build, PHP compiled without cURL TLS 1.1+ support, or OpenSSL libraries that do not offer the mandated protocol versions. These typically surface as "ionCube Loader not found" fatal errors, cURL SSL connect failures, or silent module deactivation. Always confirm that the extension is enabled for the exact PHP handler serving your WHMCS admin area; multiple PHP versions on one server can produce misleading phpinfo() results.

ini 
extension=ioncube_loader.so

; Required for outbound secure connections
extension=curl.so

Review your PHP error log immediately after any failed activation. If the test script passes but the module still fails to load, verify that the WHMCS cron and admin area execute under the same PHP binary. Once all checks are green, install the addon following standard WHMCS procedure: extract to the modules/addons directory, activate it in the addon manager, and test a sample product order flow.

Meeting these requirements before deployment eliminates the majority of support cases related to white screens or partial functionality. With a validated environment you can focus on configuring the fraud override rules rather than chasing compatibility problems.