DigiLocker Fetch

Overview

India’s government-endorsed digital locker for securely storing and sharing documents. Logs the user into DigiLocker via phone, PIN and OTP, then returns verified Aadhaar attributes.

ID: india-digilocker-aadhaar
Type: eID (app)
Verification Type: Presentation
Regions: Asia
Countries: IN
Adoption: 677,000,000
URL: https://www.digilocker.gov.in

Integration with Trinsic

The DigiLocker Fetch verification is integrated into Trinsic's identity acceptance network allowing businesses to verify users against the government system of record in India.

Permission required: Yes. Contact the Trinsic team to request access to this provider.
Cost: Contact the Trinsic team.

User Flow

The user is required to log into their DigiLocker account using their phone number, PIN and a one time passcode. By doing so, the user consents to sharing their data with the service which returns the verified data to the relying party. To see a demo of this flow, watch this video.

Direct API Requirements

📘
Direct is not a requirement.
You can integrate with this provider using the Widget or Hosted UI instead, with no additional integration requirements on your end.

What your integration must support in order to use this provider with the Direct Provider Sessions API.

Supports Direct Provider Sessions: ✅
Launch Method: LaunchBrowser — Send the user's browser (via redirect, popup, or new tab) to the given URL.
Collection Method: CaptureRedirect — The user is redirected back to your app with a resultsAccessKey upon completion.
Results May Be Delayed Post-Redirect: The results of a verification with this provider may not be available immediately upon user redirect back to your application.

Outputs

ℹ️
Normalized Attributes
These attributes form part of our normalized model, a standardized set used across providers. Trinsic normalizes this for you and lets you know when a property is available for each provider.

Field	Availability	Notes
`person.fullName`	Always	-
`person.dateOfBirth`	Always	-
`person.sex`	Always	-
`person.address.line1`	Sometimes	If available
`person.address.line2`	Sometimes	If available
`person.address.line3`	Sometimes	If available
`person.address.city`	Always	-
`person.address.subdivision`	Always	-
`person.address.postalCode`	Always	-
`person.address.country`	Always	-
`document.number`	Always	-
`attachments.documentPortrait`	Always	-

Frequently Asked Questions

What if a user does not have an account with DigiLocker?

Anyone registered with Aadhaar can create a DigiLocker account on the fly during the verification flow, they will just need to complete a couple additional steps.

How can a user sign in to DigiLocker?

Users can sign in with their mobile number, username, or via another identifier like Aadhaar number.

Is the PIN required?

The user can select “PIN less authentication” within the DigiLocker interface to skip the PIN. The interface is fully controlled by DigiLocker, so we’re not able to control what they choose.

Can we change the language on the Digilocker consent screen?

At this time we cannot change the language on the consent screen. If a relying party has an entity in India, they could get registered and then their name could be displayed within the Digilocker consent screen.

Which documents can be fetched from DigiLocker through this integration?

Right now our integration supports the e-Aadhaar card. We plan to support PAN card and Driving License in the future.

Can users sign in to DigiLocker with Jan Parichay or ePramaan?

These options are currently not supported in our DigiLocker integration. Jan Parichay is a government single sign-on (SSO) system used by citizens and government users. ePramaan is a government authentication framework, primarily used for legacy or department-linked government accounts. Users should choose one of the three sign in methods (mobile number, username or their Aadhaar number.