When Aadhaar Authentication Fails: Rajasthan’s Ration Safeguards

If a fingerprint check fails at a Rajasthan ration shop, has the person lost their right to food?

The Union food department's answer is that a genuine beneficiary must not lose their entitled grain solely because biometric authentication fails for technical reasons. Rajasthan also has a formal grievance and appeal system. The harder question is whether the alternative works at the counter, before a household has to make another journey.

The distinction to keep: an identity match, an eligibility decision and a bag of grain handed over are three different events.

The National Food Security Act separates Priority Households, whose entitlement is 5 kg of foodgrain per person per month, from Antyodaya Anna Yojana households, entitled to 35 kg per household per month. The Centre's present PMGKAY decision provides these NFSA quantities free for five years from 1 January 2024. It is not an additional pandemic-era ration quota. NFSA, Cabinet decision.

Inclusion in Rajasthan's eligible list is a separate matter, governed by state rules and criteria. Possessing Aadhaar does not by itself establish NFSA eligibility. A failed authentication does not by itself establish ineligibility. Rajasthan's 2023 rules, amended in 2025, must be read separately from the device's response. Rajasthan rules, 2025 amendment.

The April 2025 amendment adds an e-KYC deadline to exclusion criteria, with age and exempt-category exceptions, and gives the Collector power to order inclusion or exclusion. A list-status decision under that provision is different from an unsuccessful fingerprint attempt during ration collection. The amendment alone does not prove that a particular household was removed.

This is why the reason for a failed visit matters. A fingerprint mismatch, an unavailable network, a wrong Aadhaar-to-ration-card link, an eligibility-list problem and an empty shop stock require different responses. Treating them all as “Aadhaar failure” obscures who must fix what.

Rajasthan's own 2023 rules prohibit an open fair-price shop from refusing an eligible household presenting its ration card the outstanding quantity due on that card. That state safeguard and the Union's authentication exceptions address different parts of the same journey. Rajasthan Gazette, Schedule 2.

The Department of Food and Public Distribution's Hindi FAQ describes iris authentication and Aadhaar-OTP or PDS-OTP as alternatives. It also advises states not to refuse genuine beneficiaries grain because of biometric failure, missing Aadhaar/seeding, an ePoS malfunction, connectivity failure or another technical problem. It refers to alternative identity documents in the February 2017 notification. These are official safeguards, not proof that every shop has every option available. DFPD Hindi FAQ.

For a separate problem—ePoS being unavailable—the same FAQ advises distribution in the presence of a responsible government officer or employee. That is a national operational safeguard, not evidence that a particular Rajasthan shop has arranged it.

The distinction remains current: in a 12 August 2025 parliamentary answer, the department reiterated its no-denial advice for genuine beneficiaries facing technical authentication failures. It also said it does not maintain reports of failed biometric authentications. The absence of that departmental count is neither evidence that failures do not occur nor a basis for calculating how many people went without grain. Rajya Sabha answer.

There is an unresolved local detail. The available record does not establish the current Rajasthan shop-level sequence for every exception: which method must be attempted first, how the national safeguards are authorised and recorded locally, and whether the required officer or alternative is available. A general Union safeguard should not be converted into a promise that an individual dealer can immediately issue grain through an unspecified override.

Rajasthan's 2023 Food Security Rules identify the Additional District Collector (Administration), or another state-authorised or designated officer, as District Grievance Redressal Officer. If the complaint is against the District Collector, the rules name the Divisional Commissioner or another notified divisional officer. An appeal against a DGRO order goes to the Rajasthan State Food Commission, ordinarily within 30 days, with provision for accepting a delayed appeal. Confirm the current district designation rather than relying on an old office-holder's name. Official bilingual Gazette, grievance provisions.

The official NFSA Rajasthan page lists Rajasthan Sampark as its grievance system and 181 among its helpdesk numbers. A helpdesk complaint and a statutory appeal are separate steps; an Aadhaar-support request cannot itself decide a ration entitlement dispute. NFSA Rajasthan service page.

For a clear complaint, distinguish the shop/date, listed entitlement, device response, alternative requested, distribution entry and quantity actually received. Keep an acknowledgement or order so the next authority can identify the unresolved issue. Do not post Aadhaar numbers, OTPs or biometric information publicly. Use the official complaint channel and provide only the information it requires.

A March 2024 study of Mundoti, in Rajasthan's Ajmer district, reported fingerprint-related PDS access difficulties. It also described an older woman using a mobile OTP as an alternative. The paper states a sample of 40 people, but presents only ten participant rows and no representative statewide failure estimate. Its evidence shows reported local friction and an alternative used in one account; it cannot establish today's statewide denial rate or the present procedure at another shop. Original Mundoti paper.

A different problem appears in Down To Earth's December 2024 reporting from Aasan village, Rajsamand. Two women called Bhuri Bai reportedly became entangled in a ration-record mix-up: one household's allocation appeared collected while the intended recipient said she had received none. The dealer was not reached for a response. This is an attributed reported case, not a fresh finding about their situation today or proof of how UIDAI's matching engine behaved. It illustrates why a recorded collection and correct physical receipt need separate scrutiny. Down To Earth report.

The food department presents Aadhaar integration as a way to identify beneficiaries correctly and improve delivery. That purpose is legitimate to test. A correctly matched identity could make impersonation harder; that is a plausible mechanism, not a measured benefit established here. The relevant outcome is whether the eligible household receives its full entitlement, including after an error. Successful checks and deleted records alone cannot prove that outcome. DFPD's stated delivery approach.

The administrative risk runs in both directions: a weak exception can permit wrongful distribution, while an inaccessible exception can leave a genuine recipient carrying the cost of the system's error. More retries, travel and waiting can shift that cost onto the person least able to absorb it. The documents establish safeguards and reported access problems; they do not establish a hidden government objective to deny food.

Verified: technical authentication failure is covered by the Union's no-denial advice; Rajasthan has a named grievance office and State Food Commission appeal route. Published local research and reporting describe access difficulties and record errors.

Contested: in 2017, civil-society groups challenged Aadhaar-linked exclusion and UIDAI disputed blaming Aadhaar, while saying denial violated government instructions. That historical disagreement does not settle current Rajasthan performance. Reported exchange, 18 August 2017.

Unresolved: current Rajasthan exception compliance, how many eligible households miss grain because a fallback fails, and how quickly complaints restore actual receipt.

The accountability test is concrete: after the machine fails, does the household still receive the grain it is entitled to—and can a named authority correct the record when it does not?