Subscription billing vs recurring payments: the structural distinction

Subscription billing and recurring payments are often used interchangeably, but they describe different layers of the revenue stack.

Subscription billing is software that automates recurring-charge collection, dunning retries, plan-change proration, tax jurisdiction, customer self-serve, and revenue recognition on top of a payment processor.

Recurring payments (in the strict sense) is the underlying mechanism — a card on file that the payment processor re-charges on a schedule — without the subscription-billing layer’s dunning, proration, and hosted portal workflows.

All subscription billing uses recurring payments under the hood; not all recurring payments use subscription billing.

Run a quick stress-test: when a SaaS operator uses plain Stripe Subscriptions (or the legacy Stripe Subscriptions API) without ever adopting Stripe Billing, Chargebee, Recurly, or Maxio, the operator has recurring payments — the card is on file, Stripe charges monthly, the invoice is emailed.

What the operator does not have is smart retries (you would have to build the retry logic), proration (Stripe will calculate but you need to handle the upgrade flow UI), the hosted customer self-serve portal (or you build one), and revenue recognition posting (or you manual-journal-entry it each month).

Adopting Stripe Billing, Chargebee, or Recurly turns “recurring payments” into “subscription billing”.

Subscription billing is software that manages the recurring-revenue lifecycle (charges, dunning, proration, portal, recognition). Recurring payments is the underlying mechanism: a card on file that the payment processor re-charges on a schedule, without the lifecycle infrastructure. All subscription billing uses recurring payments; not all recurring payments use subscription billing.

Key facts: Recurring payments in the strict sense is the Stripe Subscriptions / Stripe Payment Intents API on a stored card.

Subscription billing is the platform layer (Stripe Billing, Chargebee, Recurly, Maxio) that adds the lifecycle.

A retailer that takes a card on file at checkout and charges it for a one-time repeat purchase uses recurring payments but not subscription billing.

A SaaS operator that charges subscribers monthly with smart retries + plan-change proration uses subscription billing.

Merchant of record (Paddle, Lemon Squeezy) is a separate model where the MoR sells on the operator’s behalf and handles all tax + compliance.

The structural distinction in plain language

Both terms are widely used in marketing copy and often conflated. The structural distinction is about which capabilities the platform handles.

The cost of “recurring payments only” is not the absence of per-transaction fees; it is the engineering and support time to build the lifecycle. For a five-person SaaS team, that adds up to ~$10K-$30K in engineering cost per quarter — more than a year of Stripe Billing fees at typical MRR.

What subscription billing adds on top of recurring payments

Subscription billing is recurring payments + five capability layers. The capabilities matter when the operator’s revenue depends on them.

Smart retries on failed payments. Naive retry logic (charge again in 3 days) recovers some failed payments; smart retries (Bayesian model that picks the day-of-month / time-of-day / card-update cycle with the highest historical success rate) recover 15% more revenue per Stripe’s published benchmarks. For a SaaS at $40K MRR, that is $600/month or $7,200/year saved.

Plan-change proration. When a customer upgrades from Pro ($49/month) to Team ($99/month) mid-cycle, the platform prorates: charges $50 immediately for the remaining days, refunds the unused $24.50 of Pro, and re-anchors the next billing date to the upgrade day. Building this from scratch is non-trivial; Chargebee and Stripe Billing’s Proration API handle it.

Customer self-serve portal. The hosted page (Stripe Customer Portal, Chargebee Self-Serve Portal, Recurly Account Portal) lets customers update their card, change their plan, pause, or cancel without emailing support. For a SaaS with 5K+ subscribers, this eliminates 5-15 hours/week of support load — a meaningful cost reduction.

Tax by jurisdiction. Stripe Tax (a Stripe Billing add-on) calculates US sales tax by state and EU VAT by member state. Chargebee and Recurly have similar add-ons. The compliance value: for a SaaS selling in 30 US states, the operator does not have to track nexus, calculate tax, or file returns themselves. Stripe Tax charges per-transaction at $0.50/month minimum.

Revenue recognition under ASC 606. For accrual-basis SaaS accounting, revenue from a $49/month subscription is recognized $1.63/day over 30 days, not $49 at the moment of charge.

The platform posts the deferred-revenue entry to QBO / Xero / NetSuite.

Stripe Revenue Recognition (formerly Stripe Sigma Revenue) is a separate add-on at $0.50/month minimum; Maxio (formerly SaaSOptics) bundles it.

The accounting details are covered in the SaaS revenue recognition article.

When each one applies in practice

Three operating scenarios make the distinction matter.

One-time repeat purchases (coffee subscription box without a portal). Recurring payments is enough. The card is on file, the operator charges monthly, the invoice is emailed. No need for Chargebee; Stripe Subscriptions API alone handles it.

Mid-market SaaS with 100+ subscribers and churn sensitivity. Subscription billing is the right answer. Smart retries + plan-change proration + a self-serve portal handle the customer-experience load. Stripe Billing, Chargebee, Recurly, Maxio are all candidates.

DTC subscription box at high monthly volume. Subscription billing is canonical. The churn analytics (Recurly’s strength) help operators tune the box, the dunning handles the inevitable failed-charge rate, and the hosted portal lets customers skip / pause / change frequency.

The marketing copy conflations

The terms get used interchangeably because the legal effect (a recurring charge) is the same and the layer is invisible to most users. Three places where the conflation hurts a SaaS team.

Confusion 1: “Stripe Subscriptions” vs “Stripe Billing”. Same product after Stripe renamed “Stripe Subscriptions” to “Stripe Billing” in 2023. The legacy Stripe Subscriptions API is still available but is being deprecated in favor of Stripe Billing. The capability difference: Stripe Billing adds proration, smart retries, revenue recognition, and the customer portal on top of the legacy Subscriptions API.

Confusion 2: “Recurring billing” in product marketing. Most vendors use “subscription billing” in their product copy; some use “recurring billing”. The market uses both terms; structurally they refer to the same layer (subscription billing = the platform, recurring billing = the action).

Confusion 3: Merchant of record vs subscription billing. Paddle / Lemon Squeezy / FastSpring are “merchant of record” (MoR) services, NOT “subscription billing platforms”.

The MoR sells on the operator’s behalf and owns tax + compliance globally; the operator receives a net payout.

The MoR model is structurally different from subscription billing; some MoRs (Paddle) do include subscription-billing capabilities (recurring charges), but the operating model is MoR, not SaaS seller.

Practical implications for a US SMB

The decision rule for most US SMBs is straightforward: use subscription billing from day one — the engineering cost of building the lifecycle on plain recurring payments is higher than the platform fee at any MRR above ~$2K.

For a SaaS operator at $10K MRR, the math is: Stripe Billing costs ~$70/month in platform fees (0.7% of $9.8K). The alternative — building the equivalent in-house — costs $10K-$30K in engineering time per quarter. Subscription billing pays for itself by month 2 at this MRR.

For an operator at $1K MRR (very early stage), the math is closer: Stripe Billing’s 0.7% adds $7/month at $1K MRR, but the engineering cost of building the lifecycle is still $10K-$30K per quarter.

The platform is the right answer at any MRR above ~$500; below that, plain Stripe Subscriptions API is fine, and Stripe Billing is the right answer before the operator’s first failed-charge wave.

For the cost math at your MRR level and the per-vendor fee structure, the subscription billing pricing page covers the math.

For the practical comparison of the three canonical subscription billing vendors at each MRR tier, the Stripe Billing vs Chargebee vs Recurly page runs the comparison.

For the broader vendor coverage (Paddle, Maxio, Square Subscriptions, Pabbly) and the right pick for your business shape, the best subscription billing software for small business comparison covers the math.

For the underlying mechanism of how payment processors route the card-on-file that subscription billing manages — including settlement timing and chargeback handling — the how payment processors work page covers the lower layer. For the broader entity definition of what subscription billing is end-to-end, the what is subscription billing page walks through the lifecycle.

Last updated: October 2026