NGO Website Development in India: Building a Donor Help Page for Receipt Requests, Failed Payments, Wrong Amounts and Data Corrections
A donor help page is a single, easy-to-find page on your NGO website that tells people what to do when something goes wrong with a donation: the payment failed but the bank shows a deduction, the receipt never arrived, the amount or PAN was entered wrongly, or a donor wants to change or stop a recurring gift. Done well, it answers common questions in plain language, collects each request through one structured form, and gives your team a trackable queue instead of a scatter of phone calls and personal WhatsApp messages. This guide explains what such a page should contain, how to build the request form and workflow, what to promise and what not to, and how to connect it to your records and to Indian data-protection duties. It is written for NGO website development in India, where donors use UPI, cards and net banking, expect a receipt and often write to you on WhatsApp.
We keep to the website side. Tax treatment of donations, the rules for deductions and the handling of foreign contributions belong with your chartered accountant and legal adviser; the page should say so and should not make promises in their place.
Why a help page is worth building
Donors rarely contact an NGO to complain; they contact it because they are worried. A person whose money has left their bank account but who has no receipt feels uncertain about whether the gift arrived. Staff who answer these worries one by one, from memory, make inconsistent promises and lose time. A help page does three things:
- It answers the common questions at once, so many donors never need to write.
- It captures the rest in a consistent way, with the details your team needs to look up the donation without a second round of questions.
- It protects trust. A donor who sees a clear process and a realistic response time is more likely to give again than one who receives silence.
It also protects your staff. A shared, written process means that when a team member is away, the next person can pick up a request and know what has been promised.
The six situations a donor help page must cover
Review your own email and WhatsApp history for the last three months and count the requests by type. The following six are common for Indian NGOs, but your list may differ.
1. "My payment failed but money was deducted"
This is the most anxious situation. Payment failures and delays occur between the donor's bank, the payment network and your payment gateway, and the website often cannot tell which step went wrong. The page should explain, in plain words:
- that a deduction without a confirmation can occur, and that in many cases the amount is automatically returned to the donor's account by the bank or payment provider after a period that depends on the bank and payment method;
- that donors should keep the transaction reference or screenshot;
- how to check the status on your site, if you provide a lookup;
- how to contact you with the transaction reference and the date.
Do not promise a refund time you do not control. State what donors can verify themselves and what you will do after receiving the reference. TODO: confirm with your payment gateway the typical reversal timelines for each payment method and quote them only as "usually" ranges that the provider has confirmed. Reserve any reference to the Reserve Bank of India's rules on failed-transaction timelines for a statement your adviser has checked against the current circular.
The technical side matters too. Your site should record a pending payment as pending, and only mark it successful on a confirmed gateway notification. If your system treats a closed browser tab as a failure, you will lose track of payments that succeeded. See our guide to donation records and reconciliation exports for how to keep the website, gateway and bank statement aligned, and our article on building an NGO donation checkout with webhooks and testing for how payment status should flow.
2. "I did not receive my receipt"
The cause is usually small: a typo in the email address, a spam folder, an email that was delayed, or a receipt that could not be generated because of a missing field. The page should offer a self-service route first, because it is faster for the donor and cheaper for you:
- a "Find my receipt" form that asks for the email or mobile number and the approximate date, then sends the receipt to the address on record;
- a note to check spam or promotions folders;
- a link to the donor account area if you have one. Our article on a donor account area with giving history and receipt downloads explains how to build this.
To avoid leaking donor information, the lookup must never display a donor's details to whoever types an email address. It should send the receipt only to the address or number already on file, and show a neutral message such as "If we find a matching donation, we will send the receipt" in either case.
3. "I entered the wrong amount, name, PAN or address"
Donors make mistakes, particularly on mobile. Receipts that carry the wrong name or PAN may matter to the donor's own tax filing, and an incorrect amount creates an accounting mismatch. The page should say:
- which details can be corrected and which cannot (for example, the amount of a completed payment normally cannot be changed, though a refund and re-donation might be possible);
- what proof you will ask for (for example, a copy of an identity document, if your policy requires it), and why;
- how a corrected receipt is issued, and that the original is cancelled and recorded as such, not silently overwritten.
Your accountant should decide how corrected receipts are numbered, whether a revised or duplicate receipt is issued, and how it is labelled. The website should make it easy to follow that rule, for example by storing the cancelled receipt and its replacement as linked records. Do not delete the original. TODO: record your accountant's rule for corrected receipts in your internal procedure.
4. "I was charged twice" or "I want a refund"
Duplicate payments happen when a donor taps twice, the page reloads or two sessions run at once. Your page should explain how to report it and what you need: both transaction references, dates and amounts. It should also state your refund policy honestly. Some NGOs refund genuine duplicate or mistaken payments; some do not refund donations at all as a matter of policy; and some rules depend on the donor's payment method or on whether the gift was a recurring one. Write down what your organisation actually does and say it plainly, with your accountant's agreement. If refunds are possible, say how long the review takes and that the time for the money to reach the donor's account depends on their bank.
On the technical side, prevent duplicates where you can: disable the donate button after the first tap, use an idempotency reference so that the same attempt cannot create two orders, and show a clear "processing" state.
5. "I want to change or stop my monthly donation"
Recurring donors need a simple, dignified way to change the amount, pause or stop, and a page that makes this hard damages trust and may create complaints with the donor's bank. If the donor can manage a recurring gift in an account area, link to it. If changes must go through your team, the page should explain how, and your system must reflect the change before the next scheduled debit. See our guides on recurring monthly giving and UPI Autopay for recurring donations for how the mechanics differ between payment methods.
Do not use the help page to try to talk donors out of cancelling. Offering a lower amount or a pause is reasonable if it appears as a choice next to the cancel option and not instead of it.
6. "How is my data used, and can I correct or delete it?"
Donors may ask what you hold about them, want it corrected, want to stop receiving messages or want it deleted. India's Digital Personal Data Protection Act, 2023 gives individuals rights regarding their personal data and places duties on organisations that decide how it is used, and the implementing rules are being phased in. TODO: confirm the current commencement dates for the DPDP Rules and the exact rights and grievance-handling duties that apply to your organisation, and have your legal adviser review the wording. Your help page should therefore:
- link to your privacy notice in plain language;
- offer a clear route to correct details, withdraw consent for marketing messages and ask about deletion, with a named contact;
- explain that some records, such as receipts and accounts, may have to be kept for legal or audit reasons even after other data is removed, if that is your position, after your adviser has confirmed it;
- make unsubscribing from emails and WhatsApp messages as easy as subscribing.
Our guide to NGO donor data protection under the DPDP Act explains the data side in more depth.
Designing the page itself
Put the help link where worried people look
A help page that nobody can find solves nothing. Place a "Donor help" link in the footer of every page, on the thank-you page after a donation, in the receipt email and in the failure message when a payment does not complete. Use plain labels such as "Need help with a donation?" instead of "Grievance redressal".
Structure the page by the donor's problem
Open with a short statement of what the page covers and how quickly you normally respond. Then list the six situations as short headings with two to four sentences each, and a single button or link for each next step. Put the most urgent one, the payment deducted without a receipt, first. A donor reading on a phone should see the answer to their situation without scrolling through unrelated text.
Use plain language and give honest timelines
Avoid legal or banking jargon where you can. State response times you can actually meet, for example "We reply within two working days", and have someone responsible. If you cannot staff a promised time during a campaign peak, change the promise rather than breaking it. Our guide to traffic spike readiness for campaigns explains how to plan for the busiest days, which are also the days support requests pile up.
Keep it accessible and light
Many donors use older phones on slow connections, and some use screen readers. Make the page text-based, with proper headings, form labels and error messages, and avoid heavy images. See our articles on accessibility and donor trust and low-bandwidth mobile donors.
Building the request form
A structured form beats a general "contact us" box because it makes donors supply the details your team needs.
Fields to include
| Field | Why you need it | Notes |
|---|---|---|
| Request type | Routes the request and sets the checklist | A dropdown with the six situations plus "other" |
| Name | To address the donor | As used on the donation |
| Email and mobile number | To reply and to find the record | Ask for the ones used on the donation |
| Approximate date and amount | To locate the transaction | Optional but useful |
| Transaction reference or UTR | The fastest way to find a payment | Explain where donors find it; make it optional |
| Details | Free text for the problem | Short limit with a counter |
| Attachment | Screenshot of the bank message | Optional; limit type and size and scan files |
| Consent line | How you will use their details to respond | Link to the privacy notice |
Keep the number of required fields small. Do not ask for a full PAN or identity documents in the first form; request them only if the request type needs them, through a secure follow-up. Never ask donors to send card numbers, CVV, OTPs or net-banking passwords, and say so on the page. Your team will never need them. A short line such as "We will never ask for your card number, OTP or password" is a useful warning against fraudsters who imitate NGOs.
Protect the form from spam and abuse
Public forms attract bots. Add server-side checks, rate limits and a spam-protection challenge that does not block real donors. Our guide to contact form spam and bot protection covers options that do not rely on hard-to-read puzzles.
Confirm receipt immediately
After submission, show a confirmation with a reference number and the expected reply time, and send the same by email or WhatsApp if the donor has opted in. A donor who receives "We have received your request, reference HELP-0231, and will reply within two working days" is far less likely to submit it again or call.
Building the back-end workflow
The form is only the front door. What happens next decides whether the page is useful.
One queue, one owner
Send all requests to a shared queue that more than one person can see: a helpdesk tool, your CRM or even a well-structured spreadsheet at small scale. Assign each request an owner and a status such as New, Checking, Waiting for donor, Resolved. If you use a CRM, link the request to the donor record so that staff see the giving history. Our guide to NGO donor CRM software explains what to look for, and our CRM services can connect a request form to your donor database.
Give staff a checklist for each request type
Write a short internal checklist per type. For "payment deducted, no receipt", for example: find the transaction in the gateway dashboard by reference or amount and date; check whether the payment is successful, pending or failed; if successful, check why the receipt was not sent and resend it; if failed or pending, tell the donor the status and what usually happens next; record the outcome. Checklists keep answers consistent and make it possible to train a new volunteer in an hour.
Use templates, but keep them human
Prepare reply templates for each type, with the donor's name and reference filled in automatically, and edit them where the case differs. A reply should say what you found, what you did and what the donor should expect next. Avoid pasting policy text without explanation.
Handle WhatsApp carefully
Many donors will write to your WhatsApp number whatever your page says. Decide whether WhatsApp is an official channel for help. If it is, say so on the page, state the working hours, and use the WhatsApp Business app or API with shared access, not a personal phone. If it is not, say so and direct donors to the form. Keep in mind that messages you send outside the customer-service window may need approved templates and consent. Our overview of the WhatsApp CRM integration explains how conversations can be logged against donor records, and our article on WhatsApp Business API usernames and CRM covers a change in how contacts are identified.
Record and review
Log each request's type, dates received and resolved, and outcome. Review monthly. If half your requests are "no receipt", fix the receipt emails; if many are "failed payment", investigate the checkout. The help page then becomes a diagnostic tool and not just a cost.
What not to promise
- Do not promise refunds or reversal times you do not control. Describe what normally happens and what you will do.
- Do not promise tax outcomes. Say that eligibility for a deduction depends on the donor's circumstances and your registration, and refer them to their adviser.
- Do not promise deletion of everything. Some records may have to be kept. Say which and why, after taking advice.
- Do not publish donor details. Never show names, amounts or contact details in public status pages or comments.
- Do not collect sensitive credentials. Never ask for card details, OTPs or passwords.
- Do not pretend a human replies when it is automated. Be clear about what is automatic.
A worked example: a hypothetical Pune education trust
Imagine a small education trust in Pune with an online donation page and a team of three. In its first campaign month, staff answer donor worries on four personal phones and cannot say how many remain open. It builds a donor help page in a week.
- The page lists six situations, with the payment-deducted one first, and a "Find my receipt" box that emails the receipt to the address on file.
- The request form has a dropdown, contact details, an optional transaction reference and an optional screenshot. It never asks for card details, and it says so.
- Requests go to one shared queue in the trust's CRM, with an owner and a status. Each type has a six-line checklist.
- A confirmation with a reference number appears on screen and is emailed.
- The accountant reviews the wording on corrected receipts and refunds, and the trust adds a line stating what it does and does not refund.
- After a month, the trust counts requests by type, finds that most are "no receipt", and finds that a spam filter on a common email provider is catching its receipts. It adjusts its sending setup. See our guide to email deliverability with SPF, DKIM and DMARC for that kind of fix.
The trust and the figures in this example are illustrative and do not describe a real organisation.
Related reading: If your donors read Hindi or Marathi, the help page should exist in those languages too; our guide to building a multilingual donation website covers how.
Related: see our guide to building the NGO contact and grievance page.
Frequently Asked Questions
What should an NGO do if a donor's money was deducted but no donation was recorded?
Ask the donor for the transaction reference and date, then check the payment gateway dashboard to see whether the payment succeeded, is pending or failed. If it succeeded, record it and send the receipt. If it failed or is pending, explain the status and that the bank or payment provider normally returns failed amounts automatically, without promising a specific time you cannot control.
Can an NGO change the name or PAN on a receipt after issuing it?
Often a corrected receipt can be issued, but the rules for how to cancel, reissue and number it should come from your chartered accountant. Keep the original on record, mark it as cancelled and link it to the replacement instead of overwriting it.
Should an NGO use WhatsApp for donor support?
It can work well because donors already use it, but only if you treat it as a managed channel: a business account with shared access, stated hours and a record of conversations. Do not run support from a personal phone, and be mindful of consent and template rules when you message first.
How quickly should an NGO answer donor help requests?
Choose a time you can reliably meet, such as two working days, and say it on the page. A realistic promise that you keep builds more trust than a fast promise you miss during a campaign peak.
Do donors have the right to ask an NGO to delete their data?
The DPDP Act gives individuals rights over their personal data, but some records may need to be kept for legal or audit reasons. Offer a clear contact route, and ask your legal adviser to confirm what you must delete, what you must keep and the timelines that apply to you.
If you also thank supporters publicly, see how to build a donor wall and supporter recognition page without exposing donor data.
Related reading: Writing the Donation Refund, Cancellation and Terms Pages Donors, Payment Gateways and Auditors Expect.
Sources: Digital Personal Data Protection Act, 2023 (Government of India), Reserve Bank of India: Harmonisation of Turn Around Time (TAT) and customer compensation for failed transactions, NPCI: UPI procedural guidelines and dispute resolution, Income Tax Department of India. Legal and banking rules change; confirm each point with your chartered accountant, legal adviser and payment provider before publishing.
Working with Govindani Infotech on donor help and donation records
Govindani Infotech is a Pune-based website design and development company at 2nd Floor, Landmark Plaza, 206 Satara Road, Parvati Paytha, Pune 411009, and we have built donation websites for more than 500 non-profit organisations. We build the donation flow, receipts, records and request forms on the NGO website platform so that donor help requests connect to the underlying donation data.
If you would like to review how your own site handles failed payments, receipts and donor requests, message us on WhatsApp at wa.me/919201958278 or use the contact page. You can also see how we approach a new build on our website creation page.
About the author: written by the Govindani Infotech NGO website team in Pune, drawing on our experience building and supporting non-profit donation websites.