Billing and Services

An order records the purchase, an invoice records the amount to be paid, a transaction records money received or refunded, and a service records the software or hosting you receive. These records are related but describe different stages.

Review a purchase

1. Open Invoices and identify the invoice by its number, date, and items.
2. Check its status and remaining amount before making a payment.
3. Use Transactions to review recorded payment activity.
4. Open Services to confirm fulfillment and the service's current state.

An active license and a completed hosting deployment are separate outcomes. A paid invoice confirms settlement; it does not prove that a domain transfer or application deployment finished.

Pay an outstanding invoice

Use the payment action offered for the invoice and follow the card flow. Wait for confirmation, then refresh the invoice to check its recorded status. If payment has succeeded but the status has not caught up, check transactions and contact support before trying another payment.

Keep the invoice number, payment date, and account email when reporting a billing problem. Do not send card details.

Understand renewals

Review each service's billing cycle and next due date in its details. Hosting, software, domains, and cloud usage can have different billing arrangements; do not assume a single renewal covers everything.

Renewal invoices and payment reminders depend on the platform's billing configuration. Automatic charges may be attempted against a stored payment method when enabled. Check the invoice balance and service dates after payment; domain renewal may also require successful registrar fulfillment.

The CMS's cached license validity window is a connectivity mechanism, not an extension to your purchased subscription. See licenses.

If a service is pending or suspended

For a pending service, check whether its invoice is paid and whether provisioning is still running. For a suspended service, check outstanding invoices and contact support if payment is already recorded.

Staff may need to investigate failed provisioning or renewals after settlement. Provide the existing service and invoice references so they can reconcile the records without creating duplicate purchases.

Changes, cancellation, and refunds

Use any relevant controls exposed for your service, or request help through Support Tickets. State which service should change and the intended effective date. Removing an item from the cart does not cancel a purchased service, and stopping your CMS process does not stop billing.

Review the terms shown for your purchase. A deployment failure, cancellation request, or support ticket does not itself issue a refund or guarantee a particular cancellation date.