When the transfer is pending
uetr.ai keeps checking tracker data so you can see whether the transfer is still in progress, on hold, rejected, completed, or not found yet.
uetr.ai is the free UETR tracker for SWIFT transfers, a UETR tracking online app that you can use in any browser.
Paste your UETR, add the amount and date, and we check its SWIFT gpi status across the world's banking network in seconds.
Then leave it with us.
uetr.ai re-checks your transfer daily for 30 days and emails you when the status changes. Free.
Trusted by employees at Fortune Global 500 companies, and by thousands of businesses and individuals across 120+ countries.
uetr.ai has already traced the equivalent of over USD 1.8 billion in SWIFT transfers, across 29 currencies.
How it works
Turn "it has left our bank" into the next question worth asking.
Add the 36-character reference, amount, date, and the email you want alerts sent to.
We pull public tracker data into one timeline and translate visible codes like ACSP, ACWC, RJCT into plain English.
Monitoring keeps running after you close the tab. The next status change arrives in your inbox, not after a long wait on a phone queue.
Where the UETR hides on your bank confirmation and MT103, what statuses like ACSP and ACCC mean, and how uetr.ai keeps watching after you close the tab.
SWIFT transfer tracking
Sender bank
London
Correspondent
Frankfurt
Beneficiary bank
Singapore
Tracking a SWIFT transfer starts with the UETR, whichever reference number your bank quoted you. The Unique End-to-end Transaction Reference is the 36-character identifier banks use to follow many SWIFT payments across correspondent banks. With that one reference you can check international wire transfer status yourself instead of waiting for a bank to call back. It may appear on your payment confirmation, MT103 details, payment advice, or in online banking under transaction details.
A UETR number is the 36-character reference that the sending bank puts on a SWIFT payment so every bank in the chain can identify it. The format is a version 4 UUID, and SWIFT has required one on every customer credit transfer since 18 November 2018. It is carried in MT103 field 121 and in the pacs.008 message envelope under ISO 20022. uetr.ai uses that reference to find the status the banks report, so a delayed payroll, supplier payment, or deal no longer depends on guessing.
uetr.ai turns that reference into an always-on status check. Enter the UETR, payment amount, currency, payment date, and your email. From there an agent queries multiple international banks on the SWIFT network for that payment, pulls what each one reports into a single timeline, translates every status code into plain English, and carries on working after you close the page. No bank login, no integration, and nothing for an IT team to approve.
Find your UETR
Your UETR is on the payment confirmation or transfer advice your bank issued when the payment was sent. On an MT103 it is field 121. In most banking apps it appears under the payment's transaction details, sometimes labeled Unique End-to-end Transaction Reference or End-to-end Reference. If you cannot see it, ask the sending bank for the UETR of your transfer.
A UETR is 36 characters in version 4 UUID format: 32 hexadecimal characters in five groups of 8-4-4-4-12, separated by hyphens, and normally shown in lower case. An example UETR looks like 3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43. It is not your account number, not the SWIFT/BIC code, and not the sender's own payment reference.
| Where to look | What it is called there |
|---|---|
| Outbound payment confirmation or transfer advice | Labeled "UETR" or "Unique End-to-end Transaction Reference" |
| MT103 message | Field 121 |
| Online or mobile banking, under the payment's details | Labeled "End-to-end Reference", "Transaction Reference", or "UETR" |
| The sending bank, by phone or secure message | Ask for "the UETR of my transfer" |

Step by step
Gather the exact 36-character UETR, the payment amount, the currency, and the payment date. Enter them at uetr.ai with an email address for alerts. uetr.ai queries multiple international banks on the SWIFT network for that payment, translates every status code into plain English, and keeps watching after you close the tab.
uetr.ai is a free, independent UETR tracker that runs in any browser. You paste the UETR, add the amount, currency, and payment date, and it queries multiple international banks on the SWIFT network for that payment and shows what they report, with no login and no bank credentials.
You need the exact 36-character UETR, the payment amount, the currency, and the payment date. Banks use the amount and date to locate the payment, so all four matter.
Paste the UETR into the form at the top of this page and add the email address where you want alerts sent. No login and no bank credentials are required.
uetr.ai pulls what each bank reports into one timeline and translates every status code, such as ACSP for in transit or ACCC for credited to the beneficiary, into plain English.
Checking continues after you close the tab. A free transfer is re-checked once every 24 hours for 30 days, and you get an email when the status moves.

Domestic and international
For an international SWIFT transfer, trace it by its UETR: give the sending bank that reference, or enter it in a tracker to see which banks have reported it. Domestic transfers do not usually carry a UETR, so they are traced through the sending bank by its own reference, such as a Fed reference or IMAD number.
| International SWIFT transfer | Domestic transfer | |
|---|---|---|
| Reference | UETR, 36 characters | The sending bank's own reference, such as a Fed reference or IMAD number |
| Where to find it | Field 121 of the MT103, or the payment confirmation | The payment confirmation or your bank's transaction details |
| Who can trace it | The sending bank, or an independent monitoring service such as uetr.ai | The sending bank. There is no UETR to look up, so uetr.ai cannot trace it |
| Reference | Assigned by | Changes between banks | Tracks the payment |
|---|---|---|---|
| UETR | The sending bank, once | Never, it stays the same end to end | Yes |
| Transaction reference, field 20 | Each bank, for its own records | Every time the payment changes bank | No |
| End-to-end identification | The person or business paying | Never, but banks do not track by it | No |
| IBAN or account number | The bank holding the account | Not applicable, it identifies an account | No |

Before you call the bank
Start the next call to your bank with specifics.
When a transfer is delayed, the hardest part is often knowing what to ask. A bank may ask for the UETR, wire transfer tracking number, sender reference, payment date, amount, currency, beneficiary bank, or correspondent bank details. uetr.ai helps you organize the status information that is visible from bank trackers so your next call to the sending or receiving bank starts from facts.
When the trail goes quiet
The bank name is not enough when the deadline is moving.
The first instinct is to search for the bank: the sender, the receiver, or the correspondent in the middle. That makes sense. Your money left a familiar name, then seemed to disappear into a chain of banks you may never speak to directly.
But international transfers do not travel by brand name alone. They travel by reference. The UETR can help identify a SWIFT payment from one bank to the next. When a bank tracker has data, uetr.ai uses that reference to look for available transfer status and turn whatever it finds into something you can use when you call the bank.
A transfer can be sent and still not be received. Somewhere between those two statements are correspondent banks, compliance reviews, bank cutoff times, weekends, holidays, and systems that do not all update at the same time. All of it shapes how long an international transfer takes, which is exactly when you need the UETR, the available status, the last observed timestamp, any visible status code, and the next question to ask.
uetr.ai keeps checking tracker data so you can see whether the transfer is still in progress, on hold, rejected, completed, or not found yet.
Use the UETR, latest status, timestamps, and any visible bank processing codes to ask the sending bank for a trace or investigation.
The agent checks every day, weekends and holidays included, so you are not waiting for one office to open before you know whether tracker data changed.
Which side are you on
If you sent the payment, ask the sending bank for the UETR, then track it yourself. If you are waiting to be paid, you cannot get the UETR from your own bank, because it belongs to the sender's payment. Ask the sender for the UETR and the payment confirmation, then track it with them.
Ask the sending bank for the MT103, the sending bank's record of the payment instruction it released. Send it with a uetr.ai tracking link, so the supplier can also see the status the tracker sources report. The link replaces the sender's amount, currency and payment date field by field, using the bank reports that have reached the link, and only where those reports carry an amount: a reported date on its own does not replace anything. Every figure those reports have not covered is still the one the sender entered, and the date is shown as a value date only where a bank reported one.
A document is something you are handed. A link is something the other side can check, and it keeps updating after they check it. See what an MT103 contains.
Ask the sender for the UETR and a uetr.ai tracking link. The link shows what supported bank tracker sources reported for that reference: how far along it is, and a bank's amount, currency and value date field by field, wherever the bank reports that have reached the link provide them and carry an amount. Every figure those reports have not covered is still the one the sender entered, and a reported date with no amount beside it covers nothing. So the status, and whichever of the three those reports have covered, is the part that does not come from the sender.
A shared tracking link shows the status the tracker sources reported, and it shows the amount, the currency and the payment date as the banks reported them field by field, for whichever of the three the bank reports that have reached the link cover, and only where those reports carry an amount: a reported date on its own does not replace anything. Any of the three those reports do not cover is still the figure the sender entered. So the status, and whichever of the three those reports have covered, is the part that does not come from the person telling you about the payment.
Status codes
A code is only useful if it gives you the next sentence.
ACSP means accepted and in progress. The reason code that follows says why: G000 passed to another gpi bank, G001 passed to a bank outside gpi, G002 credit may not complete the same day, G003 credit pending documents, G004 credit pending funds, G005 and G006 delivered to the beneficiary bank. ACCC means credited to the beneficiary account. RJCT means rejected.
Bank and SWIFT-related tracker pages may show payment status codes, bank processing statuses, timestamps, or rejection messages. A code like ACSP, ACWC, or RJCT can matter. But it only helps if you can translate it into a practical next step.
uetr.ai explains visible status codes in plain English and sets out the question you can take back to the bank. Where was the payment last seen? Was it accepted, changed, rejected, or still in progress? What should the sending or receiving bank confirm next?

| Code | Stands for | What it means for your transfer |
|---|---|---|
| ACSP | AcceptedSettlementInProcess | Your transfer is on its way. |
| ACSC | AcceptedSettlementCompleted | Settlement is complete at a bank in the chain. The credit to the beneficiary is not confirmed yet. |
| ACCC | AcceptedCreditSettlementCompleted | The beneficiary's bank is reporting that it credited the account. |
| ACWC | AcceptedWithChange | Accepted, but something changed along the way. |
| ACWP | AcceptedWithoutPosting | The beneficiary's bank has the money but is holding it. |
| PDNG | Pending | A bank in the chain is reviewing the transfer. |
| RJCT | Rejected | The transfer was rejected. The money is coming back. |
An ACSP status is often followed by a slash and a reason code. The reason code is the useful half: it says which kind of bank now holds the payment, or what the crediting bank is waiting for.
| Code | What it means for your transfer |
|---|---|
| ACSP/G000 | Passed to the next SWIFT gpi member bank. A normal handover, and tracking continues. |
| ACSP/G001 | Passed to a bank that is not a SWIFT gpi member. Tracker updates may stop from this point, which does not mean the payment stopped. |
| ACSP/G002 | Settlement or credit may not complete the same day, often during a manual review, an FX step, or a wait for the value date. |
| ACSP/G003 | Credit pending documents or further information from the beneficiary or an intermediary bank. |
| ACSP/G004 | Credit pending the availability of funds. The beneficiary bank is waiting for the cover payment. |
| ACSP/G005 | Delivered to the beneficiary bank with the gpi service level intact. The account still has to be credited, which is reported separately as ACCC. |
| ACSP/G006 | Delivered to the beneficiary bank outside the gpi service level. The money is at the bank, but the final credit may not be tracked, so ask the beneficiary to confirm it. |
Why teams monitor
Some status changes start a clock.
Most of the time a status is simply news. The payment is moving, nothing is wrong, and knowing that is enough to stop the team worrying. But not every update is news. Three of them are the beginning of a deadline.
A bank in the chain refuses the payment and it travels back to the sender, carrying a reason code that says exactly what to correct before sending again.
The payment goes through, but a bank deducted a fee, converted the currency, or moved the value date, so the beneficiary receives something other than what you instructed.
A bank pauses the transfer while it waits for a document or an answer, and the person who could supply it is often never told that it is waiting.
Each one is easiest to resolve close to the day it happens, while the banks involved still have the transaction in front of them. A week later the same conversation takes far longer, and the money has been somewhere else the whole time.
That is the real cost of silence. Not the waiting, but missing the day your team could still act on it.
A free check answers the question you have right now: can the banks see this transfer, and what did the last one report. Monitoring answers a different one. It keeps watching the transfer around the clock, names the banks that reported it, explains every code in plain English, and emails your team the moment anything moves rather than the next day.
FAQ
A UETR is a Unique End-to-end Transaction Reference, usually shown as a 36-character reference on a SWIFT or international wire transfer confirmation.
Your UETR is on the payment confirmation or transfer advice your bank issued when the payment was sent. On an MT103 it is field 121. In most banking apps it appears under the payment's transaction details, sometimes labeled Unique End-to-end Transaction Reference or End-to-end Reference. If you cannot see it, ask the sending bank for the UETR of your transfer.
A UETR is 36 characters in version 4 UUID format: 32 hexadecimal characters in five groups of 8-4-4-4-12, separated by hyphens, and normally shown in lower case. An example UETR looks like 3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43. It is not your account number, not the SWIFT/BIC code, and not the sender's own payment reference.
Gather the exact 36-character UETR, the payment amount, the currency, and the payment date. Enter them at uetr.ai with an email address for alerts. uetr.ai queries multiple international banks on the SWIFT network for that payment, translates every status code into plain English, and keeps watching after you close the tab.
For an international SWIFT transfer, trace it by its UETR: give the sending bank that reference, or enter it in a tracker to see which banks have reported it. Domestic transfers do not usually carry a UETR, so they are traced through the sending bank by its own reference, such as a Fed reference or IMAD number.
ACSP means accepted and in progress. The reason code that follows says why: G000 passed to another gpi bank, G001 passed to a bank outside gpi, G002 credit may not complete the same day, G003 credit pending documents, G004 credit pending funds, G005 and G006 delivered to the beneficiary bank. ACCC means credited to the beneficiary account. RJCT means rejected.
If you sent the payment, ask the sending bank for the UETR, then track it yourself. If you are waiting to be paid, you cannot get the UETR from your own bank, because it belongs to the sender's payment. Ask the sender for the UETR and the payment confirmation, then track it with them.
Ask the sending bank for the MT103, the sending bank's record of the payment instruction it released. Send it with a uetr.ai tracking link, so the supplier can also see the status the tracker sources report. The link replaces the sender's amount, currency and payment date field by field, using the bank reports that have reached the link, and only where those reports carry an amount: a reported date on its own does not replace anything. Every figure those reports have not covered is still the one the sender entered, and the date is shown as a value date only where a bank reported one.
Ask the sender for the UETR and a uetr.ai tracking link. The link shows what supported bank tracker sources reported for that reference: how far along it is, and a bank's amount, currency and value date field by field, wherever the bank reports that have reached the link provide them and carry an amount. Every figure those reports have not covered is still the one the sender entered, and a reported date with no amount beside it covers nothing. So the status, and whichever of the three those reports have covered, is the part that does not come from the sender.
Checking a transfer is free, with no account and no card. uetr.ai then re-checks it automatically once every 24 hours for 30 days and emails you once a day if the status moves. Paid plans re-check on demand, name the banks that reported, explain each code, and email you the moment anything changes.
Yes. uetr.ai is a UETR tracking online app that runs in any web browser. You open the page, enter your UETR, amount, currency, and payment date, and it queries multiple international banks on the SWIFT network for that payment and emails you when the status changes. There is nothing to download or install.
uetr.ai uses your UETR and payment details to query multiple international banks on the SWIFT network for that payment, and consolidates whatever they report into one timeline. It is not SWIFT, a bank, or a payment network, and it never needs your banking login.
Enter the UETR, amount, currency, payment date, and your email. uetr.ai starts a tracker lookup, keeps checking for updates, and emails you the moment the status changes.
Some bank trackers update slowly or show limited information. uetr.ai keeps checking and emails you when the available status changes.
You can start a free UETR lookup on uetr.ai. If public tracker data is available, the free preview shows available high-level status before you decide whether to keep monitoring the transfer.
International SWIFT transfers carry a UETR, a 36-character identifier the sending bank generates and SWIFT requires on every customer payment since November 2018. Domestic transfers use different bank-internal reference numbers and typically do not carry a UETR.
Yes, banks can trace international transfers, and a UETR helps identify the payment across correspondent banks. uetr.ai does not replace a bank trace, but it can give you available tracker status before you call the bank.
uetr.ai is an independent monitoring service rather than SWIFT itself, and it does not resell SWIFT gpi network access. It queries multiple international banks on the SWIFT network for your payment, consolidates what they report into one timeline, and keeps checking, so your team watches one view instead of several bank portals.
If a public tracker is available and readable, uetr.ai can check it with the details you provide. It is independent and not affiliated with any bank, SWIFT, or payment network, so the useful question is less which bank and more whether you have the UETR, amount, currency, and payment date.
SWIFT and bank trackers can show codes such as ACSP, ACWC, RJCT, or similar bank processing statuses. uetr.ai explains visible status codes in plain English so you know what to ask the sending or receiving bank next.
International transfers often arrive within one to five business days, but correspondent banks, compliance reviews, weekends, holidays, and missing details can delay them. uetr.ai keeps checking bank trackers across time zones while you wait.
Thirty-six characters on a payment confirmation are enough to find out whether the banks can see your transfer. Checking is free, and it takes about a minute.
Check a transfer free