NGO Website Development in India: Designing a Donation Page That Donors Actually Complete
A donation page that gets completed is short, clear and trustworthy: it states what the gift achieves, offers a few sensible amounts, asks only for what is genuinely needed (and what 80G receipts legally require), works smoothly on a phone, and tells the donor exactly what happens next. Most donation pages that lose donors fail on basics rather than on design flair: too many fields, a confusing amount selector, a payment step that feels unfamiliar, or no reassurance that the money will be used as promised. This guide is for NGO leaders, fundraising managers and the people who commission NGO website development in India. It sets out what each part of the donation page should do, how to design the form, and how to test it without guessing.
It draws on how we approach donation pages when we build NGO websites. Govindani Infotech has engineered more than 500 non-profit websites, and the patterns below are the practical ones that come up again and again. We do not quote conversion percentages here, because they vary enormously by cause, traffic source and audience; the point is to give you a checklist and a testing method, not a promise.
The donation page has one job
Every element on the page should help one person complete one action. That sounds obvious until you look at the typical NGO donation page: a long story, a menu with twelve items, a sidebar of news, three competing buttons, a form with fifteen fields and a footer full of links. Each element is reasonable in isolation; together they add friction at the exact moment a donor has decided to give.
Think of the donation page as a checkout. It should be reachable in one click from every page of the website, readable in seconds, and finished in a minute or two. Everything else, such as detailed impact stories, annual reports and governance information, belongs on supporting pages that the donor can read first if they wish. For that supporting content, see our guide on building a transparency and impact section.
Page structure: what goes above the fold
The top of the page, visible without scrolling on a typical phone, should carry four things:
- A clear headline stating what the donor is doing: "Support a child's education" or "Fund a month of meals for a family". Specific beats generic.
- One or two sentences on what the donation achieves and who benefits.
- The donation form or its first step, not a button that leads to another page.
- A trust cue: your registration or tax-exemption status where it applies, and a visible indication that the payment page is secure.
Place the form where the donor's eyes land, not under a wall of text. If the story is important, put a short version above the form and the longer version below.
Designing the amount selector
The amount step is where many donors hesitate. Design it with these principles:
- Offer a handful of preset amounts, commonly three to five, plus a field for another amount. Too many choices slow the decision.
- Tie each amount to something tangible only if the link is true. "A gift in this range typically helps cover one month of school supplies for a child" works when it reflects your actual programme costs. Do not invent unit costs; use figures from your own accounts, and update them yearly. If you cannot back up a mapping, show amounts without it.
- Set sensible defaults. A default selected amount that reflects your typical gift reduces effort, but make sure it is easy to change.
- Show the currency symbol and format numbers the Indian way that your audience reads, and make the custom field accept plain digits.
- Be explicit about minimums. If the payment method or your policy requires a minimum, say so before the donor types, not after an error.
- Consider a monthly option as a visible choice, not a hidden checkbox. See below.
One-time and monthly giving
Monthly giving is the foundation of many NGOs' sustainability, but a recurring option only works if the donor understands what they are agreeing to. Present the choice as two clear tabs or buttons, "Give once" and "Give monthly", and state what happens: the amount, the date it recurs, how to change or stop it, and how receipts will be sent.
The technical side matters too. Recurring giving in India now relies on mandates that follow regulatory rules for authentication, notification and limits, and they differ by payment method. Rather than repeat the details here, read our guides on recurring monthly giving on an NGO website and UPI Autopay for recurring donations, and ask your developer to confirm current requirements with your payment provider before design is finalised.
Form fields: ask for the minimum, and explain the rest
Every extra field reduces completions, so each one must earn its place. Divide fields into three groups.
Always needed
- Name.
- Email address or mobile number, for the receipt and confirmation.
- Amount.
Needed for an 80G receipt, when the donor wants one
- PAN, which is required on a tax-deduction receipt in the form the rules prescribe, and address details where applicable. Confirm exactly which fields your chartered accountant needs you to capture. Ask for these only when the donor chooses to claim a tax benefit, using a clear toggle such as "I want an 80G receipt", so that donors who do not need one are not slowed down. Our guide to 80G-compliant donation platforms explains what a receipt must contain.
Needed only in special cases
- Foreign nationals or foreign-currency donors raise separate requirements under FCRA. If your NGO accepts foreign contributions, take specialist advice and read our FCRA payment gateway notes. Do not mix domestic and foreign donation paths without proper separation.
- Dedication or "in memory of" fields, if your campaign supports them.
Good form practice:
- Use the right keyboard. A mobile number field should open the numeric keypad; an email field should open the email keyboard.
- Label every field above the box, not as grey placeholder text that disappears.
- Validate as the donor types or on leaving a field, with specific, friendly messages: "PAN should be 10 characters, like ABCDE1234F".
- Support autofill so phones can complete name, email and address.
- Show progress if the form spans several steps, and let donors move back without losing data.
- Never require an account or password to donate. Offer account creation after the donation, if at all.
Consent and data protection
A donation form collects personal data, and in some cases sensitive financial identifiers. Tell donors in plain language what you collect, why, and how long you keep it. Provide a link to your privacy notice next to the submit button. Keep marketing consent separate from the transaction: a checkbox for updates must not be pre-ticked and must not be a condition of donating. India's data protection law and its rules are being phased in, so check current obligations with a qualified adviser. Our guide on donor data protection under the DPDP Act covers the practical steps for NGOs.
Trust: the quiet conversion factor
Donors, especially first-time ones, are asking silently: "Is this real? Will my money be used properly?" The page can answer without clutter:
- Registration details, shown accurately and kept current: legal registration, tax exemption status, and any certificates you hold. Only state what you can prove, and link to the documents.
- Where the money goes, in simple terms, linked to your annual report or financial summary.
- A named person or team and a way to contact you: phone, email and address.
- Secure payment cues: the standard browser padlock, and well-known payment methods the donor recognises.
- Real photographs and honest stories, with consent from the people shown.
- Privacy notice and refund or cancellation information.
Avoid fake urgency, invented counters and ticking clocks. Overstating need or progress damages trust and can breach consumer and charity advertising rules. A calm, honest page converts better over time than one that shouts.
Payment methods and failure handling
Indian donors expect to pay by UPI, cards, net banking and wallets, and many will pay from a phone with a UPI app installed. Offer the methods your payment provider supports and make the most common ones prominent. Be careful about how the payment step is presented: a redirect to an unfamiliar domain, with no explanation, looks like phishing. Tell the donor beforehand ("You will complete payment securely with our payment partner") and make sure the return page shows your branding.
Plan for failure. Payments fail for reasons unrelated to your site: bank downtime, a UPI app timeout, a lost connection. If failure ends in a blank error, you have lost a donor who wanted to give. A good failure state says what happened, whether the donor was charged, and offers a one-tap retry with details preserved. For slow networks and mid-range phones, see our guide to building a donation site for low bandwidth.
The thank-you page and the first receipt
The moment after payment is the best opportunity you will get to start a relationship. The confirmation page should:
- Thank the donor by name and state the amount received.
- Say when and how the receipt will arrive, and, when 80G applies, what the donor should expect.
- Offer one natural next step: share the cause, subscribe to updates, or consider monthly giving. Do not pile on five asks.
- Include a contact route if something looks wrong.
Send an immediate email or WhatsApp confirmation, followed by the formal receipt. Automating this with templates that include the donor's name and gift details reduces support queries and errors. See our guides on automated 80G receipts and common errors and sending donation receipts on WhatsApp. A short, warm welcome sequence in the weeks after the first gift helps donors feel seen; our article on the donor welcome journey outlines one.
Mobile first, because most donors are on phones
For many Indian NGOs, the majority of donation traffic arrives from a social media link or a WhatsApp forward opened on a phone. Design for that context:
- A single-column layout with large tap targets and generous spacing.
- A sticky donate button on long pages.
- Text that is readable without zooming, with strong colour contrast.
- Fast load, with compressed images and minimal scripts on the donation page. Our article on accessibility and donor trust covers contrast, labels and keyboard use.
- Local-language versions where your audience needs them; see our guide to the multilingual NGO website.
Test on real devices, including an older, low-cost phone, on a mobile connection rather than office Wi-Fi.
Measuring and improving without guesswork
You cannot improve what you do not measure, but you also should not act on a handful of donations. Set up tracking for the steps in the donor journey:
- Visits to the donation page, by source.
- Donors who start the form.
- Donors who reach the payment step.
- Completed donations, and failed payments.
Compare steps to find where the biggest drop occurs. If many drop at the amount step, review the choices. If many drop at the payment step, check failure rates and the redirect experience. If completed donations are low on one source but not another, the problem may be the audience or the message, not the form.
When you test changes, change one thing at a time and give each version enough traffic and time to mean something. For small NGOs with modest traffic, formal split tests are often impractical; instead, make a well-reasoned improvement, record the date, and compare the weeks before and after, keeping in mind seasonality and campaigns. Our guide to fundraising dashboard metrics lists what is worth tracking, and campaign attribution explains how to tie donations back to the campaign that earned them.
A pre-launch checklist for the donation page
- The page loads quickly on a mobile connection and is usable one-handed.
- Preset amounts are sensible and any impact mapping is backed by your real costs.
- One-time and monthly choices are clear, with terms stated.
- The form asks only for required fields; PAN and address appear only for 80G receipts.
- Validation messages are specific and kind.
- Payment methods work on test transactions, including failure and retry.
- The confirmation page and the email or WhatsApp receipt arrive and are correct.
- Receipt numbers, names and amounts match across systems.
- The privacy notice, consent wording and contact details are visible.
- Registration and tax-exemption information is accurate and current.
- Analytics events fire for each step, and bots and spam are filtered out.
- The page has been checked by someone who has never seen it before.
Campaign pages versus the main donation page
Most NGOs end up with two kinds of donation page. The main page serves general giving and is linked from the menu. Campaign pages serve a specific appeal, such as a disaster response, a festival drive or a school-year fund, and are linked from ads, emails and social posts.
Keep the form identical in behaviour across both so that receipts, reports and analytics work the same way, and vary only the headline, imagery, story and suggested amounts. A campaign page should carry a campaign identifier in its link, so that every gift can be traced back to the appeal that raised it. When the campaign ends, do not delete the page: redirect it to the main donation page or leave it up with a clear note that the appeal has closed, so that old links shared on social media do not lead donors to an error. Make sure the campaign's claims stay accurate; if a target has been met, say so rather than leaving a stale progress bar.
Work with us
Govindani Infotech Pvt. Ltd. is a website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009, and our NGO website service covers donation platforms, receipts and reporting. For the wider choices behind your site, read our overview of NGO website development in India and the must-have features of an NGO website. If you want us to review your current donation page or plan a new one, message us on WhatsApp or use the contact page.
Related reading: our guide on peer-to-peer fundraiser pages for NGOs goes deeper on this topic.
Once the page is live, measure it: our guide to donation analytics with GA4, UTM tags and a simple donor funnel shows which steps to track.
Not sure whether to build your own donation page or use a crowdfunding platform? Our comparison of an own donation website and a crowdfunding platform covers fees, donor data, receipts and the hybrid approach.
Frequently Asked Questions
What should an NGO donation page include?
A clear headline, a short explanation of what the gift achieves, a few preset amounts with a custom option, a one-time and monthly choice, a minimal form, visible trust information such as registration details, secure payment options and a clear confirmation and receipt process.
How many fields should a donation form have?
As few as possible: name, email or mobile number and amount for everyone, with PAN and address requested only when the donor wants an 80G receipt. Every extra field tends to reduce completed donations, so add one only when it serves a real purpose.
Should I ask donors to create an account?
No. Requiring an account adds a barrier at the moment of giving. Let donors give first, and offer an optional account or a magic-link login afterwards if you provide a donor portal.
Why do online donations fail, and what should the page do?
Failures often come from bank or UPI app downtime, timeouts or lost connections rather than your website. The page should explain what happened, say whether the donor was charged, and let them retry in one tap with their details preserved.
How can a small NGO test whether a donation page is working?
Track visits, form starts, payment attempts and completed donations, find the step with the biggest drop, then make one reasoned change at a time and compare similar periods. Small NGOs often lack the traffic for formal split tests, so careful before-and-after comparison with notes on campaigns is a sensible alternative.