PAN mismatch: Why IPO UPI bids get rejected in India

Retail investors on Reddit and other social platforms have been swapping notes on a frustrating pattern: IPO applications that look “submitted” but later show “bid rejected” or fail silently at mandate stage. Much of the discussion points to a small set of repeat errors that are avoidable if caught early. The most common themes are PAN-linked validation, UPI mandate execution, and basic data accuracy across demat and bank records. Several posts also highlight that technical problems can look like rejection, even when the root cause is simply a mandate that never reached the investor. Another recurring point is that registrars and systems de-duplicate applications based on PAN, so duplicate attempts can backfire. Below is a summary table of the reasons repeatedly cited online and the immediate checks investors say helped.

Why PAN mismatch and UPI rejections are trending

Viral threads repeatedly mention “PAN mismatch” and “UPI rejection” as the top explanations investors hear after a failed IPO attempt. Many posts describe the same experience: the application is placed, but the mandate is not approved or the bid later shows as rejected. Users also point to errors like wrong PAN entry, mismatched demat details, incorrect bank account number, or insufficient funds. Another often repeated claim is that the UPI ID must match the applicant’s bank account and name, otherwise it is treated as a third-party application. Some commenters add nuance by saying third-party cases sometimes appear to pass, but can be filtered out if the registrar applies stricter checks. The discussion is also fueled by people applying through multiple apps or brokers to “increase chances” and then seeing every linked bid rejected. Hindi posts circulating alongside these threads emphasise one simple idea: avoid data mismatches and apply at cut-off, while using separate family members’ accounts if each has their own valid PAN. Across platforms, the main takeaway is that rejections are often procedural, not market-related.

One PAN, one IPO application: the de-duplication rule

A dominant theme in the threads is the “multiple bids on one PAN” mistake. Posters repeatedly state you can submit only one retail application per PAN for a single IPO. If an investor applies through two brokers, or applies once via broker and once via net banking, the registrar can reject every linked bid after PAN-based validation. Several users describe this as the most common avoidable rejection because it is fully within the investor’s control. Social posts also warn that even if the bank account or broker differs, PAN remains the unique identifier for de-duplication. A related point shared is that having a family member apply “on your behalf” using your PAN can still trigger rejection, because the PAN is not unique anymore for that issue. Some threads mention that certain IPOs may have reserved categories such as employee or shareholder quotas, where one application under individual and one under a reserved category using the same PAN can be allowed. Those posts stress it is an exception and depends on eligibility, so unsure investors should keep it to one. The practical implication from these discussions is simple: pick one platform and stick to one application per PAN per category.

PAN and bank account mismatch: third-party red flags

Another repeated explanation is that the UPI handle used for mandate approval should belong to a bank account in the applicant’s own name. Users say that using a spouse’s or friend’s UPI ID can break the third-party rule and lead to rejection. Several posts broaden this into “identity chain” matching, where PAN name, demat name, and bank name should align closely. A specific scenario discussed is joint accounts where the applicant is the second holder, because some UPI systems may fetch only the primary holder’s name. In that case, commenters suggest generating a UPI ID from an account where the applicant is the primary holder, then using that handle for IPO mandates. At the same time, social feeds also contain counter-claims that a strict PAN mismatch between demat and UPI-linked account does not always cause rejection, based on individual experiences shared online. Other replies challenge those experiences and argue the outcome can vary with registrar filtering of third-party applications. The consistent part across both sides is that mismatches increase the probability of additional scrutiny and failure. The safest approach repeated across threads is to keep PAN, demat, and the mandate-approving bank account in the same name.

The 5:00 PM deadline and why timing matters

Timing around mandate approval is a major source of missed applications, according to multiple posts. The UPI mandate must be accepted by 5:00 PM on the IPO closing day, as repeated across threads. Users warn that approving even a minute late does not count, and funds may never be blocked. Several commenters highlight that investors often apply early but forget to approve the mandate until the last hour. Others say the mandate can be attempted any time before the issue closes, so the investor should keep funds available even after applying. A common tip is to approve the mandate the same day the application is submitted, not on the deadline. Threads also caution against waiting until 4:55 PM, because network delays, app issues, or notification delays can push approval past the cutoff. Some posts recommend checking the “pending requests” or “mandates” section in the UPI app instead of relying on notifications. If the IPO is still open and the mandate has clearly failed, investors discuss cancelling and reapplying after correcting the issue. Overall, these discussions treat mandate timing as a basic operational step, not something to manage at the last minute.

Wrong UPI ID, inactive handle, and app glitches

Beyond identity and rules, users frequently blame simple UPI input errors. A typo in the UPI ID, or using an ID not linked to an active account, can prevent the mandate request from reaching the investor at all. Threads also mention that sometimes the UPI ID entered does not match the user’s active bank handle, leading to confusion when the mandate never appears. Outdated UPI apps are cited as a frequent cause, with commenters advising updates before asking the broker to resend the mandate. App glitches and intermittent failures are also mentioned, especially when investors try to approve close to the deadline. Another recurring tip is to open the UPI app and manually check pending mandates, because the request can sit inside the app without a clear push notification. Posts also remind investors to enter the correct UPI PIN on the first try, because failed attempts can lead to mandate failure or delays. If no mandate shows up within an hour, some users suggest cancelling the bid inside the broker app and submitting a fresh one with corrected details while the issue is still open. Taken together, the social consensus is that many “rejections” start as a mandate delivery problem, not a registrar decision.

Insufficient funds, transaction limits, and retail caps

Insufficient balance is repeatedly listed as a direct reason for mandate failure. If the bank cannot block the full bid amount when it attempts the mandate, the mandate can fail and the application can lapse. Commenters stress that the money should remain available and untouched until allotment, because the block can be attempted before the issue closes. Some posts also mention transaction limits as a practical obstacle, where the account may have funds but the mandate amount exceeds the bank or UPI limit. Retail category limits are also discussed, with threads stating that retail investors cannot apply for more than Rs 2,00,000, and exceeding category limits can lead to rejection of the entire application. A related point is that selecting the wrong investor category can create avoidable validation issues. Users who apply via net banking (ASBA) also note that manual data entry increases the chance of mistakes in bank or demat fields. A few posts bring up KYC issues such as PAN being unverified or “on hold” at the KRA as another rejection trigger. Another claim seen in threads is that if PAN is not linked with Aadhaar, a trading account can be technically frozen, potentially impacting IPO applications. The recurring message is to treat funding and eligibility checks as part of the application, not an afterthought.

Demat details and bid choices that trigger rejection

Demat accuracy is another repeated pain point, especially for investors not using pre-filled broker flows. Threads warn that wrong DP ID or client ID can result in rejection because shares cannot be credited even if an allotment would otherwise occur. Users also mention “wrong PAN” entry when typing details manually, including mixing up digits. Bidding below cut-off in a book-built IPO is cited as a simple mistake that can lead to rejection if the final issue price is above the bid price. As a result, many posts advise applying at the cut-off price to avoid price-related invalidation. The social conversations also link demat mismatches with PAN mismatch, arguing the PAN linked to demat must align with the PAN used during the IPO application. In addition, discussions about third-party applications frequently connect back to demat ownership, because the credited shares must go to the correct beneficiary account. Several threads highlight that technical “bid rejected” messages often do not clearly state whether the problem was demat, PAN duplication, or mandate failure. That ambiguity is why checklists and step-by-step verification posts have become popular. Investors consistently say that careful data entry and cut-off bidding remove a large portion of rejection risk.

A step-by-step checklist investors are sharing

The most repeated habit is to apply once per PAN per category and avoid duplicate submissions across platforms. Users say the next priority is to ensure the UPI ID is correct and tied to an active bank account in the applicant’s own name. Right after placing the bid, posters recommend opening the UPI app and checking pending mandates instead of waiting for notifications. If the mandate is missing, the common advice is to update the UPI app and ask the broker to resend the request. Threads also emphasise holding the full bid amount in the account until allotment, because insufficient funds can cause the mandate to fail. Timing is treated as non-negotiable, with multiple posts repeating that approval must happen before 5:00 PM on the closing day. If the mandate does not arrive within an hour and the issue is still open, some investors suggest cancelling and reapplying after fixing UPI ID or account issues. The final check investors keep repeating is to confirm demat identifiers and avoid typos, especially when applying via net banking. Across these discussions, the “best practice” approach is operational discipline: correct identity chain, one application per PAN, sufficient funds, and early mandate approval.