DigiLocker Verification Failed? Fix Missing Documents

When DigiLocker cannot fetch or verify a document, start with the exact error and the issuing organisation. A missing issuer record, a name mismatch, an account problem and a failed QR scan require different checks. Keep the original acknowledgement or document available while you work through them.

• No record found / document not available. First check: Issuer, document type, number and other requested fields. Where to take an unresolved problem: Issuer for a missing record, DigiLocker Support for a persistent fetch problem.
• Details do not match issuer data. First check: Compare what you entered with the actual issued record. Where to take an unresolved problem: Issuer's correction process if the record is wrong.
• Name mismatch. First check: Compare the Aadhaar-linked name and the document's name. Where to take an unresolved problem: The authority responsible for the record that needs correction.
• Aadhaar already registered. First check: Check whether you have an earlier DigiLocker account. Where to take an unresolved problem: Official account-recovery or support process.
• QR verification failed. First check: Use the original digital document and the supported verification method. Where to take an unresolved problem: Issuer/verifier and DigiLocker Support with the exact failure.
• FP001 or another unexplained code. First check: Save the full message, issuer, date and document type. Where to take an unresolved problem: DigiLocker Support. The code alone does not establish a cause.

The first four checks follow DigiLocker's official FAQ. The FP001 entry is a practical reporting step: this review did not verify a universal official explanation for that code. Do not pay someone claiming to have a guaranteed code-specific fix.

1. Open the official DigiLocker service and select the correct issuing organisation and document type.
2. Compare each requested field with the document or issuer record. Keep the issuing year and reference number alongside the name.
3. Check whether the issuer has made that record available. For a driving licence or vehicle registration, DigiLocker depends on the transport record in the National Register.
4. If the source record is wrong or missing, ask the issuer how to correct or publish it. If it is available and the entered details match, report the fetch failure to DigiLocker Support.
5. After a correction, retry and compare the retrieved document with the corrected source. Keep both the correction acknowledgement and support ticket until the matter is resolved.

For academic records, DigiLocker NAD identifies the educational institution as the custodian of its awards. For document availability more broadly, see our DigiLocker issuer guide.

Choose the record that is actually incorrect. Do not change Aadhaar automatically, and do not assume the certificate must always be changed instead. Write the two versions side by side and check the supporting records required by the relevant issuer.

DigiLocker's official Ask Our Experts answers confirm that name matching can prevent a document from being fetched, including when the order of names differs. A support ticket should include the mismatch in words and the affected document type. Share identity documents only through the official process when required.

For a problem spanning several records, continue with PAN and Aadhaar name-mismatch guidance. For an Aadhaar update already submitted, use Aadhaar update status by SRN, URN or EID.

Issued Documents come from an integrated issuer. DigiLocker Drive stores files that you upload. Keeping a scan in your Drive can be useful for your own records, but it does not turn that scan into a digitally issued certificate. DigiLocker explains this distinction in its FAQ.

The legal provision is Rule 9A of the Information Technology (Preservation and Retention of Information by Intermediaries Providing Digital Locker Facilities) Rules, 2016, introduced by the 2017 amendment. It concerns digitally signed documents shared through the system and issuer-linked access. It is not “section 9A of the IT Act.” See the official circular and annexed rules and DigiLocker's explanation.

If an organisation refuses a document, ask what failed: identity matching, access to the issued record, verification, or a document requirement. Keep its written explanation. Do not assume a screenshot proves that verification succeeded.

Use the original issued digital document where possible. Compare its issuer, reference and visible details with the source. Ask the receiving organisation which verification method it used and what error it received. For DL/RC, DigiLocker describes verification through the digital signature or its app's QR facility in the official FAQ.

Do not edit the PDF, draw a new QR code, or repeatedly re-save screenshots as a supposed verification fix. If the error persists, preserve the original and report it. We found no basis for the earlier claim that a six-month-old printout automatically stops verifying because an issuer rotated its keys.

For the distinction between a visible signature and a verifiable file, read checks before trusting a digitally signed PDF and what changes when a digitally signed document is printed.

The current DigiLocker Helpdesk lets users sign in to submit and track requests. It also lists [email protected] for queries. DigiLocker's terms of use direct support and grievance requests to that helpdesk.

Prepare a short ticket with:

• The issuer and document type.
• The exact error text, including any code such as FP001.
• When it occurred and whether you used the app or website.
• The checks you have already made against the issuer record.
• A screenshot with unnecessary personal information hidden.
• Any earlier ticket or correction reference.

Keep follow-ups attached to the same issue where the helpdesk permits. This guide does not promise a seven-day response or a 7–21-day resolution. Those time estimates in the earlier version were not supported by a verified dataset.

This review did not verify that conclusion. Include the full message and document context in a support request instead of treating the code as proof that an identity record must change.

The official FAQ directs users towards recovering the earlier account. Use that route before creating more accounts.

No. It stores your file. The missing issuer-provided record still needs the relevant issuer or support action.

Use the official support portal and the request reference. Keep the response with the document's correction history.

The institution is the custodian of the award in NAD. Ask it about the correction. Report a platform problem separately so the two issues are not confused.

Ask the receiving institution which verified alternative it accepts while the technical issue is examined. Attach your existing ticket reference. Do not assume that opening a ticket extends an admission or employment deadline.

Read next: The RTI Playbook — practical help with drafting and appeals.

• Official DigiLocker FAQ
• Submit or track a DigiLocker support request
• Official name-matching answers
• Rule 9A and the official digital-locker circular
• NAD and the institution's role
• Keep your original files and complaint records safely
• Seek existing records from a public authority through RTI

Reviewed 8 September 2026. Corrected the Rule 9A reference, replaced the unverified support route, removed unsupported outcome statistics and removed links back to this same page.