International wire transfer not received.
Find where it stopped.

Completed at the sending bank means one thing: that bank released the instruction. It is not a network status. Look at the status the banks reported against the UETR instead. ACSP means a bank accepted the payment and it was in process when that bank filed its report. ACCC means the beneficiary bank credited the account. RJCT means a bank refused the instruction. Always read a status with its report date. A later step may not be shown by any tracker you can reach. Some portals print Completed next to a detail line such as payment credited or payment rejected. That detail line is the report that counts. Between release and credit, the payment can sit at a correspondent bank, wait for a check, or wait unapplied at the receiving bank because a detail did not match.

The money is usually at one of the banks on the route. It may still be with the sending bank, at a correspondent bank, or unapplied at the receiving bank. If a wrong account number was itself a valid account, it may have been credited there; that is a same-day recall request to the sending bank. There is one other possibility. The instruction may have been rejected or cancelled, which is a report and not a movement of money, or a separate return payment may have been raised later. Only the sender's bank can confirm which. The money does not disappear. The sender gets the UETR from the payment confirmation and checks what the banks have reported. The free check shows the plain-language status and how many banks reported. The paid view names each reporting bank. The recipient gives their bank the UETR, the exact amount and the value date, so staff can search incoming payments. Give the payment its normal delivery time. Then, if no tracker has shown a credit, a newer step, or a final report such as RJCT, the sender asks the sending bank for a written trace.

Most international wires arrive within 1 to 5 business days. Many arrive the same day. Count business days in both countries. Allow for the sending bank's daily cut-off, and for weekends and public holidays on the route. Start tracking the UETR on day one rather than waiting. After five business days, ask for a trace unless a tracker you can reach has shown a credit, a newer step, or a final report such as RJCT. Older or unrelated reports do not change that.

No. A SWIFT payment is always somewhere. If the instruction was rejected before the money moved, it is still with the sender. Otherwise it is at a bank on its route, credited to the beneficiary, or being sent back as a separate return payment. A rejection is a report about the instruction, not a place the money is. The reporting banks record those states against the UETR. But not every leg is shown by a public tracker you can reach. And a return travels as its own payment with its own reference. So the UETR identifies the original instruction; it does not guarantee that every state is visible. What usually gets lost is the information: the sender quotes an internal reference the other banks cannot see. Quote the UETR and the sending bank can trace the payment even where public trackers show nothing.

One of five things. The payment has not reached your bank yet. Or it arrived with a name or account number that did not match, and it is waiting in the unapplied queue for a person to resolve it. Or a wrong account number was itself a valid account, and the payment was credited there. Or the instruction was rejected or cancelled before it reached your bank. Or a separate return payment was raised later. In those two cases your bank truly has no incoming payment. Ask your bank to search incoming and unapplied payments for the UETR and the exact amount. That search often turns nothing arrived into a same-day credit. If the search finds nothing and the reported status is RJCT, or the sender's bank has recalled the payment, the answer sits with the sender's bank. A rejection is a report about the instruction. A recall is a request, not a completed return. Have the sender ask their bank what happened and what the next step is. If the bank cannot say, ask for a trace. If your bank confirms a credit to a different account, have the sender contact the sending bank the same day about a recall. Time matters once money sits on the wrong account.

Yes. Any bank on the route can refuse the instruction. Common reasons are an invalid account number, a closed account, or beneficiary details that fail a check. The refusal is reported against the UETR as RJCT, often with a reason code such as AC01. A rejection is a report about the instruction, not a movement of money. Any return of the funds travels as its own separate payment. Ask the sending bank what happens next.

A written request to the sending bank to follow the payment through the chain. At most banks it opens a case with a reference number. The search moves from the front line to the payments back office. That team runs a gpi trace on the UETR and sends an enquiry through the banks it instructed. The last public report is evidence for that enquiry, not the address for it. How formal the process is, and what the bank owes you in return, depends on the bank and on local rules. Most banks charge a fee for a trace. Most will not open one for the recipient, so it is the sender's step.

Ask for an amendment when the payment can be found but is misapplied. It corrects the beneficiary details on the existing payment. That is faster than a recall and a new payment. Ask for a recall when the wire went to the wrong account or the deal collapsed. It asks the holding bank to send the money back. Once the money has been credited, that bank usually needs its customer's consent. A trace comes first once the normal delivery time has passed, unless a tracker has shown a credit, a newer step, or a final report such as RJCT. A reported rejection is different. The sending bank can already give the reason and say what happens to the funds.

The UETR, the 36-character reference in the 8-4-4-4-12 pattern. On an MT103-format advice it is field 121. On a pacs.008-format document it is the UETR element inside PmtId. A bank's own confirmation number is that bank's key for the payment. When it is MT103 field 20 it travels in the message, so the receiving bank may hold it as an extra search key. No tracker reports against it. A money-transfer provider's reference works only inside that provider. Only the UETR is the reference that reporting banks file against, whichever bank handled the payment.

The recipient can check the reported status with the UETR from the sender's confirmation. They can also ask their own bank to search incoming and unapplied payments for it. A formal trace, an amendment or a recall is the sender's request to the sending bank, because that bank holds the instruction. So the recipient's best moves are: get the UETR, check it, and brief their own bank precisely.

Four things. The UETR, so staff can match the incoming SWIFT message directly. The exact amount and currency as sent, before any charges were deducted. The value date from the sender's confirmation. The sender's name and bank. With those four, the bank can search its incoming and unapplied payment queues instead of looking by name alone.

Start with the sending bank's written complaints process. Quote any case or reference number the trace was given. US consumers who sent an international remittance can complain to the Consumer Financial Protection Bureau. Remittance transfers sent by US consumers carry error-resolution rights, with deadlines for the bank to investigate and report back. Elsewhere, look up the banking ombudsman or financial regulator for the country of the bank you dealt with. Whether the bank has to point you to one depends on local rules, so do not wait for it to.