Razorpay vs PayU for SaaS: Subscriptions, Security and Integration Compared (2026)

For a SaaS product in India, choosing a payment gateway is mostly a recurring billing decision. This guide compares Razorpay vs PayU for SaaS teams using one example plan, following a customer from signup through renewal, a failed payment, an upgrade and cancellation.

Product details come from each provider’s documentation and pricing pages and from the RBI. Rates were checked in October 2026. Where a provider does not publish something, we say so.

Quick answer: For most Indian SaaS businesses that want a managed subscription engine, Razorpay Subscriptions is the easier fit. It handles retries, pre-debit timing and customer card changes out of the box, and its pricing is published. PayU can cost less on published card rates and suits teams that want to control each charge through its standing instruction APIs or already have negotiated PayU pricing.

The example SaaS plan

• Plan: Rs 999 per month, billed monthly from the day of signup.
• Customer: an Indian business paying by domestic Visa or Mastercard card, or UPI AutoPay.
• Journey: signup, two normal renewals, a failed renewal in month three, an upgrade to Rs 1,999 in month four, and cancellation in month six.

This is plan-based recurring billing, not saving a card for faster one-off purchases. A saved card does not give you permission to debit a customer on a schedule; a registered mandate does.

What each provider calls its subscription product

Razorpay Subscriptions works with plans (amount and frequency) and subscriptions (a customer attached to a plan), and Razorpay charges the customer automatically each cycle. You can set it up from the Dashboard, through APIs or with subscription links.

PayU markets a “Subscription Suite”. In its developer documentation the managed billing engine is called Zion. PayU also offers standing instruction (SI) APIs, where your own code registers the mandate, sends the pre-debit notification and triggers each charge. Zion is enabled by the PayU Onboarding Team, and PayU asks merchants to contact their Key Account Manager to enable subscriptions.

Which payment methods work for recurring SaaS billing?

• Razorpay: Visa, Mastercard and RuPay cards; UPI AutoPay; and eMandate (eNACH) authorised by netbanking, debit card or Aadhaar. Its product page also lists international cards.
• PayU Zion: Visa and Mastercard credit cards issued in India (Amex listed as coming soon), Visa and Mastercard debit cards from 40+ banks, UPI, and net banking through eNACH. Zion’s UPI option does not support a daily frequency.

Every option works for a Rs 999 monthly plan. Razorpay’s settings page notes that cards and UPI currently support recurring charges up to Rs 15,000, so check limits before selling high-value annual plans on these rails.

What do the RBI e-mandate rules require?

The RBI consolidated its rules in the Digital Payments: E-mandate Framework, 2026, issued on 21 April 2026, covering recurring transactions on cards, prepaid instruments and UPI. The points that matter for SaaS:

• A mandate is registered only after the customer completes an additional factor of authentication (AFA).
• Later debits can go through without AFA up to Rs 15,000 per transaction (Rs 1 lakh for insurance premiums, mutual funds and credit card bills). A SaaS plan above Rs 15,000 needs AFA for each debit.
• The issuer must send a pre-transaction notification at least 24 hours before the debit, and the customer can opt out of one debit or withdraw the mandate.
• Customers cannot be charged for using the e-mandate facility.

On Razorpay, the debit is initiated 36 hours before the due date and the bank sends the pre-debit SMS. On PayU’s SI APIs, your server must call the Pre-Debit Notification API at least 48 hours before a card or UPI debit, or the recurring charge call will not work. Zion handles this step for you.

How are consent and tokenisation handled?

Under the RBI’s card-on-file tokenisation rules, only card issuers and networks may store actual card numbers, and tokenisation needs explicit customer consent with AFA. Both providers tokenise the card during mandate registration, so your application never stores card numbers. For background, see our explainer on network tokens vs PCI tokens.

On Razorpay, an immediate start charges the plan amount as the authentication transaction; a future start charges Rs 5, refunded automatically. On Zion, the consent transaction is the first instalment or a Rs 5 penny transaction that the merchant refunds through PayU’s Refund API.

Subscription lifecycle compared: Razorpay vs PayU for SaaS

Failed renewals, upgrades and cancellation

Suppose the month three renewal fails. Razorpay retries card and UPI payments once a day for three days. The subscription moves to pending, then to halted when retries run out, with a webhook at each step. The customer gets an email with a link to update the card or switch to UPI or eMandate. A halted subscription becomes active again once they do, but missed invoices must be charged manually, and manual charging of domestic cards is not supported. Plan your dunning emails and access rules around that.

Zion invoices retry for three days by default. PayU does not publish a retry schedule for the SI route, so your code decides. PayU’s documentation also notes that UPI AutoPay execution attempts will be limited to four after 31 July 2026, and that NPCI asks merchants to avoid 10:00 AM to 1:00 PM and 5:00 PM to 9:30 PM.

The month four upgrade shows real limits on both sides. Razorpay can change a plan immediately (with proration) or at cycle end, but its documentation says UPI-authorised subscriptions cannot be updated and domestic card subscriptions can only change their offer. Zion’s update API only changes the auth reference, email, mobile and custom fields. For most Indian customers, plan on a new subscription with fresh consent for an upgrade.

For the month six cancellation, Razorpay cancels immediately or at the end of the cycle; Zion cancels immediately. Customers can also cancel from their UPI app or bank, and both providers report this through webhooks.

Integration effort and webhook security

On Razorpay, you create a plan and a subscription, then pass the subscription_id to Standard Checkout. You verify the payment by computing an HMAC SHA256 of the payment ID and subscription ID with your key secret. Webhooks carry an X-Razorpay-Signature header, computed with your webhook secret over the raw request body, and an x-razorpay-event-id header for discarding duplicates.

PayU uses SHA512 hashes with your merchant salt. Zion requests carry an X-PayU-Subscription-Signature, and payment responses must pass a reverse hash check before you mark them successful. PayU also publishes webhook IPs to whitelist. The SI route needs more of your own code (mandate status checks, pre-debit calls, charge calls). Our guide to payment API and webhook security covers signature checks and replay protection in more depth.

Invoicing and reconciliation

Razorpay generates an invoice at the start of each billing cycle. Zion treats each scheduled charge as an invoice with due, paid and failed events, and supports ad hoc invoices for usage billing (up to the plan amount, INR only). Store each provider’s subscription, invoice and payment IDs against your own records, update access only from verified webhooks, and confirm with your accountant whether you must issue your own GST tax invoice.

Subscription billing costs: pricing and activation

Rates checked October 2026. Razorpay’s pricing page lists a 2% platform fee plus GST, with no setup or annual maintenance fees. The Razorpay Subscriptions page adds 0.5% on every subscription payment (a limited-time rate, down from 0.9%), plus GST. Accounts activated from 1 July 2026 get a 90-day 0% platform fee offer, capped at Rs 5 lakh of transactions, GST not waived. The terms do not say whether the Subscriptions fee is covered.

PayU’s pricing page lists 2% for Visa, Mastercard, net banking, BNPL and wallets, 3% for Diners, Amex, EMI and international, 18% GST and no setup fee. A separate subscription fee is not publicly listed.

Worked example. Assumptions: 1,000 customers each paying Rs 999 by domestic Visa or Mastercard, standard rates, no promotion, GST at 18% on fees.

• Razorpay: 2.5% of Rs 9,99,000 = Rs 24,975, plus GST of Rs 4,496 = Rs 29,471 a month.
• PayU: 2% of Rs 9,99,000 = Rs 19,980, plus GST of Rs 3,596 = Rs 23,576 a month, if no recurring fee applies.

On published rates, PayU is about Rs 5,900 a month cheaper here. Negotiated pricing can change both figures.

Why we recommend Razorpay for most SaaS teams

In the Razorpay vs PayU for SaaS decision, our recommendation rests on documented criteria rather than headline price:

• Self-serve setup: payment methods are enabled in the Dashboard, and subscription links need no code.
• Managed lifecycle: published states, retry schedule, pre-debit timing and a customer card-change flow.
• Coverage: RuPay cards, UPI AutoPay, eMandate and international cards.
• Clear webhook security and published add-on pricing.

For a team without billing engineers, that saves build and support time. For controls against mandate abuse, read our guide to securing recurring billing.

When PayU may fit better

• You process high card volumes and the published 2% rate, or a negotiated rate, matters more than managed features.
• You run your own billing engine and want SI APIs to control when each charge is made.
• You bill by usage and want Zion’s ad hoc invoices, or already have a PayU account manager.

FAQs

1. Is Razorpay or PayU better for SaaS subscriptions in India?

For teams that want a managed subscription engine with self-serve setup, Razorpay is usually simpler because retries, pre-debit timing and card updates are documented and automated. PayU suits teams that want lower published card rates, already work with PayU, or prefer to control charges through standing instruction APIs. Compare both on your actual payment mix.

2. Do I need AFA for every monthly SaaS renewal?

Not for most plans. Under the RBI’s 2026 e-mandate framework, the customer completes AFA when registering the mandate. After that, recurring debits up to Rs 15,000 per transaction can go through without AFA. If your plan costs more than Rs 15,000 per debit, each charge needs AFA, which can delay or fail renewals.

3. Can a customer cancel a mandate without contacting me?

Yes. Customers can cancel or modify UPI mandates from their UPI app, and cardholders can manage card mandates through their bank. Razorpay documents this in its Subscriptions FAQs, and PayU offers a webhook that reports cancellations made at the bank or UPI app. Listen for these events and update access.

4. How should a SaaS business handle upgrades?

Check the payment method first. Razorpay supports prorated plan updates, but not for UPI-authorised subscriptions, and only offer changes on domestic card subscriptions. Zion’s update API cannot change the plan amount. For many Indian customers, an upgrade means cancelling the old subscription and collecting fresh consent for the new plan.

5. Does saving a customer’s card let me charge them monthly?

No. A saved, tokenised card speeds up one-off checkout, but scheduled debits need a registered recurring mandate with the customer’s AFA, plus a pre-debit notification before each charge. Use Razorpay Subscriptions or PayU’s recurring products for monthly billing, not a saved-card flow.