What Is Aadhaar to UAN Verification API & Why HR Teams Need It
Let me tell you the moment this stopped being abstract for me. An HR lead I work with was sitting on a finance hire she'd chased for two months. Two panels, glowing references, offer being drafted. As a last box-tick she ran the employee UAN verification she'd just set up, mostly to test the integration.
The passbook data came back and didn't line up with the CV at all. Six years, two employers on the resume. The UAN showed three PF member IDs. One belonged to a company he'd never mentioned, sitting exactly across the eight months he'd called a "sabbatical." His end date at the last firm was wrong by nearly eleven months. She called the references again, of course. They were lovely people, who said lovely things, and none of them could pin down a date. The PF record had the dates. It always does.
The offer didn't go out. And she started telling every founder she met to ask the same question: what is Aadhaar to UAN verification API, and why isn't it in our onboarding yet?
What is Aadhaar to UAN verification API?
First, what it isn't, because vendors love to imply otherwise. You don't plug in an Aadhaar number and get a stranger's UAN and career history. Aadhaar identity and EPFO records live in different worlds with different consent rules, and any UAN verification API provider promising free-form lookups is selling you a compliance problem dressed up as a feature.
Here's what it really is. The UAN, Universal Account Number, is the single number EPFO gives a salaried employee, and it never changes between jobs. Under that one UAN sit the member IDs from every employer who ever deducted provident fund for them. What an Aadhaar to UAN API does, with the candidate's consent, is two things. Aadhaar UAN verification confirms the person in front of you actually owns the UAN they typed in, through the Aadhaar identity step. Then UAN number verification pulls the employment trail under that UAN: the member IDs, the establishments, the months contributions were paid.
So aadhaar to uan verification answers the one question interviews can't. Did the work history on this CV actually happen?
How Aadhaar to UAN verification API works
Candidates who've used it say it feels like any other onboarding form. They enter the UAN, tick the consent box (that consent matters, legally and practically), the identity check confirms they're who they say they are, and the UAN verification API fetches the PF history from EPFO via the authorised channel. HR gets a report a couple of minutes later: employer names, dates, gaps, laid beside the application.
People ask how aadhaar to uan verification api works when there's a mismatch, and that's the interesting part. A mismatch is not a rejection. I've seen all of these come up as "discrepancies" that were perfectly innocent: a stint at a tiny outfit under ten employees that doesn't come under EPFO at all, a real career break, an employer who got acquired and files PF under a name the candidate doesn't even recognise, an overseas posting. The API doesn't judge. It hands a recruiter the facts, and the recruiter asks the candidate one honest question. That distinction, facts from the machine, judgement from a person, is where the good implementations live.
Why references lose to this
References are a ritual more than a control, let's be honest. The candidate hands you the numbers. Usually a friendly ex-boss, sometimes a mate, and the people who don't answer the phone tell you more than the ones who do. Ask an honest referee "which month did he join?" and watch them guess. The contribution trail doesn't guess. Money went out of a payroll every month, or it didn't. A claimed three-year stint at a covered company with no PF trail is a pre-offer conversation, not a probation-period surprise.
Technically it slots into the same onboarding flow as everything else, digital consent, reports against the candidate record, statuses that route files instead of leaving them in an inbox. The consent management notes on our side cover the consent discipline, the API security guide covers wiring it in safely, and the white collar verification guide shows where it sits in the full hiring programme.
Picking a provider
Two things, beyond the obvious security questions. Watch what happens to consent, it should be explicit, logged, and visible to the candidate. And watch what happens when things go wrong: ask any prospective UAN verification API provider what your team is supposed to do at 9 a.m. on a peak offer day when their service is down. The answer tells you a lot.
Conclusion
Resumes are editable. References are rehearsed. The monthly PF contribution trail is neither, which is the whole pitch for an aadhaar to uan verification api. It costs very little, runs in minutes, catches both the inflated CVs and the innocent errors, and honest candidates have nothing in it to fear. Put it in onboarding, keep a human in charge of the discrepancies, and the offer that nearly went out on a story stops being the thing that surprises you in week three.