A text or email claims a merchant, a delivery carrier, or your bank owes you money, and the only way to “release” it is to log in through a link they provide. Nationwide fraud losses reported to the FTC topped $10 billion in 2023, and refund and payment scams are a recurring slice of that total. More broadly, cards now dominate how people pay day to day: credit and debit cards together made up more than 60% of monthly payments in 2023, which is exactly why a message that looks like it touches your card or bank account gets opened and trusted. That trust is the entire mechanism the scam exploits, and it works just as well on people who consider themselves careful online as on anyone else, because the message is built to feel routine rather than alarming.
How the refund hook actually works
The message arrives by text, email, or a spoofed caller ID, and it names something plausible: an overcharge, a canceled subscription, a failed delivery fee, a tax rebate. It includes a link or a callback number, both controlled by the scammer. Clicking the link opens a page built to mimic a real bank or payment portal, down to the logo and color scheme. The page asks you to “log in to confirm your refund,” and whatever you type, username, password, one-time code, goes straight to the attacker, not your bank. Some versions skip the fake page entirely and route you to a live caller who asks you to read back a one-time passcode you just received, telling you it’s needed to “process” the refund. In reality that code authorizes a transfer or a new payee on your real account. The whole sequence is designed to be finished in under two minutes, before doubt has time to set in. Because the request looks like it’s giving you money rather than asking for it, people who would never hand over a password to a stranger do exactly that when it’s framed as a refund.
A quieter variant targets small, local merchants rather than big banks. A shopper gets a message that looks like it comes from a neighborhood pharmacy or a local delivery service, claiming a double charge from a recent visit and offering a “refund portal” link. Because the amount is small and the merchant is familiar, the request feels low-risk, which is precisely why people skip the caution they’d apply to a message claiming to be from a national bank. The mechanics are identical: a lookalike login page, a harvested password, and a transfer that happens somewhere else entirely.
A routine text that turns into a login prompt
The following is an illustrative scenario, not a real case.
The scene below is a composite example built to show how the pattern plays out, not a documented real event. A customer gets a text saying a recent order was overcharged by 15 euros and a refund is “pending confirmation.” The link leads to a page styled like their bank’s app, asking for an account number and a one-time code. The code arrives by real SMS seconds later because the scammer has already tried logging into the actual account. The customer, focused on confirming a refund rather than authorizing anything, reads the code aloud or types it in. Within minutes a transfer leaves the account, dressed up as a standing order to a new payee. Nothing about the text looked urgent or threatening; it looked like good news, which is exactly why it worked. The customer only notices anything wrong two days later, when a routine balance check shows a payment to a name they don’t recognize, by which point the window for an easy reversal has mostly closed.
Shutting the door on refund-based phishing
Refund scams rely on you acting inside a bank-branded page or call instead of your own banking app. Breaking that pattern removes almost all of their leverage, because the attacker needs your credentials or a live one-time code, not just your attention.
Never follow a refund link to log in
Close the message and open your bank’s app or website directly, typed from memory or a bookmark you already trust. Legitimate refunds show up in your account or transaction history without you needing to confirm anything through an external link. If there’s genuinely money owed to you, it will be visible from that direct path, and if it isn’t there, the message was fake regardless of how official it looked. This habit costs you nothing when the refund is real, since the money will simply be waiting there too.
Treat any one-time code request as a stop sign
Banks and merchants never need you to read back a one-time passcode to give you a refund; that code only exists to authorize an action on your side. If a caller or a form asks for it mid-conversation, end the interaction immediately. This single rule blocks the most damaging version of the scam, the live callback that walks you through authorizing your own account takeover, and it holds true no matter how patient or official the caller sounds.
Verify through a number or address you looked up yourself
If a message claims to be from your bank or a merchant, search for their official support contact independently rather than using anything in the message. Ask them directly whether a refund is pending. This adds thirty seconds but eliminates the entire premise of the scam, since the fake page or caller has no way to intercept a channel you initiated yourself.
Review statements on a fixed schedule, not just after a scare
Set a recurring reminder, weekly is enough, to scan recent transactions in your actual banking app rather than relying on push notifications alone. Most people only check closely after something already feels wrong, which is often too late to stop a transfer. A short, boring habit of scanning statements catches unfamiliar payees and small test charges before they turn into a larger loss, and it works whether or not you ever receive a fake refund message in the first place.
Freeze the account the moment something feels off
If you already entered credentials or read out a code, contact your bank immediately through their verified number to freeze the account and reverse any pending transfer. Change the password on that banking login and on any other account reusing it, and enable two-factor authentication through an app rather than SMS where possible, since SMS codes are exactly what this scam intercepts.
Why a password manager closes this gap
Refund phishing succeeds largely because the fake page looks convincing enough that a person typing from memory can’t tell the difference. A password manager removes that guesswork: it only auto-fills credentials on the exact domain it has stored for your bank, so a lookalike refund page simply gets no suggestion, which is itself the clearest signal that something is wrong. That small friction, the manager staying silent instead of offering to fill in your login, is often the first concrete sign a page is fraudulent, well before anyone reads the URL carefully. A password manager also makes it practical to use a long, unique password for banking and payment accounts instead of a reused one, so that even if a different site is breached, the credentials phished through a refund scam can’t be replayed elsewhere. Built-in breach monitoring flags if those specific banking credentials ever surface in a leak, giving you a chance to rotate them before anyone tries. It’s worth being honest about what this tool cannot do: it won’t stop the live-caller version of the scam, where no fake page is ever involved and the damage happens entirely through a spoken one-time code, and it can’t override a moment where someone types their password manually into a convincing page out of habit. None of this replaces verifying a refund through your bank’s real app, but it adds a layer that works even on the days attention runs low, which is precisely when these messages are built to land.
Veritasaffiliate link
Virtual cards for online payments — the main card stays out of checkouts
