All products Aadhaar KYC · eKYC and Offline

One Technology Stack. Every Aadhaar Authentication Journey.

Focus on delivering seamless Aadhaar authentication experiences while we power the technology behind them—from secure infrastructure and APIs to HSM key management and multi-ASA/KSA connectivity.

Book a demo

9:41▮▮▮

Aadhaar eKYC

Consent accepted

Capture face

Verify identity

Matching with UIDAI

Face authentication successful

Receive KYC details

Your application

Customer KYC
detailsVerified

NameXXXX

Date of birthDD/MM/YYYY

AddressXXXX, YYYY

AadhaarXXXX XXXX 4821

Authentication modes

Every supported mode. One integration.

Enable Aadhaar authentication journeys across UIDAI-supported modes through a unified API ecosystem.

OTP

Aadhaar-linked OTP authentication for simple digital journeys.

Fingerprint

Biometric authentication through supported fingerprint devices.

Iris

Secure iris-based biometric authentication journeys.

Face Auth

UIDAI-supported face authentication for convenient verification.

How it works

From authentication request to UIDAI response.

See how an Aadhaar request moves from the customer's device through AUA/KUA, DSC signing in the HSM and smart routing, to UIDAI and back.

Customer + Authentication Device
Starts the Aadhaar authentication journey and captures the selected authentication input.
AUA/KUA
Sends the request through secure APIs.
DSC Signing + HSM Enc Mapping
Signs the request using DSC in HSM and maps the encrypted data.
TSP + Smart Routing
Secure processing and ASA/KSA route selection.
UIDAI
Processes and returns the authentication response.

Features

Everything your AUA/KUA stack needs.

From HSM key custody and multi-route connectivity to APIs, vaulting and audit support, the infrastructure behind every Aadhaar journey.

See how it works

HSM

FIPS 140-2 · Level 3

01

HSM-Powered Security

Protect every authentication with HSM-backed key security. Secure key management with High Availability architecture and BYOK support delivers stronger control, security, and reliability for your AUA/KUA ecosystem.

ROUTER

ASA / KSA 1Active

ASA / KSA 2Down

ASA / KSA 3Standby

02

Smart ASA/KSA Routing

Multiple routes. Smarter connectivity. Our intelligent routing engine works across multiple ASA/KSA partners to improve service availability and reduce dependency on a single connectivity route.

API

eKYC

Authentication

Tokenisation

03

Easy API Integration

Integrate once. Power multiple Aadhaar journeys. Easy-to-integrate APIs give you access to eKYC, Authentication, and Tokenisation services with support for OTP, Fingerprint, Iris, and Face Authentication.

AADHAAR VAULT

04

Integrated Vault Solution

Extend eKYC with secure Aadhaar vaulting. Seamlessly integrate Aadhaar Vault capabilities into your ecosystem to securely manage Aadhaar-related data and tokenisation workflows.

Activity Monitoring

User Activity

API Access

Policy Changes

Data Requests

05

Audit & Compliance Support

Stay audit-ready with dedicated technology and compliance support. Get assistance with technical documentation, infrastructure evidence, and security controls for applicable UIDAI, RBI, and other regulatory audits.

On-premise

GCC hosted

06

Flexible Deployment

Deploy your way—on-premise or within a GCC-compliant hosted environment. Choose a deployment model that aligns with your infrastructure, security, and operational requirements.

3Verification routes

9Demographic fields returned

0.9sConsent to signed record

ZeroAadhaar numbers stored raw

Where Aadhaar KYC goes wrong

The customer is willing. The route is the problem.

Most Aadhaar journeys fail on the licensing route, the fallback and what happens to the number afterwards, not on the customer’s intent.

Talk to us

Exposure Photocopies nobody can defend

A drawer of Aadhaar letters with the number in the clear is a liability long after the account is opened.

The pattern One route, no fallback

When OTP fails there is no biometric desk and no offline path, so the journey simply stops.

Drop-off The OTP that never lands

An unreachable registered mobile ends the application — unless a biometric or offline route is already wired in.

Zero

Aadhaar numbers held in the clear — every route ends in a token, not a number.

↗

Trust Offline XML taken on faith

An unsigned or unverified paperless eKYC file is just an editable document — the signature check is the whole point.

The Aadhaar KYC routes

Three routes. One verified identity.

OTP eKYC for self-serve journeys, biometric eKYC for assisted and field ones, and offline paperless eKYC as an OVSE where a UIDAI authentication call is not available to you. Same demographic record, same audit trail, same token at the end.

OTP eKYC

The self-serve route, finished on the customer’s own phone.

Run as a licensed AUA/KUA. The customer consents, enters their Aadhaar number or VID, and UIDAI returns a digitally signed demographic record — name, date of birth, gender, address and photograph — straight into your journey.

No paperwork at all

Signed by UIDAI

VID accepted like the number

Finished in one sitting

How it worksOTP eKYC

1

Consent capturedPurpose, entity and retention shown on screen and recorded.Timestamped

2

Aadhaar or VID enteredChecksum validated; a virtual ID is treated identically.VID accepted

3

OTP verifiedSix digits to the registered mobile, with a retry policy.0.4s

4

Signed KYC returnedUIDAI’s signature verified, then fields mapped to yours.9 fields

Tokenised and storedSame demographic record, same audit trail, same token.

Number never stored raw Consent on the audit trail

Features

Built for a journey that has to finish in one sitting.

From consent wording to retry policy, every part is shaped for completion rates and for what an audit will ask later.

See how it works

01Licensed AUA/KUA access

Authentication runs through licensed infrastructure, so you integrate one API instead of a UIDAI programme.

02VID and Aadhaar alike

Virtual IDs are handled identically, letting privacy-conscious customers keep the number to themselves.

03Consent recorded, not assumed

Purpose, entity and retention are shown and stored with the request, ready for any audit.

Aadhaar OTP eKYC0.9s

9

signed demographic fields returned

OTP deliveryRegistered mobile

UIDAI signatureVerified

Number tokenisedVault reference returned

04Signature verified every time

UIDAI’s digital signature on the response is checked before a single field is mapped.

05Retry and fallback policy

Resend limits, lockouts and an automatic hand-off to biometric or offline when OTP will not land.

06Tokenised at the end

The number goes to the vault and your systems keep a reference, so nothing raw is retained.

Biometric eKYC

For the branch, the BC point and the doorstep.

Where a registered mobile is unreachable or the customer is being served in person, a fingerprint or iris capture on a registered device authenticates them instead — encrypted at the sensor, never held by your application.

Fingerprint or iris

Encrypted at the sensor

Operator on the trail

Works on weak networks

How it worksBiometric eKYC

1

Operator and consentOperator identity, location and purpose recorded on the request.Logged

2

CaptureA registered STQC device reads the fingerprint or iris.Registered device

3

Encrypted in deviceThe PID block is encrypted inside the sensor itself.Nothing retained

4

AuthenticatedUIDAI confirms the match and returns the same signed record.1.2s

KYC returnedSame demographic record, same audit trail, same token.

No biometric retained Operator, device and location

Features

Built for assisted journeys where the phone is not the answer.

Field teams, business correspondents and branch desks, with the same record and the same audit trail as a self-serve eKYC.

See how it works

01Fingerprint and iris

Both modalities on registered devices, so a worn fingerprint does not end the journey.

02Encrypted at the sensor

The PID block is encrypted inside the device; your application never sees a biometric.

03Operator on the trail

Every capture carries the operator identity, device and location into the audit record.

Biometric eKYCAssisted

1.2s

capture to authenticated record

DeviceRegistered · STQC

Biometric retainedNone

Operator recordedID, device and location

04Works where data does not

Designed for low-bandwidth field conditions with retry that does not restart the journey.

05Any registered device

STQC-certified readers from multiple vendors behind one integration.

06Same output as OTP eKYC

One response shape across routes, so your onboarding code does not branch.

Offline eKYC · OVSE

Aadhaar verification without a UIDAI authentication call.

As an Offline Verification Seeking Entity you never touch the Aadhaar number. The customer shares a UIDAI-issued paperless eKYC XML with their own share code, or the secure QR from their Aadhaar letter — and you verify UIDAI’s digital signature on it.

No authentication call made

Aadhaar number never exposed

Paperless verification

Same demographic record & audit trail

How it worksOffline eKYC · OVSE

1

Artefact receivedCustomer shares the offline eKYC ZIP or secure QR in your app.XML or secure QR

2

Share codeA customer-set four-character code opens the file.4 chars

3

Signature checkedUIDAI’s digital signature is validated offline.UIDAI verified

4

Fields readReference ID, name, date of birth, address and photograph.Never exposes the number

Verified offlineSame demographic record, same audit trail, same token.

No authentication call made Aadhaar number never exposed

Features

Built for entities that must verify without ever authenticating.

The route for lenders, fintechs and agents outside the AUA/KUA regime — and the fallback when OTP and biometrics are both out of reach.

See how it works

01No UIDAI call, no licence

Verification happens against UIDAI’s signature, so the route is open to entities outside AUA/KUA.

02XML and secure QR

Paperless eKYC files and the QR printed on the Aadhaar letter both read through one integration.

03Share code stays the customer’s

Only they can unlock the file, and the code is used in memory and discarded.

Offline eKYC · OVSENo auth call

Valid

UIDAI signature on the paperless eKYC

Share codeCustomer-set

Aadhaar numberNever present

Verified offlineReference ID · last four digits

04Certificate chain checked

The signature is validated against UIDAI’s certificate, with tampered files rejected outright.

05Reference ID, not the number

The last four digits and a reference ID are all that exist — there is nothing full to protect.

06Same response shape

Fields map to the identical structure as OTP and biometric eKYC, so downstream code is unchanged.

Common to all three

The platform underneath every route.

Consent, licensing, masking, audit and integration sit behind OTP, biometric and offline alike — so the route can change without your onboarding changing.

Consent Recorded before anything runs

Purpose, entity and retention are shown to the customer and stored with a timestamp against every request, on every route.

Licensing AUA, KUA or OVSE

Authenticate through licensed infrastructure where you are entitled to, and verify offline where you are not — without two integrations.

Protection Tokenised, never stored raw

The Aadhaar number goes into a 256-bit vault and your systems keep a reference; images are masked before anything is retained.

Audit Every request reconstructable

Route, operator, device, consent artefact and response signature are held together, so a regulator’s question has one answer.

Integration One response shape

OTP, biometric and offline return the same field structure, so switching or falling back between them costs no downstream code.

Fallback A second route, already wired

When the OTP will not land or the fingerprint will not read, the journey moves to the next route instead of ending.

Bring the customers
your OTP route loses.

The unreachable mobile, the worn fingerprint, the entity that cannot authenticate at all. Sandbox keys, your own journey and a solution engineer on the call — then see which route finishes it.

Book a demo

One Technology Stack. Every Aadhaar Authentication Journey.

Every supported mode. One integration.

OTP

Fingerprint

Iris

Face Auth

From authentication request to UIDAI response.

Customer + Authentication Device

AUA/KUA

DSC Signing + HSM Enc Mapping

TSP + Smart Routing

UIDAI

Everything your AUA/KUA stack needs.

HSM-Powered Security

Smart ASA/KSA Routing

Easy API Integration

Integrated Vault Solution

Audit & Compliance Support

Flexible Deployment

The customer is willing. The route is the problem.

Most Aadhaar journeys fail on the licensing route, the fallback and what happens to the number afterwards, not on the customer’s intent.

Three routes. One verified identity.

The self-serve route, finished on the customer’s own phone.

Built for a journey that has to finish in one sitting.

For the branch, the BC point and the doorstep.

Built for assisted journeys where the phone is not the answer.

Aadhaar verification without a UIDAI authentication call.

Built for entities that must verify without ever authenticating.

The platform underneath every route.

Bring the customersyour OTP route loses.

Bring the customers
your OTP route loses.