The G2A Pay Gateway module is licensed as a one-time purchase. However there is an annual maintenance fee to receive continued upgrades and new build releases. The license is valid for use on one WHMCS installation only. These terms exist to balance customer access with protection of the module's codebase and to fund ongoing development. If you move your WHMCS installation to a new IP address, change the path of the WHMCS installation or change the domain name that your WHMCS installation is running under your license will need to be re-issued so that it may activate under the new location.

This structure is typical for WHMCS payment gateway modules. It prevents casual copying across unrelated installations while allowing legitimate users to run the module indefinitely after the initial purchase. The annual maintenance fee keeps your module current with WHMCS core updates, PHP version changes, and refinements to the G2A integration. Ignoring the relocation rules is one of the most common reasons administrators see license activation failures after server moves or rebranding projects.

#Licensing Model and Maintenance Requirements

Purchase of the module grants perpetual use of the version obtained at the time of acquisition. The separate annual maintenance fee is mandatory only if you want continued upgrades and new build releases. Without an active maintenance subscription the module will continue to function at the last downloaded version, but you will not receive bug fixes, compatibility patches, or feature enhancements released afterward. Renewing maintenance each year is the recommended practice for production environments where payment reliability and security are critical.

Maintenance payments also ensure that the module stays aligned with evolving G2A API requirements and WHMCS system changes. Most administrators factor this recurring cost into their annual budgeting because the expense is significantly lower than rebuilding or replacing a payment integration from scratch.

#Single Installation Restriction

The license explicitly permits activation on only one WHMCS installation. This restriction is enforced at the license validation layer using a combination of server variables. Running the module on additional WHMCS instances without purchasing extra licenses violates the terms and typically results in activation errors on all but the first system where the license was used.

  • License tied to a single WHMCS filesystem and database
  • Cannot be shared between separate client billing systems
  • Development or staging copies require their own separate license if run in parallel with production

#License Re-Issuance After Environment Changes

WHMCS installations are often relocated during hardware upgrades, hosting provider changes, or domain migrations. The licensing system requires an updated key when any of the following occur: the server IP address changes, the WHMCS installation directory path is modified, or the primary domain under which WHMCS runs is altered. In each case the existing license must be re-issued before the module will activate at the new location.

  • Server migration that results in a different IP address
  • Change to the physical or URL path of the WHMCS root directory
  • Domain name update or switch to a new primary hostname

To obtain the re-issued license, contact the sales team with details of both the previous and the new environment. Supply the original order information or license key along with the updated IP, path, and domain. The team will invalidate the old activation record and generate a new key compatible with the revised setup. Perform this step before attempting to activate the module at the destination to avoid unnecessary troubleshooting.

#Common Pitfalls and Best Practices

The most frequent issue occurs when administrators move WHMCS without first requesting a license re-issue, then spend hours debugging connection or activation errors that are actually licensing related. Another pitfall is allowing maintenance to lapse on a production system and later discovering that a critical security patch or WHMCS compatibility update has been missed. Track your maintenance renewal date and schedule the re-issue request ahead of any planned server or domain changes.

If you operate both production and development environments, purchase a second license for the development system or use a license management approach that clearly separates the two. Always keep a record of your license key and order reference so re-issuance requests can be processed quickly.

#Contacting Sales for Licensing Questions

If you have any questions about the licensing of this product, please contact our sales team. They can provide clarification on renewal pricing, multi-license arrangements, or specific scenarios involving load balancers and clustered environments. Direct communication is the fastest way to resolve license-related issues and ensure your G2A Pay integration remains operational.

Review your current license status and schedule maintenance renewals before they expire. For step-by-step instructions on initial module installation and configuration after licensing is confirmed, see the related guide on setting up the G2A Pay Gateway in WHMCS.