Groww IPO UPI mandate not received on Google Pay

Social media users applying for IPOs via Groww are repeatedly flagging a familiar issue - the UPI mandate request does not show up on Google Pay, or the Groww status stays stuck on “sending UPI request”. The discussion is not about share fundamentals, but about the payment flow that blocks funds through UPI AutoPay and confirms the bid at the exchange. Many posts suggest the mandate exists but is hard to find inside UPI apps, especially when the app does not surface a notification. Others point to delays caused by third-party UPI rails, where the mandate arrives late and the broker app UI updates even later. Below is a practical summary of what people are doing, strictly based on the steps and explanations circulating in the threads.

What users are reporting across apps

Multiple users say they completed the IPO application in Groww, entered their UPI ID, and then did not receive the mandate prompt. In several cases, they could not see anything on Google Pay even after waiting, while the broker status still showed a pending request. Some comments add that the real issue can sit with the third-party UPI service, not necessarily with the exchange order itself. A parallel set of posts says the mandate approval happened, but Groww did not reflect it immediately. Others mention that the app demand load can cause delays, and the mandate may show up hours later. There is also caution from users not to “apply again” if the initial application was already submitted. The common thread is that the mandate is usually somewhere in the UPI app’s payment management section, not always as a pop-up.

First check - was the IPO application actually sent?

The first troubleshooting step shared is to confirm whether the application was sent from the broker app. Users advise checking the IPO section for the order you placed and looking for a status similar to “sending UPI request”. If you can see your applied IPO under the “applied” area, that typically means the order was initiated. Social posts explicitly warn against submitting another IPO application just because the mandate is not visible yet. The reasoning given is simple - if you already applied successfully and provided your UPI ID, reapplying can create confusion rather than fixing the mandate prompt. Some users also interpret an account debit as a sign that the application is through, but the system is lagging on status display. If you do not see your application listed at all, the discussion suggests rechecking the steps you used to place the bid.

Finding the mandate in PhonePe - refresh and Manage Payments

A large share of comments focus on PhonePe as the place where the request is actually visible even when Groww still says pending. The suggested flow is to open PhonePe and refresh one or two times to force the request to appear. Users then recommend scrolling and going into “Manage Payments” to check if any request is waiting for approval. If an option to approve is visible, the request has reached your UPI app and can be accepted from there. After approval, people say the interface typically shows a success confirmation for the UPI request. Several posts also point to the AutoPay area inside PhonePe as the place where IPO mandates can sit. If you approved there, you may only need to wait for the broker app to update the status. The repeated advice is to avoid repeated attempts in quick succession and instead verify the request in the UPI app’s management menus.

Finding the mandate on Google Pay - Auto-pay path shared by users

For Google Pay, the most repeated fix is to manually locate the pending mandate under Auto-pay rather than waiting for a notification. The steps shared are specific: open the Google Pay application, tap the profile icon on the top right, scroll down, and open “Auto-pay”. Users say the pending mandate can appear inside this list even if no alert was shown. You then open the pending mandate and authorize it to complete the approval. Some posters also discuss cancellations, noting that if AutoPay is configured through Google Pay, cancelling from the broker app may not automatically cancel the AutoPay setup in Google Pay. The practical takeaway is to confirm in both places if you are unsure about what got cancelled. If you have already authorized the mandate, the next issue is often just status refresh, not a missing bid.

Status not updated - but the bid may still be at the exchange

A common reassurance repeated in comments is that if you successfully approved the mandate in your UPI app, your bid has been placed at the exchange. Based on user guidance, the Groww status may still take time to reflect this, and the update can take 1-2 working days. Several users say people panic because they rely on the broker app status, even though the mandate approval is the key action. This is also why many posts recommend checking the UPI app first instead of repeating the order. The advice is framed as an operational delay rather than a failed IPO application. In this view, the UPI mandate is the decisive proof point, and the app status is secondary. If you are within the stated update window, waiting is the most common suggestion.

When to wait vs cancel and reapply

Some users suggest a simple time-based rule before taking action. One post says if you submitted the application before a certain time, you may only need to wait until later in the day for the mandate to show up. Another set of comments suggests waiting 8-9 hours because the UPI request can be delayed during high demand periods. If it has been more than 1-2 working days after you approved the mandate and you still suspect the bid may not be placed, users say you can cancel the request in the app and place a new request. A few users report that cancelling the initial request and submitting a new one triggered the mandate to arrive. However, the same threads also repeat the warning not to reapply blindly when the original application is already valid. The decision to cancel is presented as a fallback when normal waiting windows have clearly passed.

Groww UPI vs third-party UPI - what people claim works faster

One update shared widely claims the problem lies with the third-party UPI service used for mandates. In that context, posters say that if you submit your application through Groww using Groww’s UPI, you will not encounter the same issue and the status updates happen right away. This is presented as a workaround rather than an official fix. The discussion implies that the mandate flow can behave differently depending on which UPI handle or integration is used. Users do not provide technical details, but the pattern described is consistent: third-party UPI can delay the request or the status refresh, while Groww’s own UPI path appears smoother. For readers, the actionable part is to consider an alternative UPI route if you keep missing the notification. It is also a reminder to use the UPI app menus to locate mandates rather than waiting for a push notification.

Bank-side checks users keep mentioning - linkage and blocks

Beyond app UI issues, some comments point to bank-side controls that can block or delay UPI mandates. Users repeatedly say the bank account used for blocking funds should be your own, and it should be linked with PAN, because mismatches can create failures. One post gives an example of banks blocking sudden and substantial UPI transactions, especially when sending money to a new payee for the first time, and recommends waiting 24 hours after the last unsuccessful attempt. This is framed as an automated risk rule rather than a Groww-only problem. There is also a mention that a UPI mandate set above a certain monthly amount could trigger messages for some users, though the thread does not confirm it as the root cause. As a workaround, users suggest trying a different bank account or an alternative UPI application. Some also suggest shifting to a regular bank mandate if UPI mandates keep failing for recurring needs.

After allotment - when money unblocks and who to contact

Separate posts discuss what happens after allotment, focusing on when blocked funds get released. The guidance shared says the amount is usually unblocked within 3-10 working days after allotment. It also clearly states Groww does not handle blocking and unblocking, as the process is managed by your bank and the IPO RTA (Registrar and Transfer Agents). If the amount remains blocked even after 10 working days, the suggested escalation is first to contact your bank and ask them to unblock the amount. The second escalation route mentioned is to contact the IPO RTA, described as SEBI-registered entities responsible for allocating shares and processing refunds. This part of the discussion is important because users often blame the broker for a bank-side release process. The core takeaway is to separate mandate visibility issues during application from refund-unblock timelines after allotment.

Quick checklist from social posts

The steps below combine the most repeated checks users are sharing, focusing on where to look and when to wait.

This issue is trending because it sits at the intersection of broker UI, UPI app design, and bank controls. The consistent advice across posts is to confirm the mandate inside the UPI app first, avoid duplicate IPO applications, and allow for status update time when the mandate has already been approved.