Skip to content
LeanFintech DigiLocker

Verified documents. Explicit consent.

Guide an investor through DigiLocker authorization and retrieve available identity, issued documents, and parsed Aadhaar, PAN, or driving-licence data.

Consent purpose, callback state, and document results in one integration.
leanfintech.digilockerconsented
session
Lookupmobile or Aadhaar
Authorizeprovider consent URL
Callbackstate + session ID
Resultaggregate response
Investor grants consentPurpose captured for the customer workflow
redirect -> callback
available result
Identityverified data
Documentsissued list
Parsed docsAadhaar · PAN · DL
Errorssection-level detail
consent: truecustomer redirect URL
Supported document workflow
AadhaarPANDriving licenceIssued documents
The consent journey

Four steps from account check to usable documents.

Each API operation has one job, so your product controls the user experience and the processing boundary.

01

Account lookup

Optionally check a mobile number or Aadhaar number to choose a sign-in or sign-up path.

02

Start session

Capture explicit consent and purpose, then receive the authorization URL and session ID.

03

Investor consent

Redirect the investor to DigiLocker and back to your callback with state and session context.

04

Read result

Fetch identity, available issued documents, parsed data, and section-level errors in one aggregate call.

Result contract

Useful even when one section is unavailable.

Identity, issued-document inventory, and parsed-document sections are independent. An unavailable section is reported under errors without failing every other result.

  • Verified identity when supplied by DigiLocker
  • Issued document inventory
  • Parsed Aadhaar, PAN, and driving-licence documents
  • Section-specific error detail
Request shape
POST /v1/kyc/digilocker/session

{
  "consent": true,
  "consent_purpose": "KYC for account opening",
  "redirect_url": "https://yourapp.com/callback"
}
Purpose before access

Consent is part of the API contract.

The session requires explicit consent, a clear purpose, and your redirect URL. The authorization happens on DigiLocker, not inside a simulated identity screen.

Independent capability

Use it with or without PAN KYC Status.

DigiLocker retrieves consented identity and documents. PAN KYC Status checks registry state across the KRAs.

Explore KYC Status
Questions

DigiLocker, answered.

Which documents can the flow parse?

The aggregate result can parse available PAN, Aadhaar, and driving-licence documents, alongside verified identity and the issued-document list.

Is investor consent required?

Yes. Starting a session requires explicit consent and a consent purpose, and the investor authorizes access on DigiLocker.

Is account lookup required?

No. It is an optional pre-consent check that can help your product choose between DigiLocker sign-in and sign-up.

Does one missing document fail the result?

No. Identity, issued documents, and parsed-document sections are independent; unavailable sections are returned under errors.

Make document consent feel like part of your product.

Map authorization, callback state, document handling, and retention before production.

Review your DigiLocker flow