Enscale - WHMCS Module - Provisioning & service lifecycle
On this page
Once products are set up, selling is hands-off: your customers order in your WHMCS exactly as normal, and the module provisions with Brixly and bills your credit behind the scenes.
The lifecycle
When you… | What the module does |
|---|---|
Accept/activate an order | Creates the service with us, stores its provider id, and charges your credit (setup + first period). |
Suspend a service | Suspends it with us. |
Unsuspend | Reactivates it with us. |
Terminate | Ends it with us and stops future renewal charges. |
(Automatic) renewal | We charge the recurring price from your credit a few days before each due date. |
These all happen through the normal WHMCS actions and automation in your WHMCS — there's nothing separate to drive.
Your WHMCS is the system of record. When you suspend/terminate there, the module mirrors it to us. If a customer cancels, terminate the service so renewals stop being charged to your credit.
Resilience
If a service can't be created (e.g. a transient error), your credit charge is automatically refunded and the order is marked failed.
If a suspend/terminate momentarily can't reach us, the module retries it automatically (daily) until it's confirmed — so your side and ours don't drift.
What's not charged to your customer by us
We only ever bill you (wholesale, from credit). Your customer's invoices, taxes and payments are entirely handled by your own WHMCS at your retail prices.
Test the full loop early: place a real order in your WHMCS for one product, confirm it appears under Orders in the portal and the service works, then roll out the rest.
Was this article helpful?