Demat account login failures are almost never random — they trace back to one of a small set of recurring causes that affect investors across every broker platform. The frustration they create is disproportionate to their actual complexity, because most resolve within minutes using the correct fix. This article catalogues every significant demat login error, why it happens, and the verified step-by-step fix for each.
Error 1: “Invalid User ID / Client Code”
What Happens: You enter what you believe is your User ID and receive an authentication failure.
Cause: The User ID is either typed incorrectly (common with alphanumeric codes containing zeros vs letter O, or ones vs letter I), or the wrong format is being used — some platforms accept both Client ID and registered mobile number; trying mobile format on a platform expecting alphanumeric Client ID triggers this error.
Fix: Retrieve your Client ID from your account activation email. If deleted, use the “Forgot User ID” or “Forgot Client ID” option on the login page — enter your PAN and registered mobile to retrieve it. Confirm whether the platform accepts mobile number as login or requires the alphanumeric Client ID specifically.
Error 2: “Incorrect Password”
What Happens: The password entered is not accepted. After repeated failures, the account locks.
Fix: Click “Forgot Password” on the login page. Enter your Client ID, PAN card number, and date of birth. An OTP is dispatched to your registered mobile. After OTP verification, set a new password following the required complexity policy. Do not attempt more than 3 consecutive incorrect entries — most platforms lock accounts after 3 to 5 failed attempts.
Error 3: Account Locked After Multiple Failed Attempts
What Happens: A security lock activates after 3 to 5 wrong password entries, displaying an “Account Locked” or “Access Restricted” message.
Fix: Do not attempt further logins. Use the Forgot Password self-service flow immediately — this resets the password and simultaneously unlocks the account at most brokers. If the self-service reset fails (due to inactive mobile number), contact the broker’s customer care helpline for manual unlock with identity verification.
Error 4: OTP Not Received
What Happens: After correct password entry, the OTP for Two Factor Authentication does not arrive on the registered mobile, preventing login completion.
Causes: Weak mobile signal; full SMS inbox; OTP delivery delay during high-traffic periods; registered mobile number changed or deactivated.
Fix: Check signal strength and inbox capacity. Wait 2 to 3 minutes before re-requesting the OTP. Most platforms offer a “Resend OTP” button after 30 seconds. If the OTP is consistently not arriving, the registered mobile may have been changed without updating the broker’s records — contact customer care or visit the nearest branch with PAN and Aadhaar to update the registered number.
Error 5: “Session Expired” or Automatic Logout
What Happens: You are logged out mid-session or before completing a task, displaying a “Session Expired” or “Please login again” message.
Cause: Broker platforms automatically terminate inactive sessions after a defined period — typically 15 to 30 minutes of inactivity — as a security measure. Browser cookie clearing or network interruptions also trigger this.
Fix: This is a security feature, not an error. Log in again with your credentials. For web sessions with frequent expiry, ensure cookies and session storage are not being cleared by browser privacy settings.
Error 6: Temporary Password Expired
What Happens: A new account holder attempts to log in with the temporary password from the welcome email and receives an “Invalid Credentials” error.
Cause: Temporary passwords at most brokers expire within 24 to 72 hours of issue. If the first login attempt happens after this window, the temporary password is no longer valid.
Fix: Use the Forgot Password option on the login page. Enter your Client ID, PAN, and date of birth, verify OTP, and set a new permanent password. The temporary password does not need to be used — the Forgot Password flow creates fresh credentials directly.
Error 7: TOTP Authentication Failure (Zerodha Specific)
What Happens: At Zerodha, after entering Client ID and password, the TOTP (Time-based One-Time Password) generated by the authenticator app does not work.
Cause: Time sync mismatch between your device’s clock and the authentication server. TOTP codes are time-sensitive and fail if the device clock is more than 30 seconds off.
Fix: Go to your smartphone’s Settings → Date & Time → enable “Set automatically” or “Sync with internet time server.” Once the device clock is synchronised, the TOTP app will generate valid codes again.
Overview Table: Common Login Errors and Fixes
| Error | Cause | Fix |
| Invalid User ID | Wrong format or deleted email | Use Forgot User ID → PAN + mobile OTP |
| Incorrect Password | Forgotten or expired | Forgot Password → PAN + DOB + OTP |
| Account Locked | 3–5 failed attempts | Forgot Password flow resets and unlocks |
| OTP Not Received | Signal/changed number | Check signal; update number at branch if changed |
| Session Expired | Inactivity timeout | Log in again; check browser cookie settings |
| Temporary Password Expired | 24–72hr validity lapsed | Use Forgot Password to set new credentials |
| TOTP Failure (Zerodha) | Device clock out of sync | Enable automatic date and time sync |
Frequently Asked Questions (FAQs)
Q1. What is the most common reason for demat login failure?
Incorrect password — usually forgotten after a period of inactivity. Always use the Forgot Password self-service option rather than guessing, which risks account lockout.
Q2. How do I unlock a locked demat account?
Use the Forgot Password flow on the login page — this resets the password and unlocks the account simultaneously at most brokers. Contact customer care if the self-service reset fails.
Q3. My OTP is going to my old mobile number. What should I do?
Contact your broker’s customer care or visit the nearest branch with PAN and Aadhaar. Mobile number update requests are processed in 2 to 5 business days.
Q4. Why does Zerodha ask for a TOTP instead of a regular SMS OTP?
Zerodha uses a TOTP authenticator app (Google Authenticator or similar) for 2FA instead of SMS OTP, providing better security. TOTP codes are generated locally on your device, not transmitted via SMS.
Q5. What should I do if none of the self-service fixes work?
Contact your broker’s dedicated customer care helpline. All major brokers provide toll-free support: Zerodha 080-47480048; ICICI Direct 1860-123-1122; HDFC Securities 1800-266-6060; Angel One 080-47480048; SBI Securities 1800-11-3488.
