Zerodha email asking for bank proof
A Zerodha email asking you to confirm your bank account by submitting bank proof is sent when the automatic penny-drop verification fails during account opening or a bank-detail change. SEBI requires every client’s bank account to be verified, and Zerodha runs that verification automatically by penny drop: a token amount is credited to the account and the bank’s registered account-holder name is read back and matched against your PAN and KYC name. When that automated match cannot complete, SEBI’s KYC rules let Zerodha accept a manual bank proof instead, so the email asks you for one.
The check exists to enforce a single principle: funds must move only through a bank account that belongs to you. SEBI does not permit third-party fund transfers between an investor and a securities platform, so the linked account has to be confirmed in your own name. This guide explains what penny drop is and why it fails, the three documents Zerodha accepts as valid bank proof, how to submit them on a ticket, and the SEBI circular that sits behind the whole step.
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.
What penny drop is and why it fails
Penny drop is the automated bank-verification method SEBI prescribes. The intermediary credits a token amount, commonly Re 1, to the bank account the client has provided, and the bank returns the registered account-holder name as a reverse feed. The platform then matches that returned name against the client’s PAN and KYC name. A clean match verifies, in one step, that the account exists and that it belongs to the client, without any document upload.
Failure usually has one of three causes. The most common is a name mismatch: the name your bank holds against the account differs from your PAN name, even by a middle name, an initial, or a spelling variation. The second is that the bank did not respond to the penny-drop request, which happens with some account types and some banks. The third is a PAN-side issue that leaves the KYC name itself unsettled. In each case the automated route cannot close the loop, so the manual bank proof takes over.
What counts as valid bank proof
Zerodha accepts any one of three documents as bank proof:
| Document | What it must show |
|---|---|
| Recent bank statement | Account number, IFSC, bank name, and the account-holder name |
| Passbook | The page carrying account number, IFSC, bank name, and the holder name |
| Personalised cancelled cheque | A cheque pre-printed with your name, the account number and IFSC printed on it |
A personalised cheque is one on which your name is pre-printed by the bank, not a generic cheque with the name handwritten. The reason all three carry the same fields is that the document has to let Zerodha re-perform the name-to-account match by hand: confirm the account number and IFSC identify a real account, and confirm the printed or statement-header name matches your PAN and KYC name. A document where the holder name is not visible defeats the purpose, so the name must appear.
How to submit the bank proof
Submission runs through a support ticket. Create a ticket on the Zerodha support portal and attach any one of the three valid bank-proof documents. Zerodha re-verifies the account from the document, confirming the account belongs to you and that the name aligns with your KYC, then updates the bank record on the account. For the mechanics of attaching a document to a ticket, including file-size limits, see How to attach files to a Zerodha ticket and the How to create a ticket at Zerodha walkthrough.
If the request relates to adding or changing a bank account rather than to onboarding, the same proof clears it; the related flows are How to add a secondary bank account on Zerodha and How to change the bank IFSC on Zerodha . Where the root cause is a name difference, fixing the name at the bank or in your KYC so both read identically prevents the failure from recurring; see How to change your name on Zerodha .
The regulatory basis: SEBI’s 24 April 2020 KYC circular
The requirement is not a Zerodha preference. SEBI’s KYC circular SEBI/HO/MIRSD/DOP/CIR/P/2020/73, dated 24 April 2020, sets the framework: PAN is verified online against the Income Tax database, and the client’s bank account is verified by the penny-drop mechanism or another bank-API method. The same circular provides the fallback you are using: where the penny-drop match fails, or where penny drop does not return a joint-holder name, the intermediary accepts a copy of the signed cancelled cheque, and bank details may be accepted on that basis where the bank does not respond to the penny drop.
That circular is why the bank-proof step is uniform across SEBI-registered brokers, mutual fund platforms and other intermediaries, not unique to one broker. It also explains why the linked account must be in your own name: the verified account is the only channel through which money may move between you and the market, and a verified own-name account is what closes the third-party-transfer risk SEBI is guarding against. The broader account-linking mechanics are covered in Bank account validation and How to link a bank account on Zerodha .
See also
- Zerodha
- Zerodha Console
- Bank account validation
- How to link a bank account on Zerodha
- How to add a secondary bank account on Zerodha
- How to change the bank IFSC on Zerodha
- How to change the primary bank on Zerodha
- How to change your name on Zerodha
- How to fix PAN verification failed on Zerodha
- How to verify PAN and Aadhaar on Zerodha
- How to create a ticket at Zerodha
- How to attach files to a Zerodha ticket
- How to respond to a document resubmission email from Zerodha
- How to respond to an additional documents email from Zerodha
- How to verify a Zerodha email is genuine
- How to re-KYC your Zerodha account
- How to check your KYC status on Zerodha
- Zerodha email: multiple accounts share the same mobile or email
- Know your customer
- Central KYC Records Registry
- Demat account
- Trading account
- SEBI
- IFSC code
External references
- Zerodha support: Why did Zerodha send an email asking for bank proof?
- Zerodha support: Why did I receive an email from Zerodha asking to confirm my bank details?
- SEBI: KYC process circular SEBI/HO/MIRSD/DOP/CIR/P/2020/73, 24 April 2020
- SEBI
- Central KYC Records Registry (CERSAI)
References
- Zerodha support, Why did Zerodha send an email asking for bank proof? (penny-drop failure at account opening or bank modification; recent bank statement, passbook, or personalised cancelled cheque; as of 21 June 2026).
- SEBI circular SEBI/HO/MIRSD/DOP/CIR/P/2020/73, dated 24 April 2020, on the KYC process and use of technology for KYC (PAN online verification; bank verification by penny drop; signed cancelled cheque accepted where penny drop fails or returns no name).
- SEBI norms barring third-party fund transfers between a client and a securities-market intermediary, requiring the linked bank account to be in the client’s own name.
WebNotes Editorial Team prepares factual reference material based on publicly available regulatory documents and broker disclosures. WebNotes is not affiliated with Zerodha Broking Limited. Procedures and accepted documents are subject to change; verify current requirements at support.zerodha.com before acting.