TSB fraud checks and blocked payments: what to do

When TSB stops a transfer or asks for extra verification, treat the block as a security event until you know otherwise. The fastest safe route is to confirm the request through the official app or number, preserve the transaction details and avoid anyone who offers to “release” the payment by moving money elsewhere. For this security event, preserving the original message and payment status is more useful than repeatedly retrying the transaction.

For this security event, preserving the original message and payment status is more useful than repeatedly retrying the transaction.

Treat unexpected payment instructions as a fraud risk

No genuine fraud team needs you to protect money by transferring it to a “safe account”. If a caller says a blocked TSB payment proves your account is compromised, end the call and contact the bank using the app or the number on your card. Caller ID and text-message threads can be spoofed.

Read the exact status before retrying

A payment can be declined, pending, queued for review or awaiting authentication. Those are different states. Save the screen and reference before pressing send again. Repeating a large transfer can create duplicate instructions and make the account activity harder to investigate.

Before acting, check the current TSB page or in-app quote because rates, limits and eligibility can change. Save the figure you actually relied on so you can reconstruct the decision later. For this security event, preserving the original message and payment status is more useful than repeatedly retrying the transaction.

Prepare evidence through an official channel

For an unusual purchase, house deposit or new beneficiary, TSB may ask what the payment is for or request documents. Have the invoice or contract ready, but never email identity documents to an address supplied by an unsolicited caller. Use only the bank’s verified upload process.

Verify the payment, recipient and device through official channels

If the payment is to a business, solicitor or investment firm, confirm the bank details independently. A perfectly genuine TSB security check cannot protect you if the beneficiary details were changed by an email-account compromise and you approve the payment anyway.

A good decision remains workable after a minor setback. For this security event, preserving the original message and payment status is more useful than repeatedly retrying the transaction.

Protect the device and SIM

If you have unexpectedly lost mobile signal, received password-reset messages or seen a new device login, contact the mobile network and TSB promptly. A SIM swap or compromised email can undermine one-time codes and account recovery. Change the email password from a trusted device as well as securing the bank account.

If the payment was genuinely yours, avoid turning a verification delay into a second security problem. Do not send the same amount through another route simply because the first payment has not cleared, and do not let a recipient pressure you into using a new account number. Wait until TSB confirms the status of the original payment. If the bank needs supporting information, provide only what is requested through an official channel. This preserves a clean timeline and makes it easier to distinguish a legitimate fraud check from a scammer trying to exploit the confusion around a blocked transfer.

Understand scam reimbursement and evidence requirements

If you authorised a payment because you were deceived, report it as a scam rather than merely calling it an “incorrect transfer”. The APP-scam reimbursement framework can apply to eligible Faster Payments cases, subject to the scheme rules and consumer standard of caution. The classification affects how the case is investigated.

Where another bank or product is the alternative, use identical assumptions. For this security event, preserving the original message and payment status is more useful than repeatedly retrying the transaction.

Keep a short evidence pack

Save the payment confirmation, messages, phone numbers, advert or invoice and the time you first contacted TSB. Do not edit screenshots. A chronological evidence pack helps the bank and, if necessary, the Financial Ombudsman Service understand what happened.

Escalate only after the facts and loss are documented

If the complaint is not resolved, use the formal complaint route and keep the final-response letter. Payment-services complaints often have shorter response deadlines than ordinary complaints. The Financial Ombudsman Service can review eligible disputes once the firm has issued its final response or the applicable response period has expired.

Once the decision is made, set a calendar review. A review prevents an old decision from becoming an expensive default. For this security event, preserving the original message and payment status is more useful than repeatedly retrying the transaction.

• Use only official contact channels
• Do not move money to a “safe account”
• Save the exact payment status
• Verify changed beneficiary details independently
• Report scams explicitly as scams
• Keep evidence and complaint references

A stopped payment can be inconvenient, but do not let the deadline push you into bypassing a security control. If someone is waiting for the money, tell them the bank is reviewing the payment and verify the recipient details again using a channel you already trust. Keep screenshots or references from the official TSB flow, but never send one-time codes or approve a new payment because an inbound caller claims that doing so will release the first one. The safest outcome is a verified payment with a clear audit trail, not the fastest possible retry.

Sources and verification

• TSB - official website
• Current Account Switch Service
• Financial Services Compensation Scheme
• MoneyHelper

MyBankAnswers uses official provider and UK regulatory sources wherever practical. Information is general and does not constitute financial advice.