Stripe Billing charges 0.7% on top of payment processing fees

The revenue mechanism

Many newsletter platforms, membership plugins and custom paywalls that publishers use do not build their own recurring-payment infrastructure; they build on a payments processor's subscription layer instead. Stripe Billing is one such layer, infrastructure other products build on rather than a consumer-facing publisher platform itself. Stripe's own product page, retrieved 16 September 2026, describes Billing as handling recurring subscriptions, usage-based charging, automated invoicing, and failed-payment recovery through 'Smart Retries,' stating the tool 'recovered $8.2B in failed payments in 2025' and that '350,000+' companies use it.

What the documents show

Stripe's pricing page prices Billing separately from the underlying card-processing fee: a 'Pay as you go' plan costs '0.7%' 'of Billing volume,' covering 'Billing transactions processed on and off Stripe' but excluding 'one-off invoices,' with 'no recurring fees'; or a 'Pay monthly' plan 'Starting at $620.00' 'per month, 1-year contract' for higher, more predictable volume. Stripe's own developer documentation lists the mechanics behind that pricing: configurable pricing models, flat-rate, per-seat, usage-based and tiered, scheduled 'Smart retries' for failed charges, and a self-service 'customer portal' letting a subscriber manage their own plan. Neither page states whether the 0.7% figure or the flat monthly fee is fixed for a stated term beyond the contract length shown.

The assumptions exposed

The 0.7% Billing fee, or the flat monthly plan, is charged in addition to, not instead of, Stripe's separate fee for actually moving the money; a publisher comparing Stripe's all-in cost to a competitor's must add both figures rather than reading the Billing price alone as the full cost. The '$8.2B in failed payments' recovered in 2025 is Stripe's own reported aggregate across its entire customer base, not a figure specific to publishing or membership businesses, and it is self-reported rather than independently audited. Because Billing is infrastructure rather than a finished publisher product, how it actually behaves for a given site depends heavily on how the specific membership platform or developer built on top of it, a layer these three pages do not describe.

What to check before you rely on it

As an editorial checklist: get the combined quote, Billing fee plus payment-processing fee, from a specific membership platform or integrator rather than reading Stripe's Billing price in isolation; confirm which plan, pay-as-you-go or the flat annual contract, actually applies to the account in question; and ask whether failed-payment recovery is enabled by default or requires separate configuration.

• What is my platform's total combined fee, Billing plus payment processing, on a typical subscription charge?
• Am I on the 0.7% pay-as-you-go plan or a fixed monthly contract, and which is actually cheaper at my volume?
• Is Stripe's failed-payment recovery active on my account, or does my platform need to enable it separately?

A processor's own headline statistic describes its whole customer base. It says nothing about how a specific membership site's failed payments are actually being recovered.