Recurring Payments and Subscriptions
Everything you need to know to build a reliable and scalable recurring billing system
Subscription models have transformed entire industries: from software (SaaS) to streaming, food delivery and professional services. Their success hinges on generating predictable, recurring revenue — but implementing a robust recurring billing system is more complex than it appears.
This guide covers the technical and strategic aspects of recurring payments: billing models, failed payment management (dunning), proration, available tools and implementation best practices.
Recurring billing models
Not all subscriptions are the same. The billing model defines how and when you charge your customers, and it has a direct impact on retention, churn and perceived value.
- Flat rate: fixed monthly or annual price for full access (e.g. Netflix, Spotify). Simple to implement, easy to communicate
- Tiered: different plans with escalating features (e.g. Slack Free, Pro, Business). Enables natural upselling
- Usage-based: charges based on actual consumption (e.g. AWS, Twilio). Attractive for customers, complex to invoice
- Hybrid: combines a base fee with a variable component (e.g. HubSpot). Offers predictability and scalability
- Freemium + premium: limited free version with upgrade to paid plan. Lowers the entry barrier
Dunning: managing failed payments
Between 5% and 10% of recurring payments fail in each billing cycle. The most common causes are expired cards, insufficient funds or issuer blocks. Without a dunning strategy, these failures translate directly into involuntary churn.
An effective dunning process combines automatic retries with email communication. A typical sequence includes an immediate retry, another at 24–48 hours with customer notification, a third attempt at 5–7 days and, if it fails, service suspension with the option to update the payment method.
- Configure smart retries: vary the day and time to maximise success probability
- Send pre-dunning emails before the card expires
- Offer multiple alternative payment methods (SEPA, direct debit, wallet)
- Use automatic card updaters that renew expired card data with the issuer
Proration and plan changes
When a customer changes plan mid-cycle, proration calculates the difference between what was paid and what is owed. An incorrect implementation generates confusion, complaints and loss of trust.
Stripe Billing, Chargebee and Recurly handle proration automatically, calculating proportional credits and charges down to the day. The most important design decision is whether you charge the difference immediately, accumulate it on the next invoice or apply it as a credit.
Tools for managing subscriptions
There are two main approaches: using the built-in billing from your payment gateway or adopting a dedicated subscription management platform. The choice depends on the complexity of your billing model.
- Stripe Billing: the most popular option for startups and SaaS. Supports proration, dunning, coupons, trials and usage-based billing
- Chargebee: independent platform that integrates with multiple gateways. Strong in revenue recognition and analytics
- Recurly: specialised in enterprise subscription management with advanced dunning and revenue optimisation
- Paddle: combines gateway + billing + taxes as merchant of record. Simplifies tax operations
- Zuora: enterprise solution for complex billing models with multiple product lines
Technical implementation
A solid recurring payment implementation goes beyond creating an endpoint that charges every month. It requires managing subscriber states (active, paused, cancelled, delinquent), synchronising billing with service access and maintaining an auditable record of every transaction.
Webhooks are the centrepiece of the architecture. Your system must listen for events like invoice.paid, invoice.payment_failed, customer.subscription.updated and customer.subscription.deleted to keep state synchronised. Process these events idempotently to avoid duplicate charges.
- Design a clear state machine for the subscription lifecycle
- Implement idempotent webhooks with signature verification
- Store the billing state as the source of truth, not local state
- Generate invoices and receipts compliant with each country’s tax regulations
Key metrics and optimisation
A subscription business is managed with specific metrics that go beyond gross revenue. MRR (Monthly Recurring Revenue), churn rate, LTV (Lifetime Value) and CAC (Customer Acquisition Cost) are the fundamental indicators.
To reduce involuntary churn, optimise your dunning flow and offer account updaters. To reduce voluntary churn, work on the value proposition, user experience and proactive communication. A single percentage point reduction in churn can represent a substantial increase in annual revenue.
Key Takeaways
- The billing model (flat, tiered, usage-based, hybrid) defines the customer experience and technical complexity
- A good dunning system can recover between 30% and 70% of failed payments
- Correct proration is critical for maintaining trust when customers change plans
- Choose between built-in billing (Stripe) or a dedicated platform (Chargebee, Recurly) based on your complexity
- Idempotent webhooks are the foundation of a robust technical implementation
Want to implement recurring payments on your platform?
We help you design and integrate a robust subscription system, from tool selection to dunning optimisation.