Stripe Billing: Features, Pricing and When It Fits

Stripe Billing is the subscription layer on top of Stripe Payments. It stores plans, creates invoices, runs recurring charges and handles the retries and proration that come with real subscription lifecycles. Most teams asking about Stripe Billing want one thing first: what will it cost us? The honest answer is two lines on a bill, not one.

What Stripe Billing actually does

Payments handles the card charge. Billing decides when that charge happens, for how much, and what to do when it fails. That split matters for cost, because every subscription produces a payment fee and a separate billing fee.

The core pieces you get on any plan:

• Recurring price objects: flat, per-seat, tiered, usage-based or package pricing attached to a product.
• Invoicing with automatic collection, PDF invoices and customer portals for payment method updates.
• Smart Retries, which reattempt failed charges on a schedule tuned by Stripe's model instead of a fixed cadence.
• Proration when a customer upgrades, downgrades or adds seats mid-cycle.
• Tax calculation through Stripe Tax, billed separately from Billing.
• Webhooks and the Billing API so your app can react to renewals, dunning and cancellations.

Higher tiers add revenue recovery tooling, revenue recognition exports and multi-entity invoicing. If your finance team needs deferred revenue schedules that satisfy an auditor, that usually decides the plan before price does.

Stripe billing pricing: the two fees that stack

Stripe bills subscription revenue in two parts. First, the standard payment processing fee on each charge, which varies by country, card type and whether the card is domestic or cross-border. Second, a Billing fee on the recurring charge itself. Stripe publishes both rates on its pricing page; the exact percentages and the volume thresholds where Billing becomes free change over time and by region, so check the official page for your billing country before you model anything.

The pattern that matters more than the numbers: the Billing fee applies per successful recurring charge, not per subscription and not per month. A monthly plan and an annual plan at the same total revenue do not cost the same. The annual plan takes one charge, the monthly plan takes twelve, so monthly billing carries twelve times the per-charge Billing fee on the same revenue.

Payment processing behaves the same way. Each charge carries a fixed component plus a percentage, so smaller, more frequent charges lose a larger share to fixed costs. This is why an annual plan can cost meaningfully less to run than a monthly one, even when the customer pays the same amount overall.

A worked estimate for a small subscription book

The figures below are illustrative and do not represent current Stripe rates. Substitute your own from the official pricing page.

Assume a SaaS with 500 customers on a $50 monthly plan, so $25,000 in monthly recurring revenue. Assume an illustrative payment fee of 2.9% plus $0.30, and an illustrative Billing fee of 0.7% of recurring volume.

That is about 4.2% of revenue. Move the same 500 customers to a $600 annual plan and charge once a year. Payment processing drops because the fixed $0.30 applies 500 times annually instead of 6,000 times. The Billing fee drops by roughly the same ratio. The savings are real but they are not free: you have traded monthly cash flow for a lower cost base, and you now carry a year of refund and churn risk on each customer.

Where the costs hide

Three lines rarely appear in a simple quote. Stripe Tax is priced per transaction on top of Billing. Currency conversion adds a fee when you charge in a currency different from your settlement currency. Disputes carry a flat fee per chargeback, and a subscription business with card testing or friendly fraud can see this add up fast.

Failed payments are the quiet cost. Every retry that fails still consumes attempts, and churn from involuntary failures costs more than the fees themselves. Smart Retries exists to reduce that, but it cannot fix a customer whose card has genuinely expired.

When Stripe subscriptions fit well

Stripe Billing is a strong default for product-led SaaS that already uses Stripe for one-time payments. The API is well documented, the customer portal removes a build, and the pricing scales from a handful of early customers to thousands without a migration.

It fits when your plans are simple or your engineering team is comfortable modeling complex ones in code. Tiered and usage-based pricing are supported, and webhooks give you full control over what happens at renewal.

It also fits when you want one vendor for payments, billing, tax and invoicing rather than stitching together a payment processor and a separate subscription management platform.

When it does not fit

Stripe Billing gets awkward in a few situations. If your sales team needs negotiated contracts with custom approval flows across multiple entities, you will feel the gap and likely want a billing platform built for enterprise order management on top of Stripe.

If your volume is large enough that you can negotiate interchange-plus pricing directly with an acquirer, the standard Stripe rate becomes a real line item worth renegotiating. At smaller volumes the flexibility is usually worth more than the discount.

If you sell in markets where local payment methods dominate and Stripe does not support them well, coverage, not price, decides the choice. Check the supported countries list for your customer base before anything else.

How to compare Stripe against an alternative

Build one model with four inputs: monthly revenue, average invoice size, charge frequency and payment failure rate. Run it through Stripe's published rates and through each competitor's. Include tax, currency conversion and dispute fees. Then compare the totals at your current volume and at three times your volume, because per-charge fees and minimums behave differently as you grow.

Practical ways to pay less and avoid mistakes

Push customers toward annual or quarterly billing where your product supports it. The per-charge fee savings are immediate and compound as you scale.

Use the customer portal to keep payment methods current. Most involuntary churn starts with an expired card that nobody updated.

Set clear dunning rules: how many retries, what emails go out, when access is suspended. Stripe gives you the levers; the policy is yours.

Watch currency. Charging in a customer's local currency may lift conversion but adds a conversion fee. Model both outcomes rather than assuming one wins.

Reconcile Billing fees against your own revenue reports monthly. Proration credits and refunds can make the fee line look larger than expected, and catching a misconfigured price early is cheaper than catching it at year-end.

Finally, verify current rates and thresholds on Stripe's official pricing page for your country, since fees and the volume level at which Billing becomes free vary by region and change over time.

This article is general information, not financial, legal or tax advice.