WHMCS
46 posts tagged with this.
-
Requirements for the Product Fraud Override Addon Module
Confirm your WHMCS installation meets the requirements for the Product Fraud Override Addon module. Tested on WHMCS 6.x/7.x with specific PHP versions, OpenSSL TLS 1.1+, cURL, and Ioncube Loader. Use the provided test script to validate your setup.
-
What are the Licensing Terms for the Product Fraud Override Addon Module?
The Product Fraud Override Addon is licensed as a one-time purchase with no monthly or annual fees. The license binds to a single WHMCS installation; changes to IP address, installation path, or domain require re-issuance for reactivation. This article details all terms, explains when re-issuance is
-
How to Display the Public Pay Module Link to Clients
As of build 2.0.1 the Public Pay module automatically adds its link to the WHMCS Shortcuts menu above Logout for native WHMCS 6 templates. This guide details the automatic behavior, manual template edits using clientareahome.tpl, the logged-in group pay link, and the unique public hash URL format fo
-
How to Display the Pushover Module Link to Clients
Add the line 'Pushover Push Notifications' to WHMCS templates such as clientareahome.tpl or clientareadetailslinks.tpl to expose the module link in the client area. This guide covers prerequisites, exact editing steps, testing, and troubleshooting so the link functions once the module is activated a
-
How Are Public Pay Payments Added to Client WHMCS Accounts
No invoices are generated with the Public Pay module. Validated payments are added directly to the client's WHMCS credit balance. This guide details the processing flow, validation steps, credit management best practices, common pitfalls, and how the system handles these invoice-free transactions.
-
Public Pay Addon Module System Requirements
Learn the tested requirements for the Public Pay Addon module in WHMCS including PHP 5.6+, Ioncube v10.1, BCMath or GMP, cURL with TLS 1.1+, and configured PayPal gateway. Download our requirements test script to validate your server setup and ensure smooth operation of the payment addon.
-
Choosing the GeoIP Lookup Method for WHMCS Order Blocking Addon
We recommend MaxMind for the GeoIP Order Blocking Addon in WHMCS as it needs no extra PHP extensions. Compare the Native, MaxMind, and GeoPlugin lookup methods, their requirements, performance impacts, and maintenance needs. This guide helps you select and configure the best option to reliably block
-
Licensing Terms for GeoIP Order Blocking WHMCS Addon
GeoIP Order Blocking for WHMCS is licensed as a one-time purchase with no monthly or annual fees. The license is valid for exactly one WHMCS installation. Changes to IP address, installation path, or domain name require a license re-issue to reactivate the module. Contact sales for re-issuance or an
-
GeoIP Order Blocking Addon Module Requirements
Verify your WHMCS server meets these requirements for the GeoIP Order Blocking addon: PHP 5.6+, WHMCS 7.x, Ioncube 10.1+, OpenSSL with TLS 1.1+, and cURL. Includes optional geoip extension, lookup plugin dependencies, and a free test script to validate your environment before installation.
-
Supported WHMCS Events for Customer Push Notifications
WHMCS supports push notifications for customers on specific events using its hook system. This guide details every supported billing, support ticket, and service event with explanations. Customers can enable or disable each one individually, ensuring relevant real-time alerts for invoices, ticket re
-
What are the licensing terms for the Pushover Addon for WHMCS?
The Pushover Addon for WHMCS is licensed as a one-time purchase with no monthly or annual fees and is valid for exactly one WHMCS installation. Changes to IP address, installation path, or domain name require a license re-issue for activation. This guide details the full terms, what triggers re-issu
-
Requirements for the Pushover WHMCS Addon Module
Detailed breakdown of all tested requirements for the Pushover WHMCS Addon module including PHP 5.6+, WHMCS 7.x, IonCube v10.1+, cURL with TLS 1.1+, OpenSSL, and Pushover account setup with API key. Use the provided test script to validate your environment and avoid common compatibility failures wit
-
Coinbase Payment Gateway Module Changelog
Complete release history for the Coinbase Payment Gateway Module from initial 1.1.0 launch in 2014 to version 3.0.6. Documents all API rewrites for Coinbase Commerce, WHMCS compatibility updates, callback fixes, UI improvements, and dependency resolutions critical for reliable cryptocurrency transac
-
API Requirements for the Coinbase Payment Gateway Module
To accept crypto payments with the Coinbase module in WHMCS you must supply an API Key and Shared Secret, whitelist your WHMCS domain, and configure a webhook endpoint at /modules/gateways/callback/coinbase.php. This guide details every required setting, the exact steps inside Coinbase Commerce, sup
-
Coinbase Payment Gateway Requirements for WHMCS
The Coinbase Payment Gateway module for WHMCS requires PHP 5.6+, WHMCS 7.x, OpenSSL with TLS 1.1+, IonCube 10.1+, and extensions cURL, Hash, and OpenSSL. This guide lists all tested requirements, explains why each matters for stable API integration, and includes our free test script to validate your