Identity · eKYC
Verify Aadhaar and complete OTP-based eKYC with UIDAI-aligned flows — masked, consent-first and built for the scrutiny of regulated finance.
Overview
What the Aadhaar Verification API does
FinHub's Aadhaar Verification API supports OTP eKYC and offline/QR verification so you can establish identity with the customer's explicit consent. Aadhaar numbers are masked end to end, every verification is bound to a consent artifact, and the result is written to an immutable audit trail — meeting UIDAI and DPDP expectations by design.
Inputs
- Aadhaar (masked / VID)
- OTP or offline XML
- Consent artifact ID
Returns
- Verification status
- Name, DOB, gender, address (per consent)
- Masked Aadhaar reference
- Photo (optional)
POST /v1/kyc/aadhaar/ekyc
How it works
Three steps to a verified result
Capture consent
The customer consents to Aadhaar eKYC; FinHub records a purpose-bound consent artifact.
Verify with OTP
The customer authenticates with an OTP to their Aadhaar-linked number, or you submit an offline XML/QR.
Receive masked KYC
Get verified demographic fields with the Aadhaar number masked, sealed to your audit log.
Use cases
Where teams use Aadhaar Verification
- OTP eKYC for digital account opening
- Video KYC and assisted onboarding
- Re-KYC and periodic updates
- Paperless customer verification
FAQ
Aadhaar Verification API — FAQs
Common questions about FinHub's Aadhaar Verification API.
Yes. FinHub supports OTP-based Aadhaar eKYC as well as offline/QR verification, both bound to a customer consent artifact under a DPDP-ready architecture.
More verification APIs
Explore related APIs
Ready to add Aadhaar Verification to your flow?
Book a demo and see the API return a verified result on your own test data in minutes.