PAN Validation v2

Validates a PAN against the source-of-record and returns canonical holder details (pan_name, pan_number, pan_status, category).

Response contract: A successful verification returns HTTP 200 with status: "success", error_code: null, and a populated data object. A definitive no-record / invalid result ALSO returns HTTP 200 with status: "success", but carries a non-null error_code and data: null — every 2xx response is status: "success", so do NOT distinguish a full-success verdict from a no-record / invalid one by status; branch on error_code (null = full success, a non-null IDTO_2xx = no record / invalid). Only a raised error returns status: "error". Every response carries billed (whether the call was charged). All codes, messages and HTTP statuses are identical regardless of the underlying vendor. Authenticate with your X-Client-ID and X-API-KEY headers.

Codes: IDTO_202 (2xx, no such PAN record), IDTO_001 (invalid PAN format / missing field, 400), IDTO_005 (user consent required, 400), IDTO_009 (insufficient credits, 402), IDTO_006 (rate limited, 429), IDTO_007 (config error, 500), IDTO_008 (service busy, 503).

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Body Params
string
required
^[A-Z]{5}[0-9]{4}[A-Z]{1}$

PAN to verify. Must follow the 10-character PAN format (five letters, four digits, one letter). Example: ABCDE1234F

boolean
required

User consent flag required by the v2 PAN flow.

Responses

401

Missing or invalid authentication credentials (X-Client-ID / X-API-KEY).

Language
Credentials
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json