Kontrol7

Kontrol7 deliberately has no billing of its own. It exposes an orders API and stores no price beyond a display price.

The division

Owns	What
Kontrol7	What a product is: the plan, what it grants, its allowances, where it may be placed, its size
Your billing	How it is sold: price, cycles, page, checkout, invoice, reminders and suspension

With Zephyr, a product binds to one Kontrol7 plan. One price everywhere — the customer picks a location at checkout, and there is no per-location price. Zephyr connects to Kontrol7 with the panel's address and an API key.

What happens on a paid invoice

1. Zephyr marks the invoice paid.
2. It places the order with Kontrol7, naming the plan the customer bought and the location they chose.
3. Kontrol7 creates the account (a reseller account for reseller hosting), the subscription, and the first thing the plan sells: a website, database, DNS zone, mail domain, virtual machine or bucket.
4. The server it is placed on sets it up.

Nobody retypes anything. An order for a plan that is not sold in that location right now is refused before anything is created, and an order sent again after a timeout creates nothing twice.

When a payment is missed, and after

• Invoice overdue. Zephyr suspends the account. Everything under it stops serving, a virtual machine is stopped, and nothing new can be created. Nothing is deleted.
• Invoice paid. Zephyr lifts the suspension. Only what the suspension stopped comes back; anything suspended separately, for example for abuse, stays suspended.
• Cancelled. Zephyr ends the subscription and suspends the account. The account keeps everything for a grace period (30 days unless you change it in Settings; 0 never removes anything) and is told the date once. Paying again, or lifting the suspension, before then calls it off. A virtual server sold through Zephyr is removed at cancellation.
• Grace period over. Every service with backups is backed up one last time, and nothing is removed until that backup exists. Then the account's services are removed and go to Recently deleted. Backups are not touched. A reseller's customers are judged on their own.

What Kontrol7 answers, and your billing must not guess

• whether a service is up, and where it runs
• each website, zone, mailbox or database, and its state

What your billing answers, and Kontrol7 must not guess

• whether a customer exists, is billable, or is suspended for non-payment

Using something else

You can. The orders API is public and documented, and everything the panel does can be done through it. Monthly usage per account is exported as CSV or JSON for invoicing. Zephyr is simply the path that needs no integration work.