"OTP not coming" is the single most common reason people abandon the Udyam portal. It is almost never the portal's fault. Here is what is actually happening when the OTP doesn't arrive — and exactly how to fix each cause.
Reema Chakraborty runs a catering kitchen in Bhilai. In September 2024 she tried to get her Udyam done and spent two weeks in the loop no one warns you about. Enter Aadhaar. Press Send OTP. Wait. Nothing. Try again ten minutes later. Wait. Nothing. After seven attempts spread across three days, she assumed the portal was broken. It wasn't. Her Aadhaar was linked to her husband's old Vodafone number, which he had ported to Jio eighteen months earlier without updating UIDAI. The OTPs were being dispatched correctly — to a disconnected SIM.
If you're reading this, you're probably in Reema's loop. The good news is that every single "OTP not coming" situation falls into one of nine categories below. Each has a specific fix. You don't need to refresh the portal fifty times. You need to know which of the nine you're dealing with.
The Udyam portal itself doesn't send OTPs. It asks UIDAI (the central government agency that issues Aadhaar and runs all Aadhaar verification) to dispatch one. UIDAI then sends the SMS to whatever mobile number is on file against your 12-digit Aadhaar.
There are three layers between your Aadhaar entry and that SMS hitting your phone. A break at any of them shows up in the browser as the same thing — no OTP — which is why generic troubleshooting doesn't work.
Layer 1 — Portal to UIDAI: the Udyam portal sends your Aadhaar to UIDAI's verification service (the same e-KYC system used by banks and mobile operators). This returns "OTP sent" (success), "Aadhaar locked" (explicit error), or times out (silent failure).
Layer 2 — UIDAI to Telecom: UIDAI then dispatches the OTP SMS through a bulk-SMS provider to the telecom operator of your linked mobile. Jio, Airtel, Vi, and BSNL each have slightly different delivery windows.
Layer 3 — Telecom to Handset: your carrier delivers the SMS to the specific SIM. Blocked by DND-2 (a strict Do-Not-Disturb mode that blocks even bank OTPs), blocked by international roaming being off, or simply blocked by the SIM being disconnected.
Your job is to identify which of these three layers broke. The sections below walk through each specific cause.
This is by far the most common. You remember the mobile you enrolled Aadhaar with in 2015 or 2017. You don't remember if you ever updated it after porting to a new SIM.
UIDAI still has the original number on file. That SIM went dead years ago. UIDAI is still sending OTPs to it, and you're never going to see them.
What it looks like on screen: the portal shows "OTP sent to mobile ending in XXXX". The last four digits often don't match any SIM you currently hold. That's the tell.
Why it happens: UIDAI never automatically updates the linked mobile when you change your SIM. The only way it changes is if you explicitly update it — either at an Aadhaar enrolment centre or online at myaadhaar.uidai.gov.in. Most Aadhaars issued before 2018 still have the original number, even if that SIM hasn't existed for years.
The fix: first confirm which number is actually on file (see how to check below).
If it's a number you've lost, update it. Two routes:
• Online — ₹50: go to myaadhaar.uidai.gov.in. Available since late 2024 if your biometrics match. Processes in 5–10 days.
• Offline — ₹50: visit any Aadhaar enrolment centre with a filled update form, one identity proof, and cash. Biometric match at the centre confirms it's really you. 7–10 days typical.
Only after the update clears will the Udyam OTP arrive on your current phone.
Case we saw: Reema's situation above. Husband's Vodafone number from 2013 was still on her Aadhaar. We walked her through online update on myaadhaar.uidai.gov.in — biometric match worked first try — updated in 6 days. Udyam cleared on the 7th day, first attempt.
On normal days UIDAI dispatches the OTP within 15–30 seconds. On days when the Aadhaar infrastructure is strained — budget announcements, PM-Kisan enrolment drives, EPF-related surges — it can crawl to 2–3 minutes. But the Udyam portal's OTP input field timeout is shorter than that on older browsers, so users frequently think the OTP failed when it actually arrived late to a timed-out form.
What it looks like on screen: OTP arrives eventually, but when you paste it in, the portal says "Invalid OTP" or "Session expired". You're not entering a wrong OTP — you're entering a valid OTP into a dead session.
Why it happens: OTPs expire on UIDAI's side in 10 minutes. Udyam portal sessions expire in 15 minutes of inactivity. But the dynamic form validation can hiccup earlier. Chrome and Edge are generally more forgiving than Firefox or the older Safari builds still running on sub-iOS-16 iPhones.
The fix: if OTP hasn't arrived in 2 minutes, don't immediately request another. Wait 3 minutes total. If it arrives at 2:30 and the portal says "Invalid", close the tab, reopen udyamregistration.gov.in in a fresh Chrome window, and restart. Do not click "Resend OTP" more than twice in a 10-minute window — UIDAI rate-limits this.
DND (Do Not Disturb) on Indian telecom is a two-tier system.
• Category-1 blocks only promotional messages. Safe to enable — transactional OTPs still arrive.
• Category-2 blocks everything, including transactional OTPs, bank alerts, and government OTPs.
A small but non-trivial number of users enable category-2 by accident thinking they're just blocking telemarketing. Then they wonder why no OTP arrives from anywhere — not Udyam, not their bank, not Swiggy.
What it looks like on screen: portal shows "OTP sent". Your phone gets nothing. Bank OTPs also don't arrive on this SIM. That second symptom is the tell.
Why it happens: DND category-2 was introduced under the TRAP (Telecom Commercial Communications Customer Preference Regulations) rules. It can be enabled through the carrier's app, via SMS to 1909, or at a store. Some users enable it years ago and forget.
The fix: check current DND status by sending "STATUS" to 1909 from the affected SIM. If category-2 is active, send "START 0" to 1909 to disable all DND categories. Change takes 24 hours to propagate across carrier systems. After 24 hours, retry Udyam.
Carrier-specific quirks: Jio's MyJio app has DND under Services → Preferences. Airtel uses the Airtel Thanks app. Vi has it under Settings → DND. BSNL users have to physically visit a BSNL customer service centre in most circles — the online route isn't uniformly available.
The Udyam portal, like most government Indian portals, has predictable load spikes. 11 AM to 2 PM is the worst window — most businesses are trying to file Udyam during their lunch break, after morning shop setup, before afternoon deliveries. Late afternoon (4–6 PM) is second worst. The system doesn't crash, but OTP dispatch slows to 3–5 minutes and random form submissions fail halfway.
What it looks like on screen: portal loads slowly, the "Send OTP" button takes 10+ seconds to respond, OTP shows as "sent" but never arrives, and on refresh your Aadhaar entry has cleared. Tell-tale sign: repeat the exact same action at 10 PM and it works.
The fix: file early (7–10 AM) or late (9 PM–midnight IST). Weekends from 6 AM to 10 AM are usually the emptiest. Avoid 1st and 15th of each month — these are common deadlines for other filings and traffic spikes accordingly. The MSME ministry has never published load statistics, but if you have three failed attempts in peak hours, a single attempt at 10 PM almost always clears.
UIDAI allows Aadhaar holders to lock their biometric or even their Aadhaar number against third-party authentication. Some users enabled this during the 2018 Aadhaar leak scare and forgot. If your Aadhaar is locked, no OTP will dispatch regardless of everything else being correct.
What it looks like on screen: sometimes an explicit error "Aadhaar is locked for authentication". Often just the same "OTP sent" message followed by no delivery.
The fix: go to uidai.gov.in → My Aadhaar → Aadhaar Services → Lock/Unlock Biometrics (or Lock/Unlock UID). You'll need a mobile OTP to unlock — which is the same issue you're trying to resolve. Workaround: visit an Aadhaar enrolment centre with your Aadhaar card, request unlock via biometric verification at the centre, and walk out with an unlocked Aadhaar. No charge.
If your registered mobile is Indian but you're currently abroad, OTP delivery depends on whether your Indian SIM is active on international roaming. If roaming is off, the SMS never reaches you. If your registered mobile is a non-Indian number (which UIDAI has quietly started allowing for NRI Aadhaar holders since 2022), delivery depends on the foreign carrier's SMS interoperability.
What it looks like on screen: portal proceeds normally, "OTP sent" confirmation, nothing on your phone.
The fix: three options. First, ensure Indian SIM international roaming is enabled and an active data/voice pack is loaded. Second, ask a family member in India (with physical access to your SIM if you left it back home) to receive the OTP and read it out — the OTP itself is just a 6-digit number with no identity lock. Third, for genuine NRIs, update the linked mobile at myaadhaar.uidai.gov.in to your current foreign number if you hold a foreign SIM — UIDAI's international SMS aggregator supports roughly 45 countries.
Some form flows on the Udyam portal ask you to enter the mobile number where you want the OTP sent, and validate it against UIDAI before dispatching. If the number you enter doesn't match the one UIDAI has on file, you get an explicit error rather than a silent failure.
What it looks like on screen: "Mobile number not registered with Aadhaar" or "Entered mobile does not match Aadhaar record".
Why it happens: the portal is doing you a favour by failing fast. It's saying: you don't know what's linked to your Aadhaar, so you can't pre-fill the OTP field. This is common when owners delegate filing to accountants who don't know the client's actual Aadhaar-linked mobile.
The fix: don't guess. Verify the linked mobile at myaadhaar.uidai.gov.in → "Verify Mobile Number" (see how to check). Then enter that exact number at the portal.
Once or twice a quarter, the UIDAI authentication API goes down for maintenance or unplanned incidents. The Udyam portal doesn't have a fallback — the flow just fails. There's no notice banner.
What it looks like on screen: "Unable to send OTP, please try later" or a generic portal 500 error. When you check uidai.gov.in directly, it's also sluggish or throwing errors.
The fix: wait 2 hours and retry. If still failing, check @UIDAI on X (formerly Twitter) — they post maintenance advisories sporadically. The Champions Helpdesk at 011-23061574 can confirm if an incident is open on their side (they see UIDAI's status dashboard). Serious outages usually clear within 4–6 hours.
UIDAI rate-limits OTP generation to protect against abuse. The documented cap is 3 OTP requests per hour per Aadhaar, but in practice if you click "Resend OTP" five times in two minutes, further requests are silently dropped without any error. The portal still shows "OTP sent" — it's just lying.
What it looks like on screen: you've clicked resend 4, 5, 6 times. First one or two might have actually come (if you missed them). Rest are all suppressed.
The fix: stop clicking. Close the browser tab. Wait a full hour. Reopen udyamregistration.gov.in in a fresh window, enter Aadhaar once, click Send OTP once, wait 3 minutes. Accept whatever comes or doesn't. Don't re-request.
This is the step people skip, and it's the step that saves hours.
Step 1: go to myaadhaar.uidai.gov.in.
Step 2: click "Verify Email/Mobile Number" under the Aadhaar Services menu.
Step 3: enter your 12-digit Aadhaar number, choose "Mobile", enter the mobile you currently use, and submit the captcha.
Step 4: if the number you entered matches what UIDAI has on file, you see "Your mobile number is already verified with our records". If it doesn't match, you see "The mobile number entered is not verified with Aadhaar".
A "not verified" response doesn't tell you what IS linked — UIDAI never reveals that for privacy reasons. But it confirms the number you currently hold isn't it. From there the only path is to update, unless you can dig up an old SIM.
A separate tool — "Retrieve EID/Aadhaar" at myaadhaar.uidai.gov.in — tells you the masked last-4 digits of the linked mobile when you enter your Aadhaar and name. That can jog your memory about which SIM you actually used.
Once you know the linked mobile is wrong, you have two routes.
Online route (available since late 2024 for eligible residents): go to myaadhaar.uidai.gov.in, log in with existing linked mobile OTP (obviously not possible if you've lost access — in that case, use offline). Under "Update Aadhaar Online", select "Update Mobile Number". Enter the new mobile. UIDAI dispatches a confirmation OTP to the new number. You enter it to confirm. Biometric match through the MyAadhaar app may be required. Fee: ₹50 per update. Processing time: 5–10 working days, often faster.
Offline route (use this if you cannot access the old linked mobile): visit any Aadhaar enrolment/update centre (list at uidai.gov.in → Locate Enrolment Centre). Carry your Aadhaar card and one identity proof (PAN, voter ID, or driver's license). Fill Form 2 (Aadhaar Update Form). Specify "Mobile Number Update". Biometric scan at the centre confirms identity. Pay ₹50. You'll get an Update Request Number (URN). SMS notification goes to the new mobile once the update is processed, typically within 7 days.
You cannot update Aadhaar mobile via phone call, WhatsApp, email, or any third-party service. UIDAI rejects all such routes. A consultant (including us) can only guide you — the authentication itself has to happen on your end either online or at an enrolment centre.
OTP delivery isn't instant, and the portal doesn't show you where the delay is. Follow a strict retry discipline:
After clicking Send OTP: wait 3 full minutes. Most OTPs that are coming will arrive within 30 seconds, but peak-hour dispatch can take up to 2 minutes. If you resend at 30 seconds, you get nothing and now the counter is more suspicious.
After 3 minutes with no OTP: click Resend once. Wait another 3 minutes. If still nothing, the OTP isn't coming this session. Do not click resend a third time — you'll hit rate-limit territory.
Before next attempt: wait 60 minutes. The rate-limit window resets. Close the browser fully. Try again in a fresh session.
If three full attempts (each an hour apart) all fail with the same linked-mobile number: the problem is not transient. Move to the verification step at myaadhaar.uidai.gov.in and find out what's linked.
Most OTP issues are solved by the owner. But a few genuinely deserve escalation:
If: your Aadhaar-linked mobile is confirmed correct, DND is off, you're on a working Indian SIM in good network, you've waited 3 minutes and tried at 10 PM off-peak, and three attempts across two days all silently fail — there's a legitimate UIDAI-side issue with your Aadhaar record.
Call: Champions Helpdesk at 011-23061574, Monday–Friday 9:30 AM to 6 PM. Have your Aadhaar ready. They can't fix UIDAI issues but they can raise a ticket with the UIDAI liaison team at the MSME ministry. Resolution typically 7–10 days.
Email: champions@gov.in with subject line "Udyam OTP dispatch failure — ticket request" and include your Aadhaar last-4 only, a screenshot of the portal error, and three dated attempt timestamps.
Tell us the exact error you see and the last-4 of the mobile the portal says it sent OTP to. We'll tell you in one reply whether it's a linked-mobile issue, a DND issue, or something else — and the exact fix.
Get Expert Help →Sometimes the number on Aadhaar is a SIM from an ex-spouse, a deceased family member, or a job-issued mobile you no longer have access to. You can't receive an OTP on a number you don't physically control, and you can't update the linked mobile at myaadhaar.uidai.gov.in without first receiving an OTP on the current linked number. The only route is the offline enrolment centre route described above — biometric match at the centre overrides the need for the old OTP. Carry a backup identity proof just in case the enrolment officer asks.
We write these guides so owners can self-serve where possible, but there's a point at which the time cost outweighs the money saved. If you've spent more than two evenings on OTP troubleshooting, the linked-mobile update is going to take 5–10 days, and you have a bank loan or a GeM tender deadline — it's worth paying for someone to take over the whole flow the moment the linked-mobile update clears. We've cleared 40-odd OTP stuck cases in the last six months. The pattern is always one of the nine above. Start with the free self-route at udyamregistration.gov.in — if it clears, you keep the ₹0 you saved. If it doesn't after reading this piece, tell us which of the nine you're stuck on.
If the OTP is working but the form is failing at PAN, Aadhaar-PAN, or GST steps, start with our Udyam rejection reasons and fixes piece. If you're unsure what documents to have ready before retrying, the Udyam documents checklist covers every field the portal will ask for. And if you're migrating from an old Udyog Aadhar and the OTP stage is a different experience, the Udyog Aadhar migration page walks through the switchover specifically.
Nine out of ten times the mobile number linked to your Aadhaar is an old or disconnected number. UIDAI dispatches the OTP correctly — it just goes to a SIM you no longer have. Second most common cause is peak-hour portal congestion between 11am and 2pm. Third is DND category-2 blocking transactional SMS on your carrier.
Go to myaadhaar.uidai.gov.in, click "Verify Email/Mobile Number", enter your 12-digit Aadhaar and the mobile you want to verify. If it matches UIDAI's record, you'll see a confirmation. If it doesn't match, you'll see "Mobile number not registered". That tells you the mobile you thought was linked, isn't.
Under 30 seconds on a working linked mobile, most days. During peak hours (11am–2pm and just after budget announcements) it can stretch to 2–3 minutes. If nothing arrives in 3 minutes, it is not coming on this attempt. Do not request five more OTPs — UIDAI rate-limits to 3 per hour per Aadhaar and further requests are silently dropped.
No. The Aadhaar OTP is the core authentication step on the new Udyam portal. Unlike the old Udyog Aadhar Memorandum system, there is no offline paper filing route any longer. If your Aadhaar mobile is lost, you must first update the mobile at a UIDAI enrolment centre (or online via myaadhaar.uidai.gov.in if eligible), then return to the Udyam portal.
The mobile number you entered at the portal doesn't match what UIDAI has on file for this Aadhaar. The portal isn't asking you to type your mobile — it's asking you to confirm which mobile to send the OTP to, and that number must already be linked to your Aadhaar at UIDAI. If the linked number is old, update it via myaadhaar.uidai.gov.in for ₹50 or at an enrolment centre.
Regular DND (promotional category) does not block transactional OTPs. But DND category-2, which some users enable against all service messages, does block UIDAI dispatch. Check DND settings — on Jio and Airtel under Services → DND. Remove category-2 if enabled, wait 24 hours for the change to propagate, then retry.
Only if your Indian mobile is active on international roaming. UIDAI dispatches only to the registered Indian mobile. If you're abroad without your Indian SIM, authorise a family member in India to receive the OTP and read it out — the OTP itself is a 6-digit number with no identity tied to it. Or update the linked mobile at myaadhaar.uidai.gov.in to a foreign number if you're an NRI Aadhaar holder.
Three per hour per Aadhaar is the documented limit. In practice the portal silently drops further requests without any error once you cross that. Wait 60 minutes, close the browser completely, start fresh. Do not keep clicking resend — it makes things worse.
We handle the full filing flow, including the Aadhaar-linked mobile update if required. Certificate delivered to your email in 24–48 hours once authentication clears.
Start My Registration →