Connect the billing installation
The WHMCS module identifies the hosting company, products and services it is authorized to manage.
The telaForge distribution direction brings a website CMS experience to hosting services. WHMCS is the first billing integration target, with cPanel and DirectAdmin server and reseller scopes in view.
The hosting company keeps its billing and service relationship. telaForge gives the customer a connected CMS, a plan-aware starting point and a clear route to build and maintain a website.
The hosting-company module is a separate implementation stage. This page explains the intended onboarding and service model; it is not a released module download or a promise that every reseller privilege is available.
The WHMCS module identifies the hosting company, products and services it is authorized to manage.
Use a verified panel connection with the credentials and privileges actually delegated to it. Full-server access and a reseller account are different scopes.
Choose the eligible packages and destinations. Capacity and capability checks should happen before a service can be offered or provisioned.
Creation, suspension, resumption, package changes and termination need durable operation records and reconciliation when a native call has an uncertain result.
Support should follow the native panel capabilities and token privileges. Creating hosting under an existing reseller is different from creating a new reseller account.
Discuss your environmentServer and reseller connection modes must be checked independently against the permissions and account scope supplied by the hosting company.
Talk about your scopeKeep the module, CMS and connector releases versioned and reviewable. Software entitlement and a hosting account’s data lifecycle remain separate responsibilities.
Read the distribution approachTell the hosting team about your WHMCS installation, panel and account scope so the programme can be designed around real capabilities.