You submitted an international wire and almost immediately realised something is wrong — wrong account, wrong amount, or a suspected fraud. Can you cancel it? The honest answer: maybe, if you act within minutes. Here is everything you need to know about wire transfer cancellations and the SWIFT GPI recall process.
The golden rule: call your bank the moment you realise there is a problem. Do not email, do not use the app — call the international payments desk directly. Every minute matters because the window for successful cancellation narrows rapidly once the payment enters the SWIFT network.
While the payment is still at your bank (in-queue): if your bank has not yet dispatched the SWIFT MT103 message, cancellation is usually simple — the bank removes the payment from the queue at no charge. This window is typically 0–30 minutes after submission, or until the bank's next batch dispatch. Online banking systems that show "processing" may still be in this stage.
After the SWIFT message has been sent — SWIFT GPI Stop-and-Recall: once your bank sends the MT103, they can initiate a SWIFT GPI Recall using the camt.056 recall message. This message travels through the chain using the payment's UETR and instructs every bank in the chain to stop and hold the funds. Under SWIFT GPI rules, every bank in the chain must respond within 1 business day — either by stopping and returning the funds or by confirming the funds have already been credited.
If the beneficiary bank has already credited the account: the recall becomes a civil dispute. The beneficiary bank must ask the account holder (the person who received the money) for consent to reverse. If the recipient was a legitimate payee (e.g. you made a typo but the account holder is a real person), they can refuse to return — in which case you need legal assistance. If it is a fraud case, contact your bank to file a fraud report, and in the US contact the FBI Internet Crime Complaint Center (IC3).
Success rates and timelines: SWIFT GPI Stop-and-Recall has a good success rate when initiated within 4 hours of payment — most major correspondent banks process recalls within the same business day. Success rate drops significantly once the beneficiary bank has credited the funds. For fraud cases involving known criminal accounts, international law enforcement cooperation (Interpol, FBI) may be able to freeze funds even after crediting — your bank's fraud team can escalate.
Prevention is better than recall: before sending any wire, use a call-back verification — call the beneficiary on a known phone number (not one provided in the payment instruction email) to confirm their bank details. Never trust payment instructions received by email that deviate from previously known details. Invoice redirection fraud (where a fraudster intercepts supplier emails and changes the bank details) causes billions in losses annually.
As fast as possible — ideally within the first 30 minutes while the payment may still be in your bank's internal queue. After that, every hour that passes reduces the chance of successful recall. By the time the payment is credited to the beneficiary's account, cancellation without their cooperation is very difficult.
Most banks charge $25–$75 for initiating a recall. Some banks waive the fee for fraud cases. Correspondent banks along the chain may also charge recall processing fees. If the funds are returned, you typically recover them minus fees incurred.
It depends. In SEPA, Confirmation of Payee (CoP) can catch name/account mismatches before sending. For SWIFT wires without CoP, the payment may credit to whatever account that number belongs to at the beneficiary bank. Some beneficiary banks validate account numbers before crediting; others credit automatically. Initiate a recall immediately.
A successful recall shows up as RJCT or CANC status on the Ohmyfin tracker — the payment has been rejected and reversed. Check the UETR on Ohmyfin for the latest status. If the UETR still shows ACSP or ACSC after your bank says the recall was initiated, follow up with your bank to confirm the camt.056 was sent and acknowledged.