SaaS Subscription Billing: Integration Guide
Billing is the part of a SaaS product that founders most often underestimate. Taking a card payment once is easy. Charging the right amount every month, handling upgrades halfway through a cycle, retrying failed cards, issuing compliant invoices, collecting sales tax or VAT and keeping your app’s access rights in sync is not. Done well, SaaS subscription billing is invisible to customers and gives you reliable revenue data. Done badly, it leaks revenue, generates support tickets and makes pricing changes painful.
This guide covers the decisions and integration patterns we use when adding billing to products in our SaaS application development projects.
Choose Your Pricing Model First
Your pricing model determines how complex the billing integration will be, so settle it before choosing a platform. Flat and per-seat plans are simple; usage-based and hybrid pricing need metering infrastructure.
| Model | Example | Integration complexity |
|---|---|---|
| Flat rate | $49 per month for everything | Low |
| Tiered plans | Starter, Growth, Business with feature limits | Low to medium |
| Per seat | $12 per user per month | Medium (seat changes, proration) |
| Usage-based | $0.002 per API call or per GB processed | High (metering, aggregation, invoicing in arrears) |
| Hybrid | Base fee plus usage above an included allowance | High |
Start with the simplest model your customers will accept. You can add usage components later, but migrating existing subscribers between pricing models is real work. Our guide on how to build a SaaS product discusses pricing validation in more depth.
Billing Platform Options
Almost no early-stage SaaS company should build a billing engine from scratch. The real choice is between a payment provider with subscription features, a merchant of record that also handles tax, and a dedicated billing layer on top of a payment gateway.
- Payment provider with billing (for example Stripe Billing). Flexible APIs, hosted checkout and customer portal, strong developer tooling. You remain the seller, so tax registration and remittance are your responsibility, although tax calculation add-ons exist.
- Merchant of record (for example Paddle or Lemon Squeezy). The provider is legally the seller, so it handles sales tax and VAT collection and remittance in many countries. Fees are higher and you have less control over the checkout, but international tax compliance is largely taken off your plate.
- Billing layer (for example Chargebee, Recurly or Maxio). Sits on top of one or more gateways and adds advanced subscription logic, revenue reporting and finance workflows. Useful once you have complex plans, sales-led contracts or multiple gateways.
Check regional payment methods too. European customers may expect SEPA Direct Debit, Indian customers UPI-based mandates, and enterprise buyers often want to pay by invoice and bank transfer.
How a SaaS Subscription Billing Integration Fits Together
The billing provider should be the source of truth for subscriptions and payments, and your application should be the source of truth for what each customer can access. Webhooks connect the two.
- Catalog: define products, prices and plans in the billing platform, referenced by ID in your code rather than hard-coded amounts.
- Checkout: use the provider’s hosted checkout or embedded payment elements so card data never touches your servers. This keeps your PCI DSS scope to the simplest self-assessment level.
- Customer mapping: link each tenant or account in your database to its billing customer ID.
- Webhooks: listen for events such as subscription created, updated, cancelled, invoice paid and payment failed. Verify signatures, process idempotently and store event IDs to ignore duplicates.
- Entitlements: translate the current plan into feature flags and limits in your app, such as seats, projects or API quota. Check entitlements in your backend, never only in the UI.
- Self-service portal: let customers update cards, download invoices and change plans without contacting support.
- Reconciliation: run a scheduled job that compares billing state with app state and alerts on mismatches, because webhooks occasionally fail or arrive out of order.
Handling the Tricky Cases
The edge cases, not the happy path, are where billing integrations consume time. Decide your policy for each before writing code.
Upgrades, downgrades and proration
A common approach is to apply upgrades immediately with a prorated charge and apply downgrades at the end of the billing period, so customers are never charged twice and never lose features they paid for. Decide what happens to data that exceeds a lower plan’s limits.
Failed payments and dunning
Cards expire and get declined. Use automatic smart retries, card updater services where available, and a sequence of reminder emails. Define a grace period before restricting access, and make the restriction gradual (read-only before lockout) so you recover revenue without angering customers.
Strong customer authentication
In the European Economic Area and the UK, many online card payments must support strong customer authentication through 3D Secure. Modern payment providers handle this, but your flows must cope with a payment that needs the customer to come back and authenticate.
Trials and free plans
Decide whether trials require a card up front. Card-required trials convert at a higher rate but attract fewer sign-ups. Either way, send a reminder before the first charge to reduce disputes.
Tax and invoicing
Digital services are taxed differently across jurisdictions, and B2B customers often need VAT or GST numbers on invoices. Either use a merchant of record, or a tax calculation service with your own registrations, and take advice from an accountant on where you must register.
Mobile app subscriptions
If you sell digital subscriptions inside an iOS or Android app, app store rules generally require in-app purchase, with some regional and category exceptions that have changed in recent years. Read the current App Store Review Guidelines and Google Play policies, and design your entitlement service to accept purchases from web and stores alike.
Data, Privacy and Security
Store as little payment data as possible: customer IDs, plan, status and invoice references, never card numbers. Billing records contain personal data, so regulations such as the GDPR apply to retention, access and deletion requests, balanced against legal requirements to keep financial records. Restrict who on your team can issue refunds or credits, and log every manual billing action.
What a Billing Integration Costs
Integration effort ranges from a few days to several months depending on pricing complexity. These indicative figures assume an existing SaaS product and a mainstream billing platform.
| Scope | Indicative cost (USD) | Typical timeline |
|---|---|---|
| Hosted checkout, one or two flat plans, customer portal, basic webhooks | $3,000 – $8,000 | 1 – 2 weeks |
| Tiered and per-seat plans, proration, entitlements, dunning, trials | $8,000 – $25,000 | 3 – 6 weeks |
| Usage-based or hybrid pricing with metering, multi-currency, invoicing for enterprise, finance reporting | $25,000 – $70,000+ | 2 – 4 months |
For the wider picture of what a SaaS product costs to build and run, see our SaaS development cost guide. If you are serving many organizations from one codebase, billing also interacts with your multi-tenant SaaS architecture.
Frequently Asked Questions
Should I use Stripe or Paddle for SaaS billing?
Stripe offers more flexibility and lower base fees, but you handle tax registration yourself. Paddle acts as merchant of record and handles tax collection and remittance, which suits small teams selling internationally that want less compliance work.
Do I need to be PCI compliant if I use Stripe?
Yes, every business accepting cards has PCI DSS obligations, but using hosted checkout or embedded payment fields keeps card data off your servers and reduces your obligations to a short self-assessment.
How do I handle usage-based SaaS subscription billing?
Record usage events in your own system, aggregate them per billing period, and report them to the billing platform, which invoices in arrears. Show customers their current usage in-app to avoid bill shock.
Can we change pricing after launch?
Yes. Create new prices rather than editing old ones, keep existing customers on legacy plans or migrate them with notice, and make sure your entitlement logic reads from plan configuration rather than hard-coded rules.
Get Billing Right the First Time
Sigmato’s team in Bengaluru and the UK integrates subscription billing, entitlements and payment flows into web applications and mobile apps. We can review your pricing model and recommend the simplest setup that will scale with you.
Sources and References
