---
title: "DIN to PAN Verification"
method: POST
path: "/verify/din_to_pan"
tags: ["Know Your Business"]
---

# DIN to PAN Verification

`POST /verify/din_to_pan`

Fetches PAN details linked to a DIN. This API is billable even when the DIN does not exist or is not linked to any PAN.

## Request body

- DINtoPANRequest
  - `din` string, required — Director Identification Number (DIN)
  - `consent` string, required — User consent flag (must be 'Y')
  - `consent_text` string, required
  - `user_id` string — Optional user reference identifier

## Response `200`

Successful response (including billable non-data cases)

- DINtoPANResponse
  - `status` string
  - `result` union
    - DINtoPANResult
      - `name` string
      - `pan` string
    - 'Din does not exist' | 'DIN is not linked to any PAN' — Billable responses where PAN data is not available
  - `chargeble` string
  - `user_consent` string

## Other responses

- `400` — Bad request — missing DIN or consent details.
- `401` — Unauthorized — authkey missing or invalid.
- `403` — Forbidden — insufficient privileges.
- `429` — Too many requests — request limit exceeded.
- `500` — Internal server error.
- `502` — Bad gateway — vendor error or source down.
- `504` — Gateway timeout — vendor did not respond.

---

[API](https://skmtc.dev/idto/apis/verification-api.md) · [All operations](https://skmtc.dev/idto/apis/verification-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/idto/verification-api/revisions/e3d57dab8db4/schema)