International Transfer Delayed: What to Do
A transfer can be delayed by incorrect recipient data, funding settlement, compliance review, intermediaries, weekends or receiving-bank processing. Sending the same amount again can create two transfers instead of solving the first.
Diagnosis in practice: Sent does not yet mean received
A recipient reports no funds while the sender's app says sent. The sender verifies details through a trusted channel and asks who currently holds the transfer. One formal trace is opened; replacement payment waits until duplication and refund risks are understood.
This situation is illustrative. It is not a testimonial or a prediction of a provider's decision.
Trace the transfer by custody and status
A useful escalation identifies who currently controls the funds, what status the authenticated account shows and whether the sender, intermediary or recipient institution needs information. Vague claims that it is processing are not enough for a timeline.
Questions to resolve before acting
Should I send a replacement transfer?
Not until you understand whether the original can still complete or be recalled. A second payment can create a duplicate obligation.
Can the recipient solve the delay?
Sometimes recipient details, local verification or the receiving institution matter. Coordinate without sharing passwords or using contact details supplied by an unverified caller.
For the next transfer, retain the same evidence you use to compare total remittance cost so price and delivery risk can be assessed together.
Identify the status precisely
Pending funding, processing, sent, available and completed can mean different things. Ask who currently holds the funds and whether the provider has requested information.
Check or correct
Record status, timestamp and reference from the official account.
Verify recipient details safely
Compare account number, bank code, name and delivery method with information confirmed independently by the recipient. Do not accept replacement details from a compromised email thread.
Check or correct
Reconfirm through a second trusted channel.
Start a formal trace
Use the sending provider's official support or complaint route. Provide the reference, amount, date, currency and recipient details; ask for the next deadline and escalation point.
Check or correct
Keep one chronological case file rather than opening duplicate chats.
Protect the underlying bill
Tell the intended recipient or biller that payment is delayed and share non-sensitive proof where appropriate. Arrange another method only after understanding refund and duplication risk.
Check or correct
Agree in writing how a duplicate receipt would be returned.
Apply this guide with Remittance Total Cost Calculator
After the incident is resolved, compare future routes on total cost while keeping delivery time and recovery rights as separate checks.
The tool runs in your browser, stores no answers and produces no sponsored result.
Use Remittance Total Cost CalculatorKeep a recovery record
Track the checks you have completed before repeating an application, payment or contact attempt. Progress stays in this browser.
0 of 4 actions complete
Sources and verification
These official or public-interest resources support the framework. Product terms and local rules can change, so verify an important decision at the source.