These cookies are required for the website to function properly. They ensure security, enable basic features like page navigation, and store user session data. You cannot disable these cookies.
- Subscription Billing
- Who it's for
- Usage-based services
Usage-based services
API, data and infrastructure services charging for an explicitly measured unit.
How Subscription Billing is set up for you
Meter definitions
Name the unit and accepted aggregation method before publishing prices. Summing events, using the highest measurement and selecting the latest value produce different quantities, so the plan and meter version must agree.
Replay-safe ingestion
Preserve event identity, occurrence time and payload digest. A retry returns the original accepted contribution. Conflicting payloads and cross-customer corrections remain exceptions instead of increasing the next bill.
Explainable rating
Retain the accepted event set, included allowance and tier calculation with each invoice. Graduated and volume pricing follow their declared band rules and need boundary examples during configuration.
Late usage corrections
Freeze the receipt cutoff for an issued interval. A later event or approved replacement follows a reviewed adjustment path while preserving the original quantity and document the customer received.
Features to start with
Roles on the team
- Billing Manager
- Independently approve price plans, billing runs, billing adjustments, credit notes, refund requests and usage events corrections.
- Billing Operator
- Prepare Customers, price plans, subscription changes and billing runs.
- Support
- View assigned customer subscription dates, issued invoices and public usage summaries.
- Customer
- Read own Customers, Subscriptions, issued Invoices, issued credit notes and permitted usage aggregates.
- Finance Viewer
- View seller-entity scoped billing, collection and subscription reports.
Set up Subscription Billing your way.
Start free, then use Proto to change fields, steps and approvals before your team goes live.