How-to DigiLocker Aadhaar OTP UIDAI KYC

How to fix a DigiLocker or Aadhaar OTP failure during Zerodha onboarding

From WebNotes, a public knowledge base. Last updated . Reading time ~10 min.

A DigiLocker or Aadhaar OTP failure during Zerodha onboarding almost always traces to one fact: the one-time password is delivered only to the mobile number seeded with your Aadhaar at UIDAI , and the number you are holding is not that one. The DigiLocker eKYC step logs you in through Aadhaar and an SMS OTP to the Aadhaar-linked mobile, so if that mobile is stale, ported away from, or never linked, no OTP arrives no matter how many times you tap resend. This guide diagnoses the failure in order, from the trivial causes to the structural one, and gives the two real fixes: update the Aadhaar mobile at UIDAI, or open the account through the offline route.

The reason this single point of failure exists is by design. UIDAI will not send an Aadhaar authentication OTP to an arbitrary number, because the OTP is itself the proof that the person holds the device tied to that Aadhaar. A broker cannot override it, redirect it, or whitelist a different number, and neither can Zerodha support. So the fix is never on the broker side; it is either at UIDAI, where you correct the linked mobile, or in the choice of onboarding route, where you avoid the OTP entirely.

Conflict-of-interest disclosure. This guide is published by the WebNotes Editorial Team for informational purposes and is written independently. WebNotes operates a Zerodha account-opening referral programme, disclosed on the pages that carry the referral link; this guide does not carry it and earns no referral commission from the procedure described here.

Step-by-step procedure

The numbered procedure in the infobox above is the canonical diagnostic order. Work down it: most failures clear at step 1 or 2, the structural ones need step 5, and step 6 is the route for anyone who cannot link a mobile to Aadhaar at all.

1. Confirm which mobile is seeded with your Aadhaar

Start here, because it resolves the majority of cases. Go to myaadhaar.uidai.gov.in and check which mobile number is registered against your Aadhaar. The DigiLocker login and the Aadhaar OTP both go to that number and only that number. If the registered mobile is one you no longer use, the OTP is being delivered to a dead or inaccessible SIM, which looks like “no OTP” from your side. The number you type into the Zerodha form is your contact number for the account; it is not where the Aadhaar OTP is sent. Conflating the two is the single most common misunderstanding in this flow.

2. Rule out DND, network and a one-minute delay

Before assuming the link is broken, clear the cheap causes. Wait at least 60 seconds between OTP requests; tapping resend repeatedly can queue conflicting requests and slow delivery. If your number is on full Do Not Disturb, transactional SMS can be blocked, so send START to 1909 or ask your telecom operator to enable transactional messages, then retry. A weak signal or a full message inbox can also swallow the SMS. These are minor, but they account for a real share of “OTP not received” reports where the Aadhaar link is actually fine.

3. Check for UIDAI or DigiLocker downtime

DigiLocker does not hold a copy of your Aadhaar OTP; it calls UIDAI’s authentication servers in real time and relays the result. When UIDAI is down or overloaded, the OTP step fails across the board, and the error you see can look like a problem with your own Aadhaar. If steps 1 and 2 check out and the OTP still will not come, wait an hour and retry before taking any irreversible action like booking a centre visit. A transient UIDAI outage clears on its own.

4. If the number is ported or changed, this is the usual cause

Porting is widely misunderstood here. Porting your number from one operator to another keeps the same digits and keeps the Aadhaar link intact, because the link is to the number, not the operator. The failure case is different: you stopped using the old Aadhaar-seeded number and moved to a new number that you never seeded with Aadhaar. To UIDAI, your Aadhaar is still pointing at the old number. The OTP goes there, you never see it, and the new number is invisible to the authentication. The fix is to update the Aadhaar-linked mobile, covered next.

5. Update the Aadhaar-linked mobile at an Aadhaar Seva Kendra

A mobile-number update on Aadhaar cannot be done online, because the online services themselves require a working linked mobile, which is the very thing you lack. Visit an Aadhaar Seva Kendra, carry your Aadhaar and the new SIM, give your biometrics for verification, fill the update form, and pay the Rs 50 fee. No supporting document is needed to change only the mobile number. Book a slot at appointments.uidai.gov.in or locate a centre through uidai.gov.in to avoid a queue. The update takes a short while to propagate; once the new number is live on Aadhaar, the DigiLocker OTP will reach it and you can complete the online Zerodha flow.

When linking a mobile to Aadhaar is not feasible, Zerodha’s documented fallback is to open the account through the offline paper route, which does not require an Aadhaar-mobile link at all. You submit a self-attested Aadhaar copy plus a separate officially valid address proof such as a driving licence, voter ID or passport, and complete an OTP-based in-person verification rather than the DigiLocker pull. The trade-off is time: the offline route is couriered and checked manually, so it runs longer than the online eKYC , and it costs more, Rs 400 for an equity account against Rs 200 online.

Why the OTP can only go to the Aadhaar-seeded mobile

The constraint is not a Zerodha rule but a UIDAI one. Aadhaar OTP authentication exists precisely so that possession of the registered device stands in for a password: whoever receives and enters the OTP is presumed to control the mobile tied to that Aadhaar. If UIDAI delivered the OTP to any number a form supplied, the control proof would be worthless. SEBI’s digital KYC process reflects this by requiring that the mobile submitted should preferably be the one seeded with Aadhaar, because the whole eKYC depends on OTP-based Aadhaar authentication. That is why an applicant whose mobile is not linked to Aadhaar cannot complete the fully online OTP flow and must either fix the link or go offline.

When the failure is a name or record mismatch, not the OTP

Not every onboarding block is an OTP block. If the OTP arrives and the DigiLocker pull succeeds, but linking then fails, the cause is usually a name or date-of-birth mismatch between the Aadhaar record from DigiLocker and the PAN record from the Income Tax Department. That is a different problem with a different fix: reconcile the two records first, then retry. It is covered in how to fix a failed PAN verification during Zerodha account opening and in the DigiLocker KYC explainer . Diagnose which stage you are stuck at before acting, because an OTP fix will not solve a name-mismatch failure and vice versa.

See also

External references

References

  1. Zerodha support, Can I open an online account if my Aadhaar isn’t linked to my mobile number, support.zerodha.com (as of 20 June 2026); two options given: link the mobile at an Aadhaar Seva Kendra, or open the account offline.
  2. UIDAI, Update Aadhaar, uidai.gov.in (as of 20 June 2026); mobile-number update is done at an enrolment centre, not online, with a Rs 50 fee and no supporting document required.
  3. SEBI Master Circular on Know Your Client (KYC) norms for the securities market, October 2023; mobile submitted for digital KYC should preferably be the Aadhaar-seeded number.
  4. The Aadhaar (Targeted Delivery of Financial and Other Subsidies, Benefits and Services) Act 2016, on OTP-based Aadhaar authentication.

Related articles

Frequently asked questions

Why is the DigiLocker or Aadhaar OTP not coming during Zerodha account opening?
The OTP goes only to the mobile number seeded with your Aadhaar at UIDAI, not the number you typed into the Zerodha form. If that linked number is stale, ported away from or never linked, no OTP arrives. Check the registered number at myaadhaar.uidai.gov.in first.
Does the Aadhaar OTP go to the mobile number I entered in the Zerodha form?
No. The number on the Zerodha form is the contact number for the account; it does not receive the Aadhaar OTP. Aadhaar authentication delivers the OTP only to the mobile registered against your Aadhaar at UIDAI. Conflating the two is the single most common misunderstanding.
Does porting my mobile number break the Aadhaar link?
No. Porting from one operator to another keeps the same digits and keeps the Aadhaar link intact, because the link is to the number, not the operator. The OTP fails only when you moved to a new number you never seeded with Aadhaar, leaving UIDAI pointing at the old one.
Can I update my Aadhaar-linked mobile number online?
No. A mobile-number update on Aadhaar cannot be done online, because the online services themselves need a working linked mobile. Visit an Aadhaar Seva Kendra with your Aadhaar and new SIM, give biometrics, and pay the Rs 50 fee; no supporting document is needed for a mobile change.
Can I open a Zerodha account if my mobile is not linked to Aadhaar?
Yes. Zerodha’s documented fallback is the offline paper route, which needs no Aadhaar-mobile link. You submit a self-attested Aadhaar copy and a separate address proof and complete OTP-based IPV. The trade-off is cost and time: Rs 400 for an equity account against Rs 200 online.
The OTP works but linking still fails. What is wrong?
That is a different problem from an OTP failure. If the DigiLocker pull succeeds but linking then fails, the cause is usually a name or date-of-birth mismatch between the Aadhaar record and the PAN record from the Income Tax Department. Reconcile the two records first, then retry.

Reviewed and published by

WebNotes Editorial Team

The WebNotes Editorial Team covers Indian capital markets, payments infrastructure and retail investor procedures. Every article is fact-checked against primary sources, principally SEBI circulars and master directions, NPCI specifications and the official support documentation published by the intermediary in question. Drafts go through a second-pair-of-eyes review and a separate compliance read before publication, and revisions are tracked against the SEBI and NPCI rule changes referenced in the methodology section.

Last reviewed
Conflicts of interest
WebNotes is independent. No relationship with any broker, registrar or bank named in this article.