aadhaarpay.com (https://www.aadhaarpay.com/) is an independent research and educational platform on financial inclusion. This policy explains how we choose topics, do our research, write, correct mistakes, and keep our editorial work separate from money. It should be read together with our About page and Disclaimer.

Last updated: 3 October 2026

1. Our Purpose

aadhaarpay.com started as a notebook, not a business plan. Whenever a headline, a scheme brochure, or a well-meaning relative explained how digital payments "just work", we went and checked how they actually work: at the shop counter, for a first-time user, and when something fails. This site is that research, written down and shared.

India's Aadhaar-linked payments were our starting point. Our wider objective is to understand financial inclusion itself: the story behind each initiative, what works, what doesn't, and what any country or reader can learn from the comparison.

We aim to help readers form their own view, not to hand them our conclusions.

2. What We Are, and What We Are Not

• We are ordinary readers and researchers who share our research process and the reasoning behind it, with an educational and editorial purpose.
• We are not an official or government website, and we are not affiliated with UIDAI, NPCI, any government body, or any bank or company we write about.
• We are not a bank, payment app, or payment service, and we cannot apply for, update, or verify anything related to Aadhaar on your behalf.
• We are not financial, legal, or investment advisers, and we are not registered with SEBI, the RBI, or any other financial regulator.
• We are not a news service, a tips service, or a "get rich quick" publication. We do not chase headlines, and we do not tell readers which app, account, or provider to use.

3. Editorial Standards

1. Evidence before narrative. We test claims against data and primary sources wherever possible, and we say where the evidence is thin or disputed.
2. The story and the numbers. Each initiative we cover gets both: why it was started and how it evolved, and what the data shows about adoption, real usage, and outcomes.
3. What works and what doesn't. We set benefits, limitations, and criticisms side by side. We look for failures and stalled launches as well as success stories, because both teach something.
4. Adoption is not the same as use. We distinguish accounts opened from accounts actively used, launch-day figures from everyday reality, and access from trust.
5. Examples, not endorsements. Schemes, companies, and products named in a post are subjects of analysis. Naming one is not an endorsement, and leaving one out is not a criticism. We do not promote any app or provider.
6. Plain language, no pressure. We avoid unnecessary jargon, artificial urgency, fear-based framing, and "act now" language.
7. Honest about uncertainty. We separate facts, estimates, and opinions. Where numbers are simplified, rounded, or hypothetical, we say so.

4. How We Compare Countries

To keep comparisons fair, we try to ask the same four questions of every initiative:

1. Who drove it? Government, central bank, telecom operator, bank, or private fintech.
2. How were people onboarded and identified? The identity and account-opening model, and what it demanded of the user.
3. Did people keep using it? Whether sign-ups turned into real, continued use.
4. What happened to trust, fraud, and complaint handling? Including safety, privacy, and how problems get resolved.

We also note where context differs (country size, existing infrastructure, regulation, mobile coverage), so that readers do not mistake a comparison for a ranking or a recipe.

5. Research and Sourcing

• Primary sources first. We prefer official and original documents: government and regulator publications, central bank data, scheme documents and circulars, annual reports, and published research. Examples include UIDAI, NPCI, the RBI, the World Bank Global Findex, and national central banks.
• Company-reported figures are labelled. Numbers published by a provider about itself (users, agents, merchants, volumes) are identified as company-reported, and are not presented as independent data.
• Secondary and third-party sources. Where we use news, research summaries, or other third-party material, we aim to identify the source and the date, and we cross-check important figures where we can. Some third-party data may not be independently verified, and we flag this where it matters.
• When numbers disagree. Sources often differ because of different definitions, dates, or methods (for example, "registered users" versus "monthly active users"). Where this matters, we explain the difference instead of quietly picking one figure.
• Time-stamping. Schemes, limits, eligibility rules, and regulations change. Where a post depends on them, we aim to state the date or period the information reflects.
• Original work and attribution. Posts are written by us. We do not copy others' work, and where we quote or build on someone else's analysis, we attribute it.
• Images and logos. We do not use official logos or branding of UIDAI, NPCI, or any provider in a way that suggests endorsement, and we do not publish screenshots containing personal data.

6. First-Hand Accounts and Field Experiences

We value accounts from people who actually use these systems: merchants, agents, first-time users, and rural households. When we share one, we:

• Ask for consent before publishing, and explain how it will be used.
• Remove or change names, locations, and other identifying details unless the person clearly agrees otherwise.
• Never publish Aadhaar numbers, account numbers, OTPs, phone numbers, photographs of documents, or other sensitive personal data.
• Present accounts as individual experiences, not as proof of what is true for everyone.

7. Use of AI Tools

Some content may be researched, drafted, or edited with the assistance of AI tools, for example for drafting, editing, or checking calculations.

• AI output can be inaccurate, incomplete, or misleading. We do not publish factual claims or figures from AI tools without checking them against a reliable source.
• The author remains responsible for everything published on the site.
• Where a post shows AI-generated output as a demonstration, it is labelled as an illustration of a method, not as advice or a source of truth.

8. Independence and Conflicts of Interest

• Editorial independence. Advertisers, affiliates, sponsors, and the organisations we write about do not influence what we write or what conclusions we reach. We do not accept payment to publish, change, or remove an analysis.
• Advertising. The site may display third-party advertisements. We do not choose them individually, and an advertisement is not an endorsement.
• Affiliate and referral links. Some links may earn us a commission at no extra cost to you. These earnings help cover the running costs of the site. A link's presence does not mean we endorse the product.
• Sponsored content. Any sponsored or paid content will be clearly labelled and kept separate from our independent analysis.
• Our own use. The author(s) may personally use some of the services we discuss. Where this is relevant to a post, we aim to say so.
• No money handling. We do not accept, pool, or manage anyone's funds, and we will never ask you to send money for any purpose.

9. Opinions and First-Person Writing

Many posts are written in the first person as a record of how we looked at a subject at a point in time. Views may change as new evidence appears, and older posts may no longer reflect our current thinking. Where we criticise a scheme, product, or organisation, we aim to base it on public, verifiable information and to present the other side fairly.

10. Corrections and Updates

• We want to get things right, and we correct errors when we find them or when readers report them.
• Minor corrections (typos, formatting, small clarifications) are made quietly.
• Substantive corrections (a wrong number, source, or conclusion) are made in the post itself, with a visible note describing what changed and when.
• Outdated content. Where a post has been overtaken by rule changes or new data, we may update it, add a dated note, or mark it as outdated.
• To report an error, write to us at domain[DOT]coordinator[AT]gmail[DOT]com with the post link, the issue, and a source if you have one.

11. Contributors

We welcome contributors who share our approach. Prospective contributors are reviewed before being included. All contributed work is edited to the same standards as the rest of the site, and contributors are expected to disclose relevant conflicts of interest, such as employment by, or payment from, a provider they write about. We may decline, edit, or remove contributions that do not meet this policy. Contributors are not authorised to speak on behalf of, or give advice in the name of, aadhaarpay.com.

12. Comments and Reader Interaction

Comments are welcome, but views expressed in them belong to the commenter and are not endorsed by aadhaarpay.com. We may remove comments that are spam, abusive, defamatory, or promotional, that solicit money, or that contain personal or sensitive information. Please do not post or email us your Aadhaar number, OTP, PIN, passwords, bank or card details, or biometrics.

13. Content We Do Not Publish

• Recommendations to open, use, or switch to a particular account, app, or provider, or promises of returns or benefits
• Personalised advice, or answers to individual "what should I do with my money" requests
• Step-by-step methods that could help someone commit fraud, bypass identity checks, or misuse another person's Aadhaar or account
• Anyone's Aadhaar number, personal data, or document images
• Paid promotion disguised as independent analysis
• Content that is misleading, plagiarised, defamatory, or designed to create panic or false urgency

We do publish safety information, such as how scams work at a general level and how to spot red flags, so that readers can protect themselves.

14. Privacy

How we handle personal information is described in our Privacy Policy.

15. Changes to This Policy

We may update this policy from time to time. The "Last updated" date above shows when it was last revised.

16. Contact

Questions, corrections, or feedback about our editorial approach? Write to us at domain[DOT]coordinator[AT]gmail[DOT]com or use our Contact page.