MUVEX/Services/Transfer not going through

Urgent case · analysis within an hour

An international transfer
that won't go through.

The payment is not returned but not credited either. It hangs at an intermediary bank, at the recipient's compliance or somewhere in the correspondent chain. We find where the block is and decide how to move it.

Send a request Telegram

1 hour

initial analysis

24/7

urgent cases

Analysis

SWIFT copies

Plan B

if the first fails

Where it can get stuck

Typical delay points

Six points in the international-transfer chain where a payment most often hangs.

Sender bank compliance

The sender's bank paused the outgoing payment for review. Documentation was requested, but the answer doesn't close the questions.

Intermediary correspondent bank

The payment reached the intermediary but is stuck there for review. Often without notifying the sender.

Recipient bank compliance

The payment is credited to the correspondent account but does not move to the recipient's account — the bank holds it to check source of funds.

Technical errors in details

A mismatch in IBAN, SWIFT, name or address of the recipient. The payment is stuck on manual review.

Currency control

The recipient's jurisdiction has currency control requiring extra documents. Without them, crediting does not happen.

Request for more information

One of the banks on the route sent a request (MT199 / RFI). Without an answer the payment does not move.

What we do

Work plan for a stuck transfer

Four steps that usually resolve the case.

Reconstructing the picture

Requesting SWIFT copies, statements, the operation history. Understanding which link of the chain holds the payment.

Decoding the cause

Analysing the codes, reasons and wording from the banks on the route. Identifying the real request.

Documentation and reply

Preparing a document package for the specific request. Through a suitable channel — bank or partner.

Alternative if it doesn't move

If it's a return — we build an alternative route (see the “Bank declined” page). If it's crediting — we keep working.

Most often the transfer
is not "lost".

It hangs at a specific stage of the chain, waiting for a specific document or confirmation. The task is to find that stage and close the request. About 80% of "stuck" cases move after the right communication with the banks.

Urgent action order

What to do right away

Don't resend

Duplicating the payment complicates the case and blocks the first one.

Request the status

At the sender's bank — SWIFT GPI tracking.

Save the copies

All bank messages, MT103, MT199.

Brief MUVEX

Amount, direction, date, last known status.

We act

Analysis and a parallel scenario.

FAQ

Frequently asked

In a decline the payment is returned to the sender with a formal reason. “Not going through” is when the payment is neither returned nor credited — it hangs somewhere in the chain. The strategy is different.

Sometimes — yes. A recall is possible if the payment has not yet been credited to the recipient's account. The procedure is lengthy and not always successful, but MUVEX helps carry it out.

From a few days to 2–3 weeks. It depends on the banks' willingness to respond and the availability of documents. In parallel, an alternative route may be prepared in case the case does not move.

Sometimes — yes. It is done carefully to avoid creating a double transaction. The decision depends on the nature of the block.

SWIFT copies (MT103, MT199 if available), statements, correspondence with the bank, recipient details, the contract or other basis document.

Not always. The sender's bank sees only its part of the chain. SWIFT GPI helps, but not everywhere. MUVEX engages with banks through its own channels to get the full picture.

Request

Describe your task

A stuck payment
is not hopeless.

Describe the case — we'll see where the block is and how to move it.