How-to eMandate troubleshooting eNACH UPI AutoPay Zerodha

Zerodha eMandate troubleshooting

From WebNotes, a public knowledge base. Last updated . Reading time ~10 min. Level: Beginner.

An eMandate on Zerodha can stall in a few predictable ways: the registration fails outright, it sits pending for days, money leaves your account earlier than you expected, or the bank approval page refuses to open on an iPhone. Each has a different cause and a different fix, and treating one like another wastes time. This guide sorts the four common cases, so you apply the right remedy instead of recreating a mandate that just needs to be left alone. It pairs with the schedule an eMandate guide, which covers setting up transfers in the first place.

The single most useful move before you change anything is to read the mandate status on Zerodha Console . A failed mandate and a pending mandate look similar in a hurry, but the correct response is opposite: you recreate a failed one and you wait on a pending one. Start with the status, then match the symptom.

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.

Step-by-step procedure

The procedure infobox near the top of this page lists the diagnostic sequence. The sections below expand each of the four cases with the cause, the fix, and how to tell it apart from the others.

1. Check the mandate status on Console

Open console.zerodha.com/funds/mandates . Read the status column for the mandate in question. A mandate is typically Active, Pending, or in a failed or rejected state. The status is the fork in the road: it tells you whether to recreate, wait, or look elsewhere. Note the linked bank account and, if the mandate drives a SIP, the linked schedule, so you can confirm nothing else broke.

2. Identify the symptom

Match your situation to one of these four cases, each covered below:

  • Registration failed. The mandate never activated and shows as failed or rejected.
  • Registration pending over 5 days. The mandate was submitted but has not turned Active.
  • Money debited before the scheduled day. Funds left the account earlier than the date you set.
  • iOS Safari pop-up will not open. The bank approval page does not appear on an iPhone.

Registration failed

A failed registration means the bank could not authenticate the mandate. The common causes are on your side of the flow or your account type:

  • The authentication window was closed before you entered your credentials. The mandate is approved on your bank’s gateway, and closing that page early leaves the registration incomplete.
  • The netbanking or debit-card credentials entered were incorrect.
  • The account does not permit eMandates. Banks commonly block eMandates on current, joint, and NRE-PIS accounts.

Zerodha cannot determine the specific reason for a failure; only your bank has that information, because the bank runs the authentication. So the diagnostic step is to check with your bank if a retry does not work.

The fix for a failed registration is to recreate it from Console. Start a fresh mandate, and this time complete the bank authentication fully: do not close the approval window, and enter the correct credentials. If it still fails after a careful retry, and your account type is the blocker, switch to a supported account or use the beneficiary route described below. For the difference between the UPI AutoPay and netbanking eMandate registration paths, see the setup guides, since the authentication step differs between them.

Registration pending over 5 days

A mandate that stays pending past 5 days is usually waiting on the bank to confirm it. This is a different problem from a failure. The mandate was submitted correctly; the bank simply has not sent back its confirmation.

Zerodha cannot provide a timeline for successful verification, though it periodically follows up with the respective banks. Because the request is already in the bank’s queue, recreating it does not help and can produce duplicate mandates. The correct action is to wait, and if the mandate stays pending, raise a support ticket through the Zerodha support portal with the mandate reference so the follow-up is on record.

Keep this case distinct from a failed registration. A failed mandate calls for a recreate. A pending mandate calls for patience and, if it drags, a ticket. Recreating a pending mandate is the most common wrong move here.

Money debited before the scheduled day

If money left your account before the date you set on the schedule, check the timing before treating it as an error, because it usually is not one. The bank debits your account one working day before the scheduled eMandate date so the funds settle in time for the transfer or SIP. A transfer scheduled for the 5th is debited on the working day before.

You are also told in advance. Zerodha and your bank send an SMS and an email one day ahead of the debit. So the normal sequence is: notification one day before, debit one working day before the scheduled date, and the funds credited or the SIP applied on the scheduled date. If the debit matches that one-working-day-prior pattern, nothing is wrong and there is no action to take. This is the same behaviour described in the schedule an eMandate guide. If a debit does not match any schedule you set, or the amount is wrong, raise it with Zerodha support with the mandate reference.

iOS Safari: bank pop-up will not open

On an iPhone, the bank’s mandate-approval page opens as a pop-up, and Safari on iOS blocks pop-ups by default. When that happens, the authentication window never appears, so the mandate cannot be authorised and the registration stalls.

The fix is to let the pop-up through. Allow pop-ups for the bank page in Safari’s settings, then restart the mandate flow so the approval window can open. If that does not work, complete the mandate on a different browser or on another device. The exact Safari setting path can change with iOS versions, so follow the current steps in Zerodha’s official article, linked under external references below, rather than an out-of-date menu path. Once the pop-up opens and you authenticate, the mandate proceeds as normal.

When to use the netbanking beneficiary route instead

If the eMandate route keeps failing, whether because of the account type or repeated authentication problems, there is a fallback that does not use an eMandate at all. Add Zerodha’s designated account as a beneficiary in your bank’s netbanking, then set up a standing instruction to transfer funds on a schedule. The bank then pushes the money on the dates you set.

This route also helps holders of joint accounts, where some banks do not allow eMandates. The trade-off is that a standing instruction is managed entirely in your netbanking, not on Console, so you cannot pause or edit it from the Zerodha side. For funding a SIP through this route, make sure the transfer lands before the SIP date, using the same lead-time logic as a scheduled eMandate.

A few adjacent problems have their own guides:

Frequently asked questions

Why did my Zerodha eMandate registration fail?
The bank authentication did not complete, usually because the approval window was closed before entering credentials, the credentials were wrong, or the account type is not permitted. Current, joint, and NRE-PIS accounts often cannot create eMandates. Only your bank has the exact reason.
Should I recreate a mandate that is still pending after five days?
No. A pending mandate usually means the bank has not confirmed it yet. Wait, and raise a support ticket on the Zerodha portal. Recreating is the fix for a failed registration, not a pending one, so keep the two cases separate.
Money left my account before the scheduled eMandate date. Is that an error?
No. The bank debits your account one working day before the scheduled transfer date so the funds settle in time. You also receive an SMS and an email one day in advance. Early debit by one working day is expected.
Why will the bank approval pop-up not open on my iPhone?
Safari on iOS blocks the bank’s mandate-approval pop-up by default, so the authentication window does not open. Allow pop-ups for the page in Safari settings, or complete the mandate on a different browser or device.
Zerodha says it cannot tell me why my mandate failed. Why not?
Zerodha only submits the mandate to your bank for authentication. The bank runs the verification and holds the reason for any rejection, so Zerodha cannot see the specific cause. You will need to check with your bank directly.
My registration keeps failing. What is the alternative?
Add Zerodha’s account as a beneficiary in your netbanking and set up a standing instruction to transfer funds on a schedule. This bypasses the eMandate route entirely while still automating your transfers.
Can I set up an eMandate from a joint account?
Some banks do not allow eMandates from current, joint, or NRE-PIS accounts. If yours does not, use a primary or secondary savings account, or the netbanking beneficiary route instead.

See also

External references

References

  1. Zerodha Support, “Why did my eMandate registration fail?” support.zerodha.com.
  2. Zerodha Support, “eMandate registration is pending for more than 5 days,” support.zerodha.com.
  3. Zerodha Support, “Money debited before the scheduled date,” support.zerodha.com.
  4. Zerodha Support, “Setting up an eMandate on the Safari browser,” support.zerodha.com.
  5. Reserve Bank of India , “Framework for processing of e-mandates for recurring transactions,” RBI/2019-20/133, January 2020.

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.