Billing
Invoice-and-pay versus automatic charging
Two ways to collect money for hosting, with different cash flow, different disputes and different failure modes. Which one you have is often an accident.
9 min read · Reviewed 2026-09-21
In short
Compare hosting billing systems on what they do when a request fails, not on the feature list. Ask how the system records an outcome it never learned, whether provisioning can run before payment is verified, what leaves an audit line, how credentials are stored, and whether you can get your data back out. Every system demonstrates well; the differences appear on a bad day.
Every hosting billing system has invoices, clients, products and a provisioning module. Comparing those is comparing brochures. The questions below are the ones that separate them, and they are all about failure, recovery and record-keeping — because that is where the cost of the wrong choice shows up.
1. What happens when a provisioning request does not come back?
Ask for a demonstration of a timed-out account creation. The answers fall into three groups. Some systems retry, which risks a second account. Some mark it failed, which risks a paying customer with nothing. The right answer is a third state — we do not know — that stops, holds the account name so nothing else takes it, and asks a person to look.
If the system cannot show you that state, it does not have it, and you will meet the consequence eventually.
2. Can work be provisioned before money is verified?
There is a meaningful gap between "the invoice is marked paid" and "the funds settled". Systems differ on which one unlocks provisioning, and some let you configure it into a state where a failed card still delivers a service. Ask specifically: what is the condition that makes an order executable, and is it a recorded payment or a verified one?
3. What leaves a line in the history, and what does not?
Ask to see the audit trail for: issuing an invoice, applying a credit, suspending an account, changing a price, and refusing something. The last one is the tell. Systems that record only successes cannot answer "who tried to do this", which is the question you will actually be asking.
4. How are provider credentials stored, and who can read them?
You will be handing this system API tokens for your control panel and registrar — credentials that can delete a customer's hosting. Ask where they are stored, whether staff with administrative access can read them back, and what happens when one is rotated. OWASP's secrets management guidance is a reasonable checklist to hold a vendor against. More on the practical side in API credentials: least privilege and rotation.
5. What does the customer see?
The customer portal is the part of your business your customers use themselves. Check it on a phone, check it with a keyboard, and check what it looks like with your branding rather than the vendor's. A portal that fails WCAG 2.2 basics is a portal that excludes some of your customers and, in several jurisdictions, a legal exposure.
6. Can you get your data out?
Ask for an export of invoices, customers and subscriptions in a documented format, and try it during the trial. A system you cannot leave is a system that can raise its price without limit. This is also the question that determines how painful your next migration is — see migrating from WHMCS without losing invoice history.
7. How many people can work in it safely?
Roles matter earlier than people expect. The person who answers tickets does not need to issue refunds; the bookkeeper does not need to suspend hosting. If the only options are "administrator" and "not administrator", you will end up giving everybody administrator.
| Question | A weak answer | A strong answer |
|---|---|---|
| Timed-out provisioning | It retries automatically | It records an unknown outcome and asks a person |
| Provisioning gate | When the invoice is marked paid | When settlement is verified, and the rule is visible |
| Audit of refusals | Only successful actions are logged | Refusals are recorded with who and why |
| Credential storage | Encrypted in the database, readable by admins | Held by a secrets store, never displayed again |
| Data export | Support can produce one on request | Documented, self-service, tested during the trial |
| Roles | Administrator or nothing | Separate commercial and operational authority |
Where GENV sits on this list
Honestly: GENV is built around exactly these answers — an explicit unknown outcome, verified settlement as the provisioning gate, refusals recorded in history, credentials held outside the database, and separate commercial and operational roles. It is also in active development, and no provider integration has yet been certified against a live production installation. If you are choosing a system to run a business on this quarter, that is the fact that matters most, and you should weigh it accordingly.
Questions
Is open source safer for this?
It is more inspectable, which is not the same thing. You can read how an open-source system handles a lost provisioning outcome — which is genuinely valuable — but you still have to read it, and you take on the upgrade work yourself.
How long should a trial be?
Long enough to run one full billing cycle with real data, including a renewal and a failed payment. A two-week trial only ever demonstrates the happy path.
What about price?
Price is rarely the deciding factor at small scale, because the cost of a billing mistake exceeds the licence. Compare on recovery behaviour first and price second.
Sources
Official documentation, each requested on 21 September 2026. Provider behaviour changes; check the source before relying on a detail.