DigiLocker Match

Overview

A matching flow where a user can enter some details, then complete a Digilocker verification.

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

Integration with Trinsic

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

• Data Inputs: fullName, dateOfBirth
• Permission required: No, this method is live by default for all customers of Trinsic.
• Cost: Contact the Trinsic team.

User Flow

DigiLocker Match asks a user for their name and date of birth to begin the verification flow. Then we require the user 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 performs a match and returns the verified data to the relying party. To see a demo of this flow, watch this video.

Customers can bypass the form-fill step by passing in known identity data about the user when launching the integration. In this scenario the user would go directly to the DigiLocker login step.

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.
• Requires Input: This provider requires input before verification can proceed.
• 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.
• Trinsic-Hosted UI: A Trinsic-Hosted Fallback UI exists for this provider, which may be invoked to cover gaps in your integration's capabilities.

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.