💳

Business Strategy

Setting Up Subscriptions for Indian Micro SaaS: The Complete Payment Guide

Collecting monthly subscriptions from Indian customers requires understanding UPI mandates, Razorpay setup, GST on SaaS, and avoiding the pitfalls that trip up most first-time founders.

AHAD Team·12 May 2026·8 min read

Why Indian Payments Are Different

Building a subscription payment system for Indian customers is not the same as building one for US or European customers. India has unique payment methods, regulations, and customer behaviors that affect how you collect monthly revenue.

Understanding these differences before you launch prevents three common problems:

Payment methods that do not work for your customers

Failed recurring charges that destroy customer trust

GST compliance issues that create legal exposure

This guide covers everything you need to collect subscription revenue from Indian customers reliably.

---

Payment Methods Indian Customers Use

UPI AutoPay

UPI has become the dominant payment method for Indian consumers and SMBs. The NPCI (National Payments Corporation of India) launched UPI AutoPay — a recurring mandate feature — which allows customers to set up automatic monthly debits directly from their bank account via UPI.

For Micro SaaS subscriptions, UPI AutoPay is ideal because:

Customers trust it (it is the same UPI they use for everything)
No card required — works for the large portion of SMB owners who do not use business credit cards
Mandate setup is simple via PhonePe, Google Pay, Paytm, or any UPI app
Limits: ₹15,000 per mandate transaction (more than enough for most Micro SaaS pricing)

Implementation: Razorpay's Subscription API handles UPI AutoPay mandate creation natively. When a customer subscribes, you send them a mandate authorization link that they complete in their UPI app. After approval, Razorpay handles the monthly auto-debit automatically.

Debit and Credit Cards

Card-based recurring payments work well for businesses with company cards or individuals with credit cards. The auto-debit mechanism requires a second-factor authentication (OTP or 3DS) for the first charge; subsequent monthly charges are typically processed without requiring OTP under recurring mandate rules.

Net Banking

Net banking-based subscriptions are available but have higher friction for customers (requires logging into internet banking to authorize). Use as a fallback, not a primary option.

NACH (National Automated Clearing House)

NACH is the traditional bank auto-debit mechanism for larger amounts and enterprise clients. It requires more paperwork (physical or e-NACH mandate) and takes 3–7 days to process. Relevant for enterprise deals but not typical B2SMB subscriptions.

---

Razorpay Setup: Step-by-Step

Razorpay is the recommended payment gateway for Indian Micro SaaS products. Here is how to get operational:

Step 1: Create and Verify Your Business Account

Go to razorpay.com and create a business account. You will need:

Your business type (if a registered company: GST certificate, PAN, company registration; if sole proprietor: personal PAN, bank account proof)
Bank account for settlements
Business website URL (your landing page works during early stage)

Verification typically takes 2–5 business days. You can use test mode immediately.

Step 2: Create Subscription Plans

In the Razorpay dashboard under Products → Subscriptions, create your plans:

` Plan Name: Core Monthly Interval: 1 month Amount: 199900 (paise, for ₹1,999) Currency: INR `

Create plans for each pricing tier (Starter, Core, Professional) and each billing period (monthly, annual). Annual plans should have their monthly-equivalent amount for clarity, but are billed as a single charge upfront.

Step 3: Configure Webhook Events

In Razorpay settings, add a webhook endpoint at your backend URL. Subscribe to these events:

subscription.activated — a customer's subscription is live
subscription.charged — a monthly charge succeeded
subscription.payment_failed — a charge failed (trigger dunning)
subscription.cancelled — customer cancelled
subscription.completed — subscription reached its end date

Handle each event in your backend to update the customer's subscription status in your database. Never rely on polling — always use webhooks.

Step 4: Build the Checkout Flow

The customer subscription flow:

Customer selects a plan on your pricing page

Your backend creates a Razorpay Subscription using the API

You redirect the customer to the Razorpay-hosted payment page (or use the Razorpay.js SDK for embedded checkout)

Customer selects their payment method (UPI AutoPay, card, net banking)

For UPI AutoPay: customer approves the mandate in their UPI app

Razorpay sends subscription.activated webhook to your backend

Your backend provisions access for the customer

This entire flow can be built in 4–8 hours with Razorpay's documentation and a backend in any language.

---

GST on SaaS Products: What You Need to Know

Do You Need to Charge GST?

If your annual turnover is above ₹20 lakh (or ₹10 lakh for special category states), you must register for GST and charge 18% GST on your subscription revenue.

For a product approaching ₹1 lakh MRR (₹12 lakh annually), you are approaching or have exceeded this threshold. Register for GST before you hit the limit, not after.

Software-as-a-Service is classified as an OIDAR (Online Information and Database Access or Retrieval) service under GST, taxed at 18%.

GST for B2B vs B2C Customers

B2B customers: If your customer is a registered business with a GSTIN, they can claim input tax credit on the GST you charge them. This means your GST cost is effectively neutral for them — they pay you ₹1,999 + ₹359.82 GST, and they claim the ₹359.82 back from their GST liability. Your product's real cost to them is ₹1,999.

Always collect your B2B customer's GSTIN and include it on the invoice for them to claim credit.

B2C customers: Consumers cannot claim GST back. Your ₹1,999 base price becomes ₹2,358.82 with GST. Either:

Price as ₹1,999 inclusive of GST (you receive ₹1,694 base + ₹305 GST to remit)
Price as ₹1,999 + 18% GST (customer pays ₹2,358.82)

Most Indian consumer SaaS products price inclusive of GST. Most B2B products price exclusive of GST (so ₹1,999 + GST = ₹2,358.82) because B2B customers expect to see the GST component for their accounting.

GST Invoice Requirements

Every subscription payment must generate a GST-compliant invoice with:

Your company name and GSTIN
Customer name and GSTIN (if B2B)
Invoice number (sequential, not repeating)
Date of invoice
SAC code for your service (SAC 998314 for Software as a Service)
Base amount
GST amount (9% CGST + 9% SGST for same-state, or 18% IGST for inter-state)
Total amount

You can generate these invoices automatically using Razorpay's invoice feature, or build a simple invoice generator in your product. Do not manually create invoices — the risk of error or missed invoices is too high.

GST Filing

With GST registration, you file GSTR-1 (outward supplies) monthly or quarterly and GSTR-3B (summary return and payment) monthly. This is mechanical work — hire a CA for ₹2,000–₹4,000/month to handle GST filing once your MRR justifies it.

---

Dunning: Recovering Failed Payments

When a monthly charge fails (insufficient funds, expired card, bank block), Razorpay handles retries automatically according to your configuration. Set up dunning correctly or you will lose revenue to recoverable payment failures.

Razorpay's default retry behavior: 3 retries over 6 days. You can configure:

Number of retry attempts
Retry intervals
Whether to send email/SMS notifications to customers

Your dunning email sequence:

Day 1 (charge fails): Automated email + WhatsApp notification — "Your payment failed. Please update your payment method here: [link]"

Day 3 (if still failed): Personal email from you — "Hi [name], I noticed your payment hasn't gone through. Is everything okay? Here's a link to update your details."

Day 7 (if still failed): Final notice before access suspension — "Your access will be paused in 24 hours due to a payment issue. Update your payment method here or reply to this email."

Personal dunning emails (even if partially automated with mail merge) recover 40–60% of failed payments. Generic automated emails recover 20–30%. The personal touch matters significantly.

---

Setting Up Stripe for International Customers

If you plan to accept international customers paying in USD/EUR:

Stripe India Requirements

Stripe requires a registered Indian company (Pvt Ltd or LLP) to accept international payments. A sole proprietorship faces restrictions on currency conversion and international payment acceptance.

Multi-Currency Strategy

Two practical approaches:

India-only (₹ only): Use Razorpay. International customers who want to pay ₹ can do so; most serious B2B customers are fine with INR billing.

Dual market (₹ and $): Use Razorpay for Indian customers and Stripe for international. Maintain separate pricing pages with currency detection. Stripe's international infrastructure handles everything including tax calculation for different countries.

---

The Complete Payment Checklist Before Launch

[ ] Razorpay account verified with GST number and bank account
[ ] Subscription plans created for all pricing tiers and billing periods
[ ] Webhooks configured for all subscription events
[ ] Checkout flow tested end-to-end in test mode
[ ] GST registration completed (or confirmed below threshold)
[ ] GST invoice generation working for every payment
[ ] Dunning email sequence configured
[ ] Failed payment retry schedule set
[ ] Test subscription with real money before launch

Getting payments right before launch prevents the embarrassing situation of a customer trying to pay and failing, or worse, succeeding and not getting access. The payment flow is the most important user experience in your product.

Build it correctly once. Then focus on growth.