How Nagarathar Nalan Grew Donations 150% With a Verified, Anonymous Giving Platform

02The system before

The system before: phone calls, WhatsApp documents and manual transfers

The model worked on trust, but the process underneath it ran on conversations and forwarded files:

1. 01

   Verification

   Details of each person and their need were passed between volunteers and trustees over the phone, with documents sent on WhatsApp. Details were missed, and requests faced long delays.

2. 02

   Donor assurance

   Because the person seeking help stays anonymous, donors needed a foolproof way to know their money was spent well.

3. 03

   Disbursal

   Donations were dispatched manually, which led to mistakes and delays.

4. 04

   Collection

   Collecting donations was a manual process, full of friction for donors.

5. 05

   Records

   Managing and compiling donation records was tedious and unforgiving of error.

Anonymity and transparency pull in opposite directions. The process had to deliver both.

03The risk

Why it was risky to change

This system handles money, personal circumstances and community trust at the same time. A design that weakened any one of them would undermine the whole program.

• RiskAnonymity and transparency

  Donors needed confidence that money reached a real need, while the person in need could never be exposed. Transparency had to come from the process, not from disclosure.

• RiskPayment accuracy

  A transfer to the wrong account is hard to recover. Disbursal had to confirm the destination before any money moved.

• RiskRole separation

  Four kinds of users needed different, strictly limited views of the same records.

• RiskDonor documentation

  Donors rely on 80G certificates for tax purposes, so certificates had to be accurate and consistent for every donation.

04The architecture

The architecture: verification before money moves

We engineered a mobile app for iOS and Android, organized around four user roles with separate access levels. Users sign up with mobile number and OTP authentication, and both users and donation requests pass a two-step hybrid verification before a need becomes visible to donors, without the identity of the person asking.

Donors give through an integrated payment gateway across three categories. Before disbursal, penny-drop verification confirms that the recipient bank account is valid and correct. Dashboards and reports update in near real time, and 80G certificates are generated automatically.

What we engineered

• OTP onboarding

  Mobile number and OTP authentication for simple, secure sign-up.

• Two-step hybrid verification

  Users and donation requests are both verified before a need reaches donors.

• Four roles, separate access

  Role-based authentication and access control across four user roles.

• Three giving categories

  Donations are made and sought in three categories, so donors give where they choose.

• Penny-drop verification

  Bank accounts are verified before transfer, preventing payments to the wrong account.

• Dashboards and 80G certificates

  Advanced dashboards and reports at near real-time speed, and automatic 80G certificate generation.

Key tradeoffWe kept human verification in the loop rather than approving requests automatically. It takes hours rather than seconds, and that is what lets donors trust a request whose author they will never see.

05The results

The results

• 150%more donations

  Donations increased by 150%.

• Days→Hoursto verify

  The verification process timeline fell from days to hours.

• 900hours / month

  of manual work saved every month with automated workflows.

• 3new regions

  The donor network expanded beyond India to the US, Europe and the MENA region.

Transparency improved while the anonymity of help seekers was maintained, the combination the program depends on.

06Is this your situation?

Is your organization facing the same pattern?

The same controls apply well beyond charitable giving. This architecture fits organizations where:

• Approvals depend on documents shared over phone calls and messaging apps.
• Money moves only after several people verify a request.
• Stakeholders need proof of process without access to sensitive personal data.
• Payments, receipts and certificates are still issued manually.

Lending, claims, grants and any other disbursal workflow share these requirements. An architecture audit identifies where your approvals and payments are exposed to manual risk.

07Questions

Frequently asked questions