Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages

Help for owners

I need recurring billing in my SaaS and do not know where to start

Short answer

Subscription billing is a lifecycle: a customer subscribes, pays each period, sometimes fails to pay, upgrades or cancels, and your app must grant or remove access at each step. Decide your plans and what happens on failure first, then connect them to the billing provider's events.

  • Written for business owners
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Does this sound like your situation?

  • I take payments by hand or invoice and want it automatic.
  • Customers keep access after they stop paying.
  • Failed card payments are not followed up.
  • I want free trials, upgrades or different plans.
  • I do not know what my app must do when a payment fails.

Why does this happen?

  1. The provider handles billing, your app handles access

    Stripe's documentation says it creates invoices, attempts collection and manages the subscription's status. Your app still has to decide what a customer can use at each status.

  2. Payment states are many

    A subscription can be trialing, active, incomplete, past due, unpaid, paused or canceled according to Stripe, and each needs a clear rule in your product.

  3. Failed renewals are normal

    Stripe says a failed renewal makes the subscription past due and that retry settings decide what happens after the last attempt. Your app should tell the customer and follow the status.

  4. Webhooks keep both sides in step

    Billing events reach your server as webhooks, which must be verified and processed safely.

What can I do about it today?

  1. Write down your plansNames, what each includes, billing period and whether there is a trial. Keep it to a small number.
  2. Decide what happens when a payment failsFor example a reminder, a grace period, then limited access. This is a business decision.
  3. Open the billing account in your company's nameUse a company email and do the identity steps yourself.
  4. Use test mode only at firstNothing should be charged to real customers until every path has been tested.
  5. Tell existing customers before changing how they payA clear message avoids surprise charges and support tickets.

When should I bring someone in?

  • You already have paying customers and the change must not interrupt them.
  • You sell in several countries and are unsure about tax rules. Ask a qualified tax adviser.
  • Customers are keeping access without paying.

How do I handle it?

  1. Map your plans to the providerI set up products and prices in test mode and match them to features in your app.
  2. Build the access rulesYour app grants and removes access based on verified billing events, not on the browser.
  3. Handle the unhappy pathsFailed payments, expired cards, cancellations and upgrades are each tested.
  4. Move existing customers carefullyCurrent customers are brought across in a way that does not charge them twice.
  5. Add a customer portal and alertsCustomers can update their card, and you are told when events fail.

The price depends on what I find, so I quote in writing after a short discovery call. Tell me what is happening and I reply within 24 hours.

What do owners ask about this?

Which billing provider should I choose?

It depends on where you sell and who handles tax. I compare options using each provider's own documentation.

Can customers upgrade or cancel themselves?

Yes, through the provider's customer portal or screens in your app.

Will existing customers be charged twice?

Not if the move is planned. I test the migration before it touches real customers.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Found a mistake? Tell me.

For your developer: the technical fixes

Next step

Want this off your desk?

Send me a few lines on where things stand. I reply within 24 hours.