Report the transaction through your UPI app and bank immediately to improve your chances of recovering the money

Photo credit: Livemint
A wrong UPI payment can cause considerable worry, but taking prompt action may improve your chances of recovering the money. Whether you selected the wrong contact, entered an incorrect UPI ID or scanned the wrong QR code, the first step is to report the transaction without delay.
Unified Payments Interface (UPI) transactions are processed within seconds. Once a payment is successfully completed, there is no simple option to cancel it through the payment app. However, you can raise a complaint and ask your bank to initiate the recovery process.
Keep the transaction reference number, payment amount, date and recipient’s UPI ID handy. These details will help the bank trace the transaction and process your complaint.
Raise a complaint through your UPI app
The first step is to report the incorrect payment through the app you used to make the transaction. Open the transaction history, select the relevant payment and look for the option to raise a complaint or report an issue.
You should also contact your bank’s customer care department and explain that the money was transferred to the wrong UPI ID. Ask the bank to register a formal complaint and provide the transaction reference number along with the other relevant details.
Reporting the issue through the app alone may not be sufficient. Since your bank is involved in processing the transaction, registering a complaint directly with the bank will provide a formal record that you can use for subsequent follow-ups.
Why recovering the money may take time
A successful UPI payment must be distinguished from a failed transaction. If a payment fails but your account is debited, the amount may be reversed through the applicable process.
However, when a successful payment reaches another person's account, the recovery procedure is different. Banks generally cannot unilaterally withdraw the money from another customer's account.




Comments
0 commentsNo comments yet — be the first.