Vendor onboarding
Validate tax identifiers before the first purchase order is raised.
A mistyped PAN is cheap to catch at entry and expensive to find in a filing.
# Request "input": "PAN number" # Response fields { "pan_status": …, "holder_name": …, "name_match_score": …, "holder_type": …, "last_updated": … }
Overview
PAN numbers reach you by typing, by OCR, and by copy-paste from a spreadsheet. Each route has a failure mode, and none of them announce it. The number looks structurally fine and goes straight into billing.
Validate at the point of entry: confirm the PAN exists, is active, and belongs to the name you were given. One call, and the identifier that touches every invoice is one you can trust.
Response
Every field is returned structured and timestamped, ready to store against the record it belongs to. Nothing requires parsing a photograph or interpreting free text.
| Field | Description |
|---|---|
pan_status | Active, inactive or not found |
holder_name | Registered name on the PAN |
name_match_score | Match confidence against your submitted name |
holder_type | Individual, company, HUF, trust and others |
last_updated | When the record last changed |
Use cases
Validate tax identifiers before the first purchase order is raised.
Catch typos before they reach a tax filing.
Confirm business identity as part of seller verification.
Run an existing ledger through validation and isolate the records that need attention.
Also available
Consent-based Aadhaar identity confirmation with masked handling throughout and a full audit trail on every call.
Explore the APIConfirm whether a PAN is linked to Aadhaar before a transaction depends on it — and fix the problem early if not.
Explore the APIKeys the same day, realistic payloads including failure cases, and engineers on the other end of the channel.