A refund sounds like money moving toward the customer.
That makes it an effective excuse for asking the customer to cooperate.
Scammers send messages about an unexpected purchase, subscription renewal, overcharge, or refund. The message says to call a number if the charge is wrong. Once the victim calls, the supposed support agent claims remote access is needed to process or verify the refund.
The Federal Trade Commission documents this pattern in tech-support and refund scams. Scammers may impersonate well-known companies, obtain remote access, display a fake refund screen, and then claim an error caused too much money to be returned.
See the FTC’s tech-support scam guidance and its warning about refund impostors requesting remote access.
Remote control is not a normal refund requirement
A real merchant may need an order number, payment method, return authorization, or confirmation that an item was sent back.
It does not need to operate your desktop to put money back on the card that paid for the purchase.
Remote access changes the situation completely. The person on the other end may be able to view information on screen, manipulate what appears to happen, direct the victim through financial websites, or install additional software.
The original shopping problem becomes a pretext for computer access.
Verify the refund through the merchant you already know
If a message says a purchase or refund requires urgent attention, do not use the phone number or remote-access link in that message as proof of legitimacy.
Open the merchant’s app or website independently. Check your actual order history and your real bank or card statement. Contact customer service through information from the merchant’s official site.
The FTC states that it will never require remote access or payment to deliver an FTC refund. The same question is useful with commercial refunds: why would returning my money require control of my computer?
A refund should reduce a customer’s exposure to a bad transaction.
It should not create a much larger one.
