SaaS Payment Integration India 2026: UPI, RBI Compliance & Subscription Billing

Photo: Unsplash — free to use, no attribution required

The SaaS Payment Challenge in India

If you are building a SaaS product for the Indian market, payment integration is not just a technical task — it is a regulatory, tax, and user experience challenge that can make or break your subscription business. India's payment ecosystem is unlike any other country. UPI has fundamentally changed how Indians pay for services, RBI regulations impose strict rules on recurring payments, and GST compliance adds a layer of invoicing complexity that SaaS founders from the US or Europe have never encountered.

Here is what makes SaaS payment integration in India uniquely complex in 2026:

• RBI e-mandate regulations: You cannot simply store a card and charge it monthly like Stripe does in the US. Every recurring payment requires explicit mandate registration, and auto-debits above Rs 15,000 require per-transaction authentication
• UPI dominance: Over 75% of digital payments in India now happen via UPI. If your SaaS product does not support UPI payments, you are losing customers at checkout
• Card-on-file tokenization: RBI banned merchants from storing full card details. All card data must be tokenized through compliant token requestors
• GST invoicing: Every subscription charge must generate a GST-compliant invoice with SAC code, GSTIN, and proper tax breakdowns
• International payment complexity: If you sell to both Indian and international customers, you need separate payment flows, currency handling, and export documentation

Over 40% of Indian SaaS startups report payment-related churn — customers who want to pay but fail because of UPI mandate expiry, card tokenization failures, or authentication friction. Getting payments right is not just about collecting money; it is about reducing involuntary churn that silently kills your MRR.

Payment Gateways Compared: Razorpay vs Stripe vs Cashfree vs PayU

Choosing the right payment gateway is the single most important infrastructure decision for your Indian SaaS product. Each gateway has distinct strengths, and the right choice depends on your customer mix, ticket size, and international ambitions. Here is the definitive comparison for 2026.

Razorpay

Razorpay is the dominant payment gateway for Indian SaaS companies, and for good reason. It offers the most comprehensive India-focused feature set, native UPI AutoPay support, and a subscription billing product (Razorpay Subscriptions) that handles recurring payment logic out of the box.

• Transaction fee: 2% per domestic transaction (negotiable at volume)
• UPI recurring: Full UPI AutoPay support with mandate management APIs
• Subscription billing: Built-in Razorpay Subscriptions with plan management, proration, trial periods, and dunning
• Card tokenization: RBI-compliant tokenization built in
• Settlement cycle: T+2 days (instant settlement available at 1% extra)
• International payments: Supported but not the primary strength — requires separate activation
• Best for: SaaS products targeting primarily Indian customers with Rs 500 to Rs 50,000/month subscription tiers

Stripe (India)

Stripe launched in India in 2023 and has rapidly matured. Its developer experience remains the gold standard, and if your SaaS has significant international revenue, Stripe's multi-currency and global payment method support is unmatched.

• Transaction fee: 2% + Rs 2 for domestic, 3% + currency conversion for international
• UPI recurring: Supported via UPI mandates (added in late 2024)
• Subscription billing: Stripe Billing is the most powerful subscription management platform globally — invoicing, proration, metered billing, usage-based pricing, revenue recognition
• Card tokenization: Fully compliant with RBI tokenization norms
• Settlement cycle: T+2 to T+3 days for domestic, T+7 for international
• International payments: Stripe supports 135+ currencies and 50+ payment methods globally — this is where it excels
• Best for: SaaS products with mixed Indian and international customer base, or products planning global expansion

Cashfree Payments

Cashfree is the price-competitive alternative that has gained significant traction with bootstrapped SaaS startups. Their subscription management and UPI recurring support are solid, and their transaction fees are the lowest among major gateways.

• Transaction fee: 1.75% per domestic transaction — the lowest among top-tier gateways
• UPI recurring: Full UPI AutoPay support with e-mandate APIs
• Subscription billing: Cashfree Subscriptions with plan management and automated retry
• Card tokenization: RBI-compliant
• Settlement cycle: T+1 available (among the fastest in India)
• International payments: Limited compared to Stripe and Razorpay
• Best for: Bootstrapped SaaS products where every basis point of transaction fee matters, primarily domestic customer base

PayU India

PayU is one of the oldest payment gateways in India and offers reliable infrastructure. However, its developer experience and API documentation lag behind Razorpay and Stripe significantly.

• Transaction fee: 2% per domestic transaction
• UPI recurring: Supported
• Subscription billing: Basic subscription management — not as feature-rich as Razorpay or Stripe
• Card tokenization: RBI-compliant
• Settlement cycle: T+2 to T+3 days
• International payments: Available through PayU Global
• Best for: Enterprises already in the PayU ecosystem, or businesses needing PayU's EMI and BNPL integrations

UPI Recurring Payments: RBI E-Mandate Rules for SaaS

UPI recurring payments (UPI AutoPay) are the most important payment method for subscription-based SaaS products in India. With over 400 million active UPI users, this is how the majority of your Indian customers will want to pay. But the RBI's e-mandate framework imposes specific rules that every SaaS developer must understand.

How UPI AutoPay Works for SaaS Subscriptions

1. Mandate creation: Customer initiates subscription and selects UPI AutoPay. They authenticate via UPI PIN on their UPI app (GPay, PhonePe, Paytm, etc.) to authorize recurring debits
2. Mandate parameters: The mandate specifies the maximum amount, frequency (monthly, quarterly, annual), start date, and end date. You cannot debit more than the mandated amount
3. Pre-debit notification: RBI requires that the payment gateway send a pre-debit notification to the customer at least 24 hours before each recurring charge. This notification must include the amount, date, and option to pause or cancel
4. Auto-debit execution: If the customer does not object, the amount is debited automatically on the scheduled date
5. Mandate modification: If your SaaS plan price changes (upgrade, downgrade, price increase), the existing mandate must be revoked and a new mandate created with the updated amount

The Rs 15,000 Auto-Debit Limit

This is the single most misunderstood rule in Indian SaaS payments. Under the RBI's updated e-mandate framework:

• Auto-debits up to Rs 15,000: Can be processed automatically after the pre-debit notification, without additional customer authentication
• Auto-debits above Rs 15,000: Require explicit customer authentication (UPI PIN or OTP) for each individual debit. This means the payment is not truly "automatic" — the customer must approve each charge

What this means for SaaS pricing: If your SaaS product has monthly plans above Rs 15,000, expect higher payment failure rates on those plans. Customers must actively approve each charge, and if they miss the notification or forget to authenticate, the payment fails. SaaS products with plans priced above Rs 15,000/month report 15-25% higher involuntary churn compared to those priced below the limit.

Mandate Expiry and Renewal

UPI mandates have a maximum validity period (typically 5 years). When a mandate expires, the customer must re-authenticate and create a new mandate. Your system must track mandate expiry dates and proactively prompt customers to renew before expiry — otherwise, their next payment will silently fail.

Subscription Billing Architecture for Indian SaaS

A well-designed subscription billing architecture separates your payment gateway integration from your billing logic — because gateways can change, but your billing rules are your business.

Core Components

• Plan management: Define your subscription tiers (Basic, Pro, Enterprise) with pricing, billing frequency, trial periods, and feature entitlements
• Subscription lifecycle: Handle creation, activation, upgrade, downgrade, pause, resume, cancellation, and expiry — each state transition must trigger the correct billing action
• Invoice generation: Every charge must produce a GST-compliant invoice. This is not optional — it is a legal requirement
• Payment orchestration: Manage the actual charge — selecting the right payment method, handling retries for failed payments, and routing between gateways
• Dunning management: Automated retry logic for failed payments with escalating customer notifications. Good dunning flows recover 30-40% of failed payments that would otherwise become churn
• Webhook processing: Reliable processing of asynchronous payment gateway events — payment success, failure, mandate creation, mandate revocation, refunds, and disputes

Build vs Buy Decision

Most Indian SaaS startups face this decision: build subscription billing in-house or use a managed solution.

• Use Razorpay Subscriptions or Stripe Billing if your billing model is straightforward (fixed monthly/annual plans). These handle 80% of common subscription scenarios out of the box
• Build custom billing logic if you need usage-based pricing, complex proration, multi-currency with different pricing per region, or unique business rules that managed solutions do not support
• Use a billing platform like Chargebee or Zoho Subscriptions (both Indian companies) as a middle ground — more flexibility than gateway-native billing, less development effort than building from scratch

Webhook Reliability

This is where most SaaS payment integrations break. Payment gateway webhooks are asynchronous notifications that inform your system about payment events. If your webhook handler crashes, times out, or processes events out of order, your subscription state diverges from reality.

• Always implement idempotent webhook processing — the same webhook delivered twice must not create duplicate charges or state changes
• Store raw webhook payloads before processing. If your handler fails, you can replay from the stored payload
• Use a webhook queue (SQS, RabbitMQ, Redis) rather than processing webhooks synchronously in the HTTP handler
• Implement webhook signature verification to prevent spoofed events
• Build a reconciliation job that compares your subscription state with the payment gateway state daily and flags discrepancies

GST on SaaS: 18% GST, SAC Code 998314 & Invoice Compliance

GST compliance is not optional for SaaS companies in India, and getting it wrong results in penalties, interest, and lost input tax credit for your B2B customers.

GST Basics for SaaS

• GST rate: 18% on all SaaS and software subscription services
• SAC code: 998314 — "Online content: IT services"
• Registration threshold: Mandatory once annual turnover exceeds Rs 20 lakh (Rs 10 lakh for special category states like those in the Northeast)
• Invoice requirement: Every subscription payment must generate a GST-compliant tax invoice within the prescribed time

GST Invoice Requirements for SaaS

Every invoice must contain:

• Supplier name, address, and GSTIN
• Customer name and address (GSTIN if B2B)
• Unique sequential invoice number
• Date of invoice and date of supply
• SAC code (998314)
• Taxable value (subscription amount before GST)
• CGST + SGST (for intra-state) or IGST (for inter-state) breakdowns
• Total amount including GST
• Place of supply (determined by customer location for services)

B2B vs B2C SaaS GST Implications

For B2B SaaS sales: Your business customers need proper GST invoices with their GSTIN to claim input tax credit. If your invoice is incorrect or missing their GSTIN, they cannot claim ITC — and they will complain or churn. Ensure your billing system captures customer GSTIN during onboarding and prints it on every invoice.

For B2C SaaS sales: You still must charge and remit 18% GST, but the invoice requirements are simpler since there is no ITC claim involved. However, B2C invoices exceeding Rs 2.5 lakh must still include the customer's name and address.

International Payments: Accepting USD While Based in India

If your SaaS product serves international customers — and most ambitious Indian SaaS companies do — you need a clear strategy for accepting foreign currency payments while complying with RBI and FEMA regulations.

Payment Gateway Options for International Billing

• Stripe (Indian entity): Accept payments in 135+ currencies. Funds settle in INR to your Indian bank account. Stripe handles currency conversion. Fee: 3% + currency conversion markup
• Razorpay International: Accept payments in USD, EUR, GBP, and 90+ currencies. Requires separate activation for international payments. Fee: 3% per international transaction
• Stripe Atlas + US entity: If you register a US LLC/C-Corp via Stripe Atlas, you can accept payments in USD directly into a US bank account. This is the preferred approach for SaaS companies with majority international revenue
• PayPal Business: Widely recognized by international customers but has higher fees (4.4% + fixed fee) and less favorable currency conversion rates

RBI and FEMA Compliance for International Payments

• FIRC (Foreign Inward Remittance Certificate): Required for every international payment received. Your bank or payment gateway provides this — ensure you are collecting and filing FIRCs for export compliance
• SOFTEX form: Required for software export earnings. Must be filed with STPI (Software Technology Parks of India) or SEZ if applicable
• GST zero-rating: SaaS exports qualify as zero-rated supply. File a Letter of Undertaking (LUT) with GST authorities to export without charging GST. Without LUT, you must charge IGST and later claim a refund — tying up cash unnecessarily
• Transfer pricing: If you have entities in multiple countries, ensure your inter-company pricing follows arm's-length principles

Indian SaaS companies exported over $15 billion in software services in 2025 — the regulatory framework for international payments is well-established. The key is setting up the compliance infrastructure (LUT, FIRC collection, SOFTEX filing) from the beginning rather than retroactively when your CA asks for documentation during audit season.

Implementation Guide: Razorpay Subscription Integration Walkthrough

Here is a step-by-step walkthrough of integrating Razorpay Subscriptions into your SaaS product — the most common payment integration for Indian SaaS companies.

Step 1: Create Plans on Razorpay

Define your subscription plans using the Razorpay Plans API. Each plan specifies the billing amount, currency (INR), billing frequency (monthly, quarterly, yearly), and plan name. Create plans via API or the Razorpay Dashboard. Store the Razorpay plan_id mapped to your internal plan identifiers.

Step 2: Create Subscriptions

When a customer selects a plan, create a Razorpay Subscription object via API. This returns a subscription_id and a short URL for the customer to authenticate payment. Configure total billing cycles, start date (for trial periods), and customer notification preferences.

Step 3: Customer Authentication

Redirect the customer to Razorpay's hosted checkout or use the Razorpay.js embedded checkout. The customer selects their payment method (UPI AutoPay, card, or net banking) and authenticates. For UPI AutoPay, the customer approves the mandate via UPI PIN on their UPI app.

Step 4: Webhook Configuration

Configure webhooks in the Razorpay Dashboard to receive events at your server endpoint. Critical events to handle:

• subscription.activated — Subscription is live, grant access to features
• subscription.charged — Recurring payment successful, generate invoice
• subscription.pending — Payment attempt initiated but awaiting confirmation
• subscription.halted — Payment failed after all retry attempts, restrict access
• subscription.cancelled — Customer or system cancelled, handle end-of-access
• subscription.completed — All billing cycles completed

Step 5: Invoice Generation

On each subscription.charged event, generate a GST-compliant invoice with all required fields (covered in the GST section above). Store the invoice, email it to the customer, and push the data to your GST filing system.

Step 6: Dunning and Retry Logic

Configure Razorpay's automatic retry settings for failed payments. Razorpay retries failed charges up to 3 times over a configurable period. Supplement with your own dunning emails: a gentle reminder on day 1, an urgent notice on day 3, and a final warning with access restriction notice on day 7.

Step 7: Plan Changes (Upgrade/Downgrade)

Handle mid-cycle plan changes using Razorpay's subscription update API. Decide your proration strategy — charge immediately for upgrades, credit remaining value for downgrades, or apply changes at the next billing cycle. For UPI mandates, plan changes that exceed the mandated amount require creating a new mandate.

Common Mistakes to Avoid in Indian SaaS Payment Integration

These are the mistakes I see repeatedly across Indian SaaS companies — each one has cost real businesses real revenue.

1. Ignoring the Rs 15,000 Mandate Limit in Pricing

Setting your primary plan at Rs 20,000/month without realizing that every monthly charge requires customer authentication. Result: 20-30% payment failure rate on that plan, leading to involuntary churn that shows up as "customers leaving" when they actually wanted to stay and pay.

2. Not Implementing Proper Dunning

A payment fails, the system marks the subscription as inactive, and the customer loses access without any notification. Good dunning includes multiple retry attempts, customer email/SMS notifications, a grace period before access restriction, and a self-service payment update page. Proper dunning recovers 30-40% of failed payments — that is direct MRR you are leaving on the table.

3. Synchronous Webhook Processing

Processing payment webhooks in the HTTP request handler instead of queuing them. When your handler takes more than 5 seconds (database write, invoice generation, email sending), the gateway times out and retries — leading to duplicate processing, race conditions, and inconsistent subscription states.

4. Missing GST Compliance

Building the payment flow first and "adding GST later." By the time you realize every invoice needs SAC codes, GSTIN capture, place-of-supply logic, and GSTR-1 filing, you have months of non-compliant invoices to correct. GST compliance must be built into your billing system from day one.

5. Single Gateway Dependency

Using only one payment gateway with no fallback. Gateway outages happen — Razorpay, Stripe, and every other provider have experienced downtime. When your only payment gateway is down, new sign-ups fail, renewals fail, and you have no alternative. Implement at least a secondary gateway for critical payment flows.

6. Ignoring Mandate Expiry Tracking

UPI mandates and card mandates expire. If your system does not track expiry dates and proactively prompt customers to renew mandates before they expire, you will face a wave of payment failures when mandates silently lapse.

7. Not Handling Proration Correctly

A customer upgrades from Rs 999/month to Rs 2,499/month on day 15 of their billing cycle. What happens? Do they pay the full Rs 2,499 immediately? Do they get credited for the unused portion of their Rs 999 plan? If you have not defined and implemented your proration logic, customers will dispute charges and support tickets will multiply.

8. Neglecting Payment Analytics

Not tracking: payment success rates by method (UPI vs card vs net banking), involuntary churn rate, dunning recovery rate, average revenue per transaction, and failed payment reasons. Without these metrics, you cannot optimize your payment flow. Build a payment analytics dashboard from the start.

Frequently Asked Questions: SaaS Payment Integration India

Which payment gateway is best for SaaS companies in India in 2026?

Razorpay is the most popular choice for Indian SaaS companies due to its native UPI recurring payment support, robust subscription billing APIs, and competitive pricing at 2% per transaction. Stripe is better for SaaS products with a primarily international customer base, supporting 135+ currencies and 50+ payment methods globally. Cashfree offers the lowest transaction fees at 1.75%. The best choice depends on your customer mix — domestic-heavy SaaS products benefit from Razorpay, while international-focused products should consider Stripe.

How do UPI recurring payments work for SaaS subscriptions in India?

UPI recurring payments (UPI AutoPay) allow SaaS companies to automatically debit customer bank accounts for subscription renewals. Under RBI e-mandate rules, auto-debits up to Rs 15,000 require a one-time mandate registration via UPI PIN. Amounts above Rs 15,000 require explicit customer approval for each debit. The mandate specifies the exact amount, frequency (monthly, quarterly, annual), and validity period. A pre-debit notification must be sent at least 24 hours before each charge.

What is the GST rate on SaaS products sold in India?

SaaS products sold in India attract 18% GST under SAC code 998314 (Online content — IT services). GST registration is mandatory once annual turnover exceeds Rs 20 lakh (Rs 10 lakh for special category states). For B2B sales, GST must be charged and shown separately on invoices with the customer's GSTIN for input tax credit eligibility. For international sales (exports), SaaS services qualify for zero-rated supply under LUT (Letter of Undertaking), meaning no GST is charged on exports.

Can Indian SaaS companies accept international payments in USD?

Yes. Indian SaaS companies can accept international payments in USD, EUR, GBP, and other foreign currencies through Stripe (supporting 135+ currencies), Razorpay (international payments feature with 90+ currencies), or PayPal Business. RBI requires that foreign currency receipts be converted to INR within the prescribed settlement period. You will need FIRC (Foreign Inward Remittance Certificate) documentation for export compliance and LUT filing for GST zero-rating on exports.

What are the RBI compliance requirements for SaaS payment processing in India?

Key RBI compliance requirements for SaaS payment processing include: no storage of full card data — only tokenized references allowed under RBI card-on-file tokenization rules; e-mandate registration required for all recurring payments with pre-debit notification 24 hours before each charge; auto-debit limit of Rs 15,000 without additional per-transaction authentication; PA/PG guidelines requiring payment aggregators to maintain a minimum net worth of Rs 25 crore; and data localization requirements mandating that all payment data must be stored on servers located within India.