Flaem for WHMCS: WHMCS handles the money, Flaem runs the servers
If your clients pay in WHMCS and that is how it should stay, you do not have to switch it off. You add the Flaem module to WHMCS like any server module: a paid order creates a game server, VPS or website in Flaem, and the client runs it in the Flaem panel, which they reach from WHMCS in one click.
- Client details and orders
- Invoices and payments
- The billing term
- Dunning and suspension for non-payment
- A game server, VPS, LXC container or website
- Client panel with console, files and backups
- Nodes, capacity and monitoring
- Provisioning, plan changes and teardown
A WHMCS service inside Flaem: what Flaem does and what it leaves alone
A service created through the module is marked in Flaem as billed by WHMCS. It runs on the same nodes, with the same backups, limits and panel as a service bought in the Flaem store. The money stays entirely on the WHMCS side.
The same as a service from the Flaem store
- The same nodes and the same placement scheduler
- Capacity and hardware tier checks before it is created
- The same provisioning commands and the same teardown order
- Every action in the operator panel's audit log
What Flaem never does for it
- No invoices, not even zero-value ones, and no line in the client's invoice list
- No renewal reminders and no suspension for non-payment
- No wallet debits, including on a plan change
- No renewal date or renew button, only who bills the service
If the client does not pay, WHMCS suspends the service and the module tells Flaem. Flaem will never suspend it on its own or against WHMCS.
WHMCS actions and what they do in Flaem
The module handles the actions WHMCS runs on a service from the admin area, the module queue and the daily cron. Each one reaches the Flaem billing bridge API and each ends with a clear answer in WHMCS.
- CreateLinks the WHMCS client to a Flaem account, opening that account from their email address on the first order. Then it creates the service on a node.POST /services
- SuspendStops the service with the reason "non-payment" and the note from WHMCS. The data stays untouched.POST /services/{id}/suspend
- UnsuspendResumes the service after payment.POST /services/{id}/unsuspend
- TerminateTears the service down and opens a data retrieval window for the client before anything is deleted.POST /services/{id}/terminate
- Change PackageMoves the service to the new plan with the options chosen in WHMCS.POST /services/{id}/package
- Log in to panelMints a one-time sign-in link at the moment of the click, for the client and for the admin.POST /services/{id}/sso
- Client areaShows the service's state, plan and usage, read live from Flaem.GET /services/{id}
- Usage UpdateWrites disk and transfer usage back to WHMCS. When Flaem has no sample, the service is skipped rather than zeroed.GET /services/{id}/usage
A refusal reaches WHMCS whole
When Flaem cannot do something, WHMCS gets the refusal code, a sentence explaining it and the list of what is missing: in the module log, in the admin error banner and in the module queue. The bridge key is cut down to its public prefix in the log.
Services kept in sync both ways
WHMCS sends commands and Flaem answers with the service's state. When an operator suspends or cancels a service in the Flaem panel, a signed callback changes it in WHMCS too, so both systems show the same thing.
From WHMCS to Flaem
- Commands: create, suspend, unsuspend, terminate and change plan
- State, plan and usage read live in the client area
- The daily WHMCS cron writes disk and transfer usage
From Flaem to WHMCS
- Callbacks for suspensions, unsuspensions and cancellations in the Flaem panel
- Each one signed with a secret and sent only to an https address
- The secret stored encrypted in the WHMCS server record
Six service states the module understands
- provisioningAccepted, the node is building it
- activeRunning
- suspendedStopped, data intact, reversible
- terminatingOn its way out
- terminatedGone
A retry after a timeout never builds a second machine
Every command that changes a service carries an idempotency key derived from the WHMCS service id and the action, never from the attempt. When the WHMCS queue retries an action after a timeout, Flaem replays the first answer instead of creating a second machine.
A bridge key gets 600 requests a minute by default, so the nightly WHMCS cron gets through every service. Every call shows up in the panel's API usage log under the key's prefix.

A product with options in WHMCS, a fixed plan in Flaem
WHMCS sells a product with configurable options, Flaem sells fixed plans. You map the whole combination of options, not each option on its own: 4, 8 or 16 GB of memory in two locations is six plans and six rows in the bridge catalogue.
An 8 GB plan in Frankfurt is a different plan from 8 GB in Warsaw: different hardware, sometimes a different disk. That is why the bridge never composes an answer from single options.
Option names and values are normalised before the lookup, so case, spaces and option order do not matter.
An unmapped combination is refused, not guessed
The bridge never picks the nearest plan, because that would mean a machine the client did not buy. The refusal says exactly which row is missing.
- Refusal code
- option_not_mapped
- What WHMCS sent
- location=fra;ram=8192
- What the product has mapped
- location=fra;ram=4096, location=waw;ram=8192
You add the missing row in the catalogue and run the action again from the module queue. A retry after a refusal is a fresh request, not a replay of the refusal.
Signing in to the Flaem panel straight from WHMCS
The log in button in the WHMCS client area mints a one-time link at the moment of the click. The client lands in the Flaem panel without a separate password, and the admin gets in the same way from the service tab.
- 0 s
Click in WHMCS
The module asks Flaem for a link for this client and this service.
Link in the address bar
It works once. Flaem stores only its hash.
Flaem panel
The client is signed in. If they use two-factor sign-in, the panel asks for the second factor.
- 120 s
The link expires
After 2 minutes or after its first use. Unknown, expired and spent links all get the same refusal.
- The Flaem account is opened on the first order, from the client's email address and without a password.
- The client can set a password later in their account settings as a second way in.
- Every use of a link is logged with the address it was used from.
- The bridge lets a link live up to 15 minutes, for example for messages sent from an email queue.

Installing the module in eight steps
The module is one zip file, released with every Flaem version together with a checksum. It needs no Composer and no extra libraries, because it uses only what WHMCS already ships.
Requirements
- WHMCS 8 on PHP 7.4 or newer, with the cURL extension
- A Flaem panel reachable from the WHMCS server over HTTPS
- A Flaem administrator account allowed to manage billing
- 1
Download and check the file
You download the archive and its checksum file, then compare them with one command.
sha256sum -c flaem-whmcs-1.0.0.zip.sha256 - 2
Unpack it into the WHMCS root
The archive already holds modules/servers/flaem, so nothing needs moving.
unzip flaem-whmcs-1.0.0.zip -d /var/www/whmcs - 3
Mint a bridge credential
In the Flaem panel: Billing bridge, Credentials tab, billing system whmcs. The key is shown once and works only on the bridge.
- 4
Map your products
On the Catalogue tab you assign every option combination of a WHMCS product to a Flaem plan.
- 5
Add the server in WHMCS
The Flaem module, the panel address and the bridge key in the password field. Test Connection checks the key, the permission, the panel database and the bridge contract version.
- 6
Configure the products
You pick the Flaem plan, how options are sent and the service name the client sees. Leave immediate termination off: the client then gets the data retrieval window required by Article 25(2) of Regulation (EU) 2023/2854.
- 7
Register the callback
One command per WHMCS server. The signing secret is stored encrypted in the server record.
php modules/servers/flaem/tools/callback-register.php https://<whmcs-address> - 8
Usage takes care of itself
The daily WHMCS cron writes disk and transfer usage. The module log shows which services were measured, which were skipped and why.
Upgrading means unpacking the new archive over the old one. The module's tables stay untouched and nothing else needs to run.
The way to full Flaem, one service at a time
The module does not close the door on moving over completely. A running hosting business moves in stages: the panel first, then clients and billing, without one weekend in which everything changes at once.
- 1
Module
New WHMCS orders create services in Flaem. Clients pay as before and manage their services in the Flaem panel.
- 2
Handing over existing services
Services Flaem already runs, for example after a Pterodactyl import, you hand over to WHMCS one by one. The machine stays where it is, and WHMCS takes over the term, invoices and dunning.
- 3
Import from WHMCS
Clients with their profile and wallet balance, renewal dates and amounts and invoices as an archive move into Flaem. A dry run with a report comes first, and WHMCS is only read in the meantime.
- 4
Billing in Flaem
You take each service back onto Flaem billing with one button and enrol it in a billing cycle. From then on Flaem invoices it, with KSeF delivery.
You remove the module after moving the products off the Flaem server group. Machines keep running, and the mappings stay in the panel until you take the services back or unlink them.
The same bridge for Blesta, HostBill and Paymenter
The modules for the other systems use the same bridge API and the same set of actions: create, suspend, unsuspend, terminate and change plan. They differ in where you install them.
BlestaA server module and the flaem_bridge plugin for callbacks.components/modules/flaem
HostBillA HostBill hosting module.includes/modules/Hosting/flaem
PaymenterA Paymenter server extension.extensions/Servers/Flaem
Questions about the Flaem module for WHMCS
Installing, invoices, client sign-in and what happens when you remove the module.
No. It is one zip file from a direct link, released with every Flaem version together with a .sha256 checksum file.
No. For a service created through the module Flaem issues no invoice at all, not even a zero-value one, and never debits the client's wallet. Only WHMCS invoices it.
WHMCS. The module passes the suspension to Flaem with the reason "non-payment". Flaem never suspends such a service on its own.
No. They get in from WHMCS with a one-time link. They can set a password later in their account settings as a second way in, and the link does not skip two-factor sign-in if they turned it on.
Flaem replays the first answer. The idempotency key comes from the WHMCS service id and the action, so a retry never creates a second machine.
Yes. WHMCS services and services bought in the Flaem store run side by side on the same nodes. Each is billed by the system it was bought in.
They keep running. The mappings stay in the Flaem panel, and you take the services onto Flaem billing or unlink them on the billing bridge screen.
A bridge key gets 600 requests a minute by default, more than a regular API key, so the nightly WHMCS cron gets through every service. You can raise the limit for that one key in the panel.
Read next
- A WHMCS alternative: billing and the panel in one system
- Hosting billing compared: WHMCS, Blesta, HostBill and Paymenter
- Flaem integrations: gateways, KSeF and bridge modules
- API, webhooks and the billing bridge for developers
- Migrating from WHMCS, Pterodactyl and VPS panels
- The game server panel your clients get from WHMCS
- Proxmox VPS panel
- Flaem licence pricing
We will connect Flaem to your WHMCS
Tell us which products you sell in WHMCS and on how many nodes. In the demo we will show the module, help you map the catalogue and work out the licence from the price list.