Billing Transaction Volume Instead of Seats: A Walkthrough

Before touching either platform, write down the exact unit you bill on: dollar volume processed, transaction count, or a blend where the fee changes above a volume threshold. Fintech and embedded finance platforms often bill on a percentage of volume with a minimum flat fee, which can be a different shape than the simple flat or per-unit pricing many billing tools are built around, so test your exact model in each tool before you commit. Get this definition precise and in writing before you configure anything, because changing it after customers are live means a contract amendment for every account.

Stripe's Meters API is built for exactly this kind of usage reporting: you send metered events as volume flows through your platform, and Stripe aggregates them into an invoice line at the rate you define. Tiered and graduated pricing (a lower basis-point rate at higher volume) is supported natively. Where it gets harder is a true percentage-of-volume fee with a minimum floor: you'll likely need to calculate the effective charge yourself and report it as a single metered amount, rather than relying on Stripe to compute the percentage for you.

Chargebee's usage-based pricing supports percentage-of-volume billing more directly, along with the minimum-fee floor, so the basis-point-plus-minimum structure is closer to a configuration than a calculation you build yourself. The tradeoff is the same one that shows up everywhere in this comparison: more built-in flexibility, more setup and licensing cost, and a second system's ledger to reconcile against your processor's own settlement reports.

Usage-based fintech billing has a reconciliation step that seat-based SaaS billing doesn't: the volume you billed on has to tie back to what actually settled through your payment rails, not just what your metering event reported. A metering bug that double-counts a batch of transactions turns into an overcharge that a customer's own finance team will catch fast. Build a monthly reconciliation between your settlement reports and your metered billing events into your close process from the start, regardless of which platform you choose.

Keep the flat monthly platform fee and the volume-based fee as two distinct line items rather than blending them into one number, even if your sales team quotes customers a single all-in rate. Splitting them lets your finance team see, account by account, how much revenue is guaranteed recurring versus how much moves with transaction volume, which matters for both revenue recognition and for understanding which customers are actually profitable once processing costs are netted out.

Once a customer's volume crosses into a new pricing tier, say they move from the entry basis-point rate to a lower rate reserved for higher-volume accounts, that change needs to apply cleanly without a manual contract edit or a gap in billing. Stripe's graduated and tiered pricing models handle a volume threshold shift automatically within a single metered price, which is one of the areas where Stripe's usage tooling is genuinely strong for this kind of business. Chargebee supports tiered usage pricing as well, though the configuration tends to live more in its own catalog structure than in a developer-facing API, which matters depending on whether your team prefers to configure pricing changes or code them. What both platforms share is a blind spot: neither one will tell you when a customer is approaching a tier threshold ahead of time, so if you want to proactively flag an account nearing a lower rate, that alert has to come from your own analytics layer watching the same volume data feeding the bill. Set that alert up early: a customer who quietly crosses into a lower rate and keeps getting billed at the old one is a refund and a trust problem waiting a quarter or two to surface, and it's much cheaper to catch with a dashboard threshold than with an angry email from a customer's controller. Put the threshold check on the same cadence as your settlement reconciliation, since both draw from the same underlying volume data and reviewing them together is cheaper than building two separate monitoring processes for numbers that come from one source.

In short, the setup sequence looks like this:

1. Write down the exact unit you bill on: dollar volume, transaction count, or a blend where the fee changes above a threshold.
2. Model the volume fee in Stripe Billing with metered events, or in Chargebee with its percentage-of-volume usage pricing and minimum-fee floor.
3. Reconcile billed volume against what actually settled through your payment rails, not just against metering events.
4. Keep the flat platform fee and the volume fee as separate line items, even if sales quotes one all-in rate.
5. Set tiered pricing so a customer crossing a volume threshold moves to the lower rate without a manual contract edit.