How a bank actually cancels a SWIFT payment

Your bank doesn't press an "undo" button. It sends a message asking the next bank to stop the payment:

• The cancellation request. Banks send a formal message (a camt.056 in the current ISO 20022 format, or the older MT192) asking the bank holding the payment to cancel it, with a reason such as it being sent to the wrong account or a duplicate.
• Swift's Stop and Recall service. Where both banks use it, this can stop a payment automatically while it's still moving and notify every bank in the chain through the tracker, rather than waiting for each bank to act on a message in turn.
• The receiving bank's reply. It confirms back (a camt.029) whether the payment was stopped, is still pending, or has already been paid out.
• If it's already paid out, the receiving bank must ask its own customer, the recipient, for permission to debit the money back before it can return it.

None of this needs your involvement directly. Your job is to give your bank the details fast and accurately, then let it work through the network.

What happens to your money

• Stopped in time: the payment is held rather than paid out, and is returned to you or you resend it correctly, minus any handling fees banks along the chain deduct.
• Already credited, recipient agrees: their bank arranges the return once it has their permission.
• Already credited, recipient doesn't respond or refuses: your bank cannot force it. In a genuine mistake between people who know each other, this is usually resolved by asking directly. In fraud, it becomes a matter for the recipient's bank's fraud team and, often, the police.
• Fees apply either way. Banks along the chain can charge for handling a cancellation or recall, whether or not it succeeds.

There's no fixed timeframe for any of this: it depends on how many banks are involved, how quickly each one replies, and whether the recipient's bank needs to reach its customer. Ask your bank for a case reference and follow up rather than assuming a specific number of days.

What to do, right now

1. Call your bank immediately, don't just send a message through the app. Ask for the international payments or SWIFT recall team, and use those words.
2. Give the exact details: amount, currency, date and time sent, the recipient's bank and account, and, if you have it, the transaction or payment reference your bank gave you.
3. Ask for the UETR, the payment's tracking reference, and ask your bank to check the payment's current status before it submits the cancellation, so it knows whether the money has already been credited.
4. Say why: wrong account, wrong amount, duplicate payment, fraud, or a change of plans. The reason affects how the receiving bank handles it.
5. Follow up in writing (email or your bank's secure messaging) after the call, so there's a written record with the same details.
6. Don't send a replacement payment yet if you're not sure the first one is stopped. Confirm its status first.

If it was a scam

1. Call your bank straight away and say clearly that you believe it's fraud. Banks prioritise fraud-flagged cases and can alert the receiving bank to freeze the account while it investigates.
2. Report it to the police or your country's fraud-reporting service, not just your bank.
3. Keep everything: messages, invoices, the payment confirmation and any names or numbers you were given.

If you sent it to someone you know

If the recipient is genuinely reachable and it was a mistake, such as the wrong saved beneficiary, contacting them directly can be faster than a formal bank process. Explain what happened and ask them to instruct their own bank to return the money. Their bank will still need their authorisation either way, so a cooperative recipient can make this much quicker.

Avoiding the next one

• Check every detail before confirming. Use our IBAN validator, NUBAN validator or SWIFT code checker. A valid format catches typos, but doesn't prove the account belongs to who you think.
• Look at the saved beneficiary name shown on screen, not just the amount, before you confirm. Many duplicate or wrong-recipient errors come from picking the wrong saved payee.
• Confirm new or changed bank details by phone, on a number you already know, never by replying to the message that sent them.
• For a large payment to a new recipient, consider sending a small amount first and confirming it arrives correctly.

For Nigerian users

• Sent from a Nigerian bank in error? Call the bank immediately and ask for a SWIFT recall, with the same details above.
• Think you've been scammed? Report it to your bank first, then to the Economic and Financial Crimes Commission (EFCC), and you can also report to the Central Bank of Nigeria. If your bank doesn't resolve your complaint within two weeks, escalate to the CBN's Consumer Protection Department.
• Receiving money in Nigeria? If a sender's bank asks your bank to return a payment, your bank will normally ask you before debiting your account, unless it's already established as fraud.

Sources

• Payments Market Practice Group, Best Practice Guidance for the Return of Funds and Rejects of Payments (September 2023, published by Swift): the camt.056 cancellation request and camt.029 status reply; a bank that has already paid out must seek its customer's debit authorisation before returning funds.
• Swift, Swift GPI: the Stop and Recall service.
• Uniform Commercial Code, § 4A-211 (cancellation and amendment of a payment order, US law): cancellable before the bank accepts it; after acceptance, only with the bank's agreement or a system rule.
• Central Bank of Nigeria, Fraud and Scam Awareness and Complaints management.

Last reviewed 24 September 2026. Spot an error? Tell us through our corrections page.