A SWIFT Transfer Is Stuck: When a New Correspondent Route Can Help

SWIFT carries payment instructions between financial institutions. It does not move the money itself. Settlement may pass through one or more correspondent banks before the beneficiary bank receives the funds.

That distinction matters when a payment stalls. A transfer cannot safely be proxied while the original payment is still in the correspondent chain. First establish its status.

Start with the payment evidence

Ask the sending bank for:

• the MT103 or ISO 20022 confirmation
• the UETR tracking reference
• value date, amount, and currency
• ordering customer and beneficiary details
• sender, intermediary, and beneficiary BICs
• fee instruction and latest status

SWIFT explains that its network carries secure messages between institutions. HSBC provides SWIFT gpi tracking for eligible routes.

Why a correspondent route fails

A payment may stop because information is incomplete, an intermediary has no effective route for the currency, a bank needs documents, or a compliance review requires manual work. Sometimes the selected route simply passes through more institutions than necessary.

The sending bank remains responsible for investigating the original instruction.

Do not send a duplicate payment

Use this sequence:

1. Track the original payment with the UETR.
2. Ask whether it is processing, on hold, rejected, or returned.
3. Supply requested documents.
4. If the route cannot complete, request a recall or return.
5. Confirm that the original amount has returned or the banks have stopped it.
6. Only then prepare a new transfer.

A recall is a request, not an instant reversal.

When HEVN can prepare an HSBC route

For supported companies and currencies, HEVN can assess a fresh route using account details connected to an HSBC correspondent relationship.

This does not modify the original message in flight. It creates a separate route after the first transfer has been resolved. HEVN reviews the company, beneficiary, amount, currency, and purpose. The partner confirms availability and supplies approved instructions. The new payment receives its own confirmation and UETR.

HSBC notes that inaccurate intermediary or beneficiary information can delay or reject an overseas payment. Access through HEVN depends on the company, currency, destination, and partner approval. HSBC cannot be promised for every payment.

What to send support

Provide the company and HEVN account, amount, currency, initiation date, MT103, UETR, sender and beneficiary, beneficiary bank, invoice or contract, current bank response, and recall status.

Example

A company sends USD to a European supplier. The payment remains with an intermediary. The sender obtains the MT103 and UETR. Its bank confirms that the route cannot complete and starts a recall.

Once the amount returns, HEVN reviews company-named USD account details connected to an available HSBC correspondent route. The company sends a new payment with the correct beneficiary data and invoice reference.

The new correspondent replaces a failed route. It is not a shortcut around compliance and not an instruction to send twice.

How to request a new route in HEVN

1. Open Payments and select the delayed SWIFT transfer.
2. Download or attach the MT103 and UETR.
3. Select Get support and describe the latest response from the sending bank.
4. Confirm whether a recall or return has started.
5. Ask HEVN to assess an alternative correspondent route.
6. If an HSBC route is approved, wait for the original funds to return before using the new instructions.

Prepare the invoice, signed contract, sender and beneficiary details, payment purpose, and source-of-funds evidence for a large transaction.

Need help reviewing an alternative correspondent route? Book a call with the HEVN team.