4
Resolved

FamPay ₹240 Sent To Wrong UPI ID - Refund Request

Faizan
Faizan
FamPay
February 25 5:57 PM167
Faizan's Thank You Message
Thanks

On 24/02/2026, I mistakenly sent ₹240 to the wrong UPI ID through FamPay, to 6206759***@fam. The money was debited even though it was not intended for that person, and I realized after the transfer that it had gone to the wrong account. I have contacted support about this issue and I have the transaction details and screenshot/transaction ID for this payment. However, I have not yet received my money back and I am worried about how long the refund will take and whether the wrong payment will be reversed. I request that this UPI transfer be traced and reversed as soon as possible and that the full amount of ₹240 be refunded to my account without any further delay. I also request clear information on the status and expected time frame for this refund.

Faizan
Faizan
February 25 5:34 PM

By mistake money went to the wrong upi QR. Please refund it.

Faizan
Faizan
February 28 6:15 PM

Thank you

Faizan
Faizan
March 5 6:11 PM

Thanks

Comments

Q&A: Explore Popular Queries

Check out the solutions and tips on this topic.

Similar Complaints

FamPay Wrong UPI Transfer - Money Sent To Wrong Account

Anurag
Anurag
FamPay
January 22 5:13 PM509

I am writing regarding a mistaken UPI transfer I made using Fampay on 19 January at around 8:10 PM. By error, I transfer...

How to Recover Money Sent to Wrong UPI ID on FamPay

Levio
Levio
FamPay
February 21 7:27 PM111

Dear FamPay Support, On February 21, 2026, I accidentally transferred ₹700 to the wrong account (Harshrajsingh Surendra...

Fampay UPI Payment Stuck Pending After Money Deducted

Dhairya
Dhairya
FamPay
February 16 5:19 AM106

I made a UPI transaction through Fampay at around 12:39 AM, and the payment has been stuck in a “pending in stake” statu...

Fampay Payment Sent To Wrong ID - No Refund

No Lie
No Lie
FamPay
February 19 6:15 PM110

On 19 February, I accidentally sent a payment of 100 via Fampay to a wrong number/ID (*8848256***@mbkns*). This was an u...