How to accept UPI Autopay for a paid newsletter

If you have tried to run a paid newsletter in India using cards, you already know the punchline. About a third of your would-be subscribers drop off at checkout. A chunk of the ones who succeed churn silently three months later when the auto-renewal fails. It isn't the reader. It is the payment rail.

UPI Autopay is the fix. It is the reason paid newsletters can actually work for an Indian audience in 2026, and it is the single biggest platform-selection lever most creators do not think about until they have already picked the wrong stack.

This post covers what UPI Autopay is, why cards keep failing, how the mandate flow works, which gateways to use, and how to actually implement it. Both the DIY route and the shortcut.

What UPI Autopay actually is

UPI Autopay is an NPCI-standardised recurring-payment mandate built on top of UPI. A user approves a mandate once inside their UPI app (GPay, PhonePe, Paytm, BHIM, any of them). After that, your payment processor can pull a fixed or variable amount on a schedule without the user re-authenticating each time.

Two things make it interesting for a paid newsletter.

1. It is the payment method Indian readers actually trust. UPI processes something like 15 billion transactions a month. Your reader has already sent money over it this morning. Card checkouts feel foreign. UPI feels like WhatsApp.
2. It does not rely on RBI's tokenisation regime for cards. The 2022 tokenisation rules made card-on-file recurring payments legally messy and technically brittle. UPI Autopay sits under a completely different NPCI framework (the AutoPay circular) and just works.

Mandates can be up to ₹15,000 per transaction without additional authentication under the current NPCI limits. Worth re-checking on the NPCI site since these numbers are periodically revised. Above the limit, the user gets an OTP-style prompt in their UPI app on each pull.

Why cards fail so much for Indian subscribers

A quick tour of why "we take cards" is not the same as "we accept payments" in India.

• Tokenisation friction. Post-tokenisation, every merchant needs to re-tokenise cards. Not all issuing banks cooperate cleanly. Silent decline rates on the second charge of an international-processor-issued subscription can be alarmingly high.
• International vs domestic MDR. Stripe's Indian entity is improving but still does not cover the full spectrum of Indian consumer cards well. Some cards are declined for reasons the reader cannot fix.
• OTP UX on mobile. Recurring card mandates require SMS OTP re-confirmation windows that Indian users often miss, especially if they are on Jio and the SMS lands late.
• Foreign merchant flags. If your platform (say, Substack) routes payment through a US Stripe account, some Indian issuers throw up "international transaction" warnings on every renewal.

Net effect: card-based paid newsletters in India lose paying subscribers at renewal at roughly two to four times the rate that UPI Autopay-based ones do. That is anecdote from creators we have spoken to, not a benchmark study. The direction is consistent.

The mandate flow, step by step

Here is what actually happens when a reader subscribes to your paid newsletter via UPI Autopay.

1. Checkout. Reader picks a plan (say ₹299 per month) on your subscribe page.
2. UPI ID or intent. They enter a UPI VPA (name@ybl) or tap an app-intent button that opens GPay or PhonePe directly.
3. Mandate approval. Their UPI app shows a mandate screen. "Approve recurring payment of ₹299 per month to your merchant name until end date." They enter their UPI PIN once.
4. Mandate registered. The gateway (Razorpay or Cashfree) confirms the mandate ID. Your platform stores it against the subscriber's account.
5. First debit. Depending on setup, the first payment happens immediately (with the mandate) or on the mandate's start date.
6. Auto-debit each cycle. On the next billing date, the gateway triggers the mandate. The reader gets a pre-debit SMS notification 24 hours before. Money moves. Your webhook fires. You mark the subscription active.
7. On failure or cancel. If the mandate fails (insufficient funds, revoked mandate), your webhook fires with a failure event. You retry per your dunning logic or downgrade the subscriber.

The whole thing feels invisible to a reader who has used UPI before. That is the point.

What the fees actually look like

One thing worth getting right, because it comes up in every conversation. UPI itself has a regulated MDR of 0% in India, set by the government. That does not mean UPI is free for merchants. Payment gateways like Razorpay and Cashfree charge their own platform fee on UPI transactions (typically around 2%, verify current numbers on their pricing pages). This platform fee is what shows up on your gateway invoice, not MDR.

The distinction matters when you compare platforms. A platform that says "0% platform fee" (like Fluxeta) means it is not taking a cut on top of the gateway fee. You still owe Razorpay or Cashfree their percentage. A platform that says "10% platform fee" (like Substack) is taking that cut in addition to the underlying payment processor fee.

Gateway options: Razorpay vs Cashfree

Two credible options for UPI Autopay in India right now.

Razorpay is the market leader for subscription products. Their Subscriptions API supports UPI Autopay natively. Docs are readable, sandbox is functional, and the dashboard is where most Indian SaaS founders already spend their time.

Cashfree is competitive on pricing for high-volume merchants, has solid Autopay support, and is sometimes preferred by fintechs. Docs are less polished than Razorpay's but the API surface is comparable.

For 95% of paid newsletters, either works. Razorpay is the safer default because integration tutorials for it dominate the Indian dev community.

Skip PayU (older APIs, painful subscription flow), Instamojo (never invested seriously in Autopay), and international Stripe (no UPI Autopay).

Implementing it yourself (the DIY route)

If you are on Ghost, WordPress, or a custom stack, here is the shape of the work.

1. Merchant onboarding. Sign up on Razorpay with your PAN, GSTIN (if applicable), and bank account. KYC takes a few business days. You need Subscriptions enabled. This is off by default. Open a support ticket to request it.

2. Create plans. In Razorpay's dashboard, create a Plan for each tier (monthly-299, yearly-2999). Plans hold the amount, currency, and billing interval.

3. Build a checkout page. Serve a page with Razorpay's Checkout.js. When the user picks a plan, call your backend to create a Subscription via Razorpay's API and pass the returned subscription_id to Checkout. The UPI Autopay mandate flow is handled inside the Razorpay modal.

4. Handle the webhook. Razorpay POSTs to your webhook endpoint on every event: subscription.authenticated, subscription.charged, subscription.completed, payment.failed, and more. You need a queue worker that:

• Verifies the HMAC signature.
• Upserts the subscription in your database.
• Grants or revokes newsletter access based on status.
• Sends a "you're in" welcome email on first success.
• Sends a dunning email on failure.

5. Access control. In your newsletter send logic, filter recipients by active subscription status before pushing to the email queue.

6. Cancellation flow. Give the reader a self-serve cancel endpoint that hits Razorpay's subscription.cancel API. If you do not, they will revoke the mandate from their UPI app and you will be confused by ghost failures.

7. Compliance. DPDP Act 2023 requires you to collect explicit consent for storing UPI-linked identifiers. GST invoicing applies for subscription revenue if you are above the threshold. RBI's Additional Factor of Authentication rules for pre-debit notifications are handled by the gateway, but confirm your gateway is doing it.

Realistic effort. Two to three weeks of focused developer time for a first version. Ongoing: dunning tuning, edge cases when a reader upgrades mid-cycle, refund flow for annual plans.

The shortcut

If you do not want to build any of the above, and there is no medal for building payment infrastructure yourself, use a platform that already ships UPI Autopay.

Fluxeta's UPI Autopay is built directly on top of Razorpay Subscriptions. You connect your Razorpay account once, or use our platform-owned gateway if you do not have one. Define your paid tiers in INR, and your subscribe page renders with UPI as the default payment method. Mandate registration, webhook handling, dunning, invoicing, and DPDP-compliant consent are all handled. Cancellation is one click for the reader.

The tradeoff is the usual SaaS tradeoff. Less control over the checkout page's exact look, less ability to route to a specific gateway account per subscription. For most newsletter creators, that is a good trade.

What Substack and international platforms cannot do here

Worth naming explicitly. Neither Substack, nor Beehiiv, nor Ghost Pro currently support UPI Autopay natively. They route paid subscriptions through Stripe, which in the Indian market means cards, and cards mean the failure modes above. That is the single biggest reason we recommend an India-first platform for India-facing paid newsletters. See Fluxeta vs Substack for the full breakdown.

Where this leaves you

Payment infrastructure is boring until you realise it is the thing quietly determining whether your paid newsletter has 200 subscribers or 2,000 next year. Get UPI Autopay right and everything else, content, growth, retention, gets easier.

Fluxeta ships with UPI Autopay wired in. You can be taking payments on the first day. The Free forever plan lets you run the whole flow without a card on file. See how it works, or check pricing if you are comparing.