A demat account login failure can be deeply frustrating — particularly when you need to execute a trade urgently during market hours or check your portfolio during a volatile session. Demat account platforms in India have become increasingly sophisticated with multi-layer security, but this complexity also creates more potential failure points in the login process. Whether you use Zerodha, Groww, HDFC Securities, ICICI Direct, Angel One, Upstox, or any other depository participant’s platform, the troubleshooting framework remains broadly consistent. This guide covers every possible cause and fix for demat account login failures.
Understanding the Demat Login System
Demat account login in India typically involves two or three layers of authentication — your Client ID or registered mobile number as the primary identifier, your password or MPIN as the second factor, and a TOTP or OTP delivered to your registered mobile number as the third factor. Some platforms also use biometric authentication on mobile devices. Each layer is a potential failure point, and identifying which specific layer is failing guides your troubleshooting direction.
Step 1 — Check Platform Server Status
Before troubleshooting your own device or credentials, verify whether the demat platform itself is experiencing technical issues. Server outages on demat platforms are most common during peak market activity — particularly at market opening (9:15 AM), closing (3:30 PM), and during circuit breaker events with extremely high volume. Check the platform’s official Twitter handle, status page if available, or trading community forums for outage reports from other users. If a server-side issue is confirmed, no local troubleshooting will help — wait for service restoration, which typically occurs within 30–60 minutes for most platform outages.
Step 2 — Verify Your Login Credentials Carefully
Credential input errors cause the majority of login failures that users attribute to platform problems. Your Client ID is typically alphanumeric — for example, Zerodha uses a format like AB1234, ICICI Direct uses an alphanumeric client code, and Angel One uses a six-digit client code. Confirm that you are entering the exact Client ID provided in your account opening documents or welcome email.
Passwords are case-sensitive — toggle off Caps Lock and verify that your keyboard is not auto-correcting or substituting characters. If you use a password manager, verify it has not saved an outdated password. Some platforms enforce periodic mandatory password changes — if your password was last changed more than 6 months ago, it may have expired and reset may be required.
Step 3 — Reset Your Password
If your password is not working, use the Forgot Password link on the login page. Standard Indian demat platform password reset requires your Client ID, date of birth, and PAN number for identity verification, after which an OTP is sent to your registered mobile or email. Create a new password meeting the platform’s specific requirements — typically 8 characters minimum with uppercase, lowercase, numbers, and special characters. After resetting, clear browser cache and cookies completely before attempting login with the new password. On mobile app, clear app cache or reinstall before using the new credentials.
Step 4 — Resolve Account Lock After Failed Attempts
Most demat platforms lock accounts after three to five consecutive failed login attempts as a security measure. When locked, even correct credentials fail until the lock is removed. Self-service unlock is available on most platforms through your registered mobile OTP verification. If self-service unlock is not available, call your broker’s customer care — have your Client ID, PAN, and registered mobile number ready for identity verification. Account unlocks typically process within minutes with customer support assistance. After unlocking, ensure your correct credentials are ready before attempting login to avoid immediately relocking.
Step 5 — Fix OTP and TOTP Authentication Problems
Two-factor authentication failures are the second most common login obstacle after incorrect passwords. For SMS OTP failures: check mobile network signal strength; verify your registered mobile number is active and receiving messages; check the SMS spam or blocked messages folder; confirm the number has not been changed without updating your demat account records. For TOTP authenticator failures: synchronise your device’s time to automatic through device settings — TOTP generation depends on exact time matching between your device and the platform server; even a 60-second time deviation causes all TOTP codes to fail. If you have changed phones without transferring the authenticator, contact your broker’s customer support for TOTP reset.
Step 6 — Update or Reinstall the Mobile Application
Outdated demat app versions frequently cause login failures because security certificates, API endpoints, and authentication protocols are updated server-side without backward compatibility for older versions. Open the Play Store or App Store, search for your broker’s app, and install any available update immediately. After updating, clear the app’s data and cache before logging in fresh. On iOS, delete and reinstall the app if update alone does not resolve the issue. For web platform login, clear browser cache, cookies, and site data completely — try logging in through an incognito or private browsing window to rule out cached data interference.
Step 7 — Verify SEBI or Depository Compliance Issues
Demat accounts are subject to periodic compliance requirements from SEBI and the depositories — NSDL and CDSL. If your KYC is not updated — particularly following SEBI’s directive on nominee registration, mobile number and email linking to demat accounts — your account may be restricted from login. Annual income update requirements and periodic re-KYC mandates can also create login restrictions if not completed by the specified deadline. Check your registered email for any compliance requirement notifications from your broker and complete any pending KYC or nomination updates.
Step 8 — Contact Broker Customer Support
If all the above steps fail, contact your broker’s customer support directly. Provide your Client ID, registered mobile number, and PAN for identity verification. Explain the specific error message you are receiving — “Invalid credentials,” “Account locked,” “Session expired,” or any other specific message helps support diagnose the problem faster. Most major brokers in India offer multiple support channels — phone, email, live chat, and in some cases WhatsApp support — with dedicated queues for urgent trading-related issues during market hours.
Frequently Asked Questions
Q: My demat login works on the website but not on the mobile app — why?
A: This typically indicates an outdated app version. Update or reinstall the app — web and app login systems sometimes update at different rates.
Q: My registered mobile number has changed and I cannot receive OTP — what do I do?
A: Visit your broker’s nearest branch with identity documents to update your registered mobile number. Online mobile number updates require OTP to the current registered number — if that number is inaccessible, in-person verification is required.
Q: Can I trade through my broker’s website if the demat app is not working?
A: Yes — the web platform and mobile app are independent access channels. Use the website during app outages.