Skip to content
Lightning VMBeta

Features

Billing and payments

Subscriptions, invoices, renewals and the collection steps, hourly usage, payment providers, payments awaiting review and Turkish e-invoicing, with what was and was not tried.

The model

Every server and every virtual datacenter gets a subscription. Until it is paid, an invoice is "Awaiting payment" and is a pro forma without a legal number; once paid it receives its number and, if an e-invoice integrator is selected, is sent there. A balance top-up is not a sale: it has no invoice of its own and carries no VAT. Of a saved card, only the provider's token (encrypted) and the last four digits are kept.

A payment is confirmed by asking the provider from the server side or by checking its signature; a forged notification, or one that belongs to another payment, changes nothing.

Order, renewal and an unpaid invoice

  1. Order: with "Payment before setup" on, the server record and its addresses are reserved and the build waits for payment. If the balance covers it, it is paid at once. An order not paid in time is withdrawn and its addresses are released.
  2. Renewal: an 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, then from the default saved card, once a day and for the configured number of attempts.
  3. Unpaid renewal: a reminder before the due date, an overdue notice the day after, suspension after the configured number of days (the server is shut down and locked for the customer) and, if configured, deletion later. Paying lifts the suspension and the server is powered on again.
  4. Cancellation: the customer chooses "cancel at period end"; the server runs until the period ends and is then deleted.
  5. Refund: to the card or to the balance, in part if need be.

The collection run happens every five minutes. An unpaid renewal invoice whose period has not started follows the server's current price: if the size or the disks change, so does the amount, which means the amount a customer saw and the amount they pay can differ.

These steps, in detail and with examples: Billing periods, renewals and the review hold.

Hourly usage, budget and coupons

  • Hourly: if hourly sales and the balance are switched on in the billing settings and you gave the package an hourly price, a customer can order the server by the hour. 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.
  • Monthly budget: the customer sets an amount. The order page warns beforehand about an order that would exceed the budget, and a notification goes out once a month when the total passes it. The budget stops nothing.
  • Upcoming charges: the customer's Overview page shows invoices that are overdue or due within 7 days, the next renewal, and for hourly usage when the balance will run out.
  • There are also coupons and dispute handling.

Payment providers

Card payments are collected through five providers only (and the panel's own test provider):

ProviderPaymentRenewal with a saved cardNote
iyzicoCheckout Form (3D)Yes (if the account may charge without 3D)The result is verified by asking iyzico
PayTRiFrame (3D)NoThe notification address is entered in the PayTR panel
CraftgateCommon Payment Form (3D)Yes (needs a non-3D POS)
StripeCheckout (3D)YesNo webhook; does not accept companies established in Turkey
ParamCommon Payment Page (3D)NoTRY only; the payment is not processed by itself, staff close it by hand

For the other 41 providers under Settings → Payment (bank virtual POS systems, other payment institutions, Papara, PayPal, Mollie, Adyen and the like) only the account details are stored, and most are tested with a query that moves no money. No payment can be taken through them.

Payments awaiting review

Param payments awaiting confirmation, payments whose amount does not match, and payments the provider has put under review do not close by themselves. They are listed under Administration → Billing → Payments with the "Awaiting review" filter, and staff are notified. If the money has arrived, staff close the invoice with "Record a payment"; if it has not, they close the review with "Close review", and nothing counts as paid.

While a review is open, for at most reviewHoldDays days (Settings → Billing; 7 by default, 0 switches it off), suspension, deletion, order cancellation and reminders wait for that invoice, and the customer cannot pay the same invoice a second time. If the review is still open when the period ends, the invoice goes back into collection; if the decision takes that long, the customer's server can be suspended.

Turkish e-invoicing (e-Fatura and e-Arşiv)

If the buyer is registered for e-Fatura, an e-Fatura is sent; otherwise an e-Arşiv invoice goes out by e-mail (UBL-TR 1.2). The integrators are İzibiz, Uyumsoft, Nilvera, EDM, QNB eFinans, BirFatura and Paraşüt. An invoice that cannot be sent is retried at growing intervals, 8 times at most.

The docs also ask you to confirm a few matters with your accountant: invoices without VAT to customers abroad (off by default), the placeholder numbers for individuals without a Turkish ID number and for foreign buyers, and whether a hosting service counts as subscription-based.

WHMCS and WISECP

If one of these systems does the selling, the modules in the repository create the server in the panel, suspend it, resize it and delete it. The panel issues no invoices for those servers; their owner cannot enlarge them, add disks or clone them from the panel. The WISECP module was not tried on a WISECP installation.

Sources: docs/billing.md, docs/payments.md (Turkish).

Install command

curl -fsSL https://lightningvm.app/install.sh | sudo sh

Ubuntu 22.04 / 24.04 / 26.04. Requirements and options