Skip to content
FinHubBy HabileLabs

Company Verification

Map a Director Identification Number to the director's registered PAN in a single verified call.

api · POST /v1/kyc/verify
POST /v1/kyc/verify
Authorization: Bearer sk_live_••••
{ "pan": "XXXXX1234F", "consent_artifact": "ca_9f2c…" }

Overview

What the DIN to PAN API does

The DIN to PAN API resolves a director's PAN directly from their DIN, drawing on MCA registry data. It gives risk and compliance teams a reliable way to reconcile director identity across filings, loan applications, and KYC records before onboarding or disbursal.

Inputs

  • Din
  • Consent artefact id

Returns

  • Pan
  • Director name
  • Din status
  • Date of appointment
  • Verification timestamp

POST /v1/kyb/din-to-pan

How it works

Three steps to a verified result

01

Submit the director's

Submit the director's DIN with a valid consent artefact.

02

FinHub matches the

FinHub matches the DIN against MCA registry filings to resolve the linked PAN.

03

A verified, masked

A verified, masked PAN and director status are returned with a tamper-evident audit entry.

Use cases

Where teams use DIN to PAN

  • Reconciling director identity across loan and KYC applications
  • Cross-checking DIN-PAN consistency during KYB onboarding
  • Fraud screening for mismatched or fabricated director credentials
  • Supporting board-resolution verification for corporate accounts

FAQ

DIN to PAN API — FAQs

Common questions about FinHub's DIN to PAN API.

FinHub returns a masked PAN by default to limit exposure of sensitive data, in line with DPDP data-minimisation principles.

More verification APIs

Explore related APIs

Ready to add DIN to PAN to your flow?

Book a demo and see the API return a verified result on your own test data in minutes.