SaaS Subscription: How Recurring Subscriptions Work in SaaS
A SaaS subscription is the recurring payment engine of the software industry. Six subscription lifecycle states (trial, active, past due, cancelled, upgraded, annual), the correct Stripe webhook implementation for each, and how to handle cancellations without losing the relationship.
How Recurring Subscriptions Work in Software-as-a-Service
A SaaS subscription is a recurring payment agreement where a customer pays a fixed monthly or annual fee for ongoing access to a software product. The SaaS subscription model is the revenue engine of the software industry: it creates predictable, compounding revenue for the vendor and low-barrier, always-updated access for the customer. The key elements are: subscription tier (the plan and its features), billing interval (monthly or annual), trial period (typically 7-30 days), and the lifecycle events (activation, renewal, upgrade, downgrade, cancellation, and failed payment).
The subscription model creates aligned incentives: the vendor earns only as long as the customer finds value. This structural alignment is why SaaS products are generally better-maintained, better-supported, and faster-evolving than one-time software licences. The vendor’s revenue depends on continuous delivery of value.
Every State a Customer’s Subscription Passes Through
Trial
The customer explores the product without paying. Typically 7-30 days. The trial is the highest-risk phase: most churn happens here. Strong onboarding, activation tracking, and trial-ending email sequences maximise trial-to-paid conversion.
Active
Payment successful; customer has full plan access. The ongoing state. Revenue is recognised. The vendor’s focus: deliver value, minimise churn, identify expansion opportunities.
Past Due
Payment attempt failed. Stripe automatically retries. Customer is in a grace period. The vendor should: show an urgent payment banner in-app, send a failed payment email sequence, and preserve access during the grace period to maintain the relationship while payment is being resolved.
Cancelled
The subscription has ended. Either voluntary (customer cancelled) or involuntary (payment retry exhausted). Data is preserved. Access is restricted. Reactivation is made easy. Churn interview is sent within 24 hours.
Upgraded
Customer moved to a higher plan. Revenue increases immediately. Plan limits update immediately. An upgrade confirmation email is sent. This is an expansion event — the most capital-efficient revenue growth.
Annual
Customer paid for a full year upfront. Revenue recognised monthly (for MRR calculations). Customer retention locked in for 12 months. Annual plan customers churn at 40-60% lower rates than month-to-month customers.
The Correct Stripe Integration Pattern
Every subscription lifecycle event above is triggered by a Stripe webhook event. SA implements all six on every Bubble.io SaaS product it builds. The subscription status on the Workspace record is updated exclusively by these webhooks — never by a redirect URL, never by a manual workflow, never by a user action.
| Lifecycle Event | Stripe Webhook | What Bubble Does |
|---|---|---|
| Trial converts to paid | checkout.session.completed | Set status=Active; store stripe_sub_id; set plan from price ID |
| Subscription renewed | invoice.payment_succeeded | Confirm status=Active; update current_period_end |
| Payment fails | invoice.payment_failed | Set status=Past_Due; show payment banner; send email |
| Customer cancels | customer.subscription.deleted | Set status=Cancelled; preserve data; show reactivation prompt |
| Customer upgrades/downgrades | customer.subscription.updated | Update plan; update status; adjust plan limits immediately |
| Trial ending soon | customer.subscription.trial_will_end | Schedule conversion email; show upgrade prompt in app |
Free SaaS Tech Audit — 30 Minutes, No Cost
Athar Ahmad personally reviews your SaaS product: security vulnerabilities, billing gaps, performance anti-patterns — identified and ranked before they cost you customers, deals, or investor confidence.
- Multi-tenant security and privacy rule assessment
- Stripe billing architecture review
- Performance bottleneck identification
- Written remediation roadmap within 24 hours
Q: How do I handle SaaS subscription cancellations?
When a customer cancels: (1) preserve all their data, (2) restrict access to read-only or limited mode, (3) show a clear reactivation option, (4) send a cancellation confirmation with a ‘we’re sorry to see you go’ and a one-click reactivation link, (5) email within 24 hours for a churn interview.
Q: Should SaaS subscriptions auto-renew?
Yes. Auto-renewal is the standard SaaS model. Customers are informed of auto-renewal at signup and in the billing confirmation email. Stripe handles the automatic charge attempt. The customer cancels to stop renewal. Without auto-renewal, your revenue is not truly recurring.
Q: How do I handle SaaS subscription upgrades mid-cycle?
Stripe automatically prorates the price difference when a customer upgrades mid-billing cycle. The customer is charged the difference between the old plan and the new plan for the remaining days in the current billing period. In Bubble, the customer.subscription.updated webhook fires and your app updates the plan and limits immediately.
Build or Fix Your SaaS. Two Paths. Both Lead to Better Outcomes.
Free Tech Audit for SaaS products that exist and need assessment. Discovery Sprint to scope and price new SaaS ideas correctly before a single line is built.
