Stripe

What it is

Stripe Billing is the subscription and invoicing layer on top of Stripe’s payments business. It runs recurring subscriptions, multi-phase subscription schedules, quotes, invoices, a hosted customer portal and dunning (Smart Retries, reminders and up to three recovery automations), and it meters consumption through the Meters API. For most SaaS companies it is the endpoint a quote-to-cash setup hands the signed deal to: the CPQ or CRM decides the price, Stripe turns it into invoices and collects the money.

The product changed shape in 2026. Stripe completed its acquisition of Metronome in January 2026, and Stripe’s docs now call Metronome “Stripe’s primary usage-based billing platform” and the recommended starting point for new usage integrations. What used to be Stripe’s usage billing is now labelled basic usage-based billing. It remains fully supported, and existing Meters users don’t need to migrate. In July 2026 the Billing pricing page swapped its “Included” mark on usage-based billing for a “Contact Metronome” link.

Stripe also hosts a remote MCP server at mcp.stripe.com with OAuth, plus a local @stripe/mcp package and the @stripe/agent-toolkit for agent frameworks. They cover customers, subscriptions, invoices, refunds and payments, which makes it practical to ask Claude or Cursor about a customer’s billing state without opening the Dashboard.

Can Stripe Billing carry your usage true-ups?

This is the question that sends RevOps teams here, and Stripe’s own comparison page answers it. Basic usage-based billing supports pay-as-you-go, flat fee plus overages, and credit-based pricing reconciled at invoice time. It does not support prepaid credits with real-time drawdown, commits and minimums, ramp schedules, dimensional pricing or real-time usage visibility. Those are Metronome features.

So the rule is simple:

• True-up means “bill last month’s overage on this month’s invoice”: Stripe Billing carries it natively.
• True-up means “reconcile consumption against a committed annual spend, with a minimum and a ramp”: you need Metronome, Zuora, Chargebee or Nue, or you build the commit logic yourself.

Credit grants exist in basic billing, with a limit of 100 unused grants per customer. They apply only to metered prices at invoice finalization, and Stripe states plainly that customers can exceed their balance during the cycle.

Pricing reality

Billing is charged on top of payment processing, not instead of it.

• Pay as you go: 0.7% of Billing volume, no monthly fee. Billing volume includes transactions processed off Stripe, so a customer paying by wire still counts. One-off invoices are priced separately under Invoicing at 0.4% per paid invoice.
• Annual plans, paid monthly: $620 a month covers up to $100,000 of monthly Billing volume, then $1,500 up to $250,000, $2,950 up to $500,000 and $5,750 up to $1M, with 0.67% on volume above the tier. Above $1M a month is custom.
• Processing sits underneath: Stripe’s standard US card rate is 2.9% + 30¢, plus 1.5% for international cards and 1% when currency conversion applies.
• Metronome Starter: 0.8% of billing volume plus $0.04 per 1,000 ingested events. Salesforce, NetSuite and cloud-marketplace invoicing are on the Custom plan only.
• Revenue Recognition and Tax are separate products with their own fees. Stripe Tax Basic is 0.5% per transaction where you are registered.

The break-even between pay-as-you-go and the first annual tier is about $88,600 of monthly volume ($620 ÷ 0.7%). Below that, stay on pay-as-you-go. At $100,000 a month Stripe’s $620 is close to Chargebee’s roughly $749 on its commit option, but Chargebee still needs a gateway underneath, and that gateway is often Stripe. At $1M a month the annual plan is $5,750 against $7,000 on pay-as-you-go, about $15,000 a year saved for signing a contract.

Best for

A RevOps or finance-systems owner at a SaaS or AI company already processing payments on Stripe, with one or two billing entities and contracts that fit subscription plus overage. The scoped case where it wins outright: a product-led company that needs self-serve checkout, sales-negotiated subscriptions and monthly usage overages on one customer record, live this quarter, without adding a second billing vendor.

Not for

Companies that sell committed annual spend with minimums, ramps and real-time credit burndown, unless they budget for Metronome too. Multi-entity groups that need ASC 606 schedules updated in the same close cycle are better served by Zuora. Teams whose real gap is quote approvals and contract terms need a CPQ such as Nue or DealHub in front of Stripe, not instead of it.

Versus the alternatives

• Chargebee: the closest independent peer. Vendr reports a median of $57,600 a year. Pick it when you want gateway choice, retention flows and RevRec in one tool. Pick Stripe when payments already run on Stripe and one vendor for payments and billing matters more than gateway independence.
• Zuora: the enterprise incumbent, with a Vendr median of $170,000. Pick it for many entities, currencies and mid-term amendments with revenue recognition in the billing suite.
• Nue: pick it when quoting, commits and credits must live on Salesforce objects from quote to invoice. Nue integrates with Stripe, so this is often “Nue in front, Stripe for collection”.
• Orb and Lago: the independent usage-billing engines left after Metronome joined Stripe. Price one of them against Metronome when real-time metering is the core requirement and you don’t want the billing engine owned by your payment processor.

If none fit because you invoice a few dozen annual contracts, invoice from NetSuite or QuickBooks and revisit when usage pricing arrives. Background: seat-based vs usage-based AI pricing and the quote-to-cash stack.

Watch-outs

• The fee tracks revenue, including revenue Stripe never processes. Off-Stripe payments count toward Billing volume. Guard: model the bill at 2x and 3x current volume before choosing a plan, and move to an annual tier once monthly volume passes about $88,600.
• Basic credits don’t stop overspend. Credits reconcile at invoice time, so a customer can burn through a prepaid balance mid-cycle. Guard: if you sell prepaid AI credits with hard caps, enforce the cap in your own product from meter data or scope Metronome. Test the overspend case in a sandbox before launch.
• Metronome is a second console. Stripe’s docs list Connect, Adaptive Pricing, Workflows and the Stripe Dashboard as unsupported on Metronome, and Checkout as limited. Guard: list the Stripe surfaces finance uses daily before migrating, and get written confirmation of whether Metronome’s 0.8% replaces or stacks on Billing’s 0.7%.
• The CPQ handoff is yours to design. Stripe Quotes carries no approval chains and no contract-term model, so amendments from a CPQ can drift from the subscription in Stripe. Guard: name one system of record for contract terms, then run a mid-term upgrade and a co-termed add-on end to end from the CPQ (or PandaDoc) into Stripe before signing anything.
• Revenue recognition is not in the 0.7%. Billing produces invoices, not ASC 606 schedules. Guard: price Stripe Revenue Recognition and Tax in the same cycle, or confirm your ERP’s revenue module will consume Stripe’s invoice data.