Chargebee vs Stripe Billing

Chargebee

Tiered, usage-based, flat-fee and custom models are documented alongside a price book with prepaid credits and hybrid plans, with usage ingestion up to 100M events a month included and 500M as a paid add-on. Proration is configurable in both UI and API, subscription changes can be scheduled and applied automatically, quotes come through the CPQ module with approval workflows, and an open-source customer portal handles plan changes, add-ons and upgrades inside your own app. I stop short of the top because grandfathering on price changes and versioned, attributed subscription changes are not documented, and entitlements appear only indirectly as pricing and limits enforcement.

Stripe Billing

Tiered, volume, graduated and per-seat pricing are documented end to end, with the tier fields named in the API, free trials, prorated billing, scheduled subscription changes, quotes before the subscription exists and a Stripe-hosted customer portal; usage metering runs through the Meters API with up to 100 million events per month included. Two caveats from the same pages: advanced usage-based billing lives in Metronome, which is stated as not included in Stripe Billing, and a product and price are only editable until a subscription is created. I found no public information on entitlements exposed to the selling application or grandfathered price rollouts to existing customers.

Chargebee

E-invoices are delivered through named networks — Peppol, Italy's SDI, India's IRP — across 20+ countries including Germany and Denmark, with real-time status tracking, recurring e-invoices that follow subscription changes, mandate-adherence claims and a no-code template builder for regional formats, spanning B2B, B2C and B2G. Credit notes, multi-language support and multi-currency invoices are documented, and invoices are described as locally compliant and customizable. I hold back because sequential numbering, GoBD-compliant unalterable archiving, audit export of invoice data and a Verfahrensdokumentation do not appear on the captured pages, and the structured formats are not named as EN 16931, XRechnung or ZUGFeRD.

Stripe Billing

Invoices go out in 35 languages and 135 currencies, and the correction path is disciplined: credit notes serve as the source of truth, cannot be modified once issued, and multiple are allowed per invoice. The captured pages state plainly that Stripe Invoicing itself does not generate or transmit legally compliant e-invoice files — compliant XML (UBL, CII, Peppol BIS Billing 3.0) is produced by marketplace partners such as Billit, reached via webhook or app. I found no public information on sequential numbering, mandatory invoice content or GoBD-compliant archiving.

Chargebee

Real-time tax rates are applied automatically with US sales tax, EU VAT and global taxes across multiple tax profiles and regions, and third-party tax integrations can apply reverse charge regardless of the local configuration. Reverse charge is documented in detail — cross-border only, configurable per country, an editable note on the invoice, a VAT number stored on the customer and a validation setting that blocks invalid numbers at customer creation — though on manual taxation the check is country difference alone, without reading the registration number. I found no public information on OSS reporting data, customer-location evidence being kept, or a named US tax engine.

Stripe Billing

Stripe Tax automates sales tax, VAT and GST in more than 90 countries with product tax codes, tracks sales against local registration limits, performs registrations on your behalf and manages filings directly or through integrated partners — and it can be switched on per subscription right in the Dashboard, which is exactly how I want it wired. I found no public information on VIES VAT-ID validation, OSS reporting data or kept evidence of customer location on the captured pages.

Chargebee

Forty-plus gateways with routing by market, currency or method, SEPA among the named direct-debit schemes, tokenization, hosted and full-API checkout, and an Adyen-powered option for unified billing and payments. Dunning is deep: smart retries reading 200+ signals with a 12-retry ceiling and failure playbooks, custom cadences up to 5 retries, configurable final actions on both subscription and invoice, a payment failure dashboard with pre-built cohorts, and a recovery dashboard that reports revenue recovered and benchmarks against your previous retry logic. What I miss is a documented migration path for moving subscriptions and payment tokens out — the terms make export the customer's job and assistance may cost a fee.

Stripe Billing

Smart Retries with AI-chosen timing, automatic updates for expired cards, custom retry schedules and per-segment retry policies, configurable cancel/unpaid/pause outcomes on final failure, reminder emails, and automatic reconciliation of ACH and bank-transfer payments are all documented, plus webhook events like invoice.payment_failed to build on; the pages state 8,2 Mrd. $ in failed payments recovered in 2025 and 14 $ recovered per invested 1 $. I found no public information on a collection-agency handover or on a documented path to export subscriptions and stored payment tokens to another provider.

Chargebee

RevRec runs ASC 606 and IFRS 15 five-step recognition with a controlled revenue sub-ledger drillable to the transaction, deferred-revenue waterfalls and forecasts, an SSP library, period locking, and a complete audit trail from signed contract to journal entry. Summarized journal entries post to the general ledger on your fiscal calendar, A/R aging and roll-forward reports are native, native CRM and accounting integrations reflect modified invoices and credit notes, and there is a REST API with webhooks plus warehouse export to Snowflake, S3 or GCS as an Enterprise add-on. I dock a point because a complete export a successor system could import is not documented, and the terms charge a possible fee for export assistance during the retention window.

Stripe Billing

Revenue recognition to ASC 606 and IFRS 15 is offered, with six report types — debit/credit breakdowns by invoice, customer, product and line item, carrying debit and credit general-ledger codes — downloadable as CSV or pulled through the Revenue Recognition API in public preview, alongside a NetSuite connector, a QuickBooks export and data-warehouse sync as an upcharge. Webhooks such as invoice.updated are documented for keeping my own systems in step. I found no public information on a DATEV export or on a complete export of customers and subscriptions a successor system could import.

Chargebee

The contracting entity is Chargebee Inc. in Maryland, with an EU representative in Amsterdam and a UK representative, a data processing addendum incorporated into the terms, and Data Privacy Framework participation plus Standard Contractual Clauses for transfers. Processing may occur in the United States, European Union, India and Australia, so EU processing is possible but not committed as hosting; the captured pages list no subprocessors with locations and state no ISO 27001 or SOC 2 certification. Deletion on written request after termination and a 120-day retention period are documented, while Google Analytics and third-party AI processing appear on the website side of the chain.

Stripe Billing

EEA customers contract with an Irish entity registered at the Irish Companies Registration Office, and the payments entity is authorized by the Central Bank of Ireland as an electronic money institution; a data processing agreement and a subprocessor list are published, and ISO 27001 and SOC 2 are stated. The vendor itself is Stripe, Inc. of South San Francisco. I found no public information on the captured pages confirming where billing and invoice data are hosted or where the listed subprocessors operate.

Chargebee

The two billing tiers are priced publicly with an explicit scaling rule — "$0 + 0.80%" up to $500K, then "$99 + 0.65%" — plus 100M usage events a month included and the first 50 quotes free, and the contract terms are equally public: 12-month auto-renewing term, 90-day non-renewal notice, fees non-refundable and exclusive of taxes, 1.5% per month late interest. But the Enterprise tier and the RevRec, CPQ and Growth modules carry feature lists with no prices, every paid add-on (500M events, access controls, data export) is unpriced, and I found no public information on overage above the revenue band. A buyer can price the low end of the stack but not the whole thing.

Stripe Billing

The scaling rule is public: 0,7 % of billing volume pay-as-you-go, 0,67 % for additional billing volume above a monthly 80.000 €, or 500 € monthly on a one-year contract with 11 % savings, and card rates such as 1,5 % + 0,25 € for standard European cards are published. But revenue recognition, tax registration and filing, usage metering at scale, third-party payments and data-warehouse sync are only marked with an asterisk as available at an upcharge, without published prices, and VAT treatment of fees is not stated.