Skip to main content
POST
/
kyc
/
pan
/
verify
Verify PAN Details
curl --request POST \
  --url https://api.sandbox.co.in/kyc/pan/verify \
  --header 'Authorization: <authorization>' \
  --header 'Content-Type: application/json' \
  --header 'x-api-key: <x-api-key>' \
  --data '{
  "@entity": "<string>",
  "pan": "<string>",
  "name_as_per_pan": "<string>",
  "date_of_birth": "<string>",
  "consent": "Y",
  "reason": "<string>"
}'
{
  "code": 200,
  "timestamp": 1763725205000,
  "transaction_id": "196e0885-e47c-4681-88ec-d62aa289900f",
  "data": {
    "@entity": "in.co.sandbox.kyc.pan_verification.response",
    "pan": "XXXPX1234A",
    "category": "individual",
    "status": "valid",
    "remarks": null,
    "name_as_per_pan_match": true,
    "date_of_birth_match": true,
    "aadhaar_seeding_status": "y"
  }
}

Headers

ā€‹
Authorization
string
required

JWT access token

ā€‹
x-api-key
string
required

API key for identification

ā€‹
x-accept-cache
boolean

Pass true to accept the cached response. If the header is not passed, or if false is sent as the value, the request will hit the origin.

Body

application/json
ā€‹
@entity
string
required
Allowed value: "in.co.sandbox.kyc.pan_verification.request"
ā€‹
pan
string
required

PAN to be verified.

ā€‹
name_as_per_pan
string
required

Name of the holder on their PAN card

ā€‹
date_of_birth
string
required

Date of Birth/Incorporation. Format in DD/MM/YYYY

ā€‹
consent
enum<string>
required

Consent of the end-user to get their information for verification purposes.

Available options:
Y,
y
ā€‹
reason
string
required

Indicate the purpose for verification.

Response

200 - OK

ā€‹
code
integer
ā€‹
timestamp
integer
ā€‹
transaction_id
string
ā€‹
data
object