Subscription billing is software that automatically charges a customer on a recurring schedule (weekly, monthly, annual, custom interval), retries failed payments, prorates plan changes mid-cycle, applies the right tax by jurisdiction, and gives customers a self-serve portal to update their card or cancel.
The platform sits on top of a payment processor (Stripe, Adyen, Braintree) and adds the recurring-charge + dunning + revenue-recognition workflow so a five-person SaaS team does not have to build that infrastructure themselves.
Run a quick stress-test: the day you charge a customer $49 for a monthly SaaS subscription through Stripe Billing or Chargebee,
the platform records the subscription schedule, charges the saved card on day 0, retries on day 1, 3,
and 7 if the first attempt fails, sends a dunning email sequence, applies the right sales tax (Stripe Tax or TaxJar handles the jurisdiction calc),
and posts the recognized revenue to your accounting layer (QBO, Xero, NetSuite) under ASC 606 deferred-revenue rules. Across all of those surface processes,
the customer’s billing portal lets them upgrade from Pro to Team mid-cycle (prorate the difference), pause their subscription, or cancel — all without your support team touching it.
Subscription billing is software that automates recurring-charge collection, dunning retries, plan-change proration, tax jurisdiction, and customer self-serve. The platform sits on top of a payment processor (Stripe, Adyen, Braintree) and adds the recurring-charge workflow so a SaaS team does not have to build it.
Key facts: Subscription billing is the operational layer above a payment processor (Stripe, Adyen) for any business model that charges repeatedly.
Industry default vendors: Stripe Billing (0.7% of transaction for first $1M revenue), Chargebee (0.75% to 1.5% by tier), Recurly (0.9% to 1.4% by tier), Paddle (merchant-of-record model, takes a 5%+ cut), Square Subscriptions (for brick-and-mortar).
Most subscription billing platforms charge a per-transaction percentage plus, on higher tiers, a monthly platform fee plus the embedded payment processor fees.
The structural distinction from one-time payment processing: a one-time payment processor handles a single charge; subscription billing handles the lifecycle (creation, dunning, proration, retention).
A US SaaS operator that charges 200 subscribers at $49 per month runs about $9,800 MRR.
With Stripe Billing at 0.7% + 2.9% + $0.30 per transaction, the billing platform costs about $125 per month at 200 subscribers.
The recovery-rate upside: a smart-retry system that recovers an extra 15% of failed payments saves a SaaS at $40K MRR roughly $600 per month in churn — more than the platform fee itself.
How subscription billing actually works step by step
The mechanics resolve into eight steps that happen at every billing cycle. Once you see the loop, the platform pricing makes sense.
Step 1: capture the customer and card. The signup flow uses Stripe Elements / Stripe Checkout (or a hosted-page equivalent from Chargebee / Recurly) to capture the customer’s card, billing address (for tax), and agreed-to-recurring-charge consent. The ESIGN-compliant audit trail (covered in the cluster’s what is an electronic signature article) records the customer consent to recurring charges.
Step 2: create the subscription. The platform attaches the saved card to a subscription record: amount ($49/month), currency (USD), interval (monthly), start date, optional trial period (7-30 days typical), and price ID (Stripe Price object, Chargebee Plan, etc.). The subscription is the unit a SaaS scales.
Step 3: schedule the charge. The platform’s scheduler triggers a charge attempt at the billing interval. Most platforms batch charges (Stripe Billing charges at the same minute the subscription started, plus a small jitter to avoid API contention).
Step 4: attempt the charge. The first charge attempt runs through the payment processor. If the card is valid and the bank approves, the charge succeeds; revenue is recognized at the moment of successful charge (cash-basis accounting) or over the delivery period (accrual-basis accounting under ASC 606, covered in the SaaS revenue recognition article).
Step 5: retry on failure. If the charge fails (insufficient funds, expired card, fraud block, 3DS challenge failed), the platform’s dunning system schedules retries. Stripe’s smart retries use Bayesian timing to find the day-of-month and time-of-day with the highest historical success rate for that card. Recurly’s retries are configurable per currency. Chargebee’s defaults are 4 attempts over 7 days.
Step 6: send dunning emails. When a charge fails, the platform sends the customer a “your payment failed, please update your card” email, with progressive urgency. Most platforms offer templated sequences and A/B testing.
Step 7: prorate plan changes. When a customer upgrades from Pro to Team mid-cycle, the platform prorates: charges the price difference immediately, refunds the unused Pro portion, and re-anchors the next billing date. The math is built into the platform; a custom SaaS implementation would be 100+ lines of code.
Step 8: host the customer portal. The customer can update their card, change their plan, pause their subscription, cancel, view invoices, and download tax invoices — all through a self-serve hosted page (Stripe Customer Portal, Chargebee Self-Serve Portal). The hosted page eliminates the support load for routine changes.
What subscription billing handles that payment processing alone does not
Five capabilities that a Stripe Connect or Square account alone does not give you, which is why SaaS teams adopt a dedicated subscription billing platform.
Recurring-charge schedule and lifecycle. A plain Stripe Payment Intent charges once. To charge monthly with retries, the SaaS team would have to build a scheduler (cron job), a retry logic (Bayesian timing), a card-update flow (handle expired cards), and an invoice emission pipeline. Subscription billing packages all of that.
Subscription state machine. A subscription has states (trialing, active, past_due, canceled, incomplete) that the platform manages. Switching from past_due to canceled is handled by the platform’s dunning policy; building it from scratch is 50+ hours of engineering.
Customer self-service. The hosted portal (Stripe Customer Portal, Chargebee Self-Serve Portal) lets customers update their card, change their plan, and cancel without emailing support. Most SaaS teams adopt a subscription billing platform partly for this alone — the support cost reduction is larger than the platform fee.
Revenue recognition and tax. For accrual-basis SaaS accounting, ASC 606 requires revenue to be recognized over the service delivery period, not at the moment of charge. The platform posts the deferred-revenue entry to QBO / Xero / NetSuite; the alternative is a manual journal entry per invoice per month.
Smart-retry on failed payments. The single largest revenue-recovery feature for SMB SaaS. Stripe Billing’s smart retries recover 15% more revenue than naive retry logic, per Stripe’s published benchmarks. At $40K MRR, that’s $600/month saved. The math pays for the platform.
Subscription billing vs recurring payments vs merchant of record
Three adjacent pricing and operational models to distinguish.
| Model | What it is | Who owns tax + compliance | Cost structure |
|---|---|---|---|
| Subscription billing | Software on top of Stripe / Adyen / Braintree that adds recurring-charge + dunning + plan-change + portal | The SaaS operator (you sell, you collect, you file) | 0.7%-1.5% of transaction (varies by vendor) |
| Recurring payments (plain) | A bare Stripe Subscription or Recurly Charge on a saved card without platform-managed dunning | The SaaS operator | Stripe per-transaction fees only (2.9% + $0.30 US) |
| Merchant of record (MoR) | A reseller like Paddle / Lemon Squeezy / FastSpring that sells on your behalf and owns tax + compliance globally | The MoR (Paddle, Lemon Squeezy, FastSpring) | 5%-10% of transaction (the MoR takes a margin) |
The three models differ on ownership of tax + compliance + global payout.
For a US SaaS operator selling primarily to US SMB customers, subscription billing (Stripe Billing / Chargebee) gives the most control at the lowest fee.
For an operator selling globally with VAT / GST exposure, the merchant-of-record model removes the tax-compliance burden but trades away margin.
The structural distinction is covered in detail on the subscription billing vs recurring payments page.
What subscription billing is NOT
Three common confusions worth naming.
Not a payment processor. Subscription billing sits ON TOP of Stripe / Adyen / Braintree / Square. Stripe Subscriptions / Stripe Billing is itself a bundle; the underlying payment processing happens at Stripe. Chargebee, Recurly, Maxio use Stripe or Braintree under the hood by default but can route to other processors.
Not an invoicing tool. FreshBooks / Wave / Bonsai are invoicing tools for service businesses (one-time + recurring invoice collections). Subscription billing is operational infrastructure for SaaS / DTC / membership businesses that run a recurring-revenue model.
Not a CRM or contract management tool. The subscription billing platform manages the recurring-charge + dunning + plan-change. Customer relationship management and contract authoring are separate (HubSpot / Salesforce / DocuSign / Bonsai).
Practical implications for a small business
Three operating decisions that follow from choosing a subscription billing platform.
“Which payment processor pairs with the billing platform?” Stripe Billing pairs with Stripe as the payment processor; that is the canonical default for US SaaS. Chargebee pairs with Stripe / Braintree / Adyen / Authorize.Net. Recurly pairs with multiple processors. The pairing matters because the per-transaction fees compound; verify the processor fees before committing.
“How is revenue recognized under ASC 606?” For accrual-basis accounting (the default for funded SaaS), revenue from a $49/month subscription is recognized $49 over 30 days, not all at the moment of charge. The platform posts the deferred-revenue entry. The accounting details are covered in the SaaS revenue recognition article.
“What about international sales tax / VAT / GST?” Stripe Tax (a Stripe Billing add-on) handles US sales tax by state and EU VAT by member state. Chargebee and Recurly have similar add-ons. For an operator selling globally, the tax-compliance layer is a real cost; merchant-of-record vendors (Paddle, Lemon Squeezy) absorb it.
Pick the right subscription billing platform for your MRR and contract type
For the practical comparison of Stripe Billing, Chargebee, Recurly, Paddle, and Square Subscriptions at each MRR tier, the best subscription billing software for small business comparison walks through each vendor.
For the cost math at your MRR level and the per-transaction fee trade-offs, the subscription billing pricing page covers the math.
For the structural distinction between subscription billing and recurring payments (and when each fits), the subscription billing vs recurring payments page walks through the distinction.
For the underlying payment-processor mechanism that subscription billing sits on top of (recurring card charges, settlement timing, fee structure), the how payment processors work page covers the lower layer.
Last updated: October 2026
