Usage-Based Billing

Usage-based billing charges a customer for how much they use, such as API calls, gigabytes, or messages sent, instead of a fixed recurring fee. The billing system measures usage over a billing cycle and bills the total when the period ends.

How it works

You send usage events to your billing system as they happen. At the end of each period, the system multiplies the measured quantity by a price and creates an invoice item.

• Metering. Record each unit of usage. In Stripe, meters collect raw usage events into a billable total.
• Aggregation. The meter sums the usage, or takes the maximum or the last value, to get the billable quantity.
• Rating. The quantity is priced, often with tiered pricing so higher volumes cost less per unit.

Many products combine a fixed base fee with a usage charge. The base fee guarantees some recurring revenue and the usage charge grows with use.

Why it matters

Light users pay little, heavy users pay more, and new customers can start cheaply. The cost is predictability. Revenue depends on customer behavior, so pure usage-based MRR is harder to forecast, and a customer's bill can jump without warning. Committed spend, minimums, and caps add stability.

What to watch

• A sudden usage spike can produce a surprise invoice and a failed payment.
• Usage revenue rises and falls with seasons and customer activity.
• Metered totals must match what customers see in their own records, or they will dispute the bill.