Banks supporting eMandates on Zerodha

An eMandate on Zerodha is a standing authorisation that lets your bank debit your account automatically for recurring transfers or mutual fund SIPs . Whether a particular mandate can be created depends almost entirely on your bank and your account type. This reference explains which banks support eMandates and UPI AutoPay on Zerodha, how eligibility is actually decided, which account types are excluded, and, most importantly, how to check whether your own bank is supported at the moment you want to register. Bank support is not fixed, so the emphasis throughout is on checking the live position rather than trusting any static list.

Conflict-of-interest disclosure. This reference 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 page does not carry it and earns no referral commission from the process described here.

Zerodha does not keep its own bank list

The most important thing to understand is that Zerodha does not publish or maintain a proprietary list of supported banks. Bank eligibility for eMandates is governed by the National Payments Corporation of India , the body that operates the NACH and UPI rails on which eMandates run. A bank is eligible for eMandate registration when its netbanking status is shown as Live on the NPCI list. When the netbanking status for a bank is not Live, that bank cannot process eMandate authentication at that time, regardless of anything Zerodha does at its end.

This design has a practical consequence. If your bank is temporarily unavailable, the cause is usually an issue at the bank or on the NPCI network, not at Zerodha. Zerodha cannot force a bank to accept a mandate, and it cannot see why a specific mandate failed at the bank gateway. The upside is that as soon as a bank is restored to Live status on the NPCI list, it becomes usable again through Zerodha automatically, with no separate action needed from Zerodha.

Because the underlying source is the NPCI live-status list, the correct mental model is “is my bank live on the network right now,” not “is my bank on Zerodha’s approved list.” That is why every recommendation on this page is to check the current status rather than rely on a bank name appearing in an article.

Two separate registration routes, two eligibility pictures

Zerodha offers two distinct ways to set up an automatic-debit mandate, and each has its own bank-support picture at any given moment.

The first is the Console eNACH route, used for scheduling recurring fund transfers from your bank to your Zerodha trading account. You set this up at Zerodha Console by creating a new mandate, selecting the account, and authenticating with a debit card or netbanking on your bank’s mandate-approval gateway. This route can take up to five working days for the bank to activate the mandate. The full walkthrough is in the guide on setting up a net-banking eMandate on Zerodha .

The second is the UPI AutoPay route, used mainly for mutual fund SIPs on Zerodha Coin . You authorise the mandate in any UPI application, and it activates almost immediately rather than taking up to seventy-two working hours like a bank mandate. UPI AutoPay can be created on both primary and secondary bank accounts. The step-by-step is in the guide on setting up a UPI eMandate on Zerodha .

These two rails do not always support the same banks at the same time. A bank might be live for UPI AutoPay while its netbanking eNACH gateway is temporarily down, or vice versa. When one route fails for your bank, it is always worth trying the other before concluding that automatic debits are impossible for your account.

Account types that cannot create eMandates

Even when your bank is fully live on the network, the account type matters. eMandate authentication requires a single, clearly identified account holder who can authorise debits, and several account categories do not meet that requirement.

• Current accounts cannot be used to create eMandates on Zerodha. This applies to both the Console eNACH route and the Coin UPI AutoPay route. Only savings accounts registered as your primary or secondary bank account on Zerodha can back a mandate.
• Joint accounts are frequently excluded. Some banks do not allow eMandates to be created from joint bank accounts, and Zerodha lists joint accounts among the account types that commonly cannot register a mandate. The detail, and the workaround, are covered in the companion reference on setting up an eMandate on a joint account at Zerodha .
• NRE-PIS accounts are also generally not supported for eMandates. Non-resident investors operating through the portfolio investment scheme should expect the mandate route to be unavailable and plan for manual transfers instead.

If your only available account is a current, joint, or NRE-PIS account, the practical alternative is to add Zerodha as a beneficiary in your net banking and set up a standing instruction for periodic transfers. That achieves recurring funding without an NPCI mandate, though you lose the tight SIP-linked timing that a true eMandate provides.

Banks temporarily disabled, as observed

Bank support changes over time. Banks are occasionally removed from mandate creation for maintenance, integration changes, or network issues, and are restored once resolved. As observed on 30 June 2026, the following banks were temporarily disabled from creating mandates on Zerodha:

• Central Bank of India
• Standard Chartered
• Indian Overseas Bank (IOB)

This list is a snapshot, not a permanent statement. A bank on this list today may be usable next week, and a bank not on this list may be disabled tomorrow. Treat the snapshot only as an illustration of the fact that some banks can be temporarily unavailable, and always verify the live position for your own bank at the moment you want to register. Do not conclude that any bank is permanently supported or permanently blocked on the strength of a dated list.

How to check whether your bank is supported

There are two reliable ways to confirm your bank’s current status, and both take only a minute.

Try to create the mandate. The most direct check is to begin the registration flow. For a Console fund-transfer mandate, log in to Zerodha Console , go to the funds mandate section, and start creating a new mandate. If your bank is currently supported, it will appear in the account selection and the authentication window will open on the bank gateway. If it is temporarily disabled, it will either not be selectable or the authentication will fail. For a Coin SIP, begin the UPI AutoPay setup in the SIP flow; a supported bank completes the UPI authorisation, and an unsupported one fails at the app.

Check the NPCI live status. Because eligibility follows the NPCI live-status list, you can also confirm whether your bank’s netbanking is currently Live on the NPCI network. A Live status means the bank should accept eNACH mandate authentication; a non-Live status means it will not at that time.

If the mandate route is unavailable for your bank on both rails, the fallback is always the same: add Zerodha as a beneficiary in net banking and set up a standing instruction, or fund the account manually. See the overview on adding funds to Zerodha via UPI for the manual option.

What happens when a bank is not supported

When a bank is temporarily disabled, an attempted registration will fail at the authentication stage. Zerodha cannot determine the specific reason for a bank-side failure; only your bank holds that information. The registration-failed behaviour, and how to distinguish a genuine failure from a mandate that is merely pending, are covered in the Zerodha eMandate troubleshooting guide . In short, a failed mandate should be recreated once the bank is available again, while a mandate that is only pending should be left to complete rather than recreated.

If your bank was working and then stops, do not assume your mandate has been cancelled. An already-active mandate continues to function on the network. A temporary disablement usually affects new registrations rather than existing mandates. If you do want to end an existing mandate, follow the guide to cancelling an eMandate on Zerodha .

Charges and limits vary by bank

Zerodha itself levies no charge for eMandate registration or for transferring funds using an eMandate. However, individual banks may apply their own fees, such as a mandate verification charge, or a penalty for a failed debit when the account has insufficient funds. Because these amounts are set by the bank and not by Zerodha, they differ from bank to bank. The bank-side charges are set out in the reference on Zerodha eMandate charges .

Debit limits also depend on the route and, in some cases, on the bank. The eNACH and UPI AutoPay rails carry different daily ceilings, and Zerodha’s own documentation is not fully consistent on the figures, so the specific limits and the discrepancy between them are handled separately in the reference on the Zerodha eMandate daily limit . When choosing a bank and a route, check that its per-debit limit is high enough for your intended transfer or SIP amount before you register.

Choosing the right route for your bank

Putting the pieces together, the decision usually comes down to which route your bank supports and how quickly you need the mandate active.

• If you want the mandate live almost immediately and your bank supports it, UPI AutoPay is the faster route, activating instantly rather than over several working days. It works on primary and secondary savings accounts and is the natural fit for a Coin SIP set up over UPI AutoPay .
• If you are scheduling recurring transfers into your trading account, or your bank supports netbanking eNACH more reliably than UPI, use the Console eNACH route described in the net-banking eMandate guide . Allow up to five working days for activation.
• If a debit later fails, that is a bank-side or funding issue rather than a support issue; see the guidance on fixing a failed SIP debit .

For the conceptual background on how eMandates, NACH, and UPI AutoPay fit together, the Zerodha eMandate overview is the hub page that ties these guides together.

Key takeaways

• Zerodha does not keep its own bank list; eligibility follows the NPCI live-status list, where a bank must be Live for netbanking to register an eNACH mandate.
• eNACH via Console and UPI AutoPay via Coin are two separate rails, and a bank may support one but not the other at a given time.
• Current accounts cannot create eMandates, and joint and NRE-PIS accounts are commonly excluded; use a primary or secondary savings account, or the beneficiary standing-instruction workaround.
• As observed on 30 June 2026, Central Bank of India, Standard Chartered, and Indian Overseas Bank were temporarily disabled, but bank status changes, so always check the live list.
• The reliable way to confirm support is to start the mandate-creation flow and see whether your bank is selectable and the authentication completes.

See also

• Zerodha eMandate: the complete overview
• How to set up a UPI eMandate on Zerodha
• How to set up a net-banking eMandate on Zerodha
• Setting up an eMandate on a joint account at Zerodha
• Zerodha eMandate daily limit
• Zerodha eMandate charges
• Zerodha eMandate troubleshooting
• How to cancel an eMandate on Zerodha

References

1. Zerodha Support, “Which banks support eMandates,” support.zerodha.com, observed 30 June 2026.
2. Zerodha Support, “eMandate registration failed,” support.zerodha.com.
3. Zerodha Support, “Setting up an eMandate,” support.zerodha.com.
4. Zerodha Support, “Setting up a UPI mandate on Zerodha Coin,” support.zerodha.com.
5. National Payments Corporation of India , live member-bank status for NACH and UPI AutoPay, npci.org.in.