SaaS Subscription Billing India: Razorpay, UPI and GST

You have a working product and the first customers want to pay monthly. Then the questions arrive: should they pay by card or UPI, who sends the invoice, what happens when a card expires, and how do you add GST without a spreadsheet? SaaS subscription billing India has a few local rules that overseas billing tutorials do not cover.

This guide explains the pieces of a billing system, how Razorpay's subscription objects work, what RBI's recurring payment rules mean for your product, and the order in which to build it. It is written for founders and product owners who need to brief a development team.

What is SaaS subscription billing?

SaaS subscription billing is the system that charges customers on a repeating schedule, issues invoices and keeps each customer's access in line with what they have paid for. It sits between your payment gateway, your database and your product's permission checks.

A healthy billing design separates four things:

• Plan: a price and a billing cycle, such as ₹2,999 per month or ₹29,990 per year.
• Subscription: the link between one customer account (a tenant) and one plan, with a status such as trial, active, past due or cancelled.
• Invoice: a record of one charge, with tax details, which you can email or download.
• Entitlement: what the customer may do, such as seats, projects or API calls, derived from the subscription status.

Keep this state in your own database. The payment gateway is the source of truth for money movement, but your app should own the customer's plan so you are not locked to one provider. This is the same boundary we describe in our guide to multi-tenant SaaS architecture, where plan limits are stored on the tenant record.

Which payment methods should an Indian SaaS support?

An Indian SaaS should support cards, UPI Autopay and eMandate, because customers split across all three and each fails in different ways. Razorpay's supported payment methods page lists these three for Subscriptions, with different limits.

Two practical points. First, UPI Autopay mandate registration through Razorpay now uses UPI Intent, because the UPI Collect flow was deprecated for new registrations from 28 February 2026, with an iOS fallback. Second, limits depend on your merchant category, so check Razorpay's current limits table before you promise a price point to customers.

What do RBI's recurring payment rules mean for your product?

RBI's rules mean that every recurring charge must be consented to, announced in advance and easy to stop. The central bank's e-mandate directions cover cards, UPI and prepaid instruments, and they shape your user experience:

1. Registration needs additional factor authentication (AFA). The customer authorises the mandate once, and the first transaction is also authenticated.
2. A pre-debit notification goes out at least 24 hours before the charge. It names the merchant, amount, debit date and mandate reference.
3. Recurring debits up to ₹15,000 can run without AFA. Larger amounts need fresh authentication, though some categories such as mutual funds, insurance premiums and credit card bills have a higher threshold.
4. Customers can opt out of a debit or cancel the mandate. Modifications also need authentication.

For product design, this means a few things. Do not try to bill on the exact minute a trial ends, because the notice period has to run first. Show the next charge date and amount inside the app. Offer a simple cancel button. And for plans above ₹15,000 per charge, expect the customer to authenticate each time or choose eMandate or invoice-based payment.

These rules are updated from time to time, so confirm the latest text on the RBI site or with your payment provider before launch.

How do Razorpay plans and subscriptions work?

Razorpay models billing with a plan that you create once and a subscription that attaches a customer to it. According to the Razorpay Subscriptions API documentation, a plan defines the period (daily, weekly, monthly, quarterly or yearly), the interval, and an item with name, amount and currency. A subscription then references the plan_id and a total_count of billing cycles, with optional trial start, quantity and add-ons.

The quantity field suits per-seat pricing. If your software costs ₹100 per licence per month and a customer buys five seats, Razorpay charges ₹500 each cycle.

The webhooks are where your product comes alive. The ones you will use most are:

Verify webhook signatures, make your handlers idempotent so a repeated event cannot double-apply, and store the raw event for debugging.

How should you handle failed payments?

You should treat a failed payment as a normal lifecycle event with a clear customer journey, because card expiry, low balance and bank declines are routine. Razorpay's payment retries documentation says a failed card charge moves the subscription to pending and is retried automatically for up to three days after the charge date. If every retry fails, the subscription moves to halted, and the customer must retry or change the payment method.

A sensible dunning flow looks like this:

1. Day 0: the charge fails. Show an in-app banner and send an email with a link to update the payment method.
2. Days 1 to 3: let the automatic retries run, and send one reminder.
3. Halted: keep the account readable but restrict creating new data, for a grace period you define.
4. After the grace period: downgrade to a free or read-only plan, and keep the data for a stated period so a late payer can return.

Note that when a halted subscription becomes active again, Razorpay does not re-attempt earlier invoices, only future cycles. Your app should record any unpaid invoice and offer a manual pay link.

How do GST, proration and refunds fit in?

GST, proration and refunds are business rules first and code second, so decide them before the billing screens are designed. For Indian customers, a software subscription is generally a taxable service, and your invoice should carry your GSTIN, the customer's GSTIN for B2B sales, an invoice number series and the tax split between CGST and SGST or IGST. Exports of services and foreign customers have different treatment, so ask your chartered accountant to confirm rates, place of supply and any LUT requirements.

Then write down the policies your code will enforce:

• Upgrades: charge the difference for the rest of the cycle immediately, or switch at the next renewal.
• Downgrades: apply at the end of the cycle so you never refund partial months by default.
• Cancellations: access continues until the paid period ends.
• Refunds: state the window, if any, in your terms.
• Annual plans: decide whether the discount is a fixed number of free months or a percentage.

Simple rules produce fewer support tickets. A rule you cannot explain in two sentences is hard to implement correctly.

What should you build first? A practical order

Build the data model and the webhook pipeline before the pricing page, because pricing screens are easy to change and money-handling bugs are not.

1. Define plans and entitlements in a table, including seats and usage limits.
2. Create the subscription record on the tenant, with status, current period and provider IDs.
3. Integrate Razorpay Checkout for new subscriptions, using test mode first.
4. Build a webhook handler with signature checks, idempotency and an event log.
5. Add the billing page: current plan, next charge date, invoices and a payment method update link.
6. Add dunning emails and grace periods.
7. Generate GST-compliant invoice PDFs and email them on every successful charge.
8. Test unhappy paths: expired cards, cancelled mandates, upgrades mid-cycle and duplicate webhooks.

If you are still scoping the product, our SaaS MVP cost guide for India shows where billing sits in an early budget, and the REST API design best practices guide covers the API conventions that keep billing endpoints safe.

How Arham Technology approaches SaaS subscription billing

At Arham Technology we design billing alongside tenancy, not after it. Our SaaS development service includes subscription lifecycle wiring for trial, upgrade, cancel and dunning hooks, and we work with Razorpay or Stripe depending on your customers.

Our process for billing work looks like this:

• Problem compression: we confirm who pays, how often, and by which method.
• Tenancy and billing blueprint: plans, subscriptions, invoices and entitlements are modelled before interface work.
• Vertical slice: a customer can sign up, pay in test mode and see the right access.
• Pilot hardening: we test failed payments, plan changes and support lookups with early design partners.
• Scale readiness: background jobs, observability and operator dashboards are tightened as usage grows.

The Node.js and PostgreSQL stack we commonly use suits this work, and our backend development service can take over webhook, queue and API design if you already have a front end. For a comparison of backend options, read our guide to Node.js vs Laravel.

Next step

If you are about to charge your first customers, or your current billing relies on manual invoices, send us a short brief on the contact page. Tell us your plans, expected customers and payment methods, and we will suggest a billing design and a delivery estimate. You can also read about the full SaaS development offering before you reach out.