What is PAN verification?
PAN verification confirms that a Permanent Account Number is real, is active, and belongs to the person or entity presenting it. Almost every Indian financial workflow turns on a PAN. It ties a customer to their tax record, and deduction, reporting and payout processes key to it.
The cost of getting it wrong lands later, when a deduction is filed against an identifier that does not resolve or a payout is rejected.
How a PAN verification API works
Format validation catches a typo. It cannot catch a PAN that belongs to someone else, one that is no longer active, or one whose holder name does not match your customer.
An API makes the real check part of the form. Your application sends the PAN and the details you hold, and gets a structured response back. You can then accept the identifier, show the customer the mismatch, or send the case for review.
What you send to check a PAN
The request starts from the PAN itself. Where your flow needs a match outcome, send the customer-supplied name and date of birth with it. The response reports the outcome.
What comes back varies by tier, by the data source and by the record. A thin record returns less. Read the response as signals to route on.
Basic, Advanced and Comprehensive PAN coverage
| Capability | Basic | Advanced | Comprehensive |
|---|---|---|---|
| Confirms the PAN exists and reports its state | Included | Included | Included |
| Returns the holder name on the record | Included | Included | Included |
| Match outcome for a supplied name and date of birth | Included | Included | Included |
| Holder category, and date of birth or gender where held | Not included | Included | Included |
| Whether the PAN is linked to an Aadhaar record | Not included | Included | Included |
| Registered address and contact details, where available | Not included | Not included | Included |
Your service contract decides what each tier covers. Every field is still subject to what the record holds.
Who uses PAN verification
Lenders and NBFCs confirm the applicant's PAN before a credit assessment starts. The bureau pull, the loan record and the deduction trail all key to it. A PAN that does not resolve at application becomes a reconciliation problem at servicing.
Fintech and payment service providers verify a merchant or user PAN before they raise transaction limits or enable payouts. The platform carries the reporting obligation for the money it moves.
Insurers confirm the proposer's PAN on a proposal, where it supports premium processing and the tax-linked reporting that follows for years.
Marketplaces, staffing and gig platforms verify a seller, worker or partner PAN before the first payout cycle. A deduction filed against an unverified identifier is a correction the platform chases, not the individual. The check is commercial as well as compliance, since a higher deduction rate can apply where a valid PAN is not on record.
Real estate platforms capture a verified PAN before filing a reportable transaction. Logistics operators check owner-operators before a payment run, where an unresolved identifier stalls the payment.
Where the PAN check sits in your flow
Verify at capture rather than in a nightly batch. The customer who can fix a mismatch is the one still looking at the form. The same mismatch found overnight becomes a support ticket and a stalled application.
Separate a mismatch from a PAN that does not exist. They are different customer conversations, and one error message for both handles each badly. Treat the linkage signal on the higher tiers as a routing input, since a customer can resolve it and come back.
Re-check on events that matter, such as reactivating a dormant account or a change of registered details. Store each outcome with its timestamp. That record shows later what was known and when.
Consent rules for a PAN check
A PAN is sensitive personal information tied to a person's tax identity. Run a check only where the customer has given informed consent for that specific purpose, and where your business has a lawful, authorized reason to hold the result.
Keep consent specific and revocable. Retain the result only as long as the process needs it, and restrict access to the people whose work requires it. A result you obtained for onboarding is not a dataset for enrichment, profiling or marketing.
You stay responsible for how the result is used and for the obligations of your own sector.