Usage metering vs Stripe Billing
Happy path: emit an event, we meter it, Stripe invoices it. UsageMill sits in front of Stripe Billing. We do not replace it, and we do not take the money.
| UsageMill | Stripe Billing | |
|---|---|---|
| Job | Persist usage events and aggregate them | Invoice, tax, collection, customer portal |
| You send | POST /api/v1/usage — meter, quantity, optional timestamp, Idempotency-Key | Customers, prices, subscriptions, payment methods |
| Money path | Daily cron writes invoice items or metered subscription lines when keys are set | Stripe invoices and collects. Stripe is merchant of record |
| Caps | Hard caps in code. Over the ceiling is a predictable 4xx (429) | Your products, prices, and Billing meters in the Stripe Dashboard |
| Idempotency | Same tenant + Idempotency-Key counts once. No double count | Stripe Idempotency-Key on Stripe API calls — a separate surface |
Need a sales-led usage catalog above Scale? That exit is in the FAQ — not here.