Understanding Billing
Overview
- This document walks through how we bill our clients, what qualifies for billing, and what is supported by the system.
- Designed for all GTM teams to ensure standardized selling aligned with the system's capabilities.
- Also serves as reference for the Product & Strategy team when deciding pricing strategy for new modules.
Prerequisites
Understanding Client Structure
Before diving into billing, understand the client hierarchy:
- Client — The organization for which billing, pricing, and contractual agreements are defined. Billing and invoicing happen at the client level, aggregating usage across all BUs and AppIDs.
- Business Unit (BU) — A subdivision under a client. Allows tracking/filtering usage by BU with access control.
- AppID — The most granular level for usage tracking. Categorized as staging or production.
Purpose & Use Case
- GTM Teams — For onboarding new GTM members and ensuring alignment before closing deals.
- Product & Strategy Team — When defining pricing strategy for new modules/products.
Pricing Features
Minimum Monthly Commitment
- Definition: A predetermined minimum amount a client agrees to pay monthly. Client is billed either the minimum or actual usage, whichever is higher.
- MMC is defined at client-level on the admin dashboard.
- Configurable in terms of amount (in client's currency), not usage volume.
- Set via Admin Dashboard - Pricing Tab
Supported:
- MMC at client-level for each month
Not supported:
- MMC for a combination of units (e.g., minimum $320 for combined Digilocker + Fetch PAN)
Conditional Production Access
- Ensures clients can only use modules for which pricing is configured on the Admin Dashboard.
- Without this, all AppIDs can access all HyperVerge APIs by default.
Billing Methodology
Usage-Based Pricing
We follow a Usage-Based Pricing Model (pay-per-use). API billing is based on billable API hits counted by predefined status codes.
Tax-Based (Waterfall) Pricing
Each tier's rate applies only to hits within that tier. Per-hit cost decreases as volume increases.
Example:
| Volume Slab | Price per Hit (INR) |
|---|---|
| 1 - 1,000 | 2 |
| 1,001 - 5,000 | 1 |
| 5,001+ | 0.5 |
For 12,000 hits: (1,000 x 2) + (4,000 x 1) + (7,000 x 0.5) = INR 9,500
Non-Tax (Flat) Pricing
Deprecated
This model is deprecated for new clients. All new clients use Tax-Based (Waterfall) pricing.
All hits billed at the rate of the highest volume tier reached.
FAQs
Can we generate multiple invoices for one client_id?
Answer pending.
Are both staging and production appIds considered for billing?
Answer pending.