PAN verification is the cheapest high-signal check in an Indian onboarding flow. It confirms that a PAN exists and returns the name it belongs to, which lets you catch typos, fabricated identities and name mismatches before a customer reaches manual review.
What PAN verification proves
| Question | Does PAN answer it? |
|---|---|
| Does this PAN exist? | Yes |
| Whose name is on it? | Yes |
| Is this person the one submitting it? | No — pair with a document or liveness check |
| Is the person creditworthy? | No |
Recommended onboarding sequence
- Validate the PAN format client-side (five letters, four digits, one letter) to avoid wasted calls.
- Run the PAN module and fuzzy-match the returned name against the submitted name.
- For payout accounts, run the UPI module on the VPA and confirm the beneficiary name matches.
- Escalate mismatches to manual review instead of hard-failing — legal name variations are common.
Handling name mismatches
Initials, expanded middle names, transliteration differences and married surnames all produce legitimate mismatches. A token-based similarity score with a review queue rejects far fewer genuine customers than an exact string comparison.
FAQ
Is a PAN check enough for KYC?
No. It verifies the identifier and its name. Regulated KYC also requires binding that identity to the actual person, typically with a document or liveness step.
How fast is the PAN module?
It runs in the same request cycle as any other lookup and returns a JSON envelope, so it fits inline in a signup flow.
What happens if the upstream provider fails?
Credits held for the lookup are refunded automatically, so a provider outage does not cost you anything.