Investment account opening
Block a predictable downstream failure before the account goes live.
Find out about an unlinked PAN during onboarding, not during settlement.
# Request "input": "PAN + Aadhaar reference" # Response fields { "link_status": …, "pan_status": …, "name_match": …, "consent_ref": …, "checked_at": … }
Overview
An unlinked PAN is a quiet problem. Nothing fails at sign-up. It fails later — at a transaction limit, a tax deduction, a payout — by which point the customer is mid-journey and the fix is a support ticket instead of a form field.
This endpoint returns linkage status against a PAN and Aadhaar reference, so you can surface the issue at the moment the customer is already filling in details and most likely to resolve it.
Response
Every field is returned structured and timestamped, ready to store against the record it belongs to. Nothing requires parsing a photograph or interpreting free text.
| Field | Description |
|---|---|
link_status | linked, not_linked or indeterminate |
pan_status | Whether the PAN itself is active |
name_match | Whether holder names reconcile across records |
consent_ref | Consent reference, echoed back |
checked_at | Timestamp of the check |
Use cases
Block a predictable downstream failure before the account goes live.
Confirm linkage before funds move and reconciliation becomes someone's afternoon.
Sweep an existing customer base and prompt only the accounts that actually need action.
Validate tax identifiers as part of seller verification rather than after the first payout.
Also available
Consent-based Aadhaar identity confirmation with masked handling throughout and a full audit trail on every call.
Explore the APIValidate a PAN and confirm the holder name matches your record, before it propagates into billing and tax.
Explore the APIKeys the same day, realistic payloads including failure cases, and engineers on the other end of the channel.