Skip to content

PAN-to-Udyam Lookup API

New

Start from a PAN and find the Udyam registration recorded against it. A vendor record then carries checked MSME status even when the supplier cannot produce a certificate.

Overview

A PAN-to-Udyam lookup starts from a Permanent Account Number and returns the Udyam registration recorded against it, where one exists. Many teams call the same check PAN to MSME. It answers a question a supplier master usually cannot: is this counterparty a registered micro, small or medium enterprise? Most systems already hold a PAN for every counterparty. Chasing each supplier for a certificate does not scale, and a certificate on file does not show whether the registration has been updated since. Starting from an identifier you already store turns a collection exercise into a step your system runs. Which attributes appear depends on the data source and on the record itself, and access follows the service contract you agree with us. The PAN identifies a person where the holder is a proprietor. Take consent and state the business purpose before you run the lookup.

Category
KYB Services
Coverage
Udyam registrations recorded against a PAN in India
Input
A PAN
Output
The Udyam registration recorded against the PAN, with the enterprise details available
Typical users
Procurement, vendor onboarding, accounts payable, lending and merchant operations teams
Coverage note
Udyam registrations recorded against a PAN in India. Available fields differ from one record and one data source to another.

The overview and the sections after the reference are the FinSour API catalog’s own record for this service, rendered unaltered.

Reference in progress

The request and response reference for this endpoint is not published yet.

Everything below this block is the live catalog record for this service, and it is accurate. The platform’s published API contract does not include this service yet, so there is no request or response detail to document. Rather than fill these sections with a plausible example, the page lists what is missing:

Endpoint URL and method
The host, path and HTTP verb for this service.
Authentication
How a request identifies itself, and where credentials come from.
Request parameters
Field names, types, which are required, and validation rules.
Response schema
The success body, field by field, with a real example.
Error codes
What each failure means and which are worth retrying.
Rate limits
Request ceilings, and what happens at the ceiling.

No sample payload, URL, response body, error code, rate limit or latency figure appears anywhere on this site unless it has been supplied and attributed. Each item in this list is removed only when its own detail arrives; none of them is held back to wait for the rest, and none is ever placed beside a guess in the meantime.

Use cases

  • Procurement: backfill MSME status across an existing supplier master from PAN
  • Lending and NBFC: establish MSME status from PAN during business loan assessment
  • Fintech and payments: classify merchants from identifiers already on file
  • Marketplaces: identify MSME sellers at signup without a certificate upload
  • Logistics and fleet: classify small transport partners already in the network
  • Staffing and gig platforms: classify service vendors before payout terms are set

What this service does

  • Starts from an identifier you already hold

    Onboarding forms and finance systems keep a PAN for every counterparty. The lookup uses that number to find the Udyam registration recorded against the enterprise. You do not have to ask the supplier for a certificate.

  • What comes back against the PAN

    The Udyam registration recorded against the number, with the enterprise name, classification and organization type, and activity or address-related attributes. The attributes present differ from one data source and one record to the next.

  • Fill the gaps in an older supplier base

    The same lookup fills a status field at onboarding and sweeps a base you onboarded before the field existed. Payment terms and reporting then rest on a checked classification.

  • PAN to Udyam, PAN to MSME

    Both names describe this lookup. Udyam is the registration, and MSME is the status recorded on it. A supplier master that labels the field one way and a procurement policy that labels it the other are reading the same registration.

How a check runs

  1. Tell us where status is missing

    Choose Get API and tell us where the lookup fits in your supplier or merchant workflow. We agree the service contract from there.

  2. Connect the lookup to your records

    Add the lookup to your onboarding form, vendor master, procurement system, payables queue or review dashboard, following the documentation we provide at onboarding.

  3. Send the PAN you already hold

    Your application sends the PAN from the supplier or merchant record, once you have captured consent at the point it was collected.

  4. Read the registration returned

    The Udyam registration recorded against the number comes back with the enterprise details available, in a structured response.

  5. Write the status to your record

    Store the classification against the supplier with its timestamp and consent reference. Payment terms, reporting and credit workflows then read it from there.

Questions

Is PAN to Udyam the same as PAN to MSME?
Yes. Both names describe the same lookup. Udyam is the registration that records a business as a micro, small or medium enterprise. A PAN to MSME check looks up the Udyam registration recorded against the PAN.
What do I send to look up a Udyam registration from a PAN?
The PAN as the counterparty provided it. No registration number, certificate or document upload is needed to start the lookup.
Should I use this lookup or the Udyam Verification API?
Use this lookup when you hold only a PAN, because it discovers the registration for you. Use Udyam verification when a supplier has already given you a registration number and you want the enterprise profile in more depth. Teams that hold only a PAN usually run the lookup first, then verify the registration it returns.
What does an empty result mean for a supplier?
The lookup found no registration against the number in the information available. Not every business is registered, and an enterprise above the micro, small and medium criteria will not hold a registration at all. An empty result is a normal outcome. On its own it is not a negative finding about a supplier.
What consent do I need before running this lookup?
Explicit consent, where the PAN belongs to an individual. That includes the proprietors behind many micro enterprises. Collect the consent at the point you capture the PAN, and run the lookup only for the stated purpose. Handle the result under your existing retention and access rules.
How do I start a PAN-to-Udyam integration?
Use Get API to tell us where MSME status has to be filled in and the volumes involved. Say whether you classify suppliers at onboarding or backfill a base that was onboarded before anyone asked. We settle access, the attributes available to you and the integration documentation in the service contract.

Catalog entry last updated .