Aadhaar gives more than a billion people a twelve-digit identity number backed by demographic and biometric data. At that scale, even a very good authentication rate produces a large number of failures.
The crucial design decision is what failure means.
If a fingerprint does not match while unlocking a phone, the owner can enter a code. If it fails while collecting food or wages, the system has placed a technical confidence score between a person and an entitlement.
UIDAI’s own materials acknowledge poor fingerprint quality, network availability and other technological or biometric limitations. They require service providers to maintain alternate identification and exception-handling processes so genuine residents are not denied service.
That requirement reveals the real architecture. Aadhaar is not only a biometric system. It is a biometric system plus the person at the point of service who recognises an exception.
Fraud prevention meets asymmetric harm
The state has a legitimate interest in stopping duplicate or fraudulent claims. But fraud and exclusion distribute costs differently. A false acceptance costs a programme. A false rejection can cost a family dinner tonight.
Optimising only the central accuracy figure hides that asymmetry. The quality of the system depends on whether the exception path is available, dignified, fast and safe from arbitrary discretion.
This is a recurring lesson for digital identity. The fallback is not outside the design. It is where the design admits what it does not know.
Before connecting any credential to a necessity, ask:
- Is authentication evidence or a verdict?
- Who can override a failed match?
- Can the person obtain service before the dispute is resolved?
- Is the fallback monitored as carefully as the main path?
- Does preventing one kind of fraud create another kind of unaccountable gatekeeper?
A system should be judged not only by how confidently it recognises the majority, but by what it asks the uncertain person to survive.