Loading article...
Slot ID: blog-post-top
You hit send on €1,800 to a supplier in Porto on Tuesday morning. By Thursday the money has left your account, your banking app still says "in progress", and the supplier says nothing has landed. Now you're stuck in that familiar loop: refreshing the app, checking the clock, wondering whether you should call someone or just wait.
Tracking a transfer properly isn't about refreshing harder. It comes down to three things: knowing which reference number to follow, understanding what the status labels actually mean, and knowing the point at which silence stops being normal and becomes something worth escalating.
Every international payment carries at least one identifier, and it is almost never the same as the reference you typed into the "payment description" box. That box is for the recipient's bookkeeping. The tracking number lives somewhere else.
Take a screenshot of the confirmation screen and paste the number into a note you'll actually find again. If you're moving money between your own accounts at two banks, the sending bank's payment reference is often the only thing the receiving bank can search on, which matters more than most people realise when transferring money between banks without wasting days or dollars.
This is the first stop and usually enough for transfers under a few thousand pounds or dollars. Look for a timestamp, not just a status word. "Processing since 09:14 on 14 March" tells you far more than "processing".
Most large banks now expose a gpi tracker inside online banking, and it shows each hop: which correspondent bank received the funds, when, and how much. If your bank doesn't display it, phone support and ask them to run a gpi trace on the UETR. That single request gets you a definitive answer about where the money physically sits, rather than a customer service agent reading the same screen you can see.
This is the step people skip. Plenty of transfers show "in transit" on the sender's dashboard for a full day after the money has already landed, simply because the sending system updates in batches. A two-minute message to the recipient asking them to check both their posted balance and any pending or held items will resolve more confusion than another hour of refreshing.
Providers use different words for the same five stages, and the gaps between them are where worry creeps in.
The delivered-to-credited gap causes more support calls than any other stage. Nine times out of ten it's because the sender's reference was missing or the account name didn't match closely enough for the receiving bank's automated checks, so the payment is parked in a manual queue. That queue often clears within a business day, but nobody tells you that unless you ask.
A payment from a US bank to a small regional bank in Kenya might pass through two intermediary institutions before it arrives. Each one applies its own cut-off time, its own compliance screening, and its own weekend. Send on a Friday afternoon in New York and the funds can genuinely sit untouched until Monday.
Currency conversion adds another pause. If the receiving bank converts on arrival rather than your provider converting upfront, the payment waits in a queue for the next rate application. It's worth understanding how long an international money transfer actually takes before you assume something has gone wrong, because a two-day gap on a bank-to-bank payment to an emerging market is ordinary, not alarming.
Once a payment has passed its provider's stated maximum delivery time, work through these in order. Don't skip the first two.
Here's the part that rarely shows up in a tracking dashboard. A transfer can arrive exactly on time and still cost you 3% more than it should, because the rate you were quoted at send isn't always the rate applied at settlement, and intermediary banks sometimes deduct their handling fee from the principal before it lands.
Compare the amount debited from your account with the amount credited to the recipient. If the gap is bigger than the fee you were quoted, the difference is usually an exchange rate markup or a shared-charge deduction. Senders get hit by this more often than receivers, which is why it pays to know how to transfer money internationally without handing over 3% to the exchange rate. If you're on the receiving end of a payment, the same logic applies in reverse, and receiving money from abroad without losing 4% along the way covers the questions worth asking before the funds are sent.
One practical fix: ask whether the transfer is being sent as OUR, SHA or BEN. OUR means the sender covers all intermediary fees, so the recipient gets the full amount. SHA splits them. BEN means the recipient absorbs everything. A supplier invoicing for €5,000 expects €5,000, and the difference between SHA and OUR can be €30 to €60 on a transfer that size.
The people who never seem to lose transfers aren't luckier. They've built a handful of habits that remove the guesswork.
They keep a running note with every reference number, provider, amount and date, because reconstructing a payment history six weeks later from bank statements is miserable. They send on Tuesday or Wednesday mornings, which gives a full three business days of settlement runway before a weekend interrupts anything. They confirm the recipient's account details by voice or video at least once, especially with a new payee, since bank name-matching checks reject more payments than most people expect.
They also choose providers that publish realistic delivery windows rather than optimistic ones, and they treat a missed window as information rather than an emergency. If you want to reduce the odds of a payment going sideways in the first place, the same principles that help you send money abroad without losing 3% on the way also give you a shorter, more predictable route with fewer intermediary banks to trace through.
Then the tracking itself becomes a five-second check rather than an anxious daily ritual. You'll know what number to search, what each status means, and exactly how long to wait before picking up the phone.
Slot ID: blog-post-bottom