MyBankAnswers — Clear answers. Brighter banking. MyBankAnswers CLEAR ANSWERS. BRIGHTER BANKING.
Your trusted
banking companion
Impersonation and phishing

TSB phishing scam refund 2026: fake calls, texts and recovery

Spot fake TSB calls, texts and phishing, protect security codes and understand the recovery or refund route if money has already been lost. Impersonation content becomes money-intent the moment the customer has acted on the fake contact. A useful TSB article must cover prevention and the refund/recovery path without implying that every phishing loss is automatically reimbursed.

Quick answer

Verify the bank independently, never disclose one-time codes and stop any further transfer. If money has already moved, report the fraud and preserve the fake message, call or website. Before responding to any message, verify the bank independently and protect any compromised email, phone or device. Use the current TSB rule while the bank remains separately regulated.

Phishing content earns its financial value by connecting prevention with the recovery path after loss. The reader needs both the warning signs and the correct refund or fraud-reporting route. TSB remains separately regulated during the Santander transition, so current TSB documents should be used directly.

Advertisement

Treat unexpected contact as untrusted by default

A text, email or call can display TSB’s name without being genuine. Do not use the contact details inside the message to verify it; open the official app or type the known website address yourself.

A high-street relationship gives TSB customers more than one service route, but the fastest option is not always the best documented one. Do not assume a Santander policy automatically applies to a TSB account during the transition; use the current TSB product and support information. For TSB, keep the current TSB reference because Santander ownership does not by itself replace today’s phishing scam refunds rule.

Never disclose one-time codes or full security credentials

Fraudsters often create urgency and then ask for a code, PIN, password or approval in the banking app. A one-time code can authorise a payment or device, so treat it as a key, not as a harmless reference number. For TSB, keep the current TSB reference because Santander ownership does not by itself replace today’s phishing scam refunds rule.

Do not approve a TSB login or payment notification you did not initiate.

Reject the 'safe account' story

A caller who says your account is compromised may instruct you to move money to a new account for protection. That is a classic impersonation tactic.

End the contact and reconnect independently. Police and genuine bank staff do not need you to defeat the bank’s own fraud controls by moving money to a stranger’s account.

Advertisement

Check links before entering banking details

Phishing pages can closely imitate a bank login. Avoid signing in through links in unexpected messages and inspect the address carefully before entering credentials.

If you already entered TSB details on a suspicious page, change or secure access through the official route and report what happened promptly.

Protect the email and phone account too

Bank security depends partly on the email address, mobile number and device used for recovery. Use strong unique passwords, screen locks and SIM/account protections where available. For TSB, keep the current TSB reference because Santander ownership does not by itself replace today’s phishing scam refunds rule.

If your phone number is unexpectedly disconnected or moved to another SIM, treat that as a security event and contact the mobile provider as well as the bank.

Keep evidence without interacting further

Save the suspicious message, sender details and website address, but do not continue the conversation simply to gather more evidence. Report through official channels and block the sender. For TSB, keep the current TSB reference because Santander ownership does not by itself replace today’s phishing scam refunds rule.

TSB remains a separately regulated retail bank during its transition into Santander UK and continues to operate its own accounts, cards and service channels. Brand familiarity should never be used as proof that an unexpected contact is genuine.

Worked example: protect the money and the evidence

In a fraud case involving £8,900, minutes can matter more than perfect documentation. Protect the TSB account and report the scam first, then organise messages, payment references, phone numbers and websites into a clean evidence file. Do not pay a third party who promises recovery, and do not continue following instructions from the person who caused the original loss.

Final fraud and recovery checks

After a bank impersonation and phishing incident, review passwords, trusted devices, email security, phone access and recent transactions rather than focusing only on the single payment. Keep the TSB fraud decision and any reimbursement correspondence. If the result appears inconsistent with the evidence or current UK protections, that record is what supports a later formal complaint.

Fraud and scam checklist

  • Use only the official TSB app, website or verified phone number
  • Save the date, time, amount, status and reference for the event
  • Do not create a duplicate payment or disclose a security code while investigating
  • Keep screenshots, receipts or messages that prove the sequence
  • Ask for a case or complaint reference when the issue is formally logged
  • Recheck live limits and processes because they can change during 2026

Why this looks different at TSB

TSB remains separately regulated during the Santander transition. That makes phishing scam refunds a good example of why current TSB documents should be used directly instead of borrowing a Santander rule that may not yet apply.

Money check: stop the second loss

After a phishing loss, do not pay a supposed recovery agent, tax, release fee or 'security deposit'. Secondary scams target people who have already lost money. Preserve the original amount and any later attempted charges separately, then use the official TSB fraud and complaint route.

Advertisement
RELATED GUIDES

Continue with these related banking guides

Impersonation and phishingStarling Bank phishing scam refund 2026: fake calls, texts and recoveryRead guide →Impersonation and phishingSantander UK phishing scam refund 2026: fake calls, texts and recoveryRead guide →Impersonation and phishingRevolut UK phishing scam refund 2026: fake calls, texts and recoveryRead guide →

Sources and verification

MYBANKANSWERS VERDICT

Eleanor Price — Consumer Rights Writer

Phishing and impersonation should be treated as a verification problem before they become a money-loss problem. Do not trust the sender name, caller ID or link inside an unexpected message. Use the official app, card or known website to reconnect, and never disclose a one-time code or approve an unexpected device. If money has already moved, report the fraud immediately and preserve the fake message, phone number, website and payment reference. Then protect email, mobile and banking access so the attacker cannot create a second loss. Any refund or recovery claim should be kept separate from fees demanded by a supposed recovery agent. TSB remains a separate regulated bank during the Santander transition, so keep the current TSB product document and support reference with the case. Recheck TSB’s own rule before assuming a Santander process now applies. After the first loss, secure email, mobile and banking access so the attacker cannot create a second one. Keep the phishing evidence without continuing the conversation. Recovery claims should be handled through the bank and official UK channels, not through someone demanding an upfront fee to retrieve the money. For TSB, keep the current TSB tariff or notice with the case because Santander ownership does not automatically replace today’s TSB rule.

TSB: Phishing guidance uses official fraud-prevention and bank-security sources. Never rely on contact details inside a suspicious message when verifying the bank or reporting a loss.