Stripe vs Chargebee

Where each vendor puts its fee

Stripe splits processing and billing logic into two lines. The Stripe pricing page shows 2.9% + 30¢ for each successful domestic card transaction, adds 1.5% for international cards and 1% when currency conversion is required, and then lists Billing as its own product: pay as you go at 0.7% of Billing volume, or a pay-monthly plan starting at $620 per month on a one-year contract. Stripe states that Billing volume includes Billing transactions processed on and off Stripe and excludes one-off invoices, so the base is narrower than every dollar you collect.

Chargebee does not publish a card rate at all. On the Chargebee pricing page, Flow is a slider labelled Monthly Invoicing Volume that runs from $0 to $500K and shows two options side by side: $0 + 0.80% and $99 + 0.65%, with a $66K breakeven. Your processor's rate sits on top, and the page names more than 40 gateways, among them Stripe, Adyen, Braintree and Mollie. A common mistake is to set Chargebee's fee against Stripe's processing fee; the fair pairing is Stripe's processing plus Billing against your gateway's processing plus Chargebee.

Both vendors give you a crossover. On Chargebee, the $99 option wins once monthly invoicing passes $66,000, because $99 divided by (0.80% minus 0.65%) is $99 divided by 0.0015, which is $66,000. On Stripe, pay as you go at 0.7% reaches the $620 starting price of the monthly plan at $620 divided by 0.007, or $88,571 of monthly Billing volume. Beyond that point, ask Stripe which volume tier applies, because its page says the monthly plan is based on a volume tier without listing the tiers.

Cost at $20,000, $100,000 and $500,000 a month

The assumptions: every payment is a domestic card, average payment sizes are $100, $250 and $500, Stripe is the gateway under both stacks, Stripe Billing is on pay as you go, and Chargebee uses whichever Flow option is cheaper at that volume. Tax, disputes, international surcharges and currency conversion are left out.

• $20,000 a month in 200 payments of $100. Card processing is 2.9% of $20,000 ($580) plus 200 payments at $0.30 ($60), so $640. Stripe Billing at 0.7% adds $140, for $780 in total ($9,360 over 12 months). Chargebee on the $0 option charges 0.80% of $20,000, which is $160, for $800 in total. The $99 option would cost $99 plus 0.65% of $20,000 ($130), or $229, and loses at this size.
• $100,000 a month in 400 payments of $250. Card processing is $2,900 plus 400 times $0.30 ($120), so $3,020. Stripe Billing at 0.7% adds $700, for $3,720 ($44,640 over 12 months). Chargebee on the $99 option charges $99 plus 0.65% of $100,000 ($650), or $749, for $3,769 in total. Stripe is cheaper by $49 a month, which is $588 a year.
• $500,000 a month in 1,000 payments of $500. Card processing is $14,500 plus 1,000 times $0.30 ($300), so $14,800. Stripe Billing at 0.7% adds $3,500, for $18,300 ($219,600 over 12 months). Chargebee on the $99 option charges $99 plus 0.65% of $500,000 ($3,250), or $3,349, for $18,149 in total. Chargebee is cheaper by $151 a month, which is $1,812 a year.

What the arithmetic says, and what could change it

The gap never exceeds $151 a month even at half a million dollars of billing, so fees alone should not decide this choice. Three things would move the numbers. A gateway with a lower card rate than Stripe's helps Chargebee, because Chargebee lets you choose among its listed gateways. A Stripe quote on the monthly plan that comes in under $700 at $100,000, or under $3,500 at $500,000, helps Stripe. And tax matters: Stripe Tax Complete adds $90 a month on a one-year contract, while Chargebee's Flow column lists tax handling without a separate line.

On the Stripe side, one caveat is worth a phone call. The pricing page says Billing volume includes transactions processed on and off Stripe, which implies Billing can sit above another processor. Ask Stripe which off-Stripe processors are supported in your country before you assume you must use Stripe for card processing, and ask what changes about the 0.7% when you do.

Failed payments: Smart Retries against smart dunning

Stripe's Smart Retries documentation says the model chooses retry times from signals such as how many devices have presented a payment method recently, and that the recommended default is 8 tries within 2 weeks. You can set the policy window to 1 week, 2 weeks, 3 weeks, 1 month or 2 months, or switch Smart Retries off and write a custom schedule of up to three retries. When recovery fails, the subscription can be canceled, marked unpaid, left past due or paused. Hard declines such as a lost or stolen card are not retried until you collect a new payment method, and the same page lists retry limits for bank debits: for ACH Direct Debit, up to 2 retries within 40 days after an insufficient-funds failure once you turn local-method retries on.

The customer email documentation covers the messages around those retries: failed-payment emails, renewal reminders, an expiring-card email one month before expiry, and a trial-ending reminder seven days before a trial ends. Each can link to a Stripe-hosted page or the Customer Portal where the customer swaps the card. Renewal reminders are sent only for subscriptions set to charge automatically, so an annual customer paying invoices by bank transfer relies on the separate unpaid-invoice reminder setting instead.

Chargebee's pricing page lists both basic dunning, covering online and offline payments, and smart dunning on Flow and Enterprise, together with lifecycle emails that have templates, segmentation and multiple reminders. It does not publish retry counts or windows, and Chargebee's navigation only describes its retries as ML-powered dunning, so request the default schedule in writing and ask whether it can vary by plan or segment. One operational rule applies to either vendor: let one system send failed-payment emails. If Chargebee owns the subscription but Stripe's customer emails are still switched on for old Stripe Billing subscriptions, a customer can receive two different card-update requests.

Usage-based and hybrid pricing

Both pages cap basic usage billing at the same size. A footnote on Stripe's pricing page says basic usage-based billing through its Meters API is part of Billing pricing with up to 100M events a month included, and Chargebee's Flow card says it includes 100M usage events a month. Enterprise lists ingest up to 500M events a month as a paid add-on. If your product meters API calls or compute minutes in the tens of millions, you are comfortably inside either ceiling.

Past basic metering the vendors diverge. Stripe lists Metronome under Revenue for real-time metering, pricing and analytics, and Metronome has its own plans and pricing page; Stripe also publishes a usage-based billing guide. Chargebee's feature table lists advanced metering with custom SQL, schemaless usage data, tiered, stairstep, volume or block pricing, included usage defined per plan, thresholds and overages, and pending-state invoices as included on Flow. For a seat-plus-overage product, the practical test is whether a mid-month plan change, an included allowance and an overage line can live on one invoice without a manual credit note.

Tax, merchant of record and revenue recognition

Stripe's tax tooling is a separate product. Tax Complete starts at $90 a month on a one-year contract and covers threshold monitoring, registrations, calculations and filings; Tax Basic covers calculations only, at 0.5% per transaction through the no-code integration where you are registered to collect taxes. Stripe also sells Managed Payments, described on its pricing page as a merchant of record solution, at 3.5% per successful transaction in addition to Payments fees. Stripe says it includes indirect tax compliance and remittance in more than 75 countries, fraud prevention, dispute management, invoicing and customer support.

Chargebee's Flow column lists sales tax for the US, EU VAT and global taxes, support for multiple tax profiles, inclusive tax and tax reports. Avalara AvaTax is a paid Enterprise add-on, and eInvoicing is marked as a paid option. The pricing page describes no merchant-of-record service, so you should assume you remain the legal seller and keep your own registrations. If outsourcing that liability is the main goal, the Stripe vs Paddle comparison covers a vendor that takes it on at 5% + 50¢ per transaction.

Revenue recognition is a separate purchase on both sides. Stripe's Revenue Recognition product has monthly and annual plans on its pricing page and states a goal of ASC 606 and IFRS 15 compliance. Chargebee's RevRec Performance plan is quoted through a demo request and is described as available only to Chargebee Billing customers, and its Enterprise plan is priced by quote too. Our revenue recognition tools list covers standalone options if your auditors want the schedule outside the billing system.

Where Chargebee Flow stops: hierarchies, entities and contracts

Chargebee's feature table marks several items as not included on Flow: account hierarchy (parent-child structures up to 30 levels deep), multi-entity management (up to 100 business entities), approvals on price points, on-demand manual discounting, contract terms, eSign integrations with GetAccept and Docusign, Salesforce subscription management, SAML, and SCIM. The Enterprise card lists multi-entity management, account hierarchy, contract terms and on-demand discounting as its additions, and the feature table marks some of these with a dollar sign, so ask for each priced separately before you budget Enterprise.

Stripe's pricing page names none of these. That does not prove Stripe cannot model them, but it does mean a customer with several billing subsidiaries under one master agreement is a design task rather than a checkbox. If your sales motion produces ramped multi-year deals, Chargebee's CPQ product lists multi-product quotes, multi-year ramped quotes and rule-based approval workflows, and CPQ Lite is free for the first 50 quotes; both require Chargebee Billing. If you rarely quote and mostly sell self-serve, none of this helps you. The quote-to-cash tools list compares dedicated options.

Running Chargebee on top of Stripe

Chargebee's migration guide describes the combined setup: you connect your live Chargebee site to your Stripe account and payments are processed through Stripe, while customers stay in Stripe because card details belong to the Customer record. The Flow column on the pricing page shows Stripe Radar transaction-level and customer-level alerts as included, so fraud screening stays Stripe's.

The cost of that combination is two vendors on one invoice stream: Stripe's processing fee and Chargebee's billing fee, as in the worked example. Its benefit is that the gateway can later change without rebuilding subscriptions, which is Chargebee's main reason to exist for companies that expect to add Adyen or Mollie for a region. If you will never leave Stripe, you are paying for a layer you may not use.

Moving from Stripe Billing to Chargebee

Source: Chargebee's guide to migrating subscriptions from Stripe while keeping Stripe as the payment gateway.

1. Enable your live Chargebee site and connect it to your Stripe account, then create every plan, add-on and coupon in both the test site and the live site. Chargebee notes that the Latest Product Catalog cannot import Stripe data from the interface, so a team on that catalog raises a request with the migration team.
2. Start taking new signups in Chargebee before you migrate old ones, with payments still processed through Stripe, so Stripe stops accumulating subscriptions that would need to be moved later.
3. Raise a migration request in Chargebee under Settings, then Import & Export Data. Support sends a checklist; once it is done, Chargebee exports subscription data from Stripe and imports it into your test site for review, where email addresses are slightly altered so customers do not get test emails.
4. Review the imported subscriptions and the card details Chargebee maps (last four digits and expiry), then give the go-ahead. Chargebee imports to the live site and, at your choice, cancels the matching Stripe subscriptions while leaving the Stripe customers and their cards in place.
5. Know the scope: the import covers subscription and customer details plus current-term invoices only. Upgrade or downgrade charges on those older invoices will not appear in Chargebee, and refunds cannot be processed on them. Chargebee says migrations usually take 5 to 8 business days from the date the data is received and the checklist is complete.

Moving from Chargebee to Stripe Billing

1. Decide where the cards live. If Stripe is already your Chargebee gateway, the cards are on Stripe Customer records and need no transfer. If your gateway is Adyen, Braintree or Mollie, you need a card-data migration; Chargebee's pricing page lists billing data portability, including payment methods, on both plans, so ask Chargebee's team to cooperate.
2. For a transfer from another processor, follow Stripe's data migration overview: build the Stripe integration first, send new customers to it, then request the import of existing customers. Stripe's import guide says you can keep charging existing customers on the old processor until the migration finishes, so customers see no downtime.
3. Recreate products and prices in Stripe from your Chargebee price book and coupons, then create each subscription through the API or Dashboard with the correct billing anchor so renewal dates do not shift and nobody is charged twice in one cycle.
4. Switch webhooks and dunning together. Stripe signals a failed subscription payment with the invoice.payment_failed event and a retry attempt count, so rebuild any Chargebee-triggered customer messages on those events and turn on Stripe's customer emails only for subscriptions Stripe now owns.
5. Keep read access to Chargebee until your next close: invoice history, credit notes and any RevRec schedules do not follow the subscriptions to Stripe automatically.