Zerodha eDIS TPIN OTP

Zerodha eDIS T-PIN OTP

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

The Zerodha eDIS T-PIN + OTP flow is the dual-factor authorisation used (historically and in residual cases) for selling CDSL-held shares without a physical DIS slip. The flow combines the holder’s CDSL T-PIN (a 6-digit transaction PIN) with a one-time password (OTP) sent to the registered mobile, providing strong authentication.

How the flow works

When you place a sell order on Zerodha Kite for CDSL-held shares (in cases where eDIS is still used):

  1. Order placement triggers the eDIS authorisation requirement.
  2. CDSL authorisation page opens (typically a CDSL-hosted iframe or popup).
  3. Enter T-PIN (6-digit Transaction PIN from CDSL).
  4. OTP request sent to your registered mobile.
  5. Enter OTP to confirm.
  6. Authorisation completes and the sell order proceeds to the exchange.

The whole flow typically takes 30-60 seconds.

Dual-factor: T-PIN + OTP

The dual-factor design provides:

  • Something you know (T-PIN): set up when you receive the PIN; you remember it.
  • Something you have (mobile receiving OTP): physical device control.

Together they make unauthorised sells significantly harder. Just stealing the T-PIN doesn’t suffice; the attacker also needs the mobile.

Setup of T-PIN

T-PIN is set up by CDSL when your demat account is opened:

  1. CDSL sends T-PIN via SMS or email to your registered mobile / email.
  2. You note it down (or memorise).
  3. The PIN is permanent unless reset.

For Zerodha clients on CDSL-side accounts, T-PIN setup typically happens during onboarding.

Mobile / OTP setup

The OTP is sent to the mobile number registered with CDSL (typically the same as your Zerodha registered mobile). If the mobile is unavailable:

  • Lost / unavailable mobile: Cannot complete eDIS flow.
  • Changed mobile: Update with CDSL before continuing.
  • Network issues: OTP may be delayed; try again.

Replacement by block mechanism

Since October 2024, the CDSL block mechanism has largely replaced per-trade eDIS authorisation for routine sell orders. The block mechanism:

  • Locks shares in the seller’s demat (no transfer needed).
  • Settles directly on T+1.
  • No per-trade T-PIN + OTP required.

For most Zerodha clients post-2024, the eDIS T-PIN + OTP flow is rarely seen for standard sell orders.

When eDIS T-PIN + OTP is still used

  • DDPI not active: If you haven’t signed the DDPI (Demat Debit and Pledge Instruction) for the broker, eDIS flow may still apply.
  • Specific authorisation cases: Some sell flows (e.g., very large positions) may still require eDIS.
  • Inter-depository transfers: Initiated by user, may require eDIS authorisation.
  • Pledge / un-pledge: Authorisation steps may use T-PIN + OTP.

DDPI alternative

DDPI is a one-time-signed authorisation that allows the broker to trigger sells on the user’s behalf without per-trade T-PIN + OTP. After DDPI activation:

  • Sell orders execute without the eDIS popup.
  • T-PIN + OTP not required per sell.
  • The DDPI scope is limited to the broker authorised.

Most Zerodha clients sign DDPI during onboarding for a smoother experience.

Security best practices

  • Never share T-PIN. CDSL and Zerodha never ask for it.
  • Never share OTP. Same rule.
  • Phishing red flags: A T-PIN entry page on a non-CDSL domain is a phishing attempt.
  • Mobile security: Don’t store T-PIN in plain text on mobile.
  • Monitor account: Check Console regularly for unauthorised activity.

Troubleshooting

If the eDIS flow fails:

  • T-PIN forgotten: See CDSL TPIN forgot Zerodha .
  • OTP not received: Check mobile signal, retry. If persistent, contact CDSL support.
  • Page stuck: Refresh; the order should be in pending state.
  • Wrong T-PIN entered: Most CDSL flows allow 3 attempts before lockout; resolve via CDSL support.

See also

External references

References

  1. CDSL, T-PIN and eDIS framework, cdslindia.com.
  2. SEBI, Electronic delivery authorisation framework, sebi.gov.in.
  3. Zerodha Support, eDIS and T-PIN authorisation, support.zerodha.com.

Reviewed and published by

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.