How-to support code ZPin telephone code IVR authentication Zerodha support Console

How to reset the Zerodha support code (ZPin)

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

The Zerodha support code, which Zerodha also labels the ZPin or telephone code, is a four-digit identifier that the interactive voice response (IVR) system asks for to authenticate you before it connects your call to a Zerodha support agent. You did not choose it and it is not a login credential. It does one job: it proves the caller is the account holder when the call comes from a number that is not registered on the account. You reset it through Console after a one-time-password (OTP) check, and you can view it any time in the Kite app, Kite web, or Console.

This guide covers what the support code is, why Zerodha gates the support desk behind it, the exact difference between this code and a login PIN, where to find your current code, and the precise reset path with its OTP verification. The reset takes under five minutes and costs nothing.

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 box at the top of this guide gives the sequence. The detail below expands the parts that trip people up: where the code lives, the Console reset path, and the OTP channel choice.

1. Understand what you are resetting

The support code authenticates a phone call, not a login. When you dial Zerodha’s support number from a phone that is not registered on your account, the IVR cannot recognise you from caller ID, so it asks for your registered number and the four-digit code as proof. Get the code wrong and the IVR will not connect you to an agent. This is the only situation in which the code is used; it appears nowhere in the order window, the funds page, or any trade flow. See Zerodha customer care number for the line the code applies to.

2. View your current support code first

Before resetting, confirm whether you even need to. The code is short and easy to note down. In the Kite app, tap your user ID, then Profile, then View, then View under Support code. On Kite web, click your user ID, then your name, then View, then View again. The four-digit value is masked until you complete that final tap, which is itself a small in-session authentication. If you can read the code here, you may not need a reset at all; just record it.

3. Open Console to reset it

The reset control lives in Console, not in Kite. Log in to Console at console.zerodha.com using your normal credentials and 2FA. Open the Account section from the Console menu and locate the Support code tab. Console is the back-office surface for account-level actions like statements, profile, and the support code; Kite is the trading surface. If you are not sure how to reach it, see How to log in to Zerodha Console .

4. Start the reset and pick an OTP channel

Inside the Support code tab, click View, then Reset. Zerodha then runs an identity check before it changes the code, so it offers a verification OTP on either your registered email address or your registered mobile number. Choose whichever channel you can access right now. If you have lost access to both, the support code reset is blocked until you update your contact details first; that is a separate procedure covered in How to recover a Zerodha account when you lost both email and mobile .

5. Enter the OTP and verify

Retrieve the OTP from the email or SMS, enter it in the designated field, and select Verify. This step confirms your identity and validates the OTP you entered. The reset does not go through until this verification succeeds, which is what stops anyone who is not the account holder from rotating your support code.

6. Note your new support code

On a successful verify, Zerodha generates a fresh four-digit code and shows it to you. Note it down somewhere you can reach when you next call from an unregistered number. You can view or reset it again whenever you want; there is no cooldown that the support article documents and no charge for the action.

Why the support code exists

Zerodha runs the support desk behind an authentication gate for the same reason it gates login behind two factors: a broking and demat account is a financial account, and an impostor who reaches a support agent could attempt social engineering, such as a contact-detail change or an account action. Caller ID alone is weak, because a number can be spoofed or borrowed. The registered-number-plus-code pair raises the bar: the caller must either be calling from the registered phone, or know both the registered number and the assigned four-digit code. This is consistent with the cyber-security and cyber-resilience framework that the Securities and Exchange Board of India (SEBI ) sets for stock brokers and depository participants, which requires controlled access to client information and systems.

The code is short, four digits, because it is a second factor layered on top of the registered number, not a standalone secret. It is not meant to resist a determined offline attack; it is meant to defeat a casual impostor calling from a random phone. That is why Zerodha is comfortable letting you view it in plain text inside an authenticated app session, while still requiring an OTP to rotate it.

How the support code differs from a login PIN

People conflate the support code with the Kite login PIN because both are short numbers tied to the same account. They are unrelated.

A login factor signs you in to a platform. At Zerodha, Kite login is a password plus a second factor, either an OS-level device lock (PIN, pattern, fingerprint, or Face ID) on the Kite app , or a time-based one-time password (TOTP) on an authenticator app, under the Kite app code and TOTP versus SMS OTP framework. None of these is the support code. The support code never appears in a login screen and cannot sign you in to anything.

The support code authenticates a voice call. It exists outside the login system entirely. Resetting it does not touch your password, your device lock, your TOTP seed, or your 2FA setup . If you forget your Kite PIN or password, the fix is a Kite PIN recovery or a password recovery , not a support-code reset. If you forget the support code, the fix is the reset in this guide, and it leaves your login untouched.

Edge cases worth knowing

If you call from your registered number, you will usually not be asked for the code at all, because the IVR identifies you from caller ID and routes you straight to an agent. The code is the fallback for the unregistered-number case: a borrowed phone, a landline, an office line, or a second SIM.

If your registered number has changed and you have not updated it on the account, the IVR will not recognise the new number, and you will be in the unregistered-number path even though the phone is yours. Update the number first through How to change your Zerodha mobile number , then the registered-number path works again.

If a single phone number is registered against more than one Zerodha account, login and IVR identification behave differently from the single-account case; you cannot use such a shared number to log in to Kite, and you may be prompted for the code more often. Keep one mobile number to one account where possible.

See also

External references

References

  1. Zerodha support, What is a support code, and why do I need it to reach Zerodha’s support desk? (as of 20 June 2026).
  2. Zerodha support, How do I reset my support code? (Console > Account > Support code > View > Reset, OTP verification; as of 20 June 2026).
  3. SEBI, Cyber Security and Cyber Resilience framework for Stock Brokers and Depository Participants (controlled access to client systems and information).

WebNotes Editorial Team prepares factual how-to guides based on publicly available regulatory documents and broker disclosures. WebNotes is not affiliated with Zerodha Broking Limited. Procedures are subject to change; verify current requirements at support.zerodha.com before acting.

Related articles

Frequently asked questions

What is the support code or ZPin at Zerodha?
It is a four-digit identifier that the IVR asks for to authenticate you before connecting your call to a Zerodha support agent. Zerodha also calls it the telephone code. It applies only when you call from a number not registered on your account.
When do I actually need the support code?
Only when you call Zerodha support from a phone that is not your registered number. If you call from the registered number, the IVR recognises you and connects you to an agent without asking for the code.
How do I use the support code in the IVR?
When calling from an unregistered number, enter your registered phone number followed by the four-digit code. If your registered number is 9XXXXXXXXX and your code is 0007, you enter 9XXXXXXXXX0007 when the IVR prompts for it.
Can I choose my own support code?
No. Zerodha assigns the four-digit code; you cannot set a custom value. You can only view it or reset it to a new system-generated code through Console, Kite app, or Kite web after an OTP check.
Is the support code the same as my Kite login PIN?
No. The support code authenticates a phone call to the support desk. It never logs you in to Kite or Console. Your Kite login uses a password plus a 2FA factor (device lock or TOTP), which is a separate mechanism.
How do I reset the support code if I forgot it?
You do not need the old code to reset it. Log in to Console, open Account, go to the Support code tab, click View then Reset, verify the OTP sent to your registered email or mobile, and Zerodha issues a fresh code.
Does resetting the support code affect my trading or holdings?
No. The support code only governs IVR authentication on a support call. Resetting it has no effect on your positions, holdings, funds, login credentials, or 2FA. It changes one four-digit number used to reach an agent.

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.