First, breathe. A transfer that hasn’t arrived is usually not a transfer that’s gone. Money in transit is normally sitting somewhere specific: waiting in a queue, held for a check, or on its way back. Your job is to find out which, in a sensible order.
Don’t resend yet. That’s the one thing that turns a delay into a double payment.
Step 1: Check the status and the date you were promised
Open the app, email or receipt and look for two things: the current status, and the date the money was supposed to be available. Providers usually give an estimate. Check it against calendars on both sides, because weekends, bank holidays and cut-off times in either country can add a day or more without anything being wrong.
A transfer sent late on a Friday, for instance, may not even start moving until Monday. That’s not a failure. It’s a calendar.
Look at the status wording too. “Processing” and “sent to bank” mean different things. “Sent to the recipient’s bank” can mean your provider’s part is done and the delay is further along the chain, though wording varies by provider. If your provider shows a status you don’t understand, ask what it means rather than guessing.
Date not here yet? Wait until it is. Date passed? Move to step 2.
Step 2: Collect the references before you contact anyone
Support teams can find a payment in seconds if you give them the right identifiers, and they can spend an hour if you don’t. Gather these first:
- The provider’s transfer or transaction number, from your receipt.
- The exact amount sent, the currency, and the date and time you paid.
- The recipient’s full name and account details as you entered them.
- If it was a bank wire, the bank’s own reference, and ask for the tracking reference described below.
Also check the receipt itself. In the US, a receipt for an international transfer has to show the date the money is expected to be available, how to report an error, how to cancel, and how to contact the company, the Consumer Financial Protection Bureau and the state regulator, according to the CFPB. Keep it. Everything below leans on it.
Write down the details of every conversation: who, when, what they said. It feels fussy now and saves you later.
Step 3: Know the common reasons for a hold
Most delays come from a short list.
Compliance checks. Banks and transfer firms screen payments against fraud and sanctions rules, and larger or unusual transfers are more likely to be paused for questions. Under the US rule, a delay caused by fraud or sanctions screening is one of the listed exceptions to the provider’s duty to deliver by the promised date. So a screening hold can be legitimate. It still needs chasing, because the provider may be waiting on a document from you.
Details that don’t match. A name spelled differently from the account holder’s, a missing account digit, or a wrong bank code can send a payment into a repair queue or bounce it.
Intermediary banks. A payment that crosses several borders may pass through one or more banks in between. Each is another place for a queue or a query. Your bank can often see where, which is why the next step exists.
Receiving-side cut-offs and local rules. The recipient’s bank might credit only on working days, or hold funds for its own checks.
Step 4: Ask your provider for a trace
Contact the company you paid. Not the recipient’s bank, not yet. Say plainly: “Please trace this transfer, here is the reference, the expected date has passed.” Ask for a written case number.
Sent a bank wire? Ask your bank whether the payment carries a UETR. That’s a Swift identifier: a string of 36 characters that appears in all payment instructions carried over Swift. It’s created by the sender’s side and can’t be changed, and Swift says intermediary banks must pass it on rather than generate a new one. Swift compares it to a courier tracking number. It lets banks in the chain locate the payment and see status changes, including confirmation that funds were credited to the beneficiary, or rejected.
Two caveats. First, Swift’s own page describes this as something the banks use. It doesn’t say customers can look it up directly, so ask your bank to run the trace and tell you what it finds. Second, plenty of transfer services don’t use Swift wires at all and move the money through local bank systems, so there may be no Swift trace to run. In that case your provider’s own tracking is the route.
What a good answer sounds like: “It’s at this stage, held for this reason, and we need X from you.” What a poor one sounds like: “It’s been processed.” Ask a follow-up until you have a stage and a next step.
Step 5: Understand what happens if it’s returned
Sometimes a payment can’t be completed and the money is sent back. You’ll want to know what you get back, and the answer depends on why it failed and where you are. The details below are for the United States; the rules elsewhere differ, and we haven’t checked them here, so ask your provider what applies where you live.
Under the CFPB’s Remittance Transfer Rule, if the recipient doesn’t get the money by the disclosed date, that is generally an error you can report, and the provider can offer a refund or a resend at no extra cost. For a late or missing delivery, the provider must also refund the fees, including those charged by third parties, unless you gave incorrect or insufficient information.
Where the problem was incorrect or insufficient details from you, the rule treats it differently. The provider must refund within three business days of reporting its findings, and it may deduct fees and taxes charged by third parties, such as an intermediary bank, but not its own fee. With the provider’s agreement the money can be applied to a fresh transfer instead.
Here’s an illustrative example, with made-up numbers. You send $1,000 and pay the provider a $5 fee. You typed one digit of the account number wrong and the money bounces back, with a different bank taking $15 on the way. On the summary of the rule above, you’d expect $1,000 + $5 − $15 = $990 back. If, instead, the provider simply missed the promised date and you hadn’t made a mistake, the same rule points to the full $1,005 returned, fees included.
Two more details. A wrong account number isn’t automatically your fault under the rule; the provider has to meet a list of conditions, including warning you beforehand that the funds could be lost and making reasonable efforts to recover them. And a refund may come in the original form of payment, so check the card or account you used. If the money is converted back, you may get a slightly different amount than you sent, depending on the rate used, so ask. To see how far a rate has drifted, check USD to PHP or whichever pair you used; the US dollar page lists the rest.
Step 6: Use your deadlines
The same CFPB guidance gives a few clocks worth knowing, for transfers covered by the US rule:
- Cancellation: a request made within half an hour of paying is normally honoured with no cancellation fee, provided nobody has collected or been credited the money yet. Refunds follow within three business days.
- Error reports: the window runs for 180 days from the availability date on your receipt.
- Investigation: once you’ve given notice, the company has 90 days to look into it and report back to you.
The 90 days is a ceiling, not a target, and the provider has to correct the error as soon as reasonably practicable once you choose a remedy. Report in writing, quote your reference, and keep a copy.
Step 7: Escalate if you’re getting nowhere
Should the company fail to resolve it, you can file a complaint with the Consumer Financial Protection Bureau at consumerfinance.gov/complaint. The bureau forwards it to the company and generally expects a response within 15 days. Your receipt also names the state agency that regulates the company, which you can contact too.
Stay factual in the complaint. Dates, amounts, reference numbers, what you were told, what you want. Skip the adjectives.
If you’re outside the US, find the financial regulator or ombudsman for the country where the provider is licensed, and check what that regulator says about time limits. They differ, and we haven’t verified the UK or EU procedures for this article. If you paid by card, your card issuer may offer its own dispute process, so ask them as well.
A short plan to keep
Check the promised date. Gather the references. Contact the provider and ask for a trace and a case number. If it’s returned, ask what was deducted and why. Mind the 180-day and 90-day clocks if you’re covered by the US rule. Then escalate in writing.
None of this is legal or financial advice. Rules and time limits change, so check with your provider, your bank and the relevant regulator.
Sources
- CFPB: Problems sending money to another country?
- CFPB: Regulation E, 12 CFR 1005.33 Procedures for resolving errors
- CFPB: Regulation E, 12 CFR 1005.34 Procedures for cancellation and refund of remittance transfers
- Swift: What is a Unique End-to-end Transaction Reference (UETR)?
- Swift: universal real-time payment tracking
Checked: November 2026