> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.ibee.co.in/docs/platform-fundamentals/billing-and-usage/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.ibee.co.in/_mcp/server.

# Billing and usage

> Learn how billing works in IBEE Solutions — prepaid wallet credits, per-product usage metering, billing admission checks, and payment methods.

IBEE Solutions uses a **prepaid credit model**. You add credits to your organization's wallet, and usage is deducted as resources run. Before creating new resources, the platform checks your billing state — if your wallet is empty or billing is suspended, you'll be prompted to add credits.

## Billing model

All billing is scoped to the **organization** level. Every workspace within an organization shares the same wallet balance, payment method, and invoices.

| Concept            | Description                                                                          |
| ------------------ | ------------------------------------------------------------------------------------ |
| **Wallet balance** | Prepaid credits available for usage. Split into **Purchased** and **Promo** credits. |
| **Billing cycle**  | The current period's accumulated usage charges.                                      |
| **Invoices**       | Per-cycle statements of usage.                                                       |
| **Payment method** | The card or payment method on file for purchasing credits.                           |
| **Usage limits**   | Configurable spending caps per product category.                                     |

## Billing summary

The **Billing → Summary** page in the sidebar shows a real-time overview:

* **Wallet balance** — purchased and promotional credits remaining.
* **Per-product breakdown** — usage by product category (Cloud VMs, GPU VMs, Block Storage, Object Storage, etc.) with expandable detail rows.
* **This billing cycle** — accumulated charges for the current period.
* **Last payment** — most recent credit purchase.

Products with active usage are expanded by default; products with zero usage are collapsed.

## Billing admission checks

When you create a billable resource, the portal and public API use the same
centralized **billing admission check** before provisioning:

1. The client sends the workspace and intended catalog SKU to the shared billing admission endpoint.
2. Portal Client API validates the organization and workspace, then obtains the decision from Billing Service.
3. Creation continues only when the decision returns `allowed: true`.
4. In the portal, a denied decision opens a **Billing needs attention** popup with a contextual message.

Public API integrations call
`POST /v1/billing/resource-eligibility?workspace_id=...` and follow the same
decision. Product APIs do not receive wallet balances or other client-supplied
billing state.

| Billing state                | Message                                               | Resolution                                   |
| ---------------------------- | ----------------------------------------------------- | -------------------------------------------- |
| Credits exhausted / past due | Billing needs attention before creating a resource.   | Click **Add Credits** to top up your wallet. |
| Hard suspended               | Organization is billing-suspended — creation blocked. | Resolve billing to restore access.           |
| Product type not allowed     | Billing does not allow creating this resource type.   | Contact support or check usage limits.       |

When the billing popup appears, you can click **Add Credits** to go directly to the billing page with the top-up flow pre-opened. After adding credits, return to the deploy page to continue.

## Adding credits

Navigate to **Billing → Payment Method** in the sidebar and click **Purchase Credits**. You can also reach the top-up flow from any billing-blocked popup by clicking **Add Credits**.

## Usage limits

Under **Billing → Usage Limits**, you can view and request increases for per-product resource quotas. These limits cap the number of active resources per product category (e.g., maximum number of Cloud VMs, total block storage capacity).

When a limit is reached, the create form shows a **"Limit reached"** indicator with a link to request an increase.

## Invoices

Under **Billing → Invoices**, view all invoices for the organization. Each invoice shows:

* Invoice number and date
* Billing period
* Total amount
* Payment status

## Related pages

* [Organizations and tenancy model](/docs/platform-fundamentals/projects-and-tenancy-model)
* [Add billing](/docs/getting-started/account-setup/add-billing)
* [Limits and quotas](/docs/platform-fundamentals/limits-and-quotas)
* [Dashboard](/docs/getting-started/overview/dashboard)

> Learn how billing works in IBEE Solutions — prepaid wallet credits, per-product usage metering, billing admission checks, and payment methods.