Updated September 2026: Stripe Billing currently lists 0.7% of Billing volume for pay-as-you-go. Its US annual pay-monthly tiers start at $620/month for up to $100k of monthly Billing volume, with higher tiers at $1,500 / $250k, $2,950 / $500k, and $5,750 / $1M; additional volume is listed at 0.67%. Stripe now positions advanced usage-based billing under Metronome, while basic Meters API functionality remains part of Billing pricing with up to 100M events/month. Use the calculator to put your own volume through the current fee schedule.
Stripe Billing's percentage looks tiny until the revenue base stops being tiny. The right question is not whether 0.7% sounds expensive. It is: what does 0.7% cost at your Billing volume, what does the published annual plan cost at the same volume, and which parts of the stack are you actually buying?
This guide keeps three products separate because mixing them is where bad cost comparisons start:
- Stripe Billing manages recurring billing and subscriptions.
- Stripe Payments processes payment methods and has its own region/method-specific fees.
- Metronome, a Stripe product is now Stripe's advanced usage-based billing product.
The current Stripe Billing fee
Stripe's current Billing pricing page lists pay-as-you-go at 0.7% of Billing volume. Stripe says this includes Billing transactions processed on and off Stripe and excludes one-off invoices. That means it is a fee for the Billing layer, not simply a surcharge on card transactions.
The published US annual pay-monthly tiers are:
| Plan | Monthly fee | Included Billing volume / month | Above the tier |
|---|---|---|---|
| Pay monthly | $620 | $100,000 | 0.67% |
| Pay monthly | $1,500 | $250,000 | 0.67% |
| Pay monthly | $2,950 | $500,000 | 0.67% |
| Pay monthly | $5,750 | $1,000,000 | 0.67% |
Those plans are annual subscriptions paid monthly. Stripe also advertises custom pricing for large Billing volume or unusual business models. Regional prices differ, so the dollar tiers above should be treated as the published US schedule, not a universal price list.
Put the percentage into dollars
The pay-as-you-go arithmetic is simple:
monthly Billing fee = monthly Billing volume × 0.007- $10k/month Billing volume: $70/month, or $840/year.
- $100k/month: $700/month, or $8,400/year.
- $250k/month: $1,750/month, or $21,000/year.
- $500k/month: $3,500/month, or $42,000/year.
- $1M/month: $7,000/month, or $84,000/year.
At the published tier boundaries, the annual monthly plans are cheaper than pay-as-you-go: $620 instead of $700 at $100k, $1,500 instead of $1,750 at $250k, $2,950 instead of $3,500 at $500k, and $5,750 instead of $7,000 at $1M.
Calculate Stripe Billing fees at your volume
Do not add a universal “Stripe processing fee” to this calculation
Payments pricing varies by country, payment method, card origin and contract. A US card example is not a valid assumption for a European ACH-like bank transfer, a negotiated enterprise contract, or a business operating under another Stripe regional schedule.
So the calculator intentionally models Billing fees only. If you want full unit economics, add your actual payment-processing cost from your own Stripe contract as a separate line item.
What changed for usage-based billing
The old mental model—“Stripe Billing includes the usage-metering product”—is now incomplete. Stripe's current Billing page lists usage-based billing through Metronome, a Stripe product. Stripe separately notes that basic usage-based billing through its Meters API remains available as part of Billing pricing, with up to 100M events per month included.
That distinction matters when comparing architectures:
- If you need ordinary subscriptions and basic metering, evaluate Billing's included capabilities.
- If you need advanced multidimensional usage rates, negotiated contracts and usage/revenue workflows, evaluate Metronome separately.
- If you want usage evidence to remain independent of whichever financial layer you choose, keep a dedicated usage ledger upstream.
Stripe / Metronome usage-based billing →
Where UsageBox fits—and where it does not
UsageBox does not remove Stripe Billing's 0.7% fee if you continue using Stripe Billing for the same Billing volume. It does not replace Stripe Payments, calculate tax, collect money, or reproduce Metronome's pricing engine.
Its role is narrower: keep the measured quantity independent. Your application sends retry-safe usage to an independent ledger, retains the accepted raw evidence, and produces rollups that can be reconciled with whatever biller sits downstream.
That gives you an architectural option instead of a fee hack:
- instrument the product once;
- keep accepted usage and retry semantics independent;
- send quantities into Stripe/Metronome or another billing workflow;
- change pricing or financial vendors later without also migrating the source usage history.
See the full Stripe + independent metering architecture.
The decision rule
Use the fee schedule as a vendor-cost input, not as ideology. At small volume the percentage may be trivial compared with engineering time. At larger volume, compare the published annual tier, ask for custom pricing, and price the operational value of the Billing features you actually use.
The part worth separating early is the usage evidence. Billing systems and fee schedules change. Your product's measurement contract should not have to change every time they do.