Skip to content

Knowledgebase

Choosing and activating a WHMCS licence

whmcs, resellers

A WHMCS licence authorises use of the billing software under its licence terms. It is separate from the hosting environment, payment gateway accounts and any commercial add-on licences. Confirm the licence source and deployment requirements before installing a production client portal.

01 Choose the appropriate entitlement

  1. Check whether your Nabtech package includes an eligible WHMCS licence or whether a separate order is required. Do not assume every reseller account includes one.
  2. Review the licence's permitted installation, active-client allowance, branding and update entitlement as shown by the authorised seller.
  3. Confirm the intended production domain and hosting location. Some reseller or bundled licences have restrictions on where the software can run.
  4. Choose a supported stable WHMCS release and verify that the hosting environment supports its PHP, ionCube, database and extension requirements.
  5. Order through the current authorised channel and complete the invoice. Obtain the licence key and download instructions through the private account or delivery process.

02 Activate and verify

Use the key during the supported installation process. After setup, open the administration area and confirm the licence is recognised. Keep the software's licence details available to the account owner, but do not publish the key in a support ticket that other customers can see.

03 Example: prepare a licence request before ordering

Before buying, send the authorised licence seller a short deployment record: the intended production address, approximate active-client count, whether the licence comes with hosting, and whether a separate test installation is required. For example, a reseller moving an existing billing portal should ask whether the bundled entitlement permits that destination before scheduling the move.

Record the answers beside the installation plan, including the supported release and any reissue step. Confirm the actual branding and update entitlement rather than inferring them from a package name.

Expected result: the licence and hosting environment fit the planned deployment before a production installation is moved or duplicated.

What if the domain or server changes?

A licence can be tied to deployment details. Before moving the installation, review the seller's reissue process and any bundled hosting restrictions. Preserve a full application and database backup and avoid using one production key for an additional installation without permission.

04 When licence validation fails

Check the exact error, invoice status, intended installation address and recent server changes. Ask the licence provider to review the entitlement rather than purchasing another key immediately. Never use a modified or unofficial copy to bypass licence checks.

The newest announced release is not automatically the appropriate production release. Beta versions are intended for testing; review release status and the compatibility of payment, registrar and provisioning modules before selecting a version.

Was this answer helpful?

Need a little more help?

Our support team can help you find the next step.

Contact support

Powered by WHMCompleteSolution