API Reseller
PAN API
PAN validation returning the registered name and status directly from the income tax database, which is what makes it a verification rather than a format check.
What you get
- Name and status returned from the issuing database
- Format and checksum validated before the lookup
- Aadhaar-PAN linkage status where available
- Bulk verification endpoint
- Sub-second typical response
The contract
- Auth
- Issued credentials per key pair, over TLS. Signed requests where the rail requires it.
- Source
- The income tax database. This is a verification, not a format check.
- Returns
- Registered name and status, plus Aadhaar linkage where available.
- Pre-check
- Format and checksum validated before the lookup is billed.
- Bulk
- A separate endpoint accepts batches.
- Environments
- Sandbox mirrors production semantics, including failures.
FAQ
About pan api
How is this different from validating the PAN format?
A format check confirms the string could be a PAN. This confirms the PAN exists and returns the registered name from the income tax database, which is what lets you match it against the name your customer gave you. Format is checked first only so an obviously invalid string is not billed as a lookup.
Can I verify a batch overnight?
Yes, through the bulk endpoint rather than by looping the single lookup. Looping works but is slower and harder to reconcile than one batch with one result set.