72 docs tagged with "billing"

Account Statement groups formal billing records and usage for the customer account.

Annually billing (also yearly or annual) charges customers on a recurring 12-month schedule. The yearly price comes from the rate card package; how much is charged at creation or renewal and when invoices are generated depend on your billing rule, payment mode, and (for postpaid/manual) advance invoice settings.

AsiaPay is a regional payment gateway used with CMP for customer payments (methods depend on your AsiaPay merchant configuration and CMP integration).

Authorize.net is a card payment gateway that CMP can use for customer payments when enabled for the branch and currency.

Auto Pay automatically purchases infra credits when an account’s available balance falls to or below a configured threshold. That helps prepaid customers keep services running without manually topping up every time the wallet runs low.

CMP bills outgoing network bandwidth as a usage-based service. On CloudStack, usage is collected at the network level (Isolated networks and, optionally, VPC) — not per VM.

CMP bills outgoing network bandwidth as a usage-based service. On OpenStack, CMP implements VM-level bandwidth billing using Gnocchi metrics (network.outgoing.bytes on the VM’s network interface).

Bi-annually billing charges customers on a recurring 24-month schedule. The bi-annual price comes from the rate card package; how much is charged at creation or renewal and when invoices are generated depend on your billing rule, payment mode, and (for postpaid/manual) advance invoice settings.

Platform Q&A for pay-as-you-go, invoices, pricing formulas, snapshot charges, and tax. Full product guides: Billing overview, Pricing formulas.

Billing for a product starts immediately when the order is placed. CMP uses the configured payment type, billing cycle, and billing rule. No separate activation step is required for billing to begin.

A billing cycle defines how often a service is priced and charged — from hourly pay-as-you-go to multi-year subscriptions.

CMP billing has three layers that work together:

Billing rules control how charges are calculated for a service — when invoices are generated, how partial periods (pro-rata) are priced, and how billing periods align to calendar boundaries.

Admins can open a live summary of portal billing configuration from the Billing Settings control on the admin Invoices page. The modal has three sections: Billing Mode, Enabled Global Settings, and Environment Flags.

CMP branches represent regional or legal entities of your cloud business. Each branch has its own invoice branding, tax percentage, and operational countries. Customers are mapped to a branch from their country of registration.

Cardlink is a card payment gateway (Greece / EU focus) that CMP can enable for customer card payments when configured for the branch and currency.

Administrators can manually generate custom, ad-hoc invoices for a client directly from the CMP Admin Panel.

The Customer Billing Dashboard is the end-customer view of billing in the portal. Customers open Billing to review wallet balance, subscriptions, payments, and formal billing documents.

DATE_TO_DATE billing generates invoices for a fixed period from the service creation date — each period runs from creation anniversary to anniversary (minus one day where applicable).

Dinger is a regional payment gateway (Myanmar / Southeast Asia focus) that CMP can enable for local payment methods supported by your merchant account.

Disciplinary actions are automated (and optionally manual) measures against accounts with overdue invoices or negative prepaid wallet balances. They protect revenue and drive payment while keeping admin control for exceptions.

CMP supports DNS domain billing — customers can be charged when they create a DNS domain, typically on an hourly or monthly cycle.

FIXED_CALENDAR_MONTH aligns the first invoice to calendar period boundaries from the start of the creation month or year — without a separate daily pro-rata for partial days in the creation month.

FIXED_PRORATA aligns billing periods to calendar boundaries and splits partial periods into daily pro-rata (creation date → end of month) plus remaining full month(s) within the cycle.

Flutterwave is an Africa-focused payment gateway supporting cards, USSD, bank, and bank transfer (availability depends on currency and merchant account configuration). In CMP it is used for prepaid wallet top-ups and checkout.

Free trials allow providers to offer selected resources to customers at no cost for a limited period. Customers can explore services and evaluate the platform before moving to paid usage.

Freeze is the first disciplinary stage. It restricts new activity and changes while leaving existing services reachable so customers can still operate workloads and settle dues.

Hourly billing (also pay-as-you-go or PAYG) charges customers only for the time a service is actually running.

HyperPay is a payment gateway commonly used for card and regional payment methods in the Middle East / North Africa. CMP uses it when enabled for the customer’s currency and branch.

Invoice numbers are generated dynamically from settings defined per subsidiary (branch). Each branch keeps its own independent sequence.

When CMP generates invoices, branch-level details from this form appear on the document. Configure them in the branch Configure wizard (Step 2: Invoice Settings).

Invoice Settings covers how CMP builds customer invoices: which branch owns the customer, what legal and branding details appear on the PDF, tax percentages, invoice numbers, and terms.

The Low Infra Credit Notification alerts prepaid customers when their available infra-credit (wallet) balance falls below a configured amount. That helps customers top up before services are affected by low or negative balance.

M-Pesa is a mobile-money payment method widely used in East Africa. CMP can accept M-Pesa payments when the gateway is enabled for the branch and currency.

In manual payment mode, customers pay outside the CMP platform (bank transfer, cheque, cash, UPI). CMP generates invoices for usage, but admins verify offline payments and mark invoices paid — there is no payment gateway auto-charge.

Mollie is a European payment gateway supporting cards and local methods (iDEAL, Bancontact, and others — availability depends on CMP integration).

Monthly billing charges customers on a recurring one-month schedule. The monthly price comes from the rate card package; how much is charged at creation or renewal and when invoices are generated depend on your billing rule, payment mode, and (for postpaid/manual) advance invoice settings.

In CMP OpenStack deployments, network provisioning is non-billed. Neither private (tenant) networks nor shared public (external) networks incur a network infrastructure package charge.

Use this checklist when requesting integration of a new payment gateway with StackConsole / CMP. Share as much as you can from the gateway’s documentation; StackConsole may ask for additional gateway-specific details during review.

One Account One Invoice lets postpaid and manual customers receive a single consolidated invoice for all services on the account each billing cycle — instead of separate invoices for every service or billing event.

ISO packages define how CMP bills customers for customer-owned ISO images stored in CloudStack Secondary Storage. Customers use these ISOs to boot virtual machines from custom install media or diagnostics rather than pre-built templates.

Payduniya is a regional payment gateway that CMP can enable for local payment methods supported by your merchant configuration.

A payment gateway is the provider CMP uses to collect payments — wallet top-ups (prepaid), invoice settlement, and (where supported) saved card / auto-charge for postpaid.

A payment mode (also called billing mode in CMP) defines how customers pay for services. CMP supports three payment modes:

PayPal lets customers pay with PayPal accounts (and related methods where integrated). CMP uses PayPal when the gateway is active for the branch and currency.

Paytm is an India-focused payment gateway (wallet, UPI, cards — availability depends on CMP integration). Enable it when customers pay through Paytm for supported currencies.

In postpaid mode, customers consume services first and pay invoices later. Saved payment methods can be auto-charged when invoices are due.

In prepaid mode, customers must maintain a wallet balance. Usage is deducted in real time. Customers can top up manually, or use Auto Pay (when enabled) to charge a saved payment method when balance falls below a threshold.

Wallet top-up, free credits, coupons, and free trial. Product guide: Prepaid.

CMP uses consistent formulas to derive all billing cycle prices from a single base value. Define one price and the others are calculated automatically.

Configure product prices on the rate card after the product exists.

Configure affiliate programs, commission rules, payout methods, and taxation before and after affiliates register.

How CMP charges public IPs vs VPC / isolated / shared network packages. Feature context: Isolated Network, VPC Network, Shared Network, IP Address (CloudStack) · IP Address (Proxmox).

Quarterly billing charges customers on a recurring 3-month schedule. The quarterly price comes from the rate card package; how much is charged at creation or renewal and when invoices are generated depend on your billing rule, payment mode, and (for postpaid/manual) advance invoice settings.

Rate cards define what customers can buy and how much they pay. A rate card is a pricing catalogue — it contains packages (Virtual Machine, Volumes, IP Address, and so on) with orchestrator mappings and billing rates.

Razorpay is an India-focused payment gateway supporting cards, UPI, netbanking, and wallets (availability depends on CMP integration). Use it when customers pay in supported Indian currencies.

This page covers provider (super admin) → reseller billing and reseller → reseller’s customer billing, plus vendor billing notes and current limitations.

Use this page to choose the right partner model and explain differences to providers and partners.

Semi-annually billing charges customers on a recurring 6-month schedule. The semi-annual price comes from the rate card package; how much is charged at creation or renewal and when invoices are generated depend on your billing rule, payment mode, and (for postpaid/manual) advance invoice settings.

SSLCommerz (SSLCOMMERZ) is a Bangladesh payment gateway aggregator. In CMP it is used for prepaid wallet top-ups and checkout in BDT.

Stoppable service billing controls whether compute charges pause when a Virtual Machine or Kubernetes cluster is stopped (including while resources are suspended/stopped by the customer or by disciplinary / schedule flows).

Stripe is a global card payment gateway commonly used with CMP for prepaid wallet top-ups and postpaid saved-card / auto-charge flows.

Suspend disables normal portal use until dues are cleared. The customer can typically only reach billing / payment flows. Stoppable cloud resources (VMs, Kubernetes, and similar) are stopped while allocated resources (disks, IPs, and so on) usually remain.

In CMP, taxation is managed at the branch level. For each country, you set a tax label and separate percentages for Organization and Personal customers.

Terminate is the final disciplinary stage. CMP blocks customer portal access. Clearing cloud resources is deliberately manual — an admin (after confirmation with the customer / provider support) must remove services.

A Threshold (Spending Cap) is a safety limit that restricts unbilled usage exposure for accounts that consume resources before paying. It protects cloud providers from runaway usage, fraudulent provisioning, and bad debt by enforcing early invoicing or service creation restrictions before the standard billing cycle ends.

Tri-annually billing charges customers on a recurring 36-month schedule — the longest standard commitment period CMP supports. The tri-annual price comes from the rate card package; how much is charged at creation or renewal and when invoices are generated depend on your billing rule, payment mode, and (for postpaid/manual) advance invoice settings.

UNFIXED_CALENDAR_MONTH combines a calendar-month pro-rata for the creation month with a rolling full-cycle invoice starting the 1st of the next month.

UNFIXED_PRORATA is mostly applicable to quarterly, semi-annual, and yearly billing cycles. Unlike FIXED_PRORATA, the next invoice period starts from the month after creation — not aligned to calendar quarters.

Usage Details shows the customer’s service consumption lines under Billing → Account Statement → Usage Details. Providers use this page to explain “what am I being charged for?” to end customers.

After connecting Veeam, configure how customers buy Veeam capacity in CMP:

Override root disk, free OS disk, scheduled stop, and related packaging choices. CloudStack offering mapping: Virtual Machine packages.