IPO UPI ASBA UPI handle NPCI PSP Zerodha IPO

Why some UPI handles are not shown on the Zerodha IPO window

From WebNotes, a public knowledge base. Last updated 21 June 2026. Reading time ~12 min.

Key facts

Root cause	The Kite window only accepts handles whose bank is live for UPI ASBA on the NPCI IPO partner list
Not a Zerodha restriction	Zerodha keeps no separate handle list; it offers whatever NPCI shows as live
Handle structure	A handle's suffix names its PSP bank, for example @okhdfcbank, @ybl, @paytm, @ibl
Third-party-app handles	Route through a PSP sponsor bank; a bank-direct handle routes through your own bank
Common fix	Switch to a bank-specific handle on the same account, or to a different supported bank
Last resort	Apply through bank ASBA via NetBanking, which does not use the UPI handle list

A UPI handle is missing or rejected on the Zerodha Kite IPO window when the bank behind that handle is not live for UPI ASBA on the NPCI IPO partner list, or when the handle’s payment service provider (PSP) route is not certified to carry the one-time block mandate . It is not Zerodha blocking your app. The Kite window keeps no separate roster of approved handles; it offers whatever banks NPCI currently shows as live, so a missing handle is an NPCI-eligibility symptom surfacing on the broker screen. This article explains the handle structure, the third-party-app versus bank-app distinction, the certification status that decides acceptance, and how to pick a handle that works.

The confusion is understandable, because the same UPI handle you use to pay a shopkeeper every day may not appear in the IPO dropdown. Everyday UPI payments and IPO block mandates run on different NPCI rails: a normal pay is a push transfer, while an IPO block is a one-time AutoPay mandate that the issuer bank and the PSP must both be certified to handle. A handle can be perfectly live for payments and not yet live for IPO mandates, which is why “it works for paying” is not evidence it will work for bidding.

How a UPI handle is structured

A UPI handle is the part after the @ sign in your UPI ID, and it names the bank acting as the PSP for that ID. The suffix tells you which bank’s rails the mandate will travel on.

Handle suffix	App that issues it	PSP bank
@okhdfcbank, @okaxis, @oksbi, @okicici	Google Pay	The named bank as PSP
@ybl, @ibl, @axl	PhonePe	Yes Bank, ICICI Bank, Axis Bank as PSP
@paytm	Paytm	Paytm’s PSP bank
@upi	BHIM	Yes Bank as PSP
@hdfcbank, @axisbank, @sbi (bank-own apps)	The bank’s own UPI app	The same bank, direct

The handle that decides IPO acceptance is the PSP bank behind the suffix, paired with your own issuer bank where the funds sit. Both must be live for the IPO mandate. A name@okhdfcbank handle on an Axis Bank account, for instance, depends on HDFC Bank as PSP and Axis Bank as issuer; if either is not live for IPO UPI, the handle is not offered.

Third-party-app handles versus bank-app handles

This distinction is the key to fixing a missing handle. A third-party app such as Google Pay, PhonePe, or Paytm is a Third-Party Application Provider (TPAP) under NPCI’s framework; it does not hold your account and routes every transaction through a partner PSP sponsor bank. So a Google Pay handle on your SBI account routes the mandate request through Google Pay’s PSP bank, not through SBI directly. A bank-own UPI app, by contrast, routes the mandate through your bank as both issuer and PSP, with no third-party hop.

When a third-party-app handle is not accepted on the IPO window, the cause is often the PSP route rather than your bank. The remedy is to create a bank-specific handle for the same account, either a bank-direct handle in your bank’s own UPI app, or a bank-mapped handle within the third-party app. A handle that routes directly through your bank removes the PSP dependency and frequently resolves a “UPI app not supported” message. How to create a BHIM UPI ID for an IPO shows the bank-specific-handle path on BHIM.

Certification status decides acceptance

NPCI certifies which banks and PSP routes can carry the IPO block mandate, and it reviews the list periodically. Three certification states explain almost every missing handle:

The issuer bank is not live for IPO UPI. Payments banks and merchant categories are excluded outright. Some smaller banks have not yet been certified for the IPO mandate even though they support ordinary UPI. The handle simply does not appear.
The PSP route is not certified. A third-party app’s sponsor PSP may not be live for the IPO mandate for your issuer bank, so the specific app-plus-bank combination fails while the same account works through a bank-direct handle.
A temporary outage or certification gap. A bank or PSP live last quarter can drop off during an outage. This is why a handle that worked for your previous IPO is sometimes not accepted for the next one; check the current NPCI list, do not assume continuity.

Because eligibility is a live, reviewed list, the authoritative check is always the NPCI UPI for IPO live partners page at npci.org.in, cross-referenced in which apps and banks support UPI ASBA .

How to pick a working handle

Work through the options in order, from least to most disruptive:

Use a handle on a bank you know is live. Confirm your issuer bank appears on the NPCI IPO partner list before you bid. A scheduled commercial bank or a mainstream small finance bank is almost always live.
Switch from a third-party-app handle to a bank-direct handle on the same account. If name@ybl is not accepted, try the same account’s handle through your bank’s own UPI app, which removes the PSP dependency.
Switch to a different supported bank account in your own name. The account must still be yours, under your demat PAN, because a third-party account is rejected at verification regardless of the handle.
Apply through bank ASBA via NetBanking. This blocks the money through your bank as the SCSB and does not use the UPI handle list at all. See how to apply for an IPO without UPI on Kite and bank ASBA via NetBanking .

The handle problem versus the mandate problem

A handle that is not shown on the IPO window is a different failure from a mandate that arrives but is not approved in time. The first is an eligibility question, solved before you bid by picking a live handle. The second is a timing or delivery question, where the handle is accepted, the bid is placed, but the mandate does not reach the app or is approved after the 5 PM IST cutoff on the closing day. If your handle is accepted but the mandate never arrives, that is the second problem; see how to fix a UPI mandate timeout for an IPO and the per-app approval guides for BHIM , Google Pay , and PhonePe . The own-account requirement, that the handle and bank account be yours under the demat PAN, is covered in the bank account linked with the UPI ID for an IPO .

References

NPCI, Apply for IPO using UPI ID product overview and UPI for IPO live partners list, npci.org.in (periodic review; issuer-bank and PSP eligibility for the IPO mandate).
NPCI, FAQs on UPI 2.0 IPO for Customer, npci.org.in (one-time block mandate; third-party UPI ID liable for rejection).
NPCI guidelines on Third-Party Application Providers (TPAP) and PSP sponsor-bank routing under the UPI procedural framework.
SEBI, FAQs on the use of Unified Payments Interface (UPI) with ASBA in public issues, April 2022 (retail individual investor UPI route; own UPI ID requirement).

External references

Frequently asked questions

Why is my UPI handle not shown on the Zerodha IPO window?

The Kite IPO window only accepts handles whose underlying bank is live for UPI ASBA on the NPCI IPO partner list. If your handle is not shown, your bank is likely not live for IPO UPI, or the handle’s PSP route is not certified for the mandate.

Is Zerodha blocking my UPI app?

No. Zerodha keeps no separate roster of approved handles; the IPO window simply offers whatever banks NPCI currently shows as live. A missing handle reflects NPCI eligibility, not a Zerodha block on your app.

What is the difference between a third-party-app handle and a bank-app handle?

A third-party-app handle like @okhdfcbank or @ybl routes the mandate through a PSP sponsor bank chosen by the app. A bank-app handle routes through your own bank directly. When a third-party handle fails, a bank-direct handle on the same account often works.

How do I pick a UPI handle that works for an IPO on Zerodha?

Pick a handle on a bank that appears live on the NPCI IPO partners list, mapped to your own account under your demat PAN. If your usual handle is not accepted, create a bank-specific handle for the same account, or use a different supported bank.

My handle worked last IPO but not this one. Why?

NPCI reviews the partner list periodically, and a bank or PSP route can drop off during an outage or certification gap. A handle live last quarter may be temporarily unsupported; check the current NPCI list rather than assuming continuity.

What if no handle of mine is accepted?

Apply through bank ASBA via NetBanking, which blocks the money through your bank as the SCSB and does not depend on the UPI handle list at all. This route carries every investor category and amount.

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: 21 June 2026
Conflicts of interest: WebNotes is independent. No relationship with any broker, registrar or bank named in this article.