Walk into almost any HR operations room in India and you’ll find the same thing in a drawer, a shared drive or an email thread: photocopies of Aadhaar cards. Front and back. Sometimes self-attested. Often blurry. Occasionally belonging to the wrong person.
For years, that copy was treated as identity verification. It never really was. A photocopy proves that someone had access to a card, or to a scanner. It doesn’t prove the card is genuine, that it belongs to the person in front of you, or that the details are current.
In 2026, that gap has a practical answer. Aadhaar app based offline verification lets an employer confirm a candidate’s identity at the source, with the candidate’s consent, without collecting a copy of the card at all.
Here’s how it works, where it fits in a background verification (BGV) process, and what it changes for HR teams.
The Challenge: Collecting Identity Is Not Verifying It
Most onboarding checklists still list “Aadhaar copy” as a mandatory document. That creates two problems at once.
The first is assurance. A scanned or photographed card can be edited in minutes. Changed fonts, swapped photographs, and altered dates are exactly the kind of edits verification teams see routinely. A copy offers no way to confirm that what you’re looking at was ever issued.
The second is liability. Every copy you store is personal data you’re now responsible for protecting, retaining correctly, and deleting on time. Multiply that by every candidate, including the ones you never hired, and a filing habit becomes a data governance problem.
How Aadhaar App Based Offline Verification Works
Offline verification is UIDAI’s framework for confirming an Aadhaar holder’s identity without the verifying organisation connecting to UIDAI’s central identity database. Organisations that use it are called Offline Verification Seeking Entities.
In practice, the flow looks like this.
1. The request. The employer triggers a verification request through a web portal, a kiosk or a QR code.
2. Consent in the candidate’s hands. The candidate receives the request in the Aadhaar app and explicitly approves it. Nothing moves without that approval.
3. Selective sharing. The candidate shares only the details the check requires. A check that needs a name and photograph doesn’t need to receive a full address or date of birth.
4. Proof of presence. On-device face verification confirms that the person sharing the credential is the person it belongs to.
5. A signed credential, returned securely. The verified details come back to the verifier’s system as a digitally signed credential. The verifier does not store the Aadhaar number.
UIDAI sums up the principle in three words: show, share, verify. The resident stays in control of what is revealed and to whom.
Adoption is moving quickly. The new Aadhaar app crossed 5 crore downloads by August 2026, and more than 200 offline verification entities have been onboarded since January.
What Changes for HR and Compliance Teams
You verify instead of collecting. The output is a signed confirmation of identity details, not an image of a card sitting in someone’s inbox.
You hold less data. Selective sharing means you receive only what the check needs. For a data protection officer, that’s the difference between minimising data by policy and minimising it by design.
Impersonation gets harder. Proof of presence ties the credential to a live person. That matters in remote hiring, where the person on the video call and the person who turns up on Day One aren’t always the same.
Onboarding gets faster. No chasing clearer scans. No manual matching of card details to forms. No back and forth over a blurred digit.
Where It Fits in a Complete BGV Process
Offline verification answers one question very well: is this person who they say they are? That’s the foundation of every background check, and it’s the step most often done badly.
It doesn’t answer the other questions a hiring decision depends on. Whether a degree was actually awarded. Whether an employment history is accurate. Whether there’s a criminal record or a pending court case. Whether the address on file is where the person lives today. The address on an Aadhaar record reflects the last update, which may not be current.
That’s why identity verification works best as the first layer of a complete background verification process, not a replacement for it. Once identity is established at source, every check that follows, from education and employment to criminal and address verification, is anchored to a verified person rather than a photocopy.
Three Questions to Ask About Your Current Process
If you’re reviewing how identity is handled in your hiring process, these three questions will tell you a lot:
• Is identity verified at the source, or matched against a document the candidate uploaded? • Does the candidate consent to specific details, and can you show a record of that consent?
• Is the Aadhaar number stored anywhere in your workflow, including emails and reports? The answers will tell you quickly whether you’re verifying identity or just filing it.
Key Takeaways
• A photocopy of an Aadhaar card is not identity verification. It proves access to a card, not ownership of it.
• Aadhaar app-based offline verification confirms identity at source, with the candidate’s consent, selective sharing, and proof of presence.
• The verifier doesn’t store the Aadhaar number, which reduces the personal data your organisation holds.
• Identity is the foundation of BGV, not the whole of it. Education, employment, criminal and address checks still matter.
The Bottom Line
Verifacts is a UIDAI partner, bringing Aadhaar app-based offline verification into background verification workflows. Combined with VIBE 2.0’s education, employment, criminal, and address verification, it gives HR teams one place to verify a new hire completely, starting with who they are.
