Aadhaar Authentication in Welfare Delivery

Aadhaar authentication electronically checks whether the identity information presented by a person matches the Aadhaar record associated with a stated number. The Central Identities Data Repository returns an authentication response, while the welfare authority separately decides eligibility. An exclusion error occurs when an eligible person is denied or delayed a benefit because enrolment, database linkage, authentication or subsequent delivery fails.

Legal basis and safeguards

Under Section 7 of the Aadhaar Act, 2016, the Union or a state government may require authentication or proof of Aadhaar for a subsidy, benefit or service financed from the Consolidated Fund of India. The Supreme Court upheld this welfare use in K.S. Puttaswamy v. Union of India, 2018, subject to constitutional and statutory safeguards.

• A person who has not received an Aadhaar number must apply for enrolment and be offered an alternate and viable means of identification until Aadhaar is assigned.
• Under Section 8, the requesting entity must obtain consent and communicate the purpose and use of authentication information.
• Under Section 29, Aadhaar information is restricted in its sharing and use, and core biometric information cannot be shared.

Authentication and welfare delivery

• The department lawfully records or seeds the beneficiary's Aadhaar number in its scheme database.
• A requesting entity may use demographic, OTP, biometric or multi-factor authentication and transmit the encrypted request to UIDAI for matching.
• The department combines the response with its own records because authentication does not prove income, disability, residence or another eligibility condition.
• For cash transfers, authentication and the Aadhaar Payment Bridge are distinct: authentication verifies identity, while the payment bridge routes funds through Aadhaar-linked bank mapping.

How exclusion errors arise

Authentication can become a barrier when a genuine beneficiary cannot satisfy a digital identity step despite meeting the scheme's eligibility conditions.

• Incorrect Aadhaar seeding or mismatches between Aadhaar and scheme records can cause the wrong record to be checked or rejected.
• Biometric mismatch, unavailable OTP access, defective devices or failures of electricity and network connectivity can prevent successful authentication.
• Enrolment difficulties or failure to update changed demographic or biometric information can obstruct access.
• Incorrect Aadhaar-linked bank mapping can cause cash-transfer failure even when identity authentication succeeds.
• Rigidly treating a failed authentication response as proof of ineligibility converts a technical failure into exclusion; alternative identification and exception handling are therefore necessary.