How-to IPO rejection Kite UPI mandate PAN mismatch Third-party UPI ASBA

How to avoid IPO application rejection on Kite

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

An IPO application on Zerodha Kite can be rejected even after the app shows it submitted, because the application is finally validated by the exchange and the registrar , not by Zerodha. The registrar de-duplicates and verifies every bid against PAN before the basis of allotment is drawn, and an application that fails any check is dropped before the lottery runs. This guide is a pre-submit checklist to clear every one of those checks, so your bid reaches the draw as a valid application.

It is written for the retail applicant bidding through Kite who wants a single, complete list of what causes rejection and how to fix each one before the issue closes. The mechanics are the same on the Kite app, Kite web and Zerodha Console , because the rejection logic lives at the registrar and follows SEBI rules common to every UPI-ASBA broker.

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 numbered infobox at the top lists the checklist in order. The sections below expand each check, the exact failure it prevents, and how to recover where recovery is possible.

1. Confirm one application per PAN

SEBI permits one application per PAN per category per issue. The registrar identifies the applicant by PAN and de-duplicates on it, so two applications under the same PAN, whether from two brokers, two demat accounts, or two family members sharing a PAN by mistake, cause the registrar to reject every one of that PAN’s bids, including the first. This is the single most common avoidable rejection. Decide one platform per IPO for each PAN and apply once. If a household wants more entries, each adult applies under their own distinct PAN, not the same PAN twice. A duplicate-PAN rejection cannot be reapplied, because the rejection is issued by the exchange after the window, so this check has to be right before you submit.

2. Match PAN across demat, bank and UPI

The registrar’s third-party verification cross-checks the applicant’s PAN against the demat linked to that PAN and the bank account linked to that PAN. If the PAN on your demat does not match the PAN on your bank account, or the name on your PAN does not match the bank record, the verification fails and the application is rejected. Because the allotted shares are credited to the demat linked to the PAN, any PAN mismatch makes the credit impossible. Confirm that the PAN on your Zerodha demat, your linked bank account, and the bank account behind your UPI handle are identical, and that your PAN is linked to Aadhaar, before applying.

3. Use only your own UPI handle and bank account

The bank account behind the UPI ID used for the IPO must belong to the same investor whose PAN is on the demat. A UPI handle backed by a spouse’s, parent’s or friend’s bank account is a third-party payment and is rejected at the verification stage. This catches people who keep their primary UPI on a joint or family account. Pick a UPI ID whose underlying account is in your own name and is the same account linked to your Zerodha profile. If your default UPI app routes through a third-party account, add and select a UPI handle on your own account before bidding.

4. Keep sufficient available balance

The IPO amount is blocked, not debited, but the mandate still needs the full bid value as available balance at the moment the bank processes it. A balance below the bid value can cause the mandate to fail or the bank to decline the block, which leaves the application incomplete. Keep the full bid value clear in the linked account from the time you submit until the mandate is approved, and do not schedule other large debits against that balance in the same window. This failure is recoverable: if a mandate is declined for funds, you can top up and reapply with a fresh bid while the issue is still open.

5. Approve the UPI mandate before 5 pm on closing day

Submitting the bid in Kite is only half the application. Your UPI app receives a collect or mandate request that you must authorise with your UPI PIN, which places the block. The deadline to approve the mandate is 5 pm on the issue’s closing day. A mandate approved at 5:01 pm, or never approved, makes the application void even though Kite still shows it as submitted. Approve the mandate as soon as it arrives rather than waiting; mandate requests can be delayed by UPI-app or bank-server load near the deadline, which is covered in how to fix a UPI mandate timeout for an IPO . Check your UPI app’s mandate or pending-request list to confirm the block is in place.

6. Bid at cut-off and within the lot rules

Bid at the cut-off price so the bid accepts whatever final price is set within the price band and is never below the final issue price. A bid pegged at a specific price below the eventual issue price is invalid for allotment. Apply in whole lots , at least the minimum lot, and keep the total within the Rs 2 lakh retail ceiling unless you intend to apply as a non-institutional investor. A malformed quantity, a sub-lot quantity, or a retail bid that crosses the retail ceiling can be rejected or reclassified.

7. Check the demat is active and unfrozen

The application also fails if the receiving demat cannot take the credit. A demat account that is frozen, dormant beyond reactivation, or whose PAN is flagged or barred by SEBI causes a registrar-side rejection. A PAN de-linked from Aadhaar can render the PAN inoperative, which also fails verification. Before applying, confirm the demat is active and unfrozen, and resolve any frozen-demat or PAN-verification issue first.

8. Verify the bid and mandate status after submitting

After submitting, do not assume completion. In Kite, open Bids and confirm the bid shows a confirmed status rather than pending. In your UPI app, confirm the mandate shows approved or active. One day after bidding, re-check the status on the registrar’s portal or the NSE IPO portal using your application number. Catching an incomplete application while the window is still open is the only point at which a fixable failure can be corrected by deleting and reapplying.

Rejections you can reapply for, and those you cannot

The recovery path depends on the failure. A rejection for insufficient funds, a declined mandate, or a mandate not yet approved is fixable while the issue is open: delete the pending or failed bid in the IPO section, ensure funds and the correct UPI handle, and submit a fresh application. A duplicate-PAN rejection is not fixable, because it is issued by the exchange after the window closes and signals that the same PAN already applied. Once you see a “multiple applications with the same details” rejection, there is no reapplication for that issue. This is why the one-application-per-PAN check is first: it is the only one with no second chance.

How rejection differs from non-allotment

A rejected application never enters the lottery; a valid application that simply loses the draw is “not allotted.” The two have different fund consequences. For a rejection where no block was ever placed, there is nothing to release. For a valid but non-allotted application, the block was placed and is released automatically after the basis of allotment, covered in how to release blocked IPO funds after non-allotment . Reading a “not allotted” status as a “rejection” sends people chasing a refund that is already on an automatic timeline. Check the precise status wording on the registrar portal before deciding whether anything needs fixing.

Regulatory basis

The verification that rejects invalid applications sits in SEBI’s ICDR framework and the registrar’s third-party verification duties, strengthened by SEBI circular SEBI/HO/OIAE/OW/P/2022/0001 dated 4 January 2022, which tightened the cross-linking of PAN, demat and UPI handle to cut benami and duplicate applications. The 5 pm closing-day mandate cutoff and the one-application-per-PAN rule are part of the UPI-in-public-issue process notified through NPCI and SEBI from 2019 onward. These are not Zerodha policies; they bind every broker offering UPI-ASBA IPO applications.

See also

External references

References

  1. SEBI (Issue of Capital and Disclosure Requirements) Regulations, 2018, registrar verification and basis-of-allotment provisions.
  2. SEBI circular SEBI/HO/OIAE/OW/P/2022/0001 dated 4 January 2022, strengthened PAN, demat and UPI cross-verification against duplicate and benami applications.
  3. SEBI, FAQs on UPI in the public issue process, July 2019 (5 pm closing-day mandate approval cutoff; one application per PAN).
  4. NPCI UPI 2.0 one-time mandate (block) specification for public issues.

WebNotes Editorial Team prepares factual how-to guides based on publicly available regulatory documents and broker disclosures. WebNotes is not affiliated with Zerodha Broking Limited. Procedures and rejection rules are subject to change; verify current requirements at support.zerodha.com before acting.

Reviewed and published by

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.