---
title: "PAN to CIN Verification"
method: POST
path: "/verify/pan_to_cin"
tags: ["PAN to CIN"]
---

# PAN to CIN Verification

`POST /verify/pan_to_cin`

Fetches CIN(s) mapped to a PAN number. Requires valid customer consent. Billable even when PAN is invalid, inactive, or no records are found.

## Request body

- PANtoCINRequest
  - `pan_number` string, required — PAN number of the business owner
  - `user_id` string — Optional user reference identifier

## Response `200`

Successful response (including billable non-data cases)

- PANtoCINResponse
  - `status` string
  - `result` union
    - PANtoCINResult
      - `cin` string[]
      - `cin_details` object[]
        - `cin` string
        - `entity_name` string
    - 'Invalid PAN' | 'Inactive PAN' | 'No Record Found' — Billable responses where no CIN data is available
  - `chargeble` string
  - `user_consent` string

## Other responses

- `400` — Bad request — missing PAN or consent details.
- `401` — Unauthorized — authkey missing or invalid.
- `403` — Forbidden — insufficient privileges or IP not whitelisted.
- `429` — Too many requests — rate 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)