Zerodha TPIN CDSL Validity

Validity of CDSL T-PIN

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

The CDSL T-PIN does not have a hard expiry. Once issued by CDSL, it remains valid indefinitely until:

  • You regenerate it (which invalidates the previous T-PIN).
  • CDSL resets it (rare; typically only for security incidents).
  • Your demat account is closed.

This article clarifies the lifecycle, the recommended refresh cadence, and the edge cases.

No automatic expiry

CDSL T-PIN is a permanent credential by default. Unlike OTPs (which expire in minutes) or session passwords (which expire in months), T-PIN is intended to persist for the lifetime of the demat account.

This is a usability decision: forcing periodic T-PIN changes would create excessive friction without a clear security benefit (T-PIN is dual-factor with OTP, so theft alone is insufficient).

Despite no hard expiry, refreshing T-PIN periodically is good practice:

TriggerAction
Annually (security hygiene)Regenerate
Mobile changedUpdate registered mobile, then regenerate
Suspect compromiseRegenerate immediately
After major account changesRegenerate
Long-dormant account being reactivatedRegenerate

For most retail clients, annual regeneration is sufficient.

What invalidates a T-PIN

EventT-PIN status
Time passing aloneStill valid
Account inactivityStill valid (does not auto-expire)
New T-PIN generationPrevious T-PIN invalidated
Demat account closureT-PIN invalidated
Major fraud incident affecting your accountCDSL may invalidate; new T-PIN issued

Differences from other PINs

CredentialExpiry
CDSL T-PINNone automatic
Kite TOTPTime-based (rotates)
Console login password90-180 day refresh recommended
OTP for transactionsMinutes
ATM PINBank-policy (varies)

T-PIN is the most persistent of these; most other security credentials have shorter lifecycles.

Replacement by block mechanism context

Since the CDSL block mechanism rollout in October 2024, T-PIN is required less often for routine sells. Most Zerodha clients’ T-PIN sits unused for months between rare authorisation events (pledge / un-pledge, inter-depository transfer, specific cases).

This means even an old T-PIN typically remains valid for the rare time you need it. But it also means you may forget it; consider keeping the T-PIN noted securely.

Documentation

CDSL doesn’t publish a formal “T-PIN validity period” because there isn’t one. Operational documentation references:

  • “T-PIN issued at account opening, used as needed”.
  • “Regenerate when forgotten or compromised”.

There’s no policy document declaring T-PIN expiry.

Compared to NSDL SPEED-e

NSDL has a parallel framework called SPEED-e. NSDL’s authorisation credential has similar (no automatic expiry) properties. Both depositories operate similarly on this dimension.

Best practice for retail clients

  1. Note the T-PIN securely when first received.
  2. Don’t share with anyone, ever.
  3. Refresh annually as a hygiene measure.
  4. Refresh after suspected compromise.
  5. Update mobile / email at CDSL when they change.

See also

External references

References

  1. CDSL, T-PIN issuance and management, cdslindia.com.
  2. Zerodha Support, T-PIN validity and regeneration, support.zerodha.com.
  3. SEBI, Demat account framework, sebi.gov.in.

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.