API Category · Identity
Confirm a customer is who they say they are, against the records that actually govern it, Income Tax Department, UIDAI, the Election Commission, not against a photograph of a card.
Trusted Across Indian BFSI
Banks, NBFCs, housing finance companies and co-operative banks run verification, Aadhaar masking and document workflows on FinHub, inside their own compliance and audit requirements.
Prüfens Advisory
In short
An identity verification API checks a submitted identifier against the authority that issued it and returns validity, the registered name and a name-match score. FinHub covers PAN, Aadhaar, voter ID and passport, plus video KYC for flows that require a live operator, each with consent capture and an audit trail.
- Checked against source records, not read off a document image
- Normalised name-match scores so you can auto-approve clean matches
- Video KYC for flows where regulation requires a live operator
- Consent artefact on every call, written to a tamper-evident log
5 APIs
Every API in Identity Verification
One integration, one authentication and one response shape across the whole category.
Reference
What Each API Returns
The endpoint and the fields that come back, so you can size the integration before you write any code.
| API | Endpoint | Key fields returned |
|---|---|---|
| PAN Verification | POST /v1/kyc/pan/verify | Validity & active status · Registered name · Name-match score (0–1) · PAN–Aadhaar link status |
| Aadhaar Verification | POST /v1/kyc/aadhaar/ekyc | Verification status · Name, DOB, gender, address (per consent) · Masked Aadhaar reference · Photo (optional) |
| Voter ID Verification | POST /v1/kyc/voter-id/verify | Validity status · Holder name · Constituency / state · Name-match score |
| Video KYC | POST /v1/kyc/vcip/session | Session status & recording reference · Liveness & face-match scores · Extracted document fields · Geotag & timestamp |
| Passport Verification | POST /v1/kyc/passport/verify | Validity status · Holder name match · Expiry & issue date · Nationality · Match confidence score |
Verification or OCR, Which One Do You Actually Need?
These get conflated constantly, and the distinction decides whether your onboarding stands up under examination. OCR reads a document. Verification asks the issuing authority. A PAN read cleanly off a card that was cancelled last year will OCR perfectly and verify as inactive.
The pattern most Indian BFSI flows settle on is both, in sequence: OCR to capture and pre-fill so the customer is not typing a twelve-digit number on a phone, then verification to confirm the identifier is live and the name matches before anything is approved.
If you are only going to do one, do verification. A pre-filled form that is wrong is worse than a typed form that is checked.
What Does a Name-Match Score Do?
Indian names defeat exact string matching. Initials expand and contract, surnames move between the front and back of the name, transliteration from a regional script is not deterministic, and honorifics come and go. 'S. Raghavan' and 'Raghavan Subramanian' are frequently the same person.
A normalised score between zero and one lets you set your own thresholds rather than accepting a vendor's binary verdict. The usual shape is a high band that auto-approves, a middle band that routes to review, and a low band that rejects, with the thresholds tuned to your product's risk appetite rather than fixed by us.
OCR + classification
PAN · Aadhaar · face match
Loan KYC · DPDP Section 7(1)
Welcome call · transcript attached
When Is Video KYC Required Rather Than Optional?
Video KYC exists because some onboarding journeys need a human in the loop and a recorded artefact of the interaction. Which journeys those are depends on your regulator and product: the RBI's Master Direction on KYC governs this for banks and NBFCs, and the specific triggers change over time.
Treat the applicable rule as something to confirm with your compliance function against the current Master Direction, not something to take from a vendor page. What we can say is what the API does: it runs the session, captures the artefacts and writes them to an auditable record.
Sealed to a tamper-evident record
Terms
Terms Worth Getting Right
The distinctions that decide whether a flow stands up under examination.
- CKYC
- The Central KYC Records Registry holds a KYC record that can be reused across regulated entities, keyed by a CKYC identifier, reducing repeat collection when a customer has already been onboarded elsewhere.
- Name-match score
- A normalised 0–1 similarity between the name a customer gave and the name on the authority's record, accounting for initials, ordering and transliteration.
- Aadhaar eKYC vs Aadhaar Authentication
- Aadhaar Authentication returns a simple yes/no match against a name, OTP or biometric, with no demographic data. Aadhaar eKYC, what this API does, additionally returns the registered name, date of birth, gender and address, per the consent captured. If your flow only needs a match/no-match answer, authentication alone may be sufficient; if you need to populate a form, you need eKYC.
FAQ
Identity Verification, Common Questions
Yes. FinHub by Habilelabs provides identity verification APIs for Indian BFSI, PAN, Aadhaar, voter ID and passport verification against source records, plus video KYC, with consent capture and a tamper-evident audit trail on every call.
Related categories
Nearby on the API Platform
Last updated · 15 August 2026
Try It Against Your Own Documents
Sandbox access with your real document mix, so you can measure accuracy on your captures rather than ours.