The recovery process for a misdirected SWIFT payment
Scams & Fraud
By Ohmyfin Organisation Editorial Team · Published 2026-05-22 · Updated 2026-05-22
Mis-sent SWIFT payments — whether from your error, a typo, or a fraud — can be recovered in many cases, but the recovery rate is inversely proportional to elapsed time. Hours matter.
Step 1, within minutes: call your bank's international payments team. Ask them to issue an MT292 recall request. Have the UETR and details ready. If the payment has not yet been credited to the beneficiary, the recall has a high chance of success.
Step 2, within hours: if you suspect fraud, file a police report. This documents the incident and may freeze further movement of funds.
Payment Located
SWIFT GPI Network · Real-time status
Payment Not Found
No record found in SWIFT GPI or any correspondent banking data
Fraud Awareness Notice
If you received a payment document from a third party, verify directly with your own bank before releasing goods or funds. Fake MT103 / pacs.008 confirmations are widely used in advance-fee scams. See our fraud guide →
Monitor for 7 Days — Free
We re-check every few hours and notify you the instant this payment appears — no account, no spam.
Watching — we'll email you the moment it appears.
Not sure what to do next?
Ask SwiftMate, our SWIFT assistant, for guidance on payment delays, rejections, and next steps.
Payments can appear hours after initiation — try again later
Step 3, within the first business day: open a formal complaint with your bank. Cite "unauthorised / misdirected payment" depending on circumstance. Demand a chargeback investigation under the Payment Services Directive (EU/UK) or Regulation E (US).
Step 4, days 2-7: your bank coordinates with the beneficiary bank via SWIFT messages. The beneficiary bank may freeze funds (if discovered before posting), reverse the credit (if the recipient cooperates), or refuse (if funds have been withdrawn).
Step 5, weeks 2-12: if cooperative reversal fails, civil recovery becomes the path. Engage a payment-recovery firm or solicitor in the beneficiary jurisdiction. Costs typically 10-25% of recovered amount.
Recovery rates: within 24h, ~60-80% recoverable. Within a week, ~30-50%. After 30 days, often under 10% without civil action. After 90 days, very rare absent criminal investigation.
Key takeaways
Call your bank within minutes — MT292 recall.
Police report within hours if fraud suspected.
Formal complaint to bank within first business day.
Recovery rate drops sharply after 24 hours.
Civil action remains an option but is costly.
Frequently asked questions
What if my bank refuses to recall?
Escalate to the complaints team citing your right under PSD2 / Reg E. If still refused, file with the regulator (Financial Ombudsman in UK, CFPB in US).
Will the beneficiary bank cooperate?
Depends on jurisdiction and whether the funds have been withdrawn. Banks in well-regulated jurisdictions generally cooperate if the recipient has not withdrawn. Withdrawal makes recovery a civil/criminal matter.
Are recall fees refundable on successful recall?
Recall fees (typically 25-75 USD) are usually charged regardless of outcome. Some banks waive on customer-error if the recall succeeds.
Can I use GPI to recall?
gCASE (a GPI service) accelerates inter-bank coordination for recalls and is supported by most major banks. Ask your bank to use gCASE if available.
Payment Located
SWIFT GPI Network · Real-time status
Payment Not Found
No record found in SWIFT GPI or any correspondent banking data
Fraud Awareness Notice
If you received a payment document from a third party, verify directly with your own bank before releasing goods or funds. Fake MT103 / pacs.008 confirmations are widely used in advance-fee scams. See our fraud guide →
Monitor for 7 Days — Free
We re-check every few hours and notify you the instant this payment appears — no account, no spam.
Watching — we'll email you the moment it appears.
Not sure what to do next?
Ask SwiftMate, our SWIFT assistant, for guidance on payment delays, rejections, and next steps.
Payments can appear hours after initiation — try again later