How to Track an International Wire Transfer: UETR, Swift GPI, and What to Do When a Payment Is Stuck
Learn how to track an international wire with a UETR, read Swift GPI status codes, find out why payments get stuck, and what to ask your bank so the money arrives faster.

How to Track an International Wire Transfer: UETR, Swift GPI, and What to Do When a Payment Is Stuck
Your buyer says the payment went out on Monday. It is Thursday and nothing has arrived. Your bank says it has no record. The buyer's bank says the money left. Somewhere between the two, a payment worth a month of payroll is sitting in a queue, and nobody on either side seems to know which queue.
International wires used to work like this most of the time. Today they mostly do not. Since 2018, every payment instruction sent over Swift carries a unique reference that every bank in the chain must pass on unchanged. Banks that belong to Swift GPI report each step to a shared tracker, so the payment's location is visible in close to real time. The trouble is that many businesses do not know the reference exists, do not ask for it, and do not know how to read the status their bank gives them.
This guide explains how an international wire moves, what the MT103 and its ISO 20022 replacement are, how to use the UETR to track a payment, what the GPI status codes mean, why payments get stuck, and what to do day by day when one is late. It is written for exporters, importers, and finance teams that send or receive cross-border payments.
Specie (Untappd Labs Inc. DBA Specie) is not a bank and does not hold deposits. Payment services run through regulated partners. See How Does Specie Work?
How an international wire moves
A domestic transfer usually moves through one clearing system that both banks belong to. A cross-border wire often needs more than that, because the sending bank may not hold an account in the currency or country of the receiving bank.
A typical USD payment from a buyer in Germany to a seller in Vietnam looks like this:
The buyer's bank (the debtor agent) debits the buyer's account and sends a payment instruction over Swift.
An intermediary bank, often a correspondent bank in the United States that holds USD accounts for both sides, moves the funds between the banks' accounts. There can be one, two, or no intermediaries.
The seller's bank (the creditor agent) receives the instruction and the funds, runs its own checks, and credits the seller's account.
Long chains are rarer than you might expect. Swift's data shows that 86% of payments on its network go directly between two institutions or through a single intermediary (Swift, 2024). Each bank in the chain can still hold a payment for checks, and each can take a fee unless the charge instruction says otherwise. Specie's guide to international business transfer costs explains the OUR, SHA, and BEN charge options and how deductions add up.
MT103, pacs.008, and the "Swift copy"
For decades the standard Swift message for a customer payment was the MT103, a single customer credit transfer. When a buyer said "I'll send you the MT103," they meant a copy of that message, showing the amount, value date, sender, receiver, and the banks involved. Sellers used it as proof that a payment had left.
That format has now been replaced for bank-to-bank payments. Swift ended the coexistence period between the old MT messages and the ISO 20022 standard on 22 November 2025, and ISO 20022 is now required for cross-border payment instructions (Swift, 25 November 2025). The ISO 20022 equivalent of the MT103 is the pacs.008 message. Swift still converts a small number of MT103s into pacs.008 as a paid contingency service, and in August 2026 it said more than 98% of payment instructions were already sent in ISO 20022 (Swift, 27 August 2026).
In practice, many people still say "MT103" when they mean "proof of payment from the bank." That is fine. What you need from the payer is a bank-issued payment confirmation that shows:
The UETR (the tracking reference, covered next)
The amount and currency sent
The value date
The beneficiary name, account number or IBAN, and bank BIC
Any intermediary bank named in the instruction
The charge option (OUR, SHA, or BEN)
The remittance information, such as your invoice number
A screenshot of an online banking screen that says "payment submitted" is weaker evidence. It shows the payer asked their bank to send money. It does not show the bank sent it.
The UETR: your payment's tracking number
The Unique End-to-end Transaction Reference (UETR) is a 36-character string, for example eb6305c9-1f7f-49de-aed0-16487c27b42d. Swift describes it as working "very much like the tracking number couriers use when you send or receive a parcel" (Swift).
Three rules make it useful:
The sending bank creates it. It is generated when the payment instruction is created, so it exists from the first minute.
No other bank may change it. Intermediary banks must pass the same UETR along. Cover payments between banks carry a copy of the original UETR too.
Every Swift user must include it. UETRs have been required on customer and bank payment messages since November 2018, for gpi and non-gpi banks alike.
Because the reference never changes, any bank in the chain can look up the same payment without matching a different internal reference at each step. When you call your bank about a missing payment, the UETR is the first thing they will ask for. If you are the seller, ask the buyer to send it with their payment confirmation. If you are the buyer, ask your bank for it the day you send.
Swift GPI and the Tracker
Swift GPI (global payments innovation) is a set of rules and tools that banks join to make cross-border payments faster and traceable. Members agree to service levels, pass the UETR along, report each payment's status, and show the fees they deduct.
The core tool is the GPI Tracker, a cloud database where each bank reports what it did with a payment: received it, passed it on, put it on hold, credited it, or rejected it. Swift says nearly 60% of GPI payments are credited to end beneficiaries within 30 minutes and almost all within 24 hours (Swift GPI).
Since November 2020, Swift's universal confirmations rule has required regulated banks on the network to confirm to the Tracker when a customer payment is credited, put on hold, or sent outside Swift, even if the bank is not a GPI member. That closed a large blind spot at the receiving end.
Who can see the Tracker
The Tracker is a bank tool. Businesses usually see it in one of three ways:
Bank portal tracking. Many banks show GPI status inside online banking, next to each outgoing or incoming payment.
Ask your bank. Give the UETR to your bank's payments team and ask for the current GPI status, the last bank to update it, and any deductions.
Corporate tools. Larger companies can use Swift's GPI services for corporates, such as pay and trace and inbound tracking, to see payments across all their banks in their treasury or ERP system. Some payment providers also offer GPI tracking through their APIs.
Swift Go for smaller payments
Swift Go is a Swift service for consumers and small businesses that runs on the same rails as GPI. Payments up to the equivalent of USD 10,000 come with upfront fee and FX disclosure, and banks agree to credit the full amount and provide tracking (Swift Go). If you pay many small suppliers abroad, ask your bank whether it offers Swift Go.
How to read GPI status codes
When your bank gives you a tracking status, it usually comes as a pair: a status code and a reason code. The codes come from the ISO 20022 code sets. Here are the ones you will see most often.
Code | What it means | What you should do |
|---|---|---|
ACSP / G000 | Accepted and passed to the next bank, which is tracked | Wait. Check again in a few hours |
ACSP / G001 | Passed to a bank that does not report to the Tracker | Ask that bank's customer (often the beneficiary) to check locally |
ACSP / G002 | Credit may not be confirmed today. Update will follow | Expect next-day credit. Check for holidays or cut-offs |
ACSP / G003 | Credit pending documents. The bank asked its customer for more information | The beneficiary should contact their bank and answer the request |
ACSP / G004 | Credit pending funds. Waiting for money from the previous bank | Ask the sending bank to check that the cover payment was made |
ACCC | Credited to the beneficiary's account | Done. If the beneficiary cannot see it, they should ask their bank |
RJCT | Rejected. A reason code explains why | Fix the problem and resend. Expect a return of funds |
Sources: Swift GPI Tracker API specification and Goldman Sachs payment status reason codes.
Common rejection reason codes include:
AC01: account number invalid or missing
AC04: account closed
AC06: account blocked
BE01: beneficiary name does not match the account
RR03: creditor name or address missing or not enough for regulatory needs
RC01: BIC in the wrong format
FF07: payment purpose missing or invalid
DUPL: duplicate payment
A rejected payment comes back to the sender, often minus fees and sometimes converted twice if a currency exchange already happened. Fix the cause before resending, or the second payment will fail the same way.
How long an international wire should take
Two numbers matter, and they are often confused.
Bank to bank. Swift reports that 90% of cross-border payments on its network reach the beneficiary's bank within an hour (Swift, 2024). In March 2026, Swift said 75% reach the beneficiary's bank within 10 minutes (Swift, Countdown to 2027).
Bank to account. Only 43% of payments were credited to the end customer's account within an hour in Swift's 2024 data. In the same March 2026 article, Swift says the last step, from the receiving bank to the customer's account, takes about 80% of a payment's total journey time. The reasons are local: regulatory checks, risk controls, manual work, and domestic systems that are not open 24/7.
The G20 has set targets for 2027. For wholesale cross-border payments, 75% should be credited within one hour and the rest within one business day (FSB, G20 targets). The Financial Stability Board's 2025 progress report measured 54.6% of wholesale payments credited end to end within one hour, and 35.4% of retail payment services crediting within an hour (FSB, October 2025).
For planning, a reasonable expectation is:
Same day for major currencies between well-connected banks, if sent before cut-off
One to two business days for most other corridors
Longer where the receiving country requires extra documents, currency controls, or manual review
Cut-off times and holidays matter more than distance. A USD payment sent from Singapore at 5 p.m. local time on a Friday may not move until U.S. banks open on Monday. A payment into a country with a public holiday the next day waits too. Swift's 2024 speed figures exclude non-banking days in the receiving country.
Why international payments get stuck
When a wire is late, the cause is usually one of these.
Compliance and sanctions screening
Every bank in the chain screens names, addresses, countries, and payment details against sanctions lists and its own risk rules. A partial name match, a sensitive country, or vague goods description can trigger a manual review. The bank may send a request for information to the previous bank, which passes it back to the payer. Each step adds hours or days. Full legal names, complete addresses, and a clear goods description reduce false matches.
Name, account, or bank details that do not match
A beneficiary name that differs from the account name, a wrong IBAN check digit, or an old BIC can stop a payment at the receiving bank. Some banks will ask their customer to confirm. Others will reject with AC01 or BE01. Swift's Payment Pre-validation service lets sending banks check beneficiary account details before the payment leaves, so ask whether your bank uses it.
Missing purpose codes or local reporting data
Some countries require a payment purpose code, tax ID, or other regulatory data for incoming foreign currency. If it is missing, the receiving bank holds the payment and asks the beneficiary for documents. That often shows up as ACSP/G003. Sellers should tell buyers in advance exactly what data their country needs.
Waiting for funds
In some payment chains, the instruction and the money travel separately. The receiving bank gets the instruction but has to wait for the cover payment. That shows as ACSP/G004. The sending bank or intermediary needs to fix it.
A bank outside the Tracker
If a payment moves to a bank that does not report to GPI, the trail goes quiet. Status G001 tells you the last tracked bank passed it on. The payment may still be fine, but you lose visibility until it is credited.
Address data
Swift had planned to stop accepting fully unstructured postal addresses in cross-border payment messages from November 2026, so that at least the town and country sit in their own fields. On 27 August 2026, Swift deferred that change after many banks said they were not ready, and said it would give a new timeline by December 2026 (Swift). Some domestic payment systems are keeping their own dates. Keep your company's full address, town, postal code, and country on file with each bank and buyer now, so the change does not affect your payments when it arrives.
Cut-offs, time zones, and holidays
A payment can be fully correct and still arrive a day or two later than expected because it missed a cut-off or hit a holiday at one of the banks along the way.
What to do when a wire is late: a day-by-day plan
Calls to a general customer service line rarely get a payment moving. Give the right bank the right reference and a clear question.
When | If you are the payer | If you are the beneficiary |
|---|---|---|
Day 0 | Get the UETR and payment confirmation from your bank. Send both to the beneficiary | Ask the payer for the UETR and the bank-issued confirmation |
Day 1 | Check GPI status in your portal or with your bank | Ask your bank whether an incoming payment with that UETR has arrived |
Day 2 | If status is G003 or the payment is on hold, ask which bank holds it and what it needs | If your bank requests documents, send them the same day |
Day 3 | Ask your bank to open a formal investigation on the UETR | Ask your bank for the date and time the funds were received, if they were |
Day 5+ | Ask for written status and any rejection reason. Consider recall if the details were wrong | Escalate with your relationship manager, citing the UETR and status |
What to send your bank
A short, precise message gets a faster answer. For example:
Please trace outgoing payment UETR eb6305c9-1f7f-49de-aed0-16487c27b42d, sent 3 November 2026, USD 85,000.00, to Example Trading Co., Ltd., account 0123456789 at [beneficiary bank, BIC]. The beneficiary reports no credit. Please confirm the current GPI status and reason code, the last bank to update it, any deductions, and any request for information. If the payment is held, please tell us what is needed.
Keep the invoice, payment confirmation, contract, and any shipping documents ready. A compliance hold often clears faster when you can send supporting documents the same day.
Stopping or recalling a payment
If you sent money to the wrong account or suspect fraud, act within minutes. Swift's GPI stop and recall service lets banks stop a payment that is still in flight. The request goes through the Tracker to the bank holding the payment, and Swift asks that bank to process the request within 24 hours (Swift developer portal).
Once funds are credited to the beneficiary's account, a recall becomes a request. The receiving bank usually needs the account holder's consent to send money back. The earlier you call your bank, the better your chances.
For business payments, you should not count on consumer protection rules. In the United States, for example, the remittance transfer rule in Regulation E covers transfers sent by consumers, not most business wires (CFPB, 12 CFR 1005.30). Business-email compromise scams often target exactly this gap. Always confirm new or changed bank details by phone using a number you already have, not one from the email that announced the change.
Before you send: a checklist that prevents most delays
Beneficiary name exactly as on the account. Ask for a bank letter or a recent statement header if you are paying a new supplier.
Correct account format. IBAN where the country uses it. Local account number plus routing code where it does not.
Correct BIC for the right branch or entity. Check it against the beneficiary's bank letter.
Full address with town and country. Use separate fields where your bank's form allows it.
Purpose of payment. Add a purpose code if the receiving country requires one, plus a plain description such as "Payment for invoice INV-2026-118, frozen shrimp."
Invoice number in the remittance information. It saves the beneficiary's finance team hours of matching.
Charge option agreed in the contract. OUR, SHA, or BEN, so nobody is short-paid.
Cut-off time and holidays checked for both countries and for the currency.
UETR saved in your payment record the same day.
For sellers, put your payment instructions on every invoice, in the same format each time, and include any purpose code or data your country needs. Ask buyers to send the UETR with every payment. A clause in your sales contract stating that the buyer will provide a bank-issued payment confirmation within one business day of sending is a reasonable request.
A worked example
A furniture maker in Brazil ships a container to a buyer in Canada on open account terms. The invoice is for USD 85,000, due 3 November. The buyer sends the payment on the due date. Four days later, the seller still has nothing.
Day 0. The seller asks for the payment confirmation. The buyer sends a screenshot from online banking. The seller asks for the bank-issued confirmation with the UETR. It arrives the next morning.
Day 1. The seller's bank in Brazil runs the UETR. The status is ACSP/G003: credit pending documents. The bank says it needs the export registration details and the commercial invoice to complete the foreign exchange contract.
Day 1, afternoon. The seller sends the documents. The payment is credited the next business day.
The money had reached the seller's bank within hours of being sent. The delay was entirely in the last step, and it cleared within a day once the seller knew what was needed. Without the UETR, the seller would likely have chased the buyer, and the buyer would have chased their own bank, for several more days.
Numbers in this example are illustrative. Real documentation needs vary by country and bank.
When tracking is not the real problem
Tracking tells you where your money is. It does not make your buyer pay sooner. If the real issue is that you wait 30, 60, or 90 days for payment after you ship, faster wires will not fix your cash gap.
Some options to look at:
Ask for a deposit before production or shipment, especially with new buyers.
Use invoice factoring to get paid early on approved invoices. Specie offers factoring when you sell into the U.S., EU, or Canada. You ship, invoice, and receive an advance, then the buyer pays on the normal due date. Specie's ballpark factoring fee orientation is about 1.5% to 3% per 30 days (not a quote; pricing depends on the buyer, tenor, and invoice quality). See recourse vs non-recourse factoring and Improve Cash Flow.
Plan the currency conversion. If you are paid in USD or EUR but spend in another currency, the rate on the day of arrival affects your margin. See FX risk hedging for exporters.
Reduce the number of banks involved. Receiving funds through a local or multi-currency account in the payer's currency zone can remove a cross-border leg. Specie's comparison of Specie vs Wise Business and its guide to global business bank accounts cover options.
Brazilian exporters can also read how to receive USD faster, which covers local FX contract steps that often cause G003-type holds.
FAQ
Can I track an international wire myself?
Usually through your bank. Many banks show Swift GPI status in online banking. If yours does not, give the UETR to the payments team and ask for the status and reason code. Some payment providers show GPI status in their apps or APIs.
Is the UETR the same as the MT103?
No. The MT103 was the old Swift message format for a customer payment, now replaced by the ISO 20022 pacs.008 for bank-to-bank instructions. The UETR is the tracking reference inside that message. A payment confirmation should show both the payment details and the UETR.
My bank says the payment was credited, but I cannot see it. Why?
Status ACCC means the beneficiary's bank reports the account as credited. If the beneficiary cannot see the funds, the issue is inside that bank: a different account, a currency sub-account, or a posting delay. The beneficiary should ask their bank with the UETR.
Who pays the fees deducted along the way?
That depends on the charge option. Under SHA, the payer pays the sending bank's fee and the beneficiary bears intermediary and receiving fees. Under OUR, the payer covers all fees, though some third-party charges can still be deducted. See international business transfer costs.
How long should I wait before raising a trace?
For major currencies, if the payment has not arrived by the end of the second business day after the value date, ask your bank. If the status shows G003 or a hold, act the same day.
Talk to Specie
If late or hard-to-trace international payments are slowing your cash, or you want early payment on invoices to buyers in the U.S., EU, or Canada, Specie can help you map cross-border payments, FX, and invoice factoring options. Specie is not a bank; services run through regulated partners. Get a soft quote at specie.finance/quote or message the team on WhatsApp.
Back to articles