NGO Website Development in India: Why Your NGO Darpan ID Now Belongs on Your Website
A valid NGO Darpan ID from NITI Aayog has quietly become one of the load-bearing credentials of Indian nonprofit compliance — required before you can file CSR-1 to receive corporate funding, required as a prerequisite for FCRA registration and renewal, and increasingly checked during routine bank KYC — and yet most NGO websites in India still don't display it anywhere a corporate donor or CSR team can actually find it. NGO website development in India in 2026 needs to treat the Darpan ID less like a filing-cabinet document and more like a visible trust signal, sitting next to your 12A and 80G numbers on the page a serious funder actually reads before writing a cheque.
What NGO Darpan actually is
The NGO Darpan portal, run by NITI Aayog and accessible at ngodarpan.gov.in, is a free national registry that gives every registered voluntary organisation, society, trust or Section 8 company a unique eleven-character DARPAN ID and a downloadable registration certificate. It was originally built as a way for government departments and PSUs to identify legitimate NGOs when disbursing grants, but its role has expanded substantially: it's now referenced by the RNPO application under Section 332 of the Income-tax Act, 2025, by the Ministry of Corporate Affairs' CSR-1 filing that companies must complete before routing CSR funds to an NGO, and by FCRA registration and renewal applications with the Ministry of Home Affairs. In practical terms, the Darpan ID has become the identity number that other, more consequential registrations now point back to.
Why This Sits Ahead of 80G and FCRA in the Compliance Sequence
For an NGO founder trying to get the order of operations right, it helps to see where Darpan actually sits: it's typically the first registration obtained, precisely because later ones require it. CSR-1 — the filing that legally permits a company to direct CSR spending to your organisation — asks for your Darpan ID as part of the application. FCRA registration and renewal similarly expect it as supporting documentation establishing your organisation's basic identity and track record. And while 12A/80G tax-exemption status is a separate registration handled through the Income Tax Department rather than through Darpan directly, a corporate donor conducting due diligence before a CSR partnership will typically expect to see all of these — Darpan ID, 12A/80G or RNPO status, and CSR-1 eligibility — presented together as a coherent compliance picture, not as documents they have to request one at a time over email.
This is exactly the gap a well-built NGO website should be closing, and mostly isn't. An NGO that has done the work of obtaining Darpan, RNPO/12A, 80G and, where applicable, CSR-1 and FCRA registrations, but presents none of it clearly on its own website, is effectively asking every prospective corporate partner to take its compliance on faith or chase the details down independently — exactly the friction a five-minute website update could remove.
The Website Problem: Compliance That Exists But Isn't Visible
Talk to almost any established Indian NGO and you'll find the Darpan certificate, the 12A order, the 80G certificate and the FCRA registration all exist as PDFs somewhere — in an admin's email, in a shared drive, occasionally in a physical file. What's far rarer is a single page on the organisation's own website where a corporate CSR team, a foundation program officer, or an individual major donor doing their own due diligence can see the Darpan ID, confirm it against the organisation's registered name, and find the other key registration numbers in one place, without emailing to ask.
This matters more in 2026 than it did five years ago because CSR due-diligence processes have become more systematic. Corporate CSR teams increasingly check an NGO's Darpan profile as a standard step before finalising a partnership, and an organisation whose own website can't even confirm the same information the CSR team is independently verifying creates an unnecessary moment of doubt at exactly the point where a funding relationship is being decided. A visible, accurate compliance page doesn't replace the CSR team's own verification — it removes friction from a process that's happening either way.
What an NGO Website Should Actually Include
Based on what CSR due-diligence processes typically look for and what the Darpan registration itself asks organisations to maintain, a well-built compliance or "about us" page for an Indian NGO in 2026 should include, plainly and in one place:
- Darpan ID, displayed as text (not only as a scanned image, which search engines and quick manual checks can't read), alongside a link to or clear reference for verification on the official ngodarpan.gov.in portal.
- 12A/RNPO registration details, since every previously 12A-registered NGO transitioned to RNPO status under the new Income-tax Act framework, and a donor checking your tax-exemption status will expect current terminology, not a reference to a status category that's since been superseded.
- 80G registration number and validity period, since donors claiming a tax deduction need this to be current and correctly stated, not just present.
- CSR-1 registration number, if obtained, since this is specifically what a corporate CSR team is checking for before a partnership can proceed legally.
- FCRA registration number, if your organisation is FCRA-registered, along with a clear statement of whether foreign contributions are accepted at all — a page that's silent on this leaves a foreign or diaspora donor unsure whether they can legally give.
- The organisation's registered legal name exactly as it appears on Darpan, since a mismatch between your public brand name and your registered legal name is one of the most common sources of confusion during a corporate donor's verification process.
None of this needs to be a separate microsite or a complex build — a single, clearly linked "Registrations & Compliance" or "Transparency" page, kept current, does the job. What matters is that it exists, that the numbers are accurate and current, and that it's linked from the main navigation or footer rather than buried three clicks deep.
The Five Registrations an NGO Website Should Explain, Side by Side
A recurring source of confusion — for donors as much as for NGOs themselves — is that Darpan, RNPO/12A, 80G, CSR-1 and FCRA are five distinct registrations issued by different authorities for different purposes, but they're routinely mentioned in the same breath as if they were interchangeable proof of "being a proper NGO." A compliance page that briefly explains what each one actually does, rather than just listing numbers, does more to build donor confidence than the numbers alone:
| Registration | Issued by | What it actually establishes | Why a donor checks it |
|---|---|---|---|
| NGO Darpan ID | NITI Aayog | Basic national identity record for the organisation | Prerequisite for CSR-1 and FCRA; increasingly checked directly by CSR teams |
| RNPO status (formerly 12A) | Income Tax Department | Income-tax exemption on the NGO's own qualifying income | Confirms the NGO itself doesn't pay tax on eligible income — a baseline legitimacy signal |
| 80G registration | Income Tax Department | Donor's right to claim a tax deduction on their donation | Directly affects the donor's own tax filing — they need this to claim the deduction |
| CSR-1 registration | Ministry of Corporate Affairs | Legal eligibility to receive CSR funds from companies | Mandatory before a company can direct CSR spending to the NGO at all |
| FCRA registration | Ministry of Home Affairs | Legal permission to receive foreign contributions | Confirms whether the NGO can legally accept a donation from outside India |
Presenting the five side by side, with a one-line explanation of each, does two things a bare list of numbers doesn't: it signals that the organisation itself understands its own compliance position (which a sophisticated CSR team notices), and it answers the donor's actual underlying question — "can I legally give to this organisation, and can I claim what I'm entitled to claim" — rather than requiring them to know what each acronym means.
How to Actually Register for a Darpan ID
For an NGO that doesn't yet have a Darpan ID, the process runs entirely through the ngodarpan.gov.in portal and doesn't require a consultant, though many organisations do use one to save time gathering documents. In outline: create an account on the portal with the organisation's basic details and a valid email and mobile number; upload the organisation's registration certificate (trust deed, society registration, or Section 8 incorporation certificate, depending on legal structure), PAN, and details of key functionaries such as the board members or trustees; and submit the application for review. There is no government fee for Darpan registration itself. Processing time varies, but organisations should treat it as a task to complete well before it becomes an urgent blocker to a CSR-1 filing or FCRA deadline, not something to start under time pressure once a specific corporate partnership is already on the table.
Once approved, the Darpan certificate and ID are downloadable directly from the portal, and it's this exact document — not a photocopy of an old trust deed — that should be the source for whatever appears on your website's compliance page, kept current if any registered detail changes.
Common Mistakes Worth Avoiding
Treating the Darpan ID as a one-time task, never revisited. Registered addresses change, board members change, and an NGO's legal name occasionally changes with rebranding — none of these automatically update on the Darpan portal without the organisation doing so. A website compliance page pointing to outdated Darpan details is often the first place a discrepancy becomes visible to an outside party.
Publishing a scanned certificate image with no accompanying text. A screenshot or PDF scan of the Darpan certificate embedded on a page satisfies a visual "we have this" impression but isn't machine-readable, isn't searchable, and is harder for a donor to quickly cross-check against the government portal. The ID and key details should appear as actual page text, with the certificate image as a supporting visual, not the only source.
Conflating Darpan ID with 80G or FCRA registration numbers in casual language. It's common, especially in donor-facing copy written quickly, to refer to "our NGO registration number" without specifying which of the five distinct numbers is meant. Precision here isn't pedantic — a CSR due-diligence reviewer checking a specific registration against a specific government database needs the specific number, not a generic reference to "being registered."
Frequently Asked Questions
Do we need to publish our Darpan ID publicly, or is it only used for internal filings?
There's no legal requirement to publish it on your website, but there's a strong practical case for doing so voluntarily: it's a piece of information corporate donors and CSR teams are already checking independently, and making it easy to find on your own site removes a step from their due-diligence process rather than leaving them to search the government portal unprompted. Organisations competing for CSR partnerships increasingly treat this kind of transparency as a differentiator, not just a compliance checkbox.
We're a small NGO without Darpan registration yet — how urgent is getting one?
If you plan to seek CSR funding from companies at any point, it's worth prioritising, since CSR-1 filing typically requires it as supporting documentation. Registration itself is free and handled directly through the ngodarpan.gov.in portal, so the barrier is mainly the time to gather the required organisational documents, not cost.
Does having a Darpan ID mean we're automatically eligible for CSR funding?
No — Darpan registration is a prerequisite that supports the CSR-1 filing process, not a substitute for it, and CSR-1 itself is a separate filing with the Ministry of Corporate Affairs that establishes your formal eligibility to receive CSR funds from companies. Think of Darpan as one required building block in a sequence, alongside 12A/RNPO and 80G status, rather than a standalone approval.
Our Darpan certificate lists an old organisational name or address — does that need to be fixed before we display it?
Yes, and before you rely on it for a CSR-1 filing or FCRA application too. A mismatch between what's on your Darpan certificate and your current registered details is exactly the kind of discrepancy a corporate donor's due-diligence team is trained to flag, and it's a straightforward update to request through the portal rather than something to leave inconsistent and hope nobody checks closely.
Does displaying our Darpan ID and other registrations on our website create any privacy or security risk?
Registration numbers like a Darpan ID, 80G certificate number or FCRA registration number are not sensitive personal data in the way, say, individual donor payment details are — they're identifiers meant to be checkable against public government records, and the entire value of displaying them comes from that verifiability. The genuine privacy consideration for an NGO website sits elsewhere: donor and beneficiary personal data, which should be handled separately and securely, not conflated with organisational compliance numbers that are meant to be public-facing.
Should our compliance page also mention our total funds raised or number of beneficiaries served?
Only figures you can actually stand behind with your own audited or verifiable records — a specific beneficiary count or funds-raised figure carries real weight with a donor precisely because it implies it's been checked, so an inflated or unverifiable number is a bigger credibility risk than simply not stating one at all. If a figure isn't confidently sourced from your own records, it's safer to describe your work in accurate general terms than to publish a number you can't defend if a donor asks how it was calculated.
We work with both domestic CSR partners and international foundations — does the compliance page need to look different for each?
The underlying facts stay the same, but the emphasis is worth adjusting for the audience reading it. A domestic CSR team is primarily checking Darpan ID, CSR-1 eligibility and RNPO/12A-80G status, since those govern whether their company can legally direct funds to you and whether their own reporting is in order. An international foundation or overseas individual donor is more likely to be checking FCRA status first, since that determines whether they can give at all. A single well-organised compliance page that clearly labels each registration and what it covers serves both audiences without needing two separate pages — it's the labelling and clarity that matters, not duplicating the content.
Where to Start
Govindani Infotech has engineered 550+ non-profit and donation platforms among 900+ websites built from Pune since 2018, and a clearly presented compliance page — Darpan ID, RNPO/12A status, 80G number, CSR-1 and FCRA details where applicable — is now a standard part of every NGO website we build, not an optional extra requested after the fact.
If you're planning NGO website development or reviewing whether your existing site actually surfaces the registrations a corporate donor will look for, we're happy to review your current compliance page and tell you plainly what's missing. You can see the general approach we take to website builds, compare NGO-specific pricing on our NGO website pricing page, or browse completed nonprofit projects in our NGO portfolio — and reach out on WhatsApp if you'd like a second opinion before your next CSR proposal goes out.