Aadhaar To PAN
Find the PAN linked to an Aadhaar number in one consent-based API call.
What is the Aadhaar To PAN?
The BILAPI Aadhaar to PAN API returns the PAN linked to a given Aadhaar number, so you can confirm the PAN–Aadhaar linkage and enrich identity during KYC — all consent-first and DPDP-aligned.
It is used by banks, NBFCs and fintechs to validate that a customer's Aadhaar and PAN belong together, satisfy linkage-compliance checks, and reduce the fields a customer must enter.
Pass an Aadhaar number with consent and receive the linked (masked) PAN as JSON. Billed only on a successful lookup.
What the Aadhaar To PAN returns
Every successful call returns a clean, predictable JSON envelope. The data object includes the fields below (exact fields vary by record availability).
| Field | Description |
|---|---|
aadhaar_ref | Tokenised reference for the Aadhaar that was checked. |
masked_pan | The linked PAN, returned masked for privacy. |
name_match | Whether the names on the Aadhaar and PAN align, where available. |
link_status | Whether a linked PAN was found. |
Sample request & response
Call the endpoint with your API key in the X-Bilapi-Api-Key header. The same request shape works in the free sandbox and in production.
POST https://api.bilapi.com/v1/aadhaar-to-pan
X-Bilapi-Api-Key: <your_api_key>
Content-Type: application/json
{
"aadhaar_number": "XXXXXXXX1234",
"consent": "Y"
}{
"status_code": 200,
"success": true,
"message": "Linked PAN found",
"data": {
"masked_pan": "ABCXXXXX4F",
"name_match": true,
"link_status": "LINKED"
}
}Key features
Real-time results
Sub-300ms median response so Aadhaar checks never slow your onboarding funnel.
Predictable JSON
The same clean response envelope as every BILAPI endpoint — parse once, reuse everywhere.
Only pay for hits
Invalid inputs and failed lookups are never charged to your wallet.
Secure by design
TLS 1.3 in transit, PII tokenisation at rest and a full audit log on every request.
One key, every API
Sandbox to production on a single key — no per-vendor contracts or integrations.
Built to scale
99.9% uptime target with bulk and webhook-friendly workflows for high volume.
Where it's used
Customer onboarding
Auto-fill and validate identity during signup to cut drop-off and manual review.
Lending & underwriting
Add a verified data point to credit decisions and reduce first-party fraud.
Fraud & risk
Flag mismatches and synthetic identities before they enter your system.
Compliance & audit
Keep a tamper-evident trail of every verification for KYC/AML reviews.
How it works
Create a free account
Sign up on the BILAPI console and get a live API key instantly.
Send a request
POST the required Aadhaar fields to the endpoint with your API key in the header.
Get structured JSON
Receive a clean, predictable JSON response in milliseconds.
Plug into your flow
Drop the result straight into onboarding, underwriting or risk decisioning.
Frequently asked questions
What does the Aadhaar to PAN API return?
It returns the PAN linked to an Aadhaar number (masked for privacy) and the link status, so you can confirm the PAN–Aadhaar linkage during KYC.
Is consent required?
Yes. This is a consent-first, DPDP-aligned API — you must capture and pass customer consent, and the PAN is returned masked.
Why check the PAN-Aadhaar link?
Banks, NBFCs and fintechs use it to confirm a customer's Aadhaar and PAN belong together and to satisfy linkage-compliance requirements.
What is the input?
An Aadhaar number along with captured customer consent.
Do failed lookups cost money?
No — you are billed only for successful responses from your wallet balance.
Related Aadhaar Verification APIs
Start verifying with BILAPI
One key, a free sandbox and a predictable JSON envelope across every endpoint.