Wrong-account and blocked transfers

TSB payment sent to the wrong account or blocked

Sending a TSB transfer to the wrong account is a recovery problem, while a transfer blocked before it leaves is a verification problem. The first step is to work out which happened. If money reached an unintended recipient, contact the bank immediately with the exact transaction; if the payment never left, check the block and beneficiary details before trying again.

Sophie BennettUpdated 2026-09-298 min read

Quick answer

For a wrong-account transfer, tell TSB immediately and ask it to start the recovery process; do not contact an unknown recipient using unverified details or send another payment to 'test' the account. For a blocked transfer, read the bank's security message, re-check the beneficiary independently and only retry once you understand why the first instruction did not execute.

Work out whether the payment was sent or blocked

If the TSB app shows the £730 transfer completed, the money may already be at the recipient bank and recovery must begin. If it shows declined, rejected or pending, the bank may still control the instruction. Record the status and reference before taking any other action.

A beneficiary name mismatch, unusual amount or security check can stop a payment without moving the money. That is inconvenient but much safer than treating a blocked transfer as lost money and sending a fresh instruction elsewhere. With TSB, establish whether the instruction is merely blocked or has actually left the account before attempting another payment.

If you entered the wrong sort code or account number and the £730 transfer completed, contact TSB as soon as you notice. Give the transaction time, amount and intended beneficiary details, and explain exactly which field was wrong. The bank can contact the receiving institution and attempt recovery.

Do not assume the bank can simply reverse a Faster Payment unilaterally after it has credited another customer's account. Recovery normally involves the receiving bank and, depending on the circumstances, the recipient. Speed and accurate information improve the process but do not guarantee return. For this mistaken-payment case at TSB, keep the provider reference beside the exact transaction or account event so later support can follow the same chronology.

Verify the payee before trying again

When TSB shows a Confirmation of Payee result, read whether it is a match, close match or no match. A close match can be legitimate - for example a trading name differs from the legal account name - but it is a reason to verify the details using a trusted channel before paying.

If a seller or solicitor pressures you to ignore a no-match result because 'the bank system is broken', stop. Call the organisation on a number you already trust. Invoice-redirection scams depend on customers accepting changed bank details during a moment of urgency. For this mistaken-payment case at TSB, record the time, amount and support reference in one place so a second adviser does not have to rebuild the incident from memory.

Sending £1 first can show that an account can receive money, but it does not prove the account belongs to the intended person. A fraudster can happily receive the £1 and then encourage the £730 balance. Verification should come from independent contact details and the expected account name.

If you do make a legitimate test payment, ask the recipient to confirm the reference and amount through a trusted channel, then re-check the saved beneficiary before sending the main sum. Never rely solely on a screenshot supplied by the recipient. Keep the TSB beneficiary record open while you compare the test payment with the main transfer, especially the sort code, account number and reference.

Why blocks happen and how a wrong payment plays out

When TSB blocks a high-value or unusual transfer, answer verification questions truthfully. Do not split £730 into several smaller transfers simply to get around the control. That can make the pattern look more suspicious and can expose more money if the beneficiary is fraudulent.

If the payment is time-critical, tell the bank the genuine deadline and purpose. A solicitor completion, vehicle purchase and family transfer have different evidence. Keep the invoice or completion statement ready if the bank asks you to explain the economic purpose. For this mistaken-payment case at TSB, keep the final bank response with the underlying statement entry until the money and account status have fully reconciled.

You intend to send £730 to a family member but select an old beneficiary with a similar name. The TSB app shows completed. Within ten minutes you realise the mistake. Screenshot the transaction, call the bank through an official route and ask for mistaken-payment recovery.

Do not message the unintended recipient demanding immediate repayment unless the bank advises that route and you can identify them safely. Keep the recovery reference and note any contact from the receiving bank. If the recipient returns money directly, reconcile the exact amount before closing the bank case. For this mistaken-payment case at TSB, record the time, amount and support reference in one place so a second adviser does not have to rebuild the incident from memory.

Recovery, prevention and the final checks

TSB's account terms make clear that customers are responsible for supplying the correct payment information. If a payment goes to the wrong person because the customer entered incorrect details, TSB says it will try to get the money back, but recovery is not guaranteed once the funds have reached another account.

Report the mistake promptly and give TSB the intended and actual beneficiary details. If the bank blocked the payment before it left, treat that as a verification event instead: re-check Confirmation of Payee and the source of the bank details before attempting another transfer.

After the case, clean up saved beneficiaries in the TSB account, remove obsolete payees and label remaining ones clearly. For high-value payments, verify bank details from a source independent of the payment request and pause if details change at the last minute.

TSB routes many card, cash and transaction problems through the individual transaction in the Mobile Banking app. Save the transaction details and any case reference, and use a separate fraud route if the issue changes from a service problem into activity you did not authorise. A transfer mistake is stressful, but the safest recovery record is simple: original intended payee, actual beneficiary, amount, time, payment reference, discovery time and bank recovery reference. Keep those six facts together until the case is closed.

Check whether the transfer actually completed
Report a mistaken payment immediately
Use Confirmation of Payee as a warning signal
Do not split payments to bypass a block
Verify changed bank details independently
Clean up old saved beneficiaries after the case

Sources and verification

MYBANKANSWERS VERDICT

Sophie Bennett - editorial verdict

The crucial distinction is whether the transfer actually left TSB. A blocked instruction calls for verification; a completed wrong-account payment calls for immediate recovery action. Do not circumvent security controls by splitting payments, and do not treat a small test transfer as proof of identity. For high-value payments, independent beneficiary verification is cheaper than trying to recover money after it has gone.

TSB: mistaken-payment recovery depends on the payment status, receiving bank and recipient circumstances. Prompt reporting improves the process but does not guarantee that completed funds can be recalled.