Mobile to MSME API
New
Resolve the Udyam registration linked to a consented mobile number, then use the MSME details you get back to classify, onboard or pay a supplier.
Overview
Mobile to MSME takes a mobile number and returns the Udyam registration recorded against it, where the number holder has consented to the check. The enterprise details available come back in a structured response. Lenders, marketplaces and procurement teams have to settle MSME status before a file moves on. A certificate the supplier sends you is not the same as a check. An API check runs inside the journey that already collects a verified mobile number. The fields you get back can differ from one record to the next, depending on the underlying data source.
- Category
- KYB Services
- Coverage
- Udyam-registered enterprises in India
- Input
- A mobile number, sent with the consent of the number holder
- Output
- The Udyam registration and enterprise details available, where a record exists for that number
- Typical users
- Lending, fintech, marketplace, procurement and insurance teams
- Coverage note
- Udyam-registered enterprises in India. Whether a record exists, and which attributes you see, varies by data source and by the service contract you select
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
- Lending and NBFC: MSME status before a business-loan decision
- Fintech and PSP: merchant classification at onboarding
- Marketplaces: seller MSME status written to the vendor master
- Procurement and finance: supplier classification for payment terms
- Insurance: small-business proposer classification at underwriting
- Logistics and fleet: transport partner checks before onboarding
What this service does
Based on the current registration record
A certificate a supplier emails you shows what was true on the day it was issued. This lookup resolves the registration from the information available at the time of the check. Your onboarding decision then rests on the current record.
Starts from the number onboarding already has
Most journeys capture a verified mobile number before anything else. That makes the number a practical starting point when an enterprise cannot recall its Udyam number, or when a field team has captured a contact and nothing more.
Consent captured in the same step
The lookup runs against a number whose holder has agreed to the check. You can collect that consent in the step that collects the number, and store the reference alongside the result.
A status your systems can read
You can write the structured result to the supplier or merchant record. Decisions about product, documentation and payment terms then read the same value instead of a note in a spreadsheet.
How a check runs
Collect the number and the consent
Capture the mobile number and the explicit consent of its holder. State the purpose of the check in plain language when you ask.
Send the number for lookup
Your application submits the consented mobile number through the API, inside the onboarding or credit workflow.
Read the Udyam details returned
The response carries the Udyam registration and the enterprise attributes available for that number, in a structured format.
Set MSME status on the record
Use the result to set MSME status on the supplier, merchant or applicant record. The rest of the workflow reads it from there.
File the outcome for review
Store the result with its timestamp and consent reference. That record shows a later reviewer why a classification was applied.
Questions
- What do I send to run a Mobile to MSME check?
- A mobile number, submitted with the consent of the person it belongs to. Nothing else is needed to start the lookup. Your own workflow may collect more for its own purposes.
- What Udyam details come back from a mobile number?
- Where a registration is recorded against the number, the response can carry the Udyam number, the enterprise name, the enterprise type, and activity and address-related attributes. The exact fields you get depend on the underlying data source and on the individual record.
- Does the mobile number holder have to consent?
- Yes. A mobile number is personal data, and resolving it to a business identity needs a lawful basis. Collect explicit consent, state the purpose, and use the result only for that purpose.
- What does a no-match on a mobile number mean?
- It means no Udyam registration could be matched to the number from the information available. The enterprise may be registered under a different contact number, or it may not be registered at all. A no-match is a normal outcome. Treat it as a prompt for a further step in your process, not as a rejection.
- Why do the details differ from one enterprise to another?
- Enterprises maintain their own registrations and update them at different times. What is available for one record may not be available for another. The attributes returned depend on the data source and on the service contract you select.
- How do I get access to the Mobile to MSME API?
- Choose Get API on this page. Our team will talk through your use case, the checks you need and the onboarding steps that follow.
Catalog entry last updated .