<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Validity on WebNotes</title><link>https://v2.webnotes.in/tags/validity/</link><description>Recent content in Validity on WebNotes</description><generator>Hugo</generator><language>en-IN</language><lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://v2.webnotes.in/tags/validity/index.xml" rel="self" type="application/rss+xml"/><item><title>GTT validity rules on Kite</title><link>https://v2.webnotes.in/gtt-validity-rules-kite/</link><pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/gtt-validity-rules-kite/</guid><description>&lt;p&gt;A &lt;strong&gt;GTT (Good Till Triggered) order&lt;/strong&gt; on &lt;a href="https://v2.webnotes.in/zerodha/"&gt;Zerodha&lt;/a&gt;
 &lt;a href="https://v2.webnotes.in/kite-zerodha/"&gt;Kite&lt;/a&gt;
 is valid for one year from the date of placement on equity and only until contract expiry on F&amp;amp;O, after which it auto-cancels; it is not a true exchange order but a conditional instruction stored on Zerodha&amp;rsquo;s own servers that fires a single regular &lt;a href="https://v2.webnotes.in/limit-order-kite/"&gt;limit order&lt;/a&gt;
 to the exchange when your trigger price is touched. The validity rules differ by segment, the trigger fires only once, and the account is capped at 500 active GTTs. Understanding these rules matters because a GTT a trader assumes is &amp;ldquo;always on&amp;rdquo; can lapse silently, and a stop-loss set through a GTT carries a broker-server dependency that a resting &lt;a href="https://v2.webnotes.in/sl-order-kite/"&gt;SL order&lt;/a&gt;
 at the exchange does not.&lt;/p&gt;</description></item><item><title>Validity of CDSL T-PIN</title><link>https://v2.webnotes.in/validity-of-cdsl-tpin/</link><pubDate>Wed, 20 May 2026 00:00:00 +0000</pubDate><guid>https://v2.webnotes.in/validity-of-cdsl-tpin/</guid><description>&lt;p&gt;The &lt;strong&gt;CDSL T-PIN&lt;/strong&gt; does not have a hard expiry. Once issued by CDSL, it remains valid indefinitely until:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You regenerate it (which invalidates the previous T-PIN).&lt;/li&gt;
&lt;li&gt;CDSL resets it (rare; typically only for security incidents).&lt;/li&gt;
&lt;li&gt;Your demat account is closed.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This article clarifies the lifecycle, the recommended refresh cadence, and the edge cases.&lt;/p&gt;
&lt;h2 id="no-automatic-expiry"&gt;No automatic expiry&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;</description></item></channel></rss>