PAN Verification
API

A complete guide to the PAN verification API

A PAN verification API confirms that a Permanent Account Number is valid and returns the details recorded against it, so you can check a customer's PAN against the source rather than trusting a typed number or a photo of a card. Because PAN is required for so many financial products in India, the PAN verification API is often the very first check in an onboarding journey. This guide explains what a PAN is, what a PAN verification API can confirm, and how to design a reliable flow around it.

Understanding the PAN

A PAN is a 10-character alphanumeric identifier issued by the Income Tax Department. It follows a fixed pattern: five letters, four digits and a final letter. The fourth character shows the type of holder, for example P for an individual, C for a company, H for a Hindu Undivided Family, F for a firm and T for a trust. For individuals, the fifth character is usually the first letter of the surname. These rules mean a lot of bad input can be caught in the form before any PAN verification API call is made.

What a PAN verification API confirms

• Validity: whether the PAN exists.
• Holder details: the name on record, which you can compare with what the customer entered.
• Status: whether the PAN is active and operative. PANs that were not linked with Aadhaar by the deadline set by the tax authorities were made inoperative, so status is worth checking, not just existence.
• Holder type: whether the PAN belongs to an individual or an entity, which matters if you only serve one or the other.

Why typed and photographed PANs are not enough

A customer can mistype their PAN, enter a relative's PAN, or upload an edited image of a card. None of those problems is visible from the input alone. A PAN verification API compares the input with the record, so a wrong or borrowed PAN shows up as a name mismatch or an invalid result before it reaches your systems.

Designing the name match

The most important part of a PAN verification API result is usually the name. Compare it with the name the customer gave you using a match score rather than an exact comparison, because PAN names are often recorded in full while customers type shortened versions. Set clear bands: a strong match proceeds automatically, a partial match goes to a quick review, and a clear mismatch prompts the customer to re-check their details.

Where the PAN verification API sits in a flow

1. Validate the PAN format in the form as the customer types.
2. Call the PAN verification API when the form is submitted.
3. Compare the returned name and check the status.
4. Only then run heavier checks such as Aadhaar-based verification, bank account validation or video KYC.

Running the PAN verification API first means every later check is spent on an applicant whose basic identity is already confirmed.

Use cases for the PAN verification API

• Lending: confirming the borrower's identity and using PAN as the key for credit checks.
• Investments and broking: PAN is required to open trading and investment accounts.
• Insurance: confirming the policyholder for higher-value policies.
• Payroll and HR: confirming employee PANs for tax deduction.
• Business onboarding: confirming the PAN of a company, firm or proprietor, often alongside a GST check.

Choosing the right level of PAN check

Not every flow needs the same depth. A basic PAN verification API check confirms validity and the name. Richer PAN checks can return more detail, such as demographic data for matching or the PAN's link status. Pick the level that matches your decision: collecting more data than you need adds cost and data-protection obligations without improving the outcome.

Handling failures well

Most PAN verification API failures are fixable by the customer. Show a precise message: ask them to re-check the number if it is invalid, explain that the PAN must be in their own name if the name does not match, and tell them how to resolve an inoperative status if that applies. A clear message recovers far more applicants than a generic error.

Data protection

A PAN is personal data. Collect it only for a defined purpose, show it masked where possible, restrict access to the full number, and keep it only as long as your rules require. Log each PAN verification API call with its purpose so you can show why the data was processed.

Re-checking over time

PAN status can change, for example when a PAN becomes inoperative or is later made operative again. For long relationships where PAN status matters, such as investment accounts, re-run the PAN verification API periodically or before key transactions rather than relying only on the check made at onboarding.

Official information

Rules about PAN, including its structure and linking requirements, are published by the Income Tax Department on the Income Tax e-filing portal. A PAN verification API reflects that official record, which is why it is a stronger signal than any document the customer can upload.