Articles
Billing periods, renewals and the review hold
The path a subscription takes from the order to renewal and from an unpaid invoice to suspension, and what waits while a payment is under review.
About 5 min read · Last updated
In this article
In a hosting panel, billing is the part that raises the most questions. This article goes through the panel's collection steps in order, as the docs describe them.
Subscription and invoice
Every server and every virtual datacenter carries a subscription. A subscription is waiting for its first payment, active, past due, suspended, cancelled or ended. An invoice is a pro forma until it is paid; it gets its legal number when it is paid.
The collection run happens every five minutes, as a single instance. An admin can also trigger it by hand with "Run collection now".
The order
With "Payment before setup" on, the server record and its addresses are reserved, the build waits for payment and the customer is taken to the invoice. If the balance covers it, the invoice is paid at once and the build starts. An order not paid in time is withdrawn, the build is cancelled and the addresses are released.
Renewal
A renewal invoice is issued a set number of days before the period ends (7 by default). With automatic collection on, the amount is taken first from the balance and then from the default saved card, once a day and at most as many times as you have configured.
There is one detail worth knowing here: an unpaid renewal invoice whose period has not yet started follows the server's current price. If the customer enlarges the server or adds a disk after seeing the invoice, the invoice's amount changes too, and it is calculated once more at the moment of payment. That is why the amount a customer saw and the amount they pay can differ. If the amount changes just as staff close an invoice by hand, the request is refused once; look at the new amount and repeat the action.
In multi-month periods (3, 6, 12 months) the difference for a resize is calculated for all the remaining months of the period.
An unpaid renewal
- A reminder goes out before the due date.
- The day after, an overdue notice goes out and the subscription becomes past due.
- After the number of days you have configured, the server is suspended: it is shut down and locked for the customer. The customer can do nothing but shut down and delete, and cannot open the console.
- If you have configured it, the server is deleted later.
Paying lifts the suspension and the server is powered on again.
Hourly usage
For an hourly server the charge is deducted from the balance. When the balance runs out the server is put on hold, and it is powered on again after a top-up; a usage invoice is issued at the end of the month. The customer's Overview page shows when the balance will run out at today's rate.
The review hold
Some payments do not settle by themselves:
- Param payments. With Param, the return cannot be verified by asking the provider, so it does not count as proof of payment; the payment stays "awaiting confirmation".
- Payments whose amount does not match the invoice.
- Payments the provider has put under review.
Such a payment appears under Administration → Billing → Payments with the "Awaiting review" filter, a counter appears next to the Billing entry in the menu, and staff with the billing.manage permission are notified. The decision is made by hand:
- If the money has arrived, you close the invoice with "Record a payment"; the invoice's payments awaiting review are closed in the same step.
- If it has not, you close the payment's review with "Close review", and nothing counts as paid.
While the review is open the panel does not punish the customer: from the moment the review began, for at most reviewHoldDays days (Settings → Billing; 7 by default), reminders, suspension, deletion and order cancellation wait for that invoice. The customer cannot pay the same invoice a second time, and the invoice page keeps the payment buttons closed until then. Automatic collection does not charge that invoice either, because the provider may be holding the customer's money.
The shutdown applied to an hourly server whose balance has gone negative is outside this hold.
You can try the flow with the panel's test provider (Sandbox) and the card number 4000 0000 0000 4954, which keeps the payment under review.
A closed tab on Stripe, iyzico and Craftgate
There is no webhook that receives notifications from Stripe. If the customer pays and closes the tab before returning to the panel, the payment is not processed at once; five minutes after the payment was started, the collection run begins asking the provider again and processes the result. A payment not completed within a day is closed as "expired". The same asking-again exists for iyzico and Craftgate; it does not exist for PayTR and Param.
After a restore
While the panel is on hold after a restore, collection does not run at all: no invoice is issued, no card is charged, no reminder goes out and no suspension is applied.
What has not been tried
None of the five payment providers was tried with a real merchant account, and the Param flow was not confirmed with the provider. The README also says that for most of the latest major changes in billing behaviour no integration test was written. Before going live, make one payment and one refund with each provider in test mode.
Sources: docs/billing.md, docs/payments.md (Turkish).
