What is Udyam registration?
Udyam is the registration under which a business is recorded as a micro, small or medium enterprise in India. It is held against the enterprise, not a single unit, and it carries a classification drawn from the investment and turnover criteria that apply.
Udyam verification checks a submitted registration number and reviews the enterprise information available against it. A claim of MSME status on an onboarding form then becomes something you have actually checked.
Why MSME classification changes what a buyer must do
MSME status is one of the few counterparty attributes that changes a buyer's own obligations.
Payments to micro and small suppliers carry a statutory settlement window. Where a payment runs past it, the tax treatment of the expense can be affected. Companies also report dues outstanding to those suppliers on a periodic return, which only works if the supplier master records status correctly.
Public procurement policy sets aside a share of buying for micro and small enterprises. Procurement reporting rests on the same field. Lenders apply the classification when they decide whether a borrower fits a scheme-linked or priority facility, and receivables discounting rests on suppliers whose status is established.
How the Udyam Verification API works
Collecting certificates works for a handful of suppliers. It does not work across a base you onboard every week, and a certificate on file does not show whether the registration has changed since.
An API check moves the step into the system where you create or pay the supplier. A vendor master can confirm the registration at onboarding. A payment run can confirm it before terms are applied, and a credit workflow can confirm it during assessment.
Basic and Advanced: what each depth returns
Both depths are described here, and we agree which one applies in the service contract.
| Capability | Basic | Advanced |
|---|---|---|
| Confirm the registration is recognized | Included | Included |
| Enterprise name and organization type | Included | Included |
| Micro, small or medium classification | Included | Included |
| Registration date and status context | Where recorded | Where recorded |
| Major activity and activity classification | Not covered | Where recorded |
| Address and unit-level context | Not covered | Where recorded |
| Other identifiers linked to the registration | Not covered | Where recorded |
| Typical fit | Status check at onboarding or before a payment run | Supplier due diligence and vendor master enrichment |
Whether any attribute is available at either depth depends on the data source and the individual registration.
What you send to verify a Udyam number
You send the Udyam registration number as the enterprise provided it. The API returns the enterprise information available for it in a structured response, which you can compare against the details the supplier declared.
Where you hold a PAN but not a registration number, a separate PAN-based lookup can find the registration first.
Who verifies Udyam registrations
- Procurement and manufacturing: confirm supplier status before payment terms are agreed and an order is raised.
- Lending and NBFC: confirm micro or small classification before a file is assessed under an MSME product.
- Fintech and payment service providers: classify a merchant at onboarding, and apply the right documentation set and limits from there.
- Marketplaces: record verified seller status in the vendor master at signup.
- Logistics and fleet: check small transport operators, garages and last-mile partners before they join a network.
- Real estate: verify contractors and material suppliers before a site account is opened.
Where the Udyam check sits in supplier and payment runs
Connect the check to a supplier onboarding form, a vendor master, a procurement system, a payables queue or a lending platform.
An enterprise can be reclassified as it grows. Most teams pair a check at onboarding with a periodic re-check across active suppliers. Storing the response with its timestamp shows which status applied when a payment term was set.
Responsible use of Udyam data
Udyam data describes an enterprise. Use it only for the authorized business purpose you collected it for: a supplier, payment, procurement or credit decision.
Where the enterprise is a proprietorship, the registration is closely tied to an individual. Capture consent where you collect the number, and treat the record with the care your organization applies to personal data.
Keep the retrieved information inside the systems that need it, apply your existing retention and access rules, and record what came back and when. The depth available depends on the service contract you select. A response is not a substitute for your own credit, tax or legal assessment.