Refunds and payment disputes need a clear paper trail
A failed transfer, a cancelled order and a payment sent to the wrong person need different follow-up. Identify the event, keep the right references, apply the relevant timeline and escalate with a concise record instead of collecting unrelated screenshots.
In this article
- Name the event before opening the complaint
- Keep one record for each disputed debit
- Apply T+1 and T+5 only to covered failure types
- Trace a merchant refund from approval to actual credit
- Handle duplicate payments and mistaken recipients honestly
- Write the request around evidence and the remedy
- Use the correct escalation route and current filing window
- Close the file only when the result is accounted for
- Sources & further reading
Name the event before opening the complaint
Start with four questions: was your account debited, was the intended recipient credited, did you authorise the payment and was the underlying order fulfilled? A failed payment, duplicate successful payment, refund after cancellation, incorrect recipient and suspected unauthorised debit are different problems. Use the bank or app status as one piece of evidence, then compare the statement and the recipient’s confirmation where available. Do not classify the event solely from a shopkeeper saying payment not received.
For example, a successful payment for a defective item is a merchant dispute even though you want the money back. An account debit with no beneficiary credit may be a technical-failure case. A payment you authorised to an incorrect address needs a mistaken-transfer process. These distinctions do not remove your right to complain; they make it easier to ask the organisation responsible for the relevant action and avoid quoting a rule that does not fit.
Keep one record for each disputed debit
Record transaction date and time, amount, payment method, funding account, recipient details, app status and reference. For UPI, preserve the UPI transaction reference as displayed rather than assuming an order number serves the same purpose. A merchant order number identifies the purchase; a payment reference identifies movement through the payment system. Both may be needed. Save the original receipt or export and make a separate redacted copy if you need to share publicly.
Add the reason for the dispute and a short chronology. Two similar payments on the same day need separate entries, even if the amount is identical. Keep the bank complaint number, merchant case number and any refund reference in separate fields. A single folder or paper file can work; expensive software is unnecessary. The essential requirement is that someone reading the record can identify which debit, order, complaint and credit belong together without guessing.
Section references: [2]
Apply T+1 and T+5 only to covered failure types
RBI’s domestic failed-transaction framework defines T as the transaction date and uses calendar dates for the relevant timelines. For a UPI transfer where the account is debited but the beneficiary is not credited, reversal is due by T+1 if the credit cannot be completed. For a UPI merchant-payment failure where the account is debited but confirmation is not received at the merchant location, the auto-reversal timeline is T+5.
For illustration, a covered transaction dated 4 November has T+1 on 5 November and T+5 on 9 November. These are examples of calendar arithmetic, not an assessment of an actual claim. The framework prescribes ₹100 per day of delay beyond the applicable period for the specified cases. Ask the bank which failure category it has recorded, whether credit was completed or reversal required, and how the prescribed compensation was calculated if the relevant deadline was exceeded.
Section references: [1]
Trace a merchant refund from approval to actual credit
A merchant saying refund approved may mean the request was accepted internally, not that money has reached your account. Ask when the refund was initiated, to which original payment method, for what amount and under which reference. Keep the cancellation or return acknowledgement and the seller’s applicable terms. The RBI technical-failure timelines should not be presented as a universal deadline for every return, cancelled booking or dispute about goods.
Suppose a ₹2,400 order is partly returned and the agreed refund is ₹900. Record the expected ₹900 against that order rather than waiting for a full ₹2,400 credit. Check whether an offer adjustment, delivery charge or other deduction is claimed and ask for its basis. Do not accept an unexplained reduced amount simply because the case is closed. A refund to an app balance or voucher is also different from money returned to the original bank account.
Handle duplicate payments and mistaken recipients honestly
If a merchant says a payment is pending, first inspect your app and account before paying again. If a second payment is necessary, preserve both references and ask for written confirmation of how any duplicate will be handled. A second successful debit does not automatically vanish because both payments bought the same item. Record it as a possible duplicate and request the appropriate reversal or refund through the provider and merchant.
For a successful payment sent to the wrong person, contact the bank or app promptly with the correct reference and explain the mistake. NPCI’s UPI FAQ states that an initiated payment cannot simply be stopped. Recovery depends on the facts and the relevant process; there is no universal cancel button or guaranteed recall. Avoid contacting a supposed recipient through an unverified number or sending an additional payment to unlock a refund. If fraud is suspected, use the urgent reporting route too.
Section references: [2]
Write the request around evidence and the remedy
Use a short message: on this date, this amount was debited under this reference; this is the status; this is what is wrong; this is the remedy requested. Attach the minimum relevant evidence through a verified support channel. Ask for an acknowledgement and expected next action. Do not bury the transaction details inside a long description of every payment problem you have ever experienced. Keep the original message so later escalation shows what the organisation was asked to resolve.
If support asks you to wait, record the date, stated reason and promised response. Set a follow-up reminder and compare the account for credits before making the next contact. If the issue changes, update the chronology: for example, a missing merchant credit may later become a duplicate-refund question. Provide the new evidence under the existing reference where possible. Never provide PINs, passwords or live OTPs as complaint evidence, and do not install remote-control software to show a statement.
Use the correct escalation route and current filing window
For a payment-service deficiency, first use the bank or provider’s grievance process. The RBI Integrated Ombudsman Scheme, 2026 has applied since 1 July 2026. It allows eligible escalation following an unsatisfactory response or the applicable no-response period. The no-response condition considers the prescribed payment-system timeline or 30 days, whichever is later; a 90-day filing calculation then applies under the scheme. Check the current FAQ rather than an older one-year summary.
For the underlying sale, the merchant or e-commerce grievance officer may be the relevant first contact. The e-commerce rules require acknowledgement within 48 hours and redress within one month for covered consumer complaints; this does not mean every refund must appear in the bank within 48 hours. Keep the sale complaint and the payment complaint connected in your file without treating them as identical. Do not claim the same loss has been finally repaid twice if multiple processes are operating.
Close the file only when the result is accounted for
Before marking a case resolved, check the credited amount, value or posting information where relevant, any compensation due and any interest or fees still disputed. Match the credit to the original debit and keep the bank or merchant’s final explanation. A support status reading resolved is not the same as your account receiving the agreed remedy. If a credit is provisional, identify that clearly instead of treating it as an unconditional final settlement.
Keep records for as long as needed for the open dispute, related accounting and applicable obligations. Delete unnecessary extra copies when they no longer serve a purpose, especially files shared on borrowed devices. Review patterns after resolution: repeated failed payments may justify asking the bank about service issues, while repeated duplicate payments may call for a clearer checkout routine. The file’s purpose is to support a specific remedy and prevent the same confusion, not to accumulate sensitive screenshots indefinitely.
Readers’ questions
Does the ₹100-per-day rule cover every delayed shopping refund?
No. It belongs to the RBI framework for specified failed transactions and applies when the relevant conditions and turnaround time are met. A merchant-approved return or cancellation refund is a different event. First establish the payment status and failure category, then ask the bank or merchant for the applicable process. Keep approval, initiation and final-credit dates separate.
What should I do if the app and merchant show different statuses?
Preserve both records and check the bank debit, reference and any later reversal. Raise the discrepancy through the app or bank and ask the merchant to check its own receiving record. Avoid paying repeatedly while the status remains unclear. If you must pay again to complete an essential purchase, retain both references and written agreement on handling any duplicate.
Can I post my full statement online to get faster help?
Use the organisation’s verified private complaint route for complete transaction details. Public posts should not reveal full account numbers, identity documents or unrelated spending. Keep an original evidence copy privately and share a limited redacted version only when useful. Public attention does not replace a registered complaint, and an unsolicited helper responding to your post may itself be attempting fraud.
Sources & further reading
- RBI: Harmonisation of Turn Around Time and customer compensation for failed transactions ↗
- NPCI: UPI Frequently Asked Questions ↗
- RBI: Integrated Ombudsman Scheme, 2026 FAQs ↗
- Department of Consumer Affairs: Consumer Protection (E-Commerce) Rules, 2020, official Gazette text ↗
Sources were checked for this edition. Scheme rules, product conditions and local requirements can change; consult the responsible provider for a decision.