This one causes more arguments at shop counters than almost any other payment problem. The customer holds up a phone showing a green tick. The shopkeeper checks and sees nothing. Each thinks the other is mistaken, or worse.
A successful UPI payment is a strong signal, but it answers a narrower question than people assume. It tells you your bank debited you and the receiving side accepted the credit. It doesn't tell you which account that was, whether the merchant's app has caught up, or whether the money has been passed on from the merchant's payment provider yet. Those gaps are where most of these disputes live.
This guide is for the case where your app shows success. If it shows pending, read UPI payment pending first. If it shows failed and you were debited, money debited but transaction failed covers RBI's reversal deadlines.
What "successful" means in UPI
UPI marks a payment successful when both legs are done: your bank has debited your account and the receiving side has accepted the credit. For a payment to a shop or website, the receiving side is the merchant's payment service provider (its "payee PSP"), which in UPI is also called the acquirer.
So the money has left you and been accepted by the merchant's side of the system. Where it lands next depends on how the merchant is set up, and that's what decides when the merchant actually sees it.
Where the money usually is
Ask the merchant one question first: how do you take UPI? The answer tells you where a successful payment goes.
| How the merchant takes UPI | Where the payment lands | Where the merchant should look |
|---|---|---|
| A small-merchant QR linked to their own account | Straight into the merchant's bank account. NPCI's rules require small-merchant ("P2PM") payments to be credited to the merchant's own account in real time. | Their bank SMS, bank app or soundbox |
| A merchant QR or UPI ID from their bank | The merchant's account with that bank | The bank's merchant app or statement |
| A payment aggregator or online checkout | The aggregator's escrow account first. It pays the merchant later, on the schedule in their agreement. | The aggregator's dashboard, searching by the payment reference, not the bank account |
| A marketplace or platform | The marketplace, which pays its sellers on its own cycle | The seller dashboard |
Why a merchant may not see a successful payment
In rough order of how often they come up:
- Looking in the wrong place: the bank account instead of the payment provider's dashboard, or the dashboard for the wrong outlet or QR.
- Settlement hasn't happened yet. The payment succeeded, but the provider hasn't paid it out, or paid it out as part of a combined amount net of fees.
- The notification didn't fire. A soundbox lost its connection, or the merchant app hasn't refreshed. The payment is in the transaction list even though nothing was announced.
- An online order wasn't updated. The payment went through, but the message that tells the store's system (a webhook) didn't arrive, so the order still says unpaid.
- The customer paid a different account: an old QR from a previous owner, another branch's QR, or a fraudulent sticker placed over the real one.
- A rare case the banks still have to settle. If the receiving bank didn't confirm the credit in time, UPI treats the payment as "deemed" and the banks resolve it when they reconcile, by completing the credit or reversing your debit.
If you paid: four things to do
Your aim is to give the merchant enough to find the payment in their own system, without paying a second time.
- Open the payment in your app and note the UPI reference number. It's the 12-digit RRN, which many apps label UTR. Our explainer on RRN and UTR shows where to find it.
- Check who you paid. Your app shows the receiver's name: for a verified business its validated brand name, otherwise the name on the bank account. If that isn't the shop's name, you may have scanned the wrong QR.
- Share the reference number, amount, date and time with the merchant, and ask them to search for it rather than scroll through their payments.
- Don't pay again until they've searched. If they confirm they can't find it and the receiver's name is theirs, raise a complaint in your UPI app.
If you're the merchant: check this before asking for payment again
Most of these cases end the moment someone searches the right list for the reference number. Your payment provider is required to give you a way to check a payment's status in real time, and a summary of your transactions with their refund status. Use them.
- Search your provider's dashboard by the customer's reference number (RRN/UTR), not by amount. Two customers paying ₹499 within minutes look identical by amount.
- Confirm which QR, UPI ID or outlet the customer used. Check the receiver name on their screen against your own.
- Separate transactions from settlements. A payment appears in your transaction report immediately; it reaches your bank only when it's settled.
- For online orders, check the payment's status through your provider's status API and look for a failed webhook. If the payment is captured, update the order.
- If you still can't find it, ask the customer for a screenshot of the receipt with the reference number, and raise it with your provider. Every payment aggregator must have a dispute process with timelines and a named officer for merchants' complaints.
Why asking the customer to pay again backfires
It's tempting to settle the argument by asking for a fresh payment. Usually, this just turns one problem into two.
A better approach for counters: mark the sale "payment under verification", take a phone number and the reference, and settle it once you've searched. For online stores, hold the order in a pending state and let reconciliation confirm it. Our guide to payment reconciliation shows how to match payments to orders every day so these cases surface on their own.
- If the first payment did reach you, you now owe a refund. Through an aggregator, refunds go back to the customer's original payment method, which takes time and paperwork.
- The customer remembers being charged twice long after they've forgotten the shop.
- If it's a deemed payment that's later reversed, the customer gets the first payment back automatically and you've lost nothing by waiting.
Three cases, and how each ended
These are typical patterns. The amounts are examples.
The silent soundbox
A customer pays ₹640 at a grocery counter with a static QR. The soundbox says nothing, and the shopkeeper asks for cash. The customer shows a successful payment with a reference number. The shopkeeper opens the bank app: the ₹640 credit is there, received a minute earlier. The soundbox had dropped off the shop's Wi-Fi. Lesson: a missing announcement is not a missing payment.
The order that stayed unpaid
A customer pays ₹4,999 for an online order. Their app shows success, but the store marks the order "payment pending" and sends a reminder. The store's payment dashboard shows the payment captured; the webhook to the store's system had timed out. The store fixes the webhook and updates the order. The ₹4,999 reaches the store's bank the following day as part of a larger settlement, after the provider's fees. Lesson: online stores should confirm payments by status check, not by whether the browser came back.
The old QR
A café changes hands, but an old QR card is still on one table. A customer pays ₹1,100 to it. Their receipt shows the previous owner's name, not the café's. The café never received it, and nothing on its side can find it. Lesson: the receiver name on the customer's screen is the quickest way to spot a wrong QR, and merchants should remove old QR codes the day they stop using them. The customer's route here is a complaint to their own bank with the reference number.
Raising a complaint, and escalating
Start with the side that can see the money.
- Customer: raise it in your UPI app, which must let you register and track complaints, including service issues with merchant payments. NPCI's UPI Help service also shows a payment's status and takes complaints.
- Merchant: raise it with your payment provider or bank, quoting the reference number, amount, date and time.
- If you were debited and the merchant genuinely received nothing, RBI's rules require the debit to be reversed within T + 5 days for merchant payments, with ₹100 a day in compensation after that.
- If your bank doesn't resolve it within 30 days, or you're not satisfied with the answer, you can take it to the RBI Ombudsman. The process is set out in our guide to money debited but transaction failed.
Frequently asked questions
My UPI app shows successful but the merchant shows pending. Who is right?
Usually both. Successful means your bank debited you and the merchant's side accepted the credit. The merchant may be looking at an order or a bank account that hasn't been updated yet. Give them the reference number (RRN/UTR) so they can search their payment provider's records directly.
How long does a UPI payment take to reach a merchant's bank account?
It depends on the set-up. Small merchants using a QR linked to their own account are credited in real time. Merchants using a payment aggregator are paid out on the schedule in their agreement with the aggregator, which RBI requires to state the settlement timeline clearly, and usually as one combined amount after fees.
Will I get my money back if the merchant didn't receive it?
If the payment didn't actually reach the merchant's side, your bank must reverse the debit within T + 5 days for merchant payments, or pay you ₹100 a day after that. If the money reached the merchant but they can't find it, it's a matter of them searching their records, not a reversal.
The receipt shows a different name from the shop. What does that mean?
You probably paid a different account, such as an old or tampered QR. UPI apps show the receiver's verified brand name or bank-registered name, not a name typed into the QR, so a mismatch is a real warning sign. Complain to your bank with the reference number.
Can the merchant ask me to pay again?
They can ask, but it's better to search first. If you do pay again and the first payment later turns up, the merchant owes you a refund of one of them. Keep both reference numbers.
Go deeper
Official sources
- NPCI — UPI Consolidated Circular, Version 1.0, NPCI/UPI/CC/01 (18 Sep 2026)Bank-registered (CBS) name shown before paying (2.13); verified brand name for verified merchants and no QR or user-defined names (2.14–2.15); real-time credit for P2PM small merchants (7.2); payee PSP as acquirer (Annexure A); deemed transactions and UDIR complaints for pending and merchant service issues (32.2–32.3); real-time status check and transaction summaries for merchants (32.11); UPI Help complaints (33).
- RBI — Reserve Bank of India (Regulation of Payment Aggregators) Directions, 2025 (15 Sep 2025)Escrow accounts and credit to the merchant 'as per the agreement', which must transparently mention the settlement timelines (16, Table 1); dispute process and merchant grievance officer (8); refunds to the original method (10(f)).
- RBI — Harmonisation of Turn Around Time and customer compensation for failed transactions (20 Sep 2019)UPI merchant payments: debit reversed within T + 5 when the merchant hasn't received confirmation; ₹100 per day after that.
- RBI — Reserve Bank – Integrated Ombudsman Scheme, 2026: FAQsWhen and how to escalate after complaining to the bank.
- NPCI — UPI Help (MyUPI)Transaction status and complaints for pending transactions and merchant service issues.
Last reviewed . Examples, amounts and screens marked illustrative are not LILPE figures.
