NGO Website Development in India: Setting Up UPI Autopay for Recurring Monthly Donors
NGO website development in India should treat recurring monthly giving as a core donation flow, not an afterthought bolted on next to a one-time donate button, and UPI Autopay is now the most practical way to build that flow for Indian donors specifically. It lets a supporter authorise a monthly debit once, at a fixed amount, without re-entering their UPI PIN for every subsequent payment below a set threshold — removing the single biggest point of friction that causes recurring donors to quietly lapse: having to actively re-authenticate and re-commit every single month.
Recurring donors are worth building for deliberately. A one-time donor gives once and has to be re-persuaded every single time; a monthly donor who stays enrolled for a year has effectively pre-committed twelve gifts through a single decision. Most Indian NGO websites still default to a one-time payment form and treat "monthly" as a checkbox that quietly does very little beyond labelling the transaction, without addressing what actually keeps a recurring donor enrolled month after month. That gap is exactly what a properly implemented UPI Autopay mandate closes.
What UPI Autopay actually is
UPI Autopay is NPCI's e-mandate framework for recurring payments over UPI, and it works differently from a plain one-time UPI payment. Instead of authorising a single transaction, a donor authorises a mandate — a standing instruction that lets a fixed amount be debited on a recurring schedule (monthly, in most donation contexts) from their bank account through their UPI app, without them opening the app and approving each individual payment.
The mechanics matter for what you build: this is a deferred-capture system. The donor gets a pre-debit notification ahead of each renewal, and the actual debit is attempted at least 24 hours later, not instantly. Your website and donor communications need to account for that delay rather than assuming a donation confirms the moment a mandate is set up — the mandate is the commitment; each month's actual debit is a separate event that happens on its own schedule afterward.
The transaction limit that shapes your design
For most recurring payment categories, mandate debits up to ₹15,000 per transaction can be processed without the donor re-entering their UPI PIN at each cycle — this is the frictionless experience that makes Autopay valuable for a recurring donor relationship in the first place. Above that amount, an additional authentication step is required for each debit, which reintroduces exactly the friction Autopay is meant to remove.
NPCI does permit mandate creation up to ₹1,00,000 per transaction for a defined list of specified merchant categories — mutual funds, insurance and credit card bill payments are commonly cited examples — but nothing in current guidance confirms charitable donations sit within that higher-limit category. Rather than assume your NGO qualifies for the higher threshold, confirm the applicable limit directly with your payment gateway or bank before designing donation tiers around an assumption that might not hold. The safer default for a donation form is to treat ₹15,000 per month as the practical frictionless ceiling, and to design your suggested-amount options with that in mind — most individual monthly giving programmes sit comfortably under this limit anyway, so it rarely constrains typical donor behaviour in practice.
A significant 2025–26 change: mandate portability
An NPCI circular dated 7 October 2025 revamped the Autopay system, with all UPI network members required to implement the changes by 31 December 2025. The headline change for donor relationships: mandates are now portable. A donor can move a recurring mandate from one UPI app to another, and a merchant (in this case, your NGO or its payment gateway) can move mandates between payment providers, subject to a rule that a specific mandate can only be ported once every 90 days. Apps are explicitly barred from using cashbacks, incentives or persistent prompts to push users into switching providers.
For an NGO, this cuts two ways. It's good news for donor retention — a supporter who switches their primary UPI app no longer has to cancel and recreate their recurring donation from scratch, which was previously a real point of silent donor loss. It's a new operational consideration if you ever switch payment gateways yourselves, because existing donor mandates may now be portable in ways your finance team should understand rather than assume are simply lost in a gateway migration.
What this means for your website's donation form
Concretely, a donation page built around UPI Autopay needs to handle a few things a simple one-time payment form doesn't:
- A clear, separate recurring-giving option, not a small checkbox easy to miss next to the primary one-time amount field. Framing monthly giving as its own path — with its own suggested amounts and its own explanation of what a mandate means — tends to convert better than treating it as a minor variant of one-time giving.
- Plain-language mandate consent, explaining in the donor's own terms what they're authorising: a fixed monthly amount, debited automatically after a pre-debit notification, cancellable at any time through their UPI app or by contacting your NGO directly.
- A visible, working cancellation and modification path. A donor who feels trapped in a recurring commitment they can't easily change is a donor who will eventually complain publicly or simply distrust your organisation going forward — the cancellation option should be genuinely easy to find, not buried to artificially inflate retention numbers, which is a bad-faith design pattern with real reputational risk for a nonprofit specifically.
- Reliable webhook handling from your payment gateway for the recurring debit events, so your CRM or donor database updates automatically each month rather than requiring manual reconciliation — this is where a lot of smaller NGO implementations quietly break down, with recurring donations processing correctly on the payment side while the donor's record in your own system falls out of sync.
The 80G receipt question for recurring gifts
Since the Finance Act 2021 changes, Form 10BD (filed by the NGO with the Income Tax Department) and Form 10BE (the certificate issued to the donor) are the system that actually matters for a donor's Section 80G deduction claim — a donor presenting only a manual or generic receipt cannot claim the deduction based on that receipt alone; Form 10BE is the valid proof.
For a recurring monthly donor, the practical approach is a consolidated Form 10BE for the financial year, covering the total of everything a specific donor gave your organisation across all their monthly payments, rather than a separate certificate issued after every individual monthly debit. This means your donor database needs to correctly aggregate a donor's UPI Autopay contributions across the full year against their PAN and other required donor details, so that when your NGO files Form 10BD by the annual deadline, each recurring donor's total is captured accurately as a single line, not lost as twelve small, unreconciled transactions that were never rolled up correctly.
This is a genuine integration requirement, not just a payments question: your website's donation flow, your donor CRM, and whatever process handles your annual 10BD filing all need to agree on the same donor record and the same running total across the year.
A practical build checklist
- Confirm with your payment gateway which providers actually support UPI Autopay mandate creation for donations specifically, since not every gateway integration has this built out equally well
- Design a dedicated recurring-giving page or section, separate from the one-time donation flow, with clear suggested monthly amounts
- Write plain-language mandate consent copy reviewed by someone who understands both the donor experience and the compliance requirement
- Build or confirm a working cancellation/modification path, visibly linked from donor communications, not just theoretically available through the donor's own UPI app
- Set up webhook handling so each successful recurring debit updates your donor CRM automatically
- Confirm your donor database aggregates a donor's total annual giving correctly, ready to feed into your Form 10BD filing at year-end
- Test the full cycle yourself with a small real mandate before launching it to donors — the pre-debit notification timing and the actual behaviour of the mandate over two or three cycles is worth verifying directly rather than assuming from documentation alone
One-time versus recurring: what actually changes on your website
| One-time UPI donation | UPI Autopay recurring donation | |
|---|---|---|
| Donor action per gift | Opens app, approves each payment individually | Approves once at signup; subsequent debits happen automatically below the threshold |
| Website's job | Process a single transaction and issue a receipt | Set up a mandate, then track a recurring schedule of separate debit events over time |
| Receipt/80G handling | One receipt per donation, straightforward | Consolidated annual Form 10BE covering all debits in the financial year for that donor |
| Where donors are lost | At the moment of donation, or simply never returning | Silently, if cancellation is confusing, or if a failed debit isn't followed up on |
| CRM requirement | Record a transaction | Track a live mandate status, plus every individual debit against it, reconciled continuously |
Common mistakes NGOs make with recurring giving
Treating "monthly" as a label, not a mechanism. Some donation forms let a donor select "monthly" as a frequency but still just process a single one-time payment, with no actual mandate or system prompting the next month's gift. This produces a donor who believes they've set up recurring giving and an NGO that never actually receives a second payment, discovered only when someone eventually checks.
No follow-up on failed debits. A lapsed mandate due to insufficient funds is not the same as a donor deciding to stop giving, but if nobody reaches out, it has the same practical effect. A simple automated message when a debit fails, giving the donor an easy way to update their payment method, recovers donors who would otherwise be silently lost.
Making cancellation harder to find than sign-up. Beyond the reputational risk already mentioned, this is also a compliance and goodwill problem specific to nonprofits, where donor trust is the core asset the organisation depends on. A donor who has to hunt for how to stop a recurring donation, or has to call and ask, remembers that friction longer than they remember the original act of giving.
Not distinguishing recurring donors in donor communications. A supporter who has committed to monthly giving deserves acknowledgement of that ongoing relationship — impact updates, an annual thank-you referencing their cumulative giving — rather than being treated identically to a first-time one-off donor in every subsequent email or WhatsApp message.
Losing the mandate reference when switching payment gateways. If your NGO changes payment gateway providers, existing donor mandates need a deliberate migration plan given the new portability rules, rather than assuming donors will simply notice their giving has stopped and re-enrol themselves.
Building the donor communication cadence around the mandate
The pre-debit notification NPCI requires is sent by the donor's own bank or UPI app, not by your NGO, which means it's easy to assume the communication side is handled and needs no attention from you. It doesn't fully cover what a donor actually wants to know from your organisation specifically: what their cumulative giving has funded, confirmation that a particular month's donation went through successfully, and a straightforward way to reach a human if something looks wrong. Building a simple automated WhatsApp or email sequence — a welcome message when the mandate is first set up, a light monthly acknowledgement, and an annual summary tied to their Form 10BE — does more for long-term retention than the payment mechanism alone, however smoothly that mechanism runs in the background.
Frequently Asked Questions
Is UPI Autopay only for large NGOs with significant payment infrastructure?
No — most major Indian payment gateways used by small and mid-sized NGOs now support UPI Autopay mandate creation as a standard feature, not an enterprise add-on. The bigger differentiator between organisations is usually whether the website and donor communications are actually designed around recurring giving, not the size of the NGO.
What happens if a donor's bank account has insufficient funds on the debit date?
The mandate debit simply fails for that cycle, similar to a bounced standing instruction, and most payment gateways will retry or notify both parties depending on their specific retry policy. This is worth confirming with your specific gateway, since retry behaviour and how failures surface in your dashboard vary by provider.
Can a donor set up UPI Autopay for donations above ₹15,000 a month?
They can, but debits above that amount require additional authentication at each cycle rather than processing frictionlessly, which works against the convenience recurring giving is meant to offer. For higher-value monthly commitments, it's worth discussing directly with major donors whether a different payment method suits them better.
Does FCRA apply to UPI Autopay donations from Indian citizens?
FCRA governs foreign contributions specifically, not domestic donations from Indian citizens or entities, so a standard UPI Autopay mandate from an Indian donor's Indian bank account sits outside FCRA's scope. FCRA compliance becomes relevant for foreign donor contributions, which is a separate part of your donation infrastructure with its own designated-bank-account requirements.
How is a recurring UPI donor different from a donor who just repeats a one-time donation manually every month?
Functionally, very differently, even though the money looks similar in your bank statement. A mandate-based recurring donor has pre-committed once and requires no further action to keep giving, which is precisely why retention tends to be dramatically higher than for donors relying on their own memory to repeat a manual donation — the entire value of building this properly is removing the monthly re-decision point.
Related Reading
Recurring giving is one part of a much broader donation infrastructure decision — our complete guide to NGO website costs in India covers how payment gateway integration and CRM features factor into overall budgeting for a donation platform.
How We Approach This at Govindani Infotech
Across the 500+ non-profit websites we've engineered, recurring giving has consistently been one of the features NGOs underinvest in relative to its actual value — a plain checkbox next to a one-time form, rather than a properly designed mandate flow with clear consent, an easy cancellation path, and a donor database that correctly aggregates a year's worth of monthly gifts for 80G filing. We build UPI Autopay integration as a first-class part of the donation flow, with the webhook handling and CRM sync needed to keep donor records accurate month over month, and we pair it with WhatsApp donor communications for renewal reminders and receipt confirmations donors actually see.
If your current site treats recurring donations as an afterthought, or you're planning a new donation platform and want this built correctly from the start, get in touch through our contact page to talk through your specific donor base and payment gateway.
Sources: NPCI — UPI Autopay for Recurring Payments, Medianama — NPCI to let users port UPI AutoPay mandates across apps, Razorpay — UPI Mandate: Meaning, Types & Benefits, ClearTax — What is Form 10BE, Due Date and How to Download Form 10BE of Income Tax, Patron Accounting — 80G Donation Rules 2026: Form 10BD & 10BE Compliance