Regulation SEBI margin pledge depository pledge CDSL NSDL TPIN Karvy client securities

SEBI margin pledge rules (September 2020 framework)

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

The SEBI margin pledge rules that took effect on 1 September 2020 fundamentally reshaped how Indian brokers collateralise client securities for derivatives margin. The framework, set out in SEBI circular SEBI/HO/MIRSD/DOP/CIR/P/2020/28 of 25 February 2020 and operationalised through subsequent depository circulars from CDSL and NSDL , replaced the long-standing Power of Attorney (PoA) regime with a depository-level pledge mechanism that requires explicit per-transaction client authorisation through a Transaction PIN (TPIN) and a one-time password (OTP).

Before September 2020, Indian retail brokers relied on broad-spectrum PoAs signed at account opening to move client securities into broker pool accounts or beneficiary accounts of the clearing corporation. The arrangement was operationally convenient: a single PoA at onboarding allowed the broker to transfer shares for delivery settlement, pledge securities for derivatives margin, and re-pledge to the clearing corporation, all without per-event client consent. The convenience came with structural risk: the same PoA could be misused, and the line between client-owned securities and broker-controlled inventory could blur. The Karvy Stock Broking crisis of 2019 was the trigger that pushed SEBI to dismantle this regime in favour of a depository-segregated pledge framework in which securities never leave the client’s demat account.

For Zerodha and every other Indian broker, the September 2020 framework was the most significant operational overhaul in over a decade. Client-onboarding workflows, margin-pledge user journeys, internal reconciliation, and exception handling were all rebuilt around the new TPIN and OTP authorisation steps. For retail traders, the new framework delivered stronger ownership protection at the cost of additional per-pledge friction.

This article covers the regulatory background and Karvy trigger, the structural difference between the old PoA regime and the new depository pledge, the operational mechanics of the TPIN and OTP authorisation, the related transition from PoA to the Demat Debit and Pledge Instruction (DDPI), the phased rollout from August 2020 onwards, and the operational consequences for retail derivatives traders and the brokers that serve them.

Pre-September 2020: the Power of Attorney regime

How collateralisation worked under the PoA system

Until August 2020, the standard onboarding pack for a retail broking account in India included a Power of Attorney form executed in favour of the broker. The PoA gave the broker discretion to move securities between specified accounts for specified purposes:

  • Delivery settlement: when the client sold shares, the broker used the PoA to transfer shares from the client’s demat account to the clearing corporation’s pool account on the pay-in date.
  • Margin pledge: when the client wanted to use shares as derivatives margin, the broker used the PoA to transfer shares to a broker-controlled beneficiary account that was then pledged to the clearing corporation.
  • Re-pledge to clearing: the broker re-pledged the same shares to the clearing corporation to obtain collateral margin.

The PoA was signed once at onboarding and remained in force for the life of the account. Individual transactions did not require fresh client consent.

Structural weaknesses of the PoA regime

Three structural weaknesses became apparent over the 2010s:

  • No per-transaction visibility: the client received an end-of-day contract note showing the transfers, but no real-time authorisation step. A client whose shares had been transferred without their knowledge had only an after-the-fact remedy.
  • Pool-account commingling: shares pledged for margin sat in broker beneficiary accounts that were not, in operational terms, fully segregated from broker proprietary holdings. Reconciliation depended on the broker’s internal records.
  • Misuse vector: the same PoA that authorised legitimate settlement transfers could authorise unauthorised pledges or transfers if the broker chose to misuse it. SEBI’s enforcement record over the 2010s included multiple instances of brokers using client securities for purposes beyond the client’s intent.

The Karvy crisis crystallised these weaknesses into a single high-profile failure.

The Karvy Stock Broking trigger

In November 2019, SEBI passed an ex-parte interim order against Karvy Stock Broking Limited finding that Karvy had transferred client securities worth approximately Rs 2,300 crore to its own beneficiary account and used the proceeds for purposes including funding its non-broking businesses. The mechanism used was the same PoA system that the entire industry relied on for routine settlement.

The Karvy order did not invent the problem; SEBI had been signalling concerns about client-securities protection through earlier circulars. The Karvy episode forced the issue. Within four months of the November 2019 order, SEBI issued the February 2020 circular that mandated a depository-pledge framework and the abolition of the broker’s ability to move client securities under a generic PoA.

The Karvy episode also accelerated parallel reforms including the September 2020 peak margin penalty regime, the abolition of broker-funded leverage beyond the SEBI-prescribed limits, and stricter segregation of client funds.

The September 2020 framework: structure

Core principle: securities stay in the client’s demat account

The defining principle of the new framework is that securities used as derivatives collateral remain in the client’s own demat account throughout the pledge period. No transfer to a broker beneficiary account or to the clearing corporation pool occurs. Instead, a pledge marker is created on the relevant securities within the depository’s records.

Under the old regime, a query on the client’s demat account on the day after a pledge would show the shares missing from the client’s balance and present in the broker’s beneficiary account. Under the new regime, the same query shows the shares still in the client’s account, with a pledge flag set and the pledgee identified.

Three-step pledge instruction

The new framework requires three discrete authorisation steps to create a pledge:

  1. Client pledge request: the client requests a pledge through the broker’s interface (Kite for Zerodha clients, equivalent interfaces for other brokers). The broker submits the request to the depository.
  2. Depository OTP to the client: the depository sends an OTP to the client’s registered mobile number and email address. The client enters the OTP on the depository’s verification page (linked from the broker’s interface), confirming the pledge.
  3. Re-pledge to clearing corporation: after the client-to-broker pledge is confirmed, the broker re-pledges the same securities to the clearing corporation. The re-pledge is a follow-on broker action and does not require fresh client OTP, but it can occur only after the client step is complete.

Each step is logged in the depository’s records. The audit trail is the depository’s, not the broker’s. A regulator or the client can pull the pledge history directly from CDSL or NSDL without depending on broker-provided records.

Transaction PIN (TPIN) at CDSL

CDSL operationalised the new framework through the TPIN system, which is the same mechanism used for electronic delivery instruction slips (eDIS) on the sell side. The TPIN is a six-digit numeric code set by the client and held by CDSL. For each pledge or eDIS transaction, the client provides the TPIN and a fresh OTP, completing the authorisation on the CDSL portal.

A common point of operational friction is that the TPIN must be generated by the client before the first pledge or eDIS transaction. New Zerodha clients are guided through TPIN generation as part of onboarding; clients who never set their TPIN cannot create pledges and must complete the TPIN setup before proceeding.

NSDL parallel framework

NSDL operates a structurally equivalent system using its SPEED-e platform and OTP-based authorisation. NSDL-served brokers route pledge instructions through the NSDL infrastructure, but the underlying principles (client-account residence, per-transaction OTP, depository-level audit trail) are identical.

The choice between CDSL and NSDL depots is a function of the broker’s depository participant arrangement, not the regulatory framework. Most retail-focused Indian brokers including Zerodha use CDSL as their primary depository; some institutional and traditional full-service brokers use NSDL.

Transition from PoA to DDPI

What the PoA was being used for

A retail PoA in the pre-2020 regime covered four distinct purposes:

  1. Delivery against sale: transferring shares to the clearing corporation on T+1 (now T+1, formerly T+2) pay-in for sold shares.
  2. Margin pledge: transferring shares to broker beneficiary account for derivatives margin.
  3. Mutual fund redemption: authorising transfer of mutual fund units on redemption.
  4. Corporate action handling: handling fractional shares, rights issues, and similar.

The September 2020 framework specifically addressed the margin pledge purpose. The other purposes continued under PoA for some time but were progressively brought under the same depository-authorisation principle.

Demat Debit and Pledge Instruction (DDPI)

In 2022, SEBI further restricted the PoA mechanism by introducing the Demat Debit and Pledge Instruction (DDPI), a narrower authorisation that allows brokers to debit securities from the client’s demat account only for specifically enumerated purposes: delivery against sale, mutual fund redemption, and margin pledge for the same client’s positions. The DDPI cannot be used for general transfers or for purposes beyond the enumerated list.

The DDPI replaced the broad PoA for new accounts opened after the SEBI circular took effect. Existing PoAs were grandfathered for a transition period, but most major brokers including Zerodha migrated existing clients to DDPI in 2022 to align with the post-Karvy posture of regulatory minimalism in client-securities authorisations.

For the purpose of the September 2020 margin pledge framework, the move from PoA to DDPI was complementary: the framework removed margin pledge from the broker’s PoA authority by requiring a depository OTP per pledge, and the DDPI codified that the broker’s residual authorisation could only be used for specifically enumerated client-benefit purposes.

Operational mechanics on Zerodha and peer brokers

Pledge initiation through the broker interface

A retail client initiating a pledge on Zerodha follows this flow:

  • Open the Kite holdings view or the Zerodha Console margin section.
  • Select the holdings to pledge and the quantity for each.
  • Review the haircut and resulting collateral margin (Zerodha’s interface displays the post-haircut value before submission).
  • Submit the pledge request.

Up to this point, no depository interaction has occurred; the request is a broker-internal queue entry.

Depository OTP confirmation

After submission, the client is redirected to the CDSL or NSDL verification page. The client enters the TPIN and the OTP received on the registered mobile and email. The verification page displays the specific securities and quantities being pledged, with the pledgee (typically the broker or the broker’s clearing member account) named.

The OTP step is operationally non-delegable. A broker cannot perform this step on behalf of the client; the OTP goes to the client’s registered contact details and the verification happens on the depository’s own portal, not the broker’s. This architectural choice was deliberate: the depository is the system of record and the broker is excluded from the authorisation step.

Re-pledge to clearing corporation

After client OTP confirmation, the broker submits a re-pledge instruction to the clearing corporation (NSE Clearing for NSE-segment positions, ICCL for BSE-segment positions). The re-pledge creates a charge over the same securities in favour of the clearing corporation. The clearing corporation then communicates the post-haircut collateral value back to the broker.

The post-haircut value is the collateral margin available to the client for derivatives positions. The haircut is set by the clearing corporation based on the security’s risk classification (Group I, II, or III) and ranges from approximately 10 per cent for highly liquid large-cap stocks to 50 per cent or more for low-liquidity small-cap stocks. Mutual fund units, exchange-traded funds, and government securities carry their own haircut bands.

For the procedural mechanics of pledge on Zerodha specifically, see Margin pledge mechanics on Zerodha .

Unpledge mechanics

Unpledging follows a similar three-step structure. The client initiates an unpledge request through the broker’s interface, an OTP confirmation is generated at the depository, and the broker reverses the re-pledge to the clearing corporation. Once complete, the pledge flag on the securities is removed and the shares return to fully-free status in the client’s demat account.

An important constraint: unpledging requires that the securities are not currently supporting open derivatives positions that would breach margin requirements after the unpledge. The broker’s risk system enforces this check before the unpledge instruction is submitted to the depository.

Phased rollout and post-Karvy timeline

Circular and deadline timeline

The implementation of the new framework followed a deliberate phased timeline that combined the pledge changes with parallel reforms:

  • November 2019: SEBI ex-parte interim order against Karvy Stock Broking Limited.
  • 25 February 2020: SEBI master circular SEBI/HO/MIRSD/DOP/CIR/P/2020/28 setting out the new pledge framework and segregation requirements.
  • June 2020: implementation deadline postponed to allow brokers and depositories more time to operationalise the OTP and TPIN systems.
  • August 2020: depositories announced go-live of the TPIN authorisation infrastructure.
  • 1 September 2020: new pledge framework operative; brokers no longer permitted to transfer client securities under PoA for margin pledge purposes.
  • 1 December 2020 onwards: phased rollout of the parallel peak margin penalty regime in four stages through 1 September 2021.
  • 2022: DDPI introduced as a narrower replacement for the PoA, further codifying the post-Karvy minimal-authorisation principle.

Parallel reforms

The September 2020 pledge framework was one of several reforms that together rebuilt the retail derivatives operational regime in 2020 and 2021:

  • The peak margin penalty regime requiring upfront collection of the highest intraday margin.
  • The abolition of broker-funded leverage beyond SEBI-prescribed limits.
  • Stricter segregation of client funds and the requirement that clients receive a daily client-balance reconciliation.
  • Mandatory reporting of pledge details to the exchanges and the clearing corporation in real time.

The cumulative effect was a tightening of the operational regime that made retail derivatives more capital-intensive but materially safer in terms of asset protection.

Operational consequences for retail traders

Higher friction per pledge transaction

The most visible consequence for retail traders is the per-transaction friction: a pledge that previously required no client action now requires the client to read the OTP on their phone, enter it on the depository portal, and confirm. For a trader who pledges occasionally, this is a minor inconvenience. For a trader who rebalances pledged holdings frequently, the friction can become operationally significant.

Brokers including Zerodha have minimised this friction through interface design (pre-filled forms, deep-link redirection to the depository portal, clear haircut display) but cannot remove the OTP step itself because it is the foundation of the regulatory framework.

Stronger asset protection

In exchange for the friction, retail clients have materially stronger asset protection. The architectural change means:

  • Client securities cannot be moved without per-transaction client consent.
  • The depository, not the broker, is the system of record for pledge status.
  • A broker insolvency does not in itself put client pledged securities at risk; the securities remain in the client’s demat account, and the pledge to the broker is a charge that the depository can resolve independently of the broker’s operational state.
  • Regulatory enforcement has direct access to the depository’s audit trail without depending on broker-provided records.

Operational implications for power users

Active F&O traders developed several adaptations after the September 2020 framework:

  • Pre-pledging in size: rather than pledging incrementally as needed, many traders now pledge a substantial portion of their long-term holdings once and leave the pledge in place for extended periods, generating standing collateral margin.
  • Monitoring of haircut changes: when the clearing corporation revises haircuts (typically twice a year), the collateral margin generated by a given holding can change without any pledge action. Traders monitor the published haircut tables and adjust their pledged composition if specific securities receive haircut increases.
  • Coordination with peak margin penalty management: pledged securities serve as part of the upfront margin requirement under the peak margin regime. Traders maintaining naked F&O positions typically combine a cash buffer with pledged collateral to cover intraday SPAN excursions.

Implications for non-trader investors

Retail investors who do not trade derivatives are also affected by the framework’s downstream changes. The DDPI replaced the PoA for delivery against sale, meaning that selling shares now requires a per-transaction OTP authorisation through the eDIS system rather than a broker-discretionary transfer under PoA. The mechanics are the same as for pledges, and the operational implication is comparable: a small friction added at the moment of sale in exchange for stronger asset protection.

For Zerodha clients specifically, see Zerodha DP charges for the cost structure that applies to delivery transactions under the new framework.

Common confusion points

“Pledge” versus “transfer”

A persistent source of confusion in client communications is the distinction between pledge (the post-September 2020 mechanism) and transfer (the pre-September 2020 mechanism). A pledge does not move the securities; it sets a flag. A transfer moves the securities to a different demat account. The September 2020 framework requires pledge, not transfer, for margin purposes. Client-facing language in older documentation that referred to “transfer of shares to the broker for margin” pre-dates the new framework and is no longer operationally accurate.

TPIN setup as a one-time prerequisite

Clients sometimes attempt their first pledge and encounter an error because TPIN is not set. The TPIN is a one-time setup at the CDSL or NSDL level, separate from the broker account password. Setting the TPIN through the depository’s portal is a prerequisite for both pledges (margin) and eDIS authorisations (delivery on sale).

Re-pledge versus pledge

The two-step pledge plus re-pledge sequence sometimes appears in client communications and contract notes. The client side of the transaction is the pledge (client to broker). The broker side is the re-pledge (broker to clearing corporation). Both are visible in the depository’s records, but only the first requires client OTP authorisation.

See also

External references

References

  1. Securities and Exchange Board of India, Circular SEBI/HO/MIRSD/DOP/CIR/P/2020/28, “Margin obligations to be given by way of Pledge / Re-pledge in the Depository System,” dated 25 February 2020 and subsequent operationalisation circulars, sebi.gov.in, accessed May 2026.
  2. Securities and Exchange Board of India, interim order against Karvy Stock Broking Limited, November 2019, sebi.gov.in.
  3. Central Depository Services (India) Limited, TPIN and pledge framework documentation, cdslindia.com, accessed May 2026.
  4. National Securities Depository Limited, pledge framework documentation, nsdl.co.in, accessed May 2026.
  5. NSE Clearing Limited, “Collateral and pledge framework,” nseindia.com, accessed May 2026.
  6. Indian Clearing Corporation Limited, “Pledge framework,” icclindia.com, accessed May 2026.
  7. Zerodha pledge and margin support documentation, support.zerodha.com, accessed May 2026.
  8. Zerodha Varsity Module 4 on Futures Trading, zerodha.com/varsity, accessed May 2026.
  9. Press coverage of the Karvy Stock Broking crisis and subsequent SEBI reforms, financial press archives 2019-2022.
  10. Securities and Exchange Board of India, DDPI circular and subsequent implementation circulars (2022), sebi.gov.in, accessed May 2026.

Related articles

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.