Digilocker Flow

The DigiLocker Journey enables users to fetch and verify official documents directly from DigiLocker in a secure and compliant manner. It supports retrieval of key documents such as Aadhaar, PAN, Driving License, and Educational Mark Sheets, which can then be used across onboarding and verification flows. The journey ensures end-to-end digital consent, document fetching, and delivery in a structured format for seamless downstream use.

Sample Digilocker Journey

The following flowchart illustrates the complete Digilocker document retrieval and verification flow:

Flow Explanation

The Digilocker journey begins with the Start API, which returns an authentication URL for the user. The process then follows a conditional path based on the types of documents needed. First, it retrieves eAadhaar details, then checks if PAN or Driving License documents are required. If additional documents are needed, the system determines whether to fetch non-issued documents (documents not yet in Digilocker) or issued documents (already present in the user's Digilocker account like marksheets). The entire flow is designed to handle different document types efficiently while maintaining proper consent and authentication throughout the process.

Overview

What is DigiLocker?

DigiLocker is one of the sources for marking documents as OSV (Originally Seen and Verified) e-documents or electronic equivalents of OVD (Officially Valid Documents).

Document Legitimacy Requirements

An electronic document is considered legitimate only if it has a digital signature, which DigiLocker provides (though not exclusively).

Regulatory Compliance

• Intermediary Requirements: Registered intermediaries are required to verify copies of OVD provided by investors with the original OVD
• Simplified Process: For investor convenience, OVD can be deemed as "seen and verified" with the original when:
  • The investor provides the OVD through the eSign mechanism as a clear photograph/scanned copy of the original, OR
  • The document is digitally signed and issued to DigiLocker by the issuing authority

SEBI Recognition

Since the SEBI notification, registered intermediaries (RI) have adopted DigiLocker as a means for verifying OVD. The act of checking if a document exists on DigiLocker serves as proof for OVD verification.

User Requirements

• Minimum Sign-up: End users need a mobile number at minimum
• Document Access: To access documents from various issuers, users must link their Aadhaar to DigiLocker

Reference Document

This official government document provides comprehensive information about DigiLocker definitions, rules, and amendments. It serves as the authoritative reference for understanding DigiLocker's regulatory framework and operational guidelines.

DigiLocker definition and rules - Government Aided Reference Documentation

Module Outputs

The Results API returns the detailed output for this module. The following section provides the sample and the corresponding details of the various responses you can expect from the module.

Success Response Sample

You will receive a success response in a format similar to the following code sample if the request is correct.

Success Response

  {
              "module": "Digilocker API",
							"moduleId:"digilocker_flow",
              "imageUrls": [],
              "apiResponse": {
                  "status": "success",
                  "statusCode": "200",
                  "result": {
                      "details": [
                          {
                              "name": {
                                  "value": "Jane Doe"
                              },
                              "dob": {
                                  "value": "06-07-1998"
                              },
                              "address": {
                                  "value": "1b, Dover Lane, Sarat Bose Road, Kolkata, West Bengal"
                              },
                              "maskedAadhaarNumber": {
                                  "value": "xxxxxxxx1234"
                              },
                              "photo": {
                                  "value": "Base64 String"
                              }
                          }
                      ]
                  }
              },
              "previousAttempts": []
          }