DigiLocker not showing or verification failed, fix guide 2026

You opened DigiLocker for a job verification, a scholarship form, or a vehicle check, and the screen will not cooperate. The issuer shows “no record found”, the marksheet is in the wrong name, the QR code on your driving licence will not scan at the toll plaza, or the bank counter politely refuses to accept the locker copy because the photo does not match. This is one of the most common citizen frustrations in 2026, and the good news is that almost every one of these failures is a data mismatch or a process gap, not a crime. You do not need the police. You need a paper trail, a calm complaint, and in many cases a one page RTI to the parent department.

This guide is written for the person standing at the counter or sitting in front of the screen at 11 pm, trying to make a portal work before a deadline. It is a sibling to our honest DigiLocker issuer reality audit and our broader documents not showing fix piece. Read those if you want the full landscape. Read this one if you are trying to fix a specific verification failure right now.

A small note on the law. The legal weight of a DigiLocker certificate comes from §9A of the Information Technology Act 2000, which puts digitally signed records on the same footing as paper originals. The MeitY notification of 8 February 2017 and the Ministry of Road Transport and Highways advisory of 8 August 2018 both make this explicit for driving licences and vehicle RCs. So when a clerk says “we want the original”, they are technically wrong, and a polite citation of these documents usually settles the question.

Before you write anything to anyone, spend 30 focused minutes. Most “verification failed” tickets are closed in this window because the cause is a routine mismatch you can see with your own eyes.

1. Open the DigiLocker app or https://digilocker.gov.in and sign in with Aadhaar OTP. If OTP does not arrive, switch to mobile OTP and re check that the mobile number on file matches the one currently linked at UIDAI.
2. Go to Issued Documents and tap the failing record. Read the exact error message. Common ones are “no record found at issuer”, “issuer service not available”, “name mismatch”, “duplicate record found”, “Aadhaar number mismatch”, and “service down for maintenance”.
3. Screenshot the error with the date and time visible. Save it to a folder named after the document, this becomes your evidence pack.
4. Open the issuer site directly in a browser, for example the UIDAI portal for Aadhaar, Parivahan Sewa for DL and RC, the CBSE Pariksha Sangam for board marksheets, the EPFO member passbook for provident fund, the Income Tax e filing portal for PAN. Sign in and confirm your record exists and the spelling and date of birth are correct at source.
5. Compare three fields, name spelling letter by letter, date of birth, and document number, between the issuer's own portal and your DigiLocker profile. Even a missing middle initial, a hyphen, or “Mohd” versus “Mohammad” breaks the fetch.
6. If your name or DOB is wrong at the issuer end, fix it at the source first, not at DigiLocker. DigiLocker only mirrors what the issuer database holds.
7. If the issuer record looks correct but DigiLocker will not fetch, sign out of DigiLocker, clear app cache (Settings, Apps, DigiLocker, Storage, Clear cache), sign back in, and use the “Refresh” or “Get” button on the issuer page. This forces a fresh API pull.
8. If a QR verification is failing on a printed or PDF copy, open the DigiLocker app, go to the document, tap the share icon, and re download the latest PDF. QR codes embed a signed payload that expires when the issuer rotates keys, so a six month old printout can stop verifying overnight.
9. If a counter clerk is rejecting a perfectly valid DigiLocker copy, ask politely for the rejection in writing on the office's letterhead with date and stamp. Nine out of ten clerks back down at this point because they know the MeitY notification is binding.

If 30 minutes of self serve has not fixed it, you move to the written complaint route. From here on, everything is on paper or email, and everything must be saved.

A grievance without evidence is closed within hours. Collect this pack first, you will reuse the same files in the DigiLocker ticket, the Sahyog escalation, and the RTI letter.

• Screenshot of the DigiLocker error screen, with date and time visible on the device clock.
• Screenshot of the same record on the issuer's own portal showing the correct or incorrect entry.
• Your DigiLocker profile screen showing name, date of birth, mobile and Aadhaar last four digits.
• Aadhaar e KYC details download from UIDAI (uidai.gov.in, My Aadhaar, Aadhaar Update History or Download Aadhaar).
• Reference numbers, the DigiLocker user ID, the issuer side reference such as roll number, RC number, EPF UAN, PAN, and the failed transaction ID if the error gave one.
• A short timeline in your own words, date, what you tried, what message you saw, who you spoke to. Keep it to one page.
• If the failure has caused a deadline miss, save the deadline notice as well. Scholarship cut off, job offer KYC window, vehicle fitness check date. This raises the priority of the grievance.

Keep all of this in a single folder, ideally also uploaded to Google Drive or your own DigiLocker uploaded documents tab. Do not delete app messages, SMS or emails from DigiLocker or the issuer, those header lines are part of your proof.

Indian e governance grievance systems work like a ladder. Skipping rungs gets your ticket closed as “not addressed at appropriate level”. Take them in order.

Inside the DigiLocker app, tap the profile icon, then Help, then Contact Us, then Raise a Ticket. Pick the category that matches your failure, for example “Issued Documents”, “Aadhaar related”, “QR Code”, or “Profile update”. Paste your evidence pack summary in the description, attach two or three screenshots, and submit. You will receive a ticket ID by email and SMS within minutes. The DigiLocker support SLA is 7 working days for a first response.

If 7 working days pass with no resolution, or you get a one line “contact issuer” reply with no action, escalate. Two parallel portals work for DigiLocker.

• MeitY Sahyog, https://sahyog.meity.gov.in. This is the Ministry of Electronics and IT's own grievance window. Pick department “National e Governance Division” and sub category “DigiLocker”. Paste the DigiLocker ticket ID in the description.
• CPGRAMS, https://pgportal.gov.in. The Centralised Public Grievance Redress And Monitoring System. Pick Ministry of Electronics and IT, then NeGD. CPGRAMS forces a response within 21 days under the central government grievance policy.

File both. They route to different desks and the duplicate visibility tends to speed things up.

DigiLocker is only a pipe. If the data is wrong or missing at source, only the issuer department can fix it. Examples,

• Aadhaar errors, UIDAI, https://uidai.gov.in. Use the My Aadhaar update flow for name, DOB, mobile and address. The 1947 helpline is the fastest live channel.
• Driving licence and vehicle RC errors, Ministry of Road Transport and Highways through https://parivahan.gov.in. Each state has its own RTO desk.
• CBSE marksheet errors, Central Board of Secondary Education through https://www.cbse.gov.in, Pariksha Sangam portal. Correction window opens annually after results.
• Income tax PAN errors, https://www.incometax.gov.in or NSDL e Governance.
• EPFO errors, https://www.epfindia.gov.in, member e Sewa, joint declaration form for name and DOB.
• State boards, ration card, land records, voter ID, each state has its own portal. See our comparison of state grievance portals for the right link by state.

For each issuer there is a published grievance email and a help desk. Write a one page email, attach your evidence pack, mark a copy to the DigiLocker support team using the ticket ID as subject prefix. Sample text is in the section below.

If the issuer department goes silent for more than 14 days, file an RTI. This is the most underused tool in the citizen kit, and it works precisely because departments are required by law to respond within 30 days under §7(1) of the RTI Act 2005, and a silence is deemed refusal which opens an automatic first appeal.

Use the RTI not to complain, but to ask procedural questions that force the department to look at your file. Examples of strong RTI questions,

• “Please provide a certified copy of the record held in the department database for [my name and unique ID]. Please state whether the record is currently pushed to DigiLocker, and if not, the reason and the officer responsible.”
• “Please provide a copy of the standard operating procedure used by the department for name correction and for re publishing the corrected record to DigiLocker.”
• “Please state the average and the maximum time taken by the department in the last 12 months to resolve DigiLocker fetch failures of this category.”

The RTI route is detailed in our citizen RTI playbook and the step by step filing flow in how to file RTI online in India. Use the AI RTI drafter if you want a clean first draft. Keep the application to a single page. Pay the ₹10 fee online wherever the issuer supports it.

This needs a clear answer because it is one of the most searched questions. The honest position is, almost never. A DigiLocker verification failure is a data or process problem. The cyber portal at https://cybercrime.gov.in and the 1930 helpline are for financial fraud and impersonation, not for “my marksheet is not loading”.

You should treat the situation as cyber or police only in three narrow cases.

• Someone else has linked your Aadhaar to a DigiLocker account you did not create. Sign in, change the mobile number after you regain access, and file a complaint on https://cybercrime.gov.in under the “social media related crimes” category. This is rare and usually traces back to a phone OTP leak.
• Your DigiLocker account is locked because an unknown actor changed the mobile number. Treat it as identity takeover. File the cyber complaint, and parallelly write to UIDAI through 1947 for an Aadhaar lock under §3A of the Aadhaar Act 2016.
• A counter clerk demands a bribe to “accept” your DigiLocker certificate. That is corruption, not a verification failure. Lodge a complaint with the State Vigilance Commission and, if the act is offered or completed, the Central Bureau of Investigation through their anti corruption window. The Bharatiya Nyaya Sanhita 2023 §198 and §201 cover public servant misconduct. This is outside the scope of this article, but you should know the right door.

For everything else, including the rejection of a valid QR, the right escalation is administrative, not penal. A cyber complaint will be closed as “not a cyber offence” and you will lose two weeks.

This is the workhorse template. Fill the bracketed fields, attach two or three screenshots, send to the issuer's official grievance address and copy DigiLocker support. Keep the tone factual and short, do not threaten.

To, The Public Information Officer / Grievance Officer
[Issuer department name, for example, Office of the State Transport Commissioner, [state]]
Email, [official grievance email from the department site]

Copy to, [email protected]
Subject, DigiLocker fetch failure for [document name], ticket [DigiLocker ticket ID], request for record correction

Respected sir or madam,

I am [your name], holder of [document number, for example, driving licence DL [number]] issued by your office on [date]. My Aadhaar number ending [last four digits] is linked to my DigiLocker account registered with mobile [last four digits].

On [date] at [time] I tried to fetch the said document into my DigiLocker. The portal returned the error "[exact error message]" (screenshot attached). I have verified that the corresponding record on your departmental portal at [URL] shows my correct name and date of birth (screenshot also attached).

The same document is required by [purpose, for example, a job verification by [employer] with a deadline of [date]]. Because §9A of the Information Technology Act 2000 and the MeitY notification of 8 February 2017 make a DigiLocker certificate legally equivalent to the paper original, I am entitled to obtain it through DigiLocker. The failure is at your departmental data feed, not at my end.

I request you to,

  - Confirm in writing within seven days that the record exists in your database, and the reason it is not currently fetchable by DigiLocker.
  - Re push the record to DigiLocker, or correct the data field that is blocking the fetch, within 21 days.
  - Provide a single point of contact for follow up.

If I do not receive a response within 14 days, I will be constrained to file an application under §6 of the Right to Information Act 2005 seeking the same information, and to escalate the matter through MeitY Sahyog and CPGRAMS.

Yours sincerely,
[Your name]
[Address]
[Mobile]
[Email]

Enclosures,
1. Screenshot of the DigiLocker error screen.
2. Screenshot of the matching record on the departmental portal.
3. Screenshot of the DigiLocker profile showing linked Aadhaar and mobile.
4. DigiLocker ticket ID [number] and date.

You will not need every paragraph in every case. For an Aadhaar mismatch, the issuer is UIDAI and you also enclose a fresh Aadhaar download. For a CBSE marksheet, the issuer is the regional CBSE office and you enclose your admit card and roll number slip. The template scales.

This is the typical shape of the fix. The DigiLocker ticket gives you a paper trail. The Parivahan correction is the actual data fix. The RTI is the lever that puts a clock on the department. Together they close most cases inside three weeks.

The error messages on DigiLocker are not always written in plain language. Here is what each one usually means and where to act.

• “No record found at issuer”, the issuer database does not contain a record matching your name and identifier. Cause is either a typo in your DigiLocker profile, a record under a slightly different name at issuer, or the record has not been digitised yet. Fix, confirm at issuer portal first, then either align the spelling or apply for digitisation.
• “Aadhaar number does not match”, the Aadhaar linked to your DigiLocker does not match the Aadhaar held by the issuer for that record. Common after an Aadhaar re enrolment or a guardian to adult transition. Fix, update Aadhaar at the issuer's end through their KYC route.
• “Mobile number mismatch”, the mobile registered with the issuer is different from the one DigiLocker is using for OTP. Some issuers will not push a record unless the mobiles match. Fix, update the mobile at the issuer side, do not change DigiLocker.
• “Issuer service not available”, the issuer API is down or has not been integrated for your state. This is a system level outage. Fix, check the issuer's own service status page, file a DigiLocker grievance and escalate to Sahyog after 7 days.
• “Duplicate record found”, the issuer holds two or more records that match your identifiers. Typical for people with two PAN cards, or two driving licences from different states. The DigiLocker API refuses to pick one. Fix, deactivate the duplicate at the issuer end, the income tax department has a specific surrender form, the transport authority has a state transfer flow.
• “Department rejected the request”, your fetch hit the issuer but the issuer's policy refused. Common reason, your record is flagged for verification, or the document type is in a “preview only” mode in your state. Fix, ask the issuer for the policy citation and the resolution timeline.
• “QR verification failed”, the verifier's scanner could not validate the digital signature on the QR code. Cause is either an expired key, a tampered or low resolution printout, or an offline verifier that cannot reach the DigiLocker verification API. Fix, re download the latest PDF, ask the verifier to scan from screen rather than print, and ask the verifier whether their device is on the latest DigiLocker verifier app.
• “Wrong name in fetched document”, the issuer pushed the record but with an out of date or misspelled name. Fix, correction at issuer source, then re push.

Each of these has a different escalation address, but the structure is identical. Save the error, fix the source, re push, RTI if the department is silent.

Verification problems hit some citizens harder than others. A few quick reminders.

• Mobile not in your name? DigiLocker will still work, the SIM holder simply has to be available when an OTP is requested. If you have moved beyond reach of that handset, update the mobile at UIDAI first using https://uidai.gov.in or 1947, then re link DigiLocker.
• Aadhaar biometrics locked? OTP based fetch still works as long as you can receive the SMS. Read our sibling note on biometric lockouts at Aadhaar biometric locked, authentication failed if you also need offline verification.
• Name spelling differs between Aadhaar and PAN? That is a recurring issue across DigiLocker and bank KYC. See PAN Aadhaar name mismatch KYC fix for the dedicated repair flow.
• Senior citizen or person with disability? UMANG can act as a fallback front end for DigiLocker. Some flows are easier in UMANG when DigiLocker is throwing API errors. Our UMANG citizen services guide lists what is supported.

If you are helping a parent, a relative, or a neighbour, do the work on their device when you can, so the OTPs land naturally and you do not have to re do the SIM link.

Yes, under §9A of the Information Technology Act 2000 and the MeitY notification dated 8 February 2017. For driving licences and vehicle RCs the MoRTH advisory of 8 August 2018 reinforces this for road side checks. A clerk who refuses a properly issued DigiLocker copy is acting against a binding government instruction and you can ask for the refusal in writing.

Most often the verifier's scanner is the problem. The QR on a DigiLocker certificate embeds a digitally signed payload that needs a current verifier app and an internet connection. Try re downloading the PDF from your DigiLocker, share it on the verifier's screen, and ask them to scan from screen. If it still fails, the issuer may have rotated keys and your old printout is stale.

Almost always fix the certificate at the issuer end, not Aadhaar. Aadhaar is the most widely linked identifier in your life, changing it has cascading effects on PAN, bank, EPF and DigiLocker. The certificate name is local to that issuer, fixing it is faster and lower risk.

Yes. DigiLocker is run by the National e Governance Division of MeitY, which is a public authority under §2(h) of the RTI Act 2005. The Central Public Information Officer at NeGD is the right addressee. Use it when DigiLocker has not responded for more than 14 days. Our citizen RTI playbook shows the exact format.

Ask the issuer in writing for the date on which the record was last pushed to DigiLocker, the signature key version used, and the contact in their technical team. Most fetches fail because the issuer technical team has not redeployed after a record correction. The written ask forces a redeployment.

In our reading of citizen complaints, the median resolution is 14 days when you only use the DigiLocker ticket route, 7 to 10 days when you parallel it with Sahyog and the issuer email, and 21 days when an RTI under §6 of the RTI Act 2005 is also filed. Cases involving a name correction at the issuer can take longer because the underlying database edit itself can run 7 to 14 days.

No, not for a verification failure. Those channels are for financial fraud and identity takeover, not for data mismatches. Filing in the wrong channel wastes two weeks. The narrow exceptions are someone hijacking your DigiLocker account or demanding a bribe to accept a valid certificate, those are covered in the dedicated section above.

Ask for the refusal on the company letterhead with the reason cited. Quote the MeitY notification and the MoRTH advisory in your reply. Forward the refusal to the company's compliance officer and to MeitY Sahyog. In our experience, a private employer almost always reverses position once a written refusal is on file, because their own legal team flags the risk.

This is the most honest pain point. Many state land records, ration cards and pension records are not on DigiLocker. There is no in app fix. Use the RTI route to the state department asking for the digitisation timeline. File a parallel grievance on CPGRAMS tagging the State IT Secretary. Until integration happens, you will need the physical issued copy.

You can, in the Uploaded Documents tab. But an uploaded scan has no legal weight, it is just a personal cloud backup. Only certificates from the Issued Documents tab carry the §9A legal equivalence. Verifiers will check the source and reject uploads.

Do not embed inline JSON LD on this article. The site wide schema generator at `/static/js/schema-auto.js` reads the `==== Q ====` H4 headers above and emits a FAQPage schema automatically, along with Article and BreadcrumbList types. Inline JSON LD will render as visible code on the DokuWiki template, which is the opposite of what we want.

• DigiLocker, https://digilocker.gov.in
• MeitY DigiLocker FAQ and grievance, https://digilocker.gov.in/help
• MeitY Sahyog grievance, https://sahyog.meity.gov.in
• CPGRAMS, https://pgportal.gov.in
• UIDAI, Aadhaar update, https://uidai.gov.in
• Parivahan Sewa, driving licence and RC, https://parivahan.gov.in
• CBSE Pariksha Sangam, https://parikshasangam.cbse.gov.in
• EPFO member e Sewa, https://unifiedportal-mem.epfindia.gov.in
• Income Tax e filing, https://www.incometax.gov.in
• UMANG web, https://web.umang.gov.in
• Information Technology Act 2000, §9A, https://www.indiacode.nic.in
• Right to Information Act 2005, §6 and §7, https://rti.gov.in

• DigiLocker issuer reality, what actually works in 2026
• DigiLocker not showing, fix Aadhaar, DL, RC, marksheet
• UMANG app citizen services
• Aadhaar biometric locked, authentication failed
• PAN Aadhaar name mismatch KYC fix
• State grievance portals comparison 2026
• MyGov and MyScheme citizen services
• Citizen RTI playbook
• How to file RTI online in India

For the social card at `/home/bighelpers/wiki/data/media/social/auto/digilocker-document-verification-fix-india.png` and the OG image at `/home/bighelpers/public_html/rtiwiki/og/digilocker-document-verification-fix-india.jpg`, use the following text to image prompt.

• Prompt. A flat editorial illustration in a calm blue and amber palette showing a citizen holding a smartphone with a glowing DigiLocker style document on screen, a faint red warning triangle next to a QR code, and a clean checklist beside the phone with three ticks. Style, modern Indian editorial, soft shadows, no faces. Aspect ratio 1200 by 630. Text overlay, top left, “DigiLocker fix and complaint guide”, bottom right small, “RTI Wiki 2026”. Avoid stock photo realism, prefer a vector flat look. No logos of any brand, no Aadhaar number visible.