DigiLocker issuer reality, what actually works in 2026

Quick answer. Install DigiLocker, sign in with Aadhaar OTP, and pull the documents you need. Aadhaar, PAN, driving licence and vehicle RC almost always auto-fetch. School marksheets, EPF, ABHA, voter ID, ration card and land records are state-dependent, many issuers are listed but return errors. A DigiLocker certificate is legally equivalent to the original under §9A of the IT Act 2000, but only for documents that actually pulled correctly. If an issuer fails, file an RTI to the parent department for the original.

Short on time? Jump to the 20-document status table below.

DigiLocker promises 2,000+ issuers and 500+ schemes. In practice citizens hit a wall: a school appears in the issuer list but the marksheet won't fetch. A ration card “issuer” exists for the state, but the API returns “no record found.” Vaccination certificates appear, then disappear after a portal migration. The legal weight is real, but only for documents that pulled cleanly and match your name and date of birth.

This article is an honest 2026 audit. It tells you which issuers are reliable, which are flaky, what the error codes mean, how to fix mismatches, and what to do when DigiLocker fails, including the RTI route to the parent department.

A small note before you start: the gold-standard test of a DigiLocker document is whether the verifier (a landlord, police officer, recruiter) can scan its QR and see a valid issuer signature. If the QR validates, the document is good in law. If it doesn't, no amount of arguing helps.

DigiLocker is a Government of India cloud locker run by the National e-Governance Division (NeGD) under the Ministry of Electronics and IT (MeitY). It lets citizens fetch original digital documents directly from the issuing department (Aadhaar from UIDAI, RC from the state transport authority) and store them in a personal locker linked to a mobile number and Aadhaar.

The legal hook is §9A of the Information Technology Act 2000, inserted by the IT (Amendment) Act 2008. It gives an electronically delivered service the same legal effect as a paper service, when the delivery is authenticated by the issuer's digital signature. The MeitY notification dated 8 February 2017 expressly recognised documents available in DigiLocker as “at par with original physical documents” for all purposes.

The Ministry of Road Transport and Highways (MoRTH) issued a separate advisory dated 8 August 2018 directing all state police and transport authorities to accept driving licence and registration certificate (RC) shown via DigiLocker or mParivahan as valid, and not to demand the physical original at the roadside. Several state high courts have since pulled up enforcement officers for ignoring this advisory.

What does this mean in practice? A document with a valid issuer signature in your DigiLocker is enforceable. A document that's only an uploaded scan (in the “Uploaded Documents” tab) carries no legal weight, it's just a personal file backup.

When you sign in via Aadhaar OTP, DigiLocker consents UIDAI to push your demographic record into the locker as an “Aadhaar Card” issued document. This is the cleanest auto-fetch on the platform. It almost never fails.

The chain reaction is what most people miss. Several other issuers, Income Tax (PAN), CBSE/state boards (marksheets), EPFO (UAN), MoRTH (DL/RC), Election Commission (Voter ID), NHA (ABHA), Co-WIN (vaccination certificate), use Aadhaar as the lookup key. If your name on the source record doesn't exactly match your name on Aadhaar, the fetch silently fails or returns “no record found”, even when the record exists.

The fix is rarely on DigiLocker's side. It's on the source-issuer side. If your PAN spells “Sanjay Kumar” but Aadhaar says “Sanjay Kr,” the PAN fetch errors. The fix is to correct PAN (or Aadhaar) at the source, not to keep retrying DigiLocker.

A second common failure: the issuer requires you to also enter the document number (DL number, RC number, PAN, roll number) along with Aadhaar. If you enter a digit wrong, the error reads as a generic “issuer unavailable.” Always double-check the number against the original.

A third failure mode: the issuer is in maintenance. Co-WIN, EPFO and some state revenue portals routinely take their DigiLocker endpoint down for hours. Try again the next day before assuming the document is missing.

Cleanly working (auto-fetch reliable, signed PDF, QR validates):

• Aadhaar (UIDAI)
• PAN (Income Tax / NSDL)
• Driving Licence (MoRTH via Sarathi)
• Vehicle Registration Certificate (MoRTH via Vahan)
• CBSE Class X and XII marksheets (2017 onwards via DigiLocker)
• EPFO UAN card and PF passbook (when UAN is Aadhaar-seeded)
• ABHA (Ayushman Bharat Health Account) ID, NHA
• Voter ID, Election Commission, since 2022 rollout
• Co-WIN COVID vaccination certificate, still served, though no longer a daily-life requirement

Flaky (issuer is listed but fetch fails 30–60% of the time):

• State board marksheets, wide variance, Tamil Nadu, Maharashtra, Karnataka, Telangana usually work; Bihar, Uttar Pradesh, Madhya Pradesh, West Bengal frequently error out for older years
• State ration card, works in Karnataka, Tamil Nadu, Andhra Pradesh, Telangana, Maharashtra; broken for Uttar Pradesh, Bihar, West Bengal pre-2022 cards
• State land records / RoR, only 12 states have a live DigiLocker integration in 2026 (Karnataka Bhoomi, Maharashtra 7/12, Telangana Dharani, MP RCMS, UP Bhulekh among them)
• Income / caste / domicile / OBC certificate, depends on state e-District build; Karnataka SevaSindhu, Maharashtra AaplE Sarkar, Tamil Nadu eSevai work; many northern states do not
• Passport, only PCC (police clearance certificate) is reliably pulled; the passport booklet itself is not in DigiLocker
• Birth and death certificate, only a few municipal corporations are integrated (Pune, Hyderabad, Chennai, Bangalore are reliable; smaller towns are not)

Missing or stub-only in 2026:

• Property registry / sale deed (no national integration; some sub-registrars on a pilot)
• Pension PPO (PFRDA APY works partially; CGHS, EPS pensioners do not have a clean fetch)
• BPL card / Antyodaya certificate (state-only, mostly absent)
• Ex-servicemen ID card (DGR portal not integrated)
• Disability UDID (partial, fetch often returns “record not found” even for valid UDIDs)
• Caste, income, domicile certificates issued before the state's e-District migration date (paper-era originals are not retroactively digitised)

The reliability rating below is a 2026 working observation, not an official rating. Reliable = the fetch succeeds for >85% of users in our test sample. Flaky = 30–70%. Avoid = <30% or known-broken.

A printable copy of this table is at the foot of the article. Treat it as a 2026 snapshot, issuer connectivity changes.

Citizens see opaque error codes in the app. Here is the decoder ring:

• “No record found at the issuer”, the source database has no row matching the Aadhaar/document-number combination you supplied. Either the number is wrong, or the record genuinely doesn't exist at source. Action: verify the original document number; if correct, RTI the issuer asking why the record is absent.
• “Issuer service unavailable” / “Backend timeout”, the issuer's API is down for maintenance. Action: wait 24 hours, try again. If it persists for more than a week, RTI the issuer.
• “Name mismatch” / “Demographic verification failed”, name or DOB on source ≠ name or DOB on Aadhaar. Action: fix the mismatch at source (not on DigiLocker). See the next section.
• “Consent expired, please re-authenticate”, UIDAI consent token has lapsed. Action: sign out, sign back in with Aadhaar OTP.
• “Document not yet digitised”, the record is older than the issuer's digitisation cut-off. Action: apply for a fresh certificate at source, or RTI the issuer asking when historical digitisation will be completed.
• “Cannot fetch, please contact issuer”, generic catch-all for unmapped errors. Action: RTI is the only honest path forward.

The fix is always at the issuing department, never on DigiLocker. DigiLocker is a wallet, not an editor.

Decision rule: change the less-used record to match the more-used one. Aadhaar is usually the more-used record, so most fixes happen on the source document.

• Aadhaar correction, myAadhaar portal or enrolment centre. See Aadhaar correction RTI guide when UIDAI sits on your request.
• PAN correction, NSDL/Protean PAN change application (Form 49A).
• DL/RC correction, RTO change-of-particulars application via Sarathi or in person.
• EPF correction, joint declaration with employer, submitted on the EPFO portal.
• CBSE marksheet correction, affidavit + gazette notification + CBSE change request.
• State board correction, board's own change-of-particulars procedure; if stalled, RTI to board PIO.
• Voter ID correction, Form 8 on voters.eci.gov.in.

After the source fix is accepted (always ask for a written acknowledgement), wait 24–72 hours and re-fetch in DigiLocker. The locker pulls the corrected record automatically on next refresh.

You will be asked to share, for a rental KYC, a job verification, a school admission, a bank loan. There are two clean ways.

Method 1, Share via DigiLocker (recommended). Open the document, tap “Share,” pick “Issued Document via DigiLocker.” The other party gets a link that proves the document came from your locker, with the issuer's digital signature intact. The shared link is time-bound (default 7 days). They can verify by scanning the QR.

Method 2, Download and forward the PDF. The PDF carries the same issuer signature. The recipient can verify it by opening it in any PDF reader that shows signature panels, or by scanning the QR through the DigiLocker app's verifier.

What you should not do: print, scan and email a paper version. That strips the signature. The recipient cannot verify it cryptographically and is within their rights to demand the original.

A safety note: never share your DigiLocker login OTP with anyone, there is no scenario where a legitimate verifier needs it. If asked, it's a scam.

If you are a landlord, employer, school admin or bank officer receiving a DigiLocker share, this is how you verify it cleanly. Don't ask for a paper original, that defeats the purpose.

1. Open the PDF in a reader that shows digital signatures (Adobe Reader, recent Foxit, in-browser Chrome shows a signature pane in the right rail).
2. Look for the issuer's name in the signature panel, UIDAI, MoRTH, CBSE, etc. The name must match the document type.
3. Confirm the signature status reads “Signature valid” or “Source trusted.” A “signature unknown” status usually means your reader hasn't loaded the issuer's trust root, install the CCA India root certificate (cca.gov.in) and retry.
4. For DL/RC, additionally scan the QR using mParivahan, it should display the live record.
5. If the document came as a share link, you can also open the link itself; DigiLocker will display the live, issuer-signed copy.

If any of these fail, reject the document and ask for a fresh share, not for a paper original.

Both work. They differ in what's convenient.

• App (DigiLocker on Android / iOS), best for fetch, share, and showing a document at a checkpoint. The verifier-side QR scan is app-only. Push notifications when an issuer pushes you a new document.
• Web portal (digilocker.gov.in), best for bulk download, organising the locker, and using the larger screen to read a marksheet or land record.

There is one quirk: some issuers only enable fetch via the app, not the web. CBSE marksheets are the most common case. If a web fetch fails, retry on the app before opening a ticket.

UMANG is the all-in-one government services app; DigiLocker is a document wallet. UMANG embeds DigiLocker inside it. You can open DigiLocker from UMANG and pull documents without installing two apps.

When to prefer UMANG: you're doing a transaction (paying a bill, booking a gas refill, filing an EPF claim) and you'll also need the document. UMANG gives you both in one flow.

When to prefer DigiLocker direct: you only want the document. The standalone app is faster and the share workflow is cleaner.

DigiLocker doesn't “expire” in the consumer sense, a dormant account stays. But three states do happen:

• Mobile number changed, your locker is tied to the mobile registered with Aadhaar. If you change the Aadhaar-linked mobile (at an enrolment centre), the locker follows. If you only update the mobile inside DigiLocker without changing it on Aadhaar, you lose access on next session.
• Account locked after failed OTP attempts, wait 24 hours and retry; the lockout is automatic.
• “Account suspended for misuse”, rare. Usually triggered by repeated abusive fetch from one device. Email [email protected] with your Aadhaar last-4 digits and registered mobile. If no reply in 30 days, file an RTI to NeGD.

DigiLocker keeps a fetch log per document, when each document was pulled, when it was shared, and with whom. You can see this in the app under “Activity.” MeitY's published privacy notice says this log is retained for the life of the account.

What DigiLocker does not do, per its own documentation:

• It does not share document contents with third-party apps without a per-document consent.
• It does not let advertisers access your locker.
• It does not store your Aadhaar biometrics, only the demographic record and a virtual ID.

What you should know anyway:

• Issuer-side logs are separate. UIDAI logs every authentication; the Income Tax department logs every PAN pull. These logs are not visible in DigiLocker.
• If a court orders disclosure, DigiLocker and the issuer must comply.
• Government law-enforcement requests follow the standard procedure, DigiLocker is not a special back door, but it is not an extra wall either.

If the locker can't fetch, the issuing department holds the answer, not DigiLocker, not NeGD. File an RTI to the issuer. Draft it cleanly with the AI RTI Drafter or use the template below.

Sample RTI to issuer (adapt as needed):

To,
The Public Information Officer,
[Issuing department, e.g. Office of the Tehsildar, Karnal]
[Address]

Subject: RTI under the Right to Information Act 2005

Sir/Madam,

Under section 6 of the RTI Act 2005, please supply:

1. Whether my [document type, e.g. income certificate] dated [date] bearing
   number [number] is currently active and digitised in your department's
   electronic records.
2. The status of integration of this department with DigiLocker
   (digilocker.gov.in) for [document type] as on [today's date].
3. If integration is live, the reason my record is returning the error
   "[exact error string]" on DigiLocker fetches dated [dates of attempts].
4. The name and designation of the officer responsible for the
   DigiLocker integration at this department, with contact email.

I enclose a copy of my [document] and a printout of the DigiLocker error
message dated [date].

The RTI application fee of ₹10 is paid by [postal order / IPO no. /
e-payment ref].

Name: [Name]
Address: [Address]
Mobile: [Mobile]
Date: [Date]
Signature

If the PIO does not reply in 30 days, file a first appeal under §19 of the RTI Act to the First Appellate Authority of the same department. After 30 more days of silence, escalate to the State or Central Information Commission depending on whether the department is a state or central one. The citizen RTI playbook walks through the full escalation ladder.

Anitha, a teacher in Coimbatore, needs her 1998 Class XII marksheet for a higher-degree application. CBSE DigiLocker fetch returns “Record not found.” She has the original mark sheet but the institution wants a verified digital copy.

Step 1, She tries the CBSE Pariksha Sangam portal directly. Same result: 1998 records aren't fully digitised.

Step 2, She files an RTI to the CBSE Regional Office (Chennai region) asking (a) the DigiLocker integration cut-off year for Tamil Nadu Class XII records (CBSE's nationwide DigiLocker cut-off is 2017), (b) the procedure to get a verified digital copy of a 1998 marksheet, © the fee.

Step 3, CBSE replies in 22 days. The DigiLocker integration cut-off is 2017. For older records (pre-2017), CBSE issues a migration certificate / verified copy on application via the Regional Office with ₹500 fee, in 30 days.

Step 4, Anitha applies, pays ₹500, gets the verified copy in 19 days. She uploads it to the “Uploaded Documents” tab of DigiLocker, knowing this carries no legal weight but is convenient for her own backup.

Total time: 41 days. Total cost: ₹510. No litigation, no agents, no shouting at a portal.

• Install DigiLocker (Android / iOS) or open digilocker.gov.in.
• Sign in via Aadhaar OTP. Confirm the demographic Aadhaar card auto-appears in “Issued Documents.”
• Fetch the four reliable documents you almost certainly need, PAN, DL, RC (if you have a vehicle), and your latest CBSE/state-board marksheet.
• Note any error code and look it up in the decoder section above.
• For any flaky issuer, don't retry endlessly, fix at source or draft an RTI in the AI RTI Drafter.
• Bookmark this page; return when an issuer changes status.

Yes, for documents in your Issued Documents section (pulled directly from the issuer with a digital signature). §9A of the IT Act 2000 and the MeitY notification of 8 February 2017 give them the same legal effect as the paper original. Documents you upload yourself to the Uploaded Documents tab are not legally equivalent, they're personal backups.

No. The MoRTH advisory dated 8 August 2018 directs all state police and transport authorities to accept the DigiLocker or mParivahan copy. Several high courts have reinforced this. If an officer still insists, ask politely for their name and badge number, comply on the spot, and complain through the state police grievance portal afterwards.

Sometimes, with a partial match score. Often it fails with “Name mismatch.” The clean fix is to align the two: usually by submitting a PAN change request (Form 49A) via NSDL/Protean. After the change is processed (15–30 days), re-fetch in DigiLocker.

The issuer is registered with DigiLocker but the underlying database integration is partial. Older years are often not digitised. Confirm by trying a direct fetch on the state board portal, if that also fails, file an RTI to the board asking the digitisation cut-off year and the manual-fetch procedure.

No. DigiLocker is recognised inside India. For international driving you need an International Driving Permit issued by your RTO, a separate paper document. DigiLocker has no IDP issuer.

Yes in legal effect, slightly different in appearance. The DigiLocker version is the latest record at fetch time and carries UIDAI's signature. The e-Aadhaar PDF you download from myAadhaar is also signed. Either is acceptable wherever Aadhaar is required.

Issued documents disappear from your locker but continue to exist at the issuer. You can re-create a DigiLocker account later and re-fetch them. Documents you uploaded yourself are deleted permanently. MeitY's data-retention notice says deleted accounts are purged within 90 days.

The Co-WIN signing certificate's trust chain isn't always installed on the verifier's reader. If the verifier uses the Co-WIN verifier app or the DigiLocker verifier, it will validate. If they use a third-party PDF reader without the CCA India trust root, signature status reads “unknown.” Politely point them to the DigiLocker app's built-in verifier.

No. You can only upload a personal copy (no legal weight) under the Uploaded Documents tab. You cannot create an “issued” entry yourself, that would defeat the integrity of the system.

File a first appeal under §19(1) of the RTI Act within 30 days of the missed reply deadline. If the appellate authority also stays silent, file a second appeal/complaint with the State or Central Information Commission. The citizen RTI playbook walks through each step with templates.

1. Issuer reliability ratings, the table reflects a 2026 working-observation sample, not an official benchmark. Re-test quarterly; state ration-card and land-record integrations change month-on-month.
2. MoRTH advisory date, quoted as 8 August 2018 from the public version in circulation; the official letter number is RT-11036/64/2017-MVL. Verify with the latest MoRTH website before any litigation use.
3. CBSE DigiLocker cut-off (2017), per the CBSE Academic Repository at https://cbse.digitallocker.gov.in. Pre-2017 records require a written application or RTI to the CBSE Regional Office. If retroactive digitisation completes by the next refresh, update the worked example.

• DigiLocker official portal (Government of India)
• Ministry of Electronics and Information Technology, MeitY, notification dated 8 February 2017 on DigiLocker legal equivalence
• Information Technology Act 2000, §9A, electronic delivery of services
• UIDAI, Aadhaar Act 2016 and Aadhaar (Authentication and Offline Verification) Regulations 2021
• MoRTH advisory dated 8 August 2018, letter RT-11036/64/2017-MVL on DigiLocker DL/RC acceptance
• UMANG portal
• Controller of Certifying Authorities (CCA India), root certificate for signature verification
• Right to Information Act 2005, §6, §7, §19

• UMANG app, every government service in one app
• Citizen RTI playbook, file, escalate, win
• State-by-state RTI master guide
• State RTI portals directory
• Free RTI AI tools, the complete suite
• How to file an RTI in India, definitive guide
• Aadhaar correction RTI, when UIDAI sits on your request
• Tool: AI RTI Drafter

Last reviewed: 16 May 2026. Maintained by the RTI Wiki editorial team. Issuer connectivity changes, verify the status of the specific issuer you need before a high-stakes use.