Chargebee vs Stripe Billing

Chargebee

The commercial model plainly lives in the product: tiered, usage-based and hybrid pricing with prepaid credits in a price book, usage ingestion, proration with configurable methods and overrides in both interface and API, scheduled subscription changes, a self-service and open-source customer portal, and CPQ quoting for multi-year deals. Contracts with minimum terms, ramps and 100-entity account hierarchies are documented, so this sits just under the top anchor; grandfathering of price changes and attributed versioning of every subscription change are not described.

Stripe Billing

Seat, tiered, graduated and volume pricing are documented for both Dashboard and API, usage metering runs through the Meters API with up to 100 million events per month included, and free trials, quotes, a Stripe-hosted customer portal and multi-phase subscriptions that schedule future changes are all evidenced. On grandfathered price rollouts, entitlements exposed to the selling application and versioned subscription history we found no public information.

Chargebee

Structured e-invoicing through Peppol, SDI and IRP across 20-plus countries including Germany and Denmark, covering B2B, B2C and B2G, with real-time invoice status tracking and credit notes, is genuinely strong for the mandates that bite this year. What I cannot find anywhere is sequential numbering, GoBD-compliant archiving or an audit export of invoice data, and XRechnung or ZUGFeRD as named formats, so I stop just short of the audit-proof level.

Stripe Billing

Credit notes are handled the way an auditor wants: not modifiable once issued, creatable only from an invoice or an associated refund, and described as the source of truth when an invoice amount must be amended, with invoices in over 135 currencies and 35 languages. For structured e-invoices, however, the documentation itself states that Stripe creates invoice records and exposes data through API and webhooks but does not itself generate or transmit legally compliant e-invoice files — UBL, CII and Peppol BIS Billing 3.0 are reached through third parties such as the marketplace partner Billit. We found no public information on sequential numbering, mandatory invoice content or GoBD-conformant archiving.

Chargebee

Real-time rates across US, EU and global tax with multiple tax profiles, and reverse-charge mechanics documented down to the invoice note, are the right shape — but the two support pages give different pictures of the VAT ID check: one states reverse charge is applied whenever buyer and supplier countries differ, even where the buyer has a tax registration number, while another documents a VAT validation setting that blocks invalid numbers at customer creation. We found no public information on VIES validation as such, OSS reporting data, evidence of customer location kept for audits, or a named US sales tax engine, so the tax position is not yet one I could defend unaided at year-end.

Stripe Billing

Stripe Tax automates VAT, sales tax and GST across 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, covering one-time and recurring payments and even payments outside Stripe. What the year-end audit will ask for next — reverse charge against a validated VAT identification number, VIES checks and OSS reporting data — we found no public information on, and no written statement of which tax liability a merchant-of-record arrangement would assume.

Chargebee

Gateway-agnostic collection across 40-plus providers with routing by market, currency and method, SEPA among the direct-debit methods, smart retries with a documented retry ceiling, configurable final actions on both subscription and invoice, rule-based recovery workflows and a dashboard reporting recovered revenue per gateway and method — that is the full anchor level for collection. Portability is the weak point: we found no public information on a documented migration path for subscriptions and payment tokens, and the terms make the customer solely responsible for exporting data and permit a fee for assistance.

Stripe Billing

Smart Retries with AI-chosen timing, custom retry schedules of up to three attempts, retry policies per customer segment, automatic reminder emails, cancellation or pausing of subscriptions once retries are exhausted, and automatic reconciliation of recurring invoices paid by ACH or bank transfer are all documented, with 8.2 billion dollars of failed payments recovered in 2025 reported. Over 100 payment methods and connections to other payment providers are offered (multiprocessor support marked as a paid extra), and there is a documented path for migrating SEPA direct-debit mandates from another provider. We found no public information on a handover to a collection agency or recovery figures broken down per dunning step.

Chargebee

Revenue recognition to ASC 606 and IFRS 15 in a controlled revenue sub-ledger with deferred-revenue waterfalls, drill-down to the individual transaction, period locking, an audit trail from signed contract to journal entry and automated journal posting to the general ledger is exactly what I want to see at an audit. Native CRM and accounting sync, REST APIs with webhooks and warehouse export as a paid add-on round it out; we found no public information on a DATEV export or a complete documented export a successor system could import, which is why this is not a ten.

Stripe Billing

Revenue recognition to ASC 606 and IFRS 15 is stated, with six debit/credit report types including per-customer, per-invoice and per-line breakdowns carrying general-ledger codes, downloadable as CSV or through an API that automates period accounting; the handoff runs through the NetSuite connector and QuickBooks exports, and data-warehouse sync exists as a paid extra. We found no public information on a DATEV export or on a complete export of customers, subscriptions and invoices that a successor system could import, and the recognition API is a public preview whose data fields may change.

Chargebee

The contracting entity is Chargebee Inc. in the USA with an EU representative, Chargebee B.V. in Amsterdam, a data processing agreement incorporated into the terms, and processing locations named as including the EU alongside the US, India and Australia. That earns the mid anchor, but the chain is not sovereign: no subprocessor list, no named EU hosting infrastructure, no security certifications stated, and Google Analytics plus a possible CCPA 'sale' of data via advertising cookies sit in the processing chain, with only framework safeguards such as SCCs and the Data Privacy Framework named.

Stripe Billing

The captured pages prove an Irish contracting side — a legal notice naming an entity at One Wilton Park, Dublin with Irish registration number 564555 and VAT number IE3396855EH — plus a Central Bank of Ireland-regulated affiliate, a published data processing agreement, a published subprocessor list and stated ISO 27001 and SOC 2 certifications. But the parent vendor is US-based, and the captured pages give no information on where customer, invoice and payment data are hosted or in which countries the listed subprocessors operate.

Chargebee

The two published bands are refreshingly concrete — a $0 base plus 0.80%, then $99 plus 0.65%, with 100 million usage events a month included and month-to-month terms for the lower tiers. But a buyer still cannot compute the real annual cost: the Enterprise tier and its listed paid add-ons carry no prices, and we found no public information on what the revenue recognition or e-invoicing modules cost; the twelve-month auto-renewing default term with 90-day non-renewal notice is at least stated in the terms.

Stripe Billing

The core scaling rule is public: 0,7 % of billing volume on pay-as-you-go with 0,67 % for additional volume above 80.000 € monthly, a 1-year contract billed monthly at 500 € with 11 % savings, and card pricing of 1,5 % + 0,25 € for standard European cards. But commonly needed modules — revenue recognition, tax registration and filing, high-volume metering, multiprocessor payments, data-warehouse sync, receivables aging — are marked with an asterisk as available at a surcharge with no prices, and we found no public information on VAT treatment of the fees. A buyer can compute the billing fee but not the total annual cost with the modules that matter.