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
A renewal is a sequence: notify, attempt payment, allow a grace period during which the service still works, suspend, then delete. Write down the number of days at each step, make them the same for every customer, and tell the customer the dates in advance. A step that happens sooner than the customer expected is an avoidable way to lose them.
Renewal is where a hosting business can quietly lose a customer who never meant to leave — because a service stopped working on a day they did not expect, or because the first they heard of a renewal was a charge on a card.
The five steps, and what each is for
| Step | Example timing | What it is for |
|---|---|---|
| Notice | 14–30 days before | The customer can budget, cancel or update a card without drama |
| Charge or invoice | On the renewal date | The commercial event |
| Grace period | 7–14 days after | Expired cards and holidays. The service keeps working |
| Suspension | End of grace | Reversible pressure. Data intact, service off |
| Deletion | 14–30 days after suspension | Irreversible. Needs its own notice |
The exact numbers matter less than that they exist, are the same for everybody, and are written where a customer can read them before they need to.
Suspension is not deletion, and the gap is the product
Suspension should be instantly reversible and obviously reversible. A customer who pays at 23:00 should be back online at 23:01 without a support ticket. If reinstating requires manual work, you have built a system that punishes late payers with downtime you then have to apologise for.
Deletion needs its own notice, its own delay and its own deliberate act. A pipeline where non-payment leads automatically to data destruction will eventually destroy the data of somebody whose card simply expired.
Domains renew on somebody else's clock
If you also sell domains, do not fold them into the hosting renewal timeline. A domain has registry-level deadlines you do not control, and the consequences of missing them are far worse than a suspended website. ICANN's Expired Registration Recovery Policy sets out the notices a registrar must send and the recovery period after expiry for gTLDs — and a name restored from redemption carries a separate restore fee, which the policy requires registrars to publish. Treat domain renewals as their own process with earlier notices; see domain renewal failures and reconciliation.
What to do when a charge fails
- Retry on a published schedule — not immediately, and not forever. Three attempts over ten days is one example; whatever you choose, publish it.
- Tell the customer after the first failure, with a way to fix it that does not require signing in to something they have forgotten the password to.
- Keep the service running through the grace period. The cost of a few days of hosting is far less than the cost of winning the customer back.
- Suspend only when the published grace period ends, and say in the suspension notice exactly what happens next and when.
The record-keeping that saves you later
Every notice sent, every charge attempted, every suspension and every reinstatement should leave a line with a timestamp. When a customer says "you never told me", the answer should be a date, not a memory. This is also the evidence you need if a payment is disputed with a card issuer.
Where GENV is
GENV models the due-renewal queue and raises renewal drafts, with the restriction states — non-payment, abuse and administrative holds — kept independent of each other so that lifting one does not silently lift another. Charging is not connected: no real payment gateway is wired into the current build, so the collection half of this timeline is something you would still do elsewhere today.
Questions
How long should a grace period be?
Long enough to survive a holiday weekend and a replaced card. There is no standard figure — ten to fourteen days is one example of a period that leaves room for both. Whatever you choose, publish it and apply it to everybody.
Should suspension be automatic?
Automatic is fine as long as the timing is published and the reinstatement is instant. What should never be automatic is deletion.
Do I need to notify before every charge?
It depends on the payment method, the rules of the scheme you collect through, the consumer law where your customers are, and your own terms. Some require advance notice for some recurring charges and some do not, so check the ones that apply to you. It is worth doing even where nothing requires it: a notice before the charge lets the customer object before the money moves.
Sources
Official documentation, each requested on 21 September 2026. Provider behaviour changes; check the source before relying on a detail.