Paste your UETR
Add the 36-character reference, message date in your timezone, and the email where you want updates.
Your transfer is not lost, it is silent. We turn that silence into a status.
UETR.io brings your transaction into view. An online tracker you can use in any browser.
Paste your UETR, add the message date and your email, and see the latest recorded update. The amount and currency come straight from your transaction.
Then stay in the loop.
Confirm your email to receive new recorded status updates. One reference, a clearer journey. Free.
Find your record and get an email when a new status is recorded.
Read-only lookup · Confirmed email alerts · Protected personal details
Turn “the message is ready” into a record you can follow.
Add the 36-character reference, message date in your timezone, and the email where you want updates.
Find the transaction’s amount, currency, banks and recorded events together in one timeline.
Confirm your email once. When a new event is recorded, the update can come to your inbox.
A quick look at how your UETR connects the details.
Start with your UETR
Explore the tracking guide ↗Tracking starts with the UETR: the unique end-to-end transaction reference attached to your message. It gives you a consistent way to identify the same transaction when asking for an update.
On UETR.io, enter the reference generated by the transaction system, the message date in your timezone, and your email. We match it against registered records and display the transaction’s recorded events with the newest first.
The amount and currency are taken from the original transaction record. You do not need to re-enter them here. This keeps your lookup tied to the original record.
Your timeline shows registered transaction records. A generated message or a system status does not independently confirm that a bank has sent, settled or credited a payment. Confirm financial outcomes with your bank.
Look up your UETR →Look on your generated transaction message. If someone else generated the message, ask them for the UETR and its generation date in your timezone.
A UETR is a 36-character identifier in five groups, separated by hyphens. It is different from an account number, a bank’s SWIFT/BIC code or a payment description.
3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43Example format only. This is not a live transaction.
| Where to look | What to look for |
|---|---|
| Transaction message | UETR or unique end-to-end reference |
| Transaction operator | Original UETR and message date in your timezone |
| Payment confirmation | Ask the issuer where the UETR is shown |
| Bank support | Ask for the reference of your transfer |
The message format can change. The transaction reference connects the record.
Tag-based plain text, blocks 1–5
{1:F01BANKBEBB...}
{2:I103BANKDEFF...}
{3:{121:3f2a91c7-5b4e-4d18-
9c6f-2ae70b8d1f43}}
{4: :20: :32A: :50K: :59: }
UETR lives in field 121
Structured XML, richer data
<FIToFICstmrCdtTrf>
<GrpHdr>...</GrpHdr>
<CdtTrfTxInf><PmtId>
<UETR>3f2a91c7-5b4e-4d18-
9c6f-2ae70b8d1f43</UETR>
</PmtId>...</CdtTrfTxInf>
</FIToFICstmrCdtTrf>
UETR is its own element
One 36-character reference connects both message formats.
Copy the UETR and confirm the local date on your message.
Add your email. Amount and currency come from the stored transaction.
See the latest recorded status and the events that led to it.
Use the confirmation link to activate alerts for new recorded events.
Use the form at the top of this page. A successful match opens a dedicated transaction page with the recorded amount, currency, banks and event timeline.
If the record is not found, check the reference and date. The transaction provider can confirm whether the transaction was successfully registered with UETR.io.
Public tracking excludes personal account details. To see the full record, sign in and verify an email that matches a sender or receiver email saved with the transaction.
Check your transaction →Original UETR
and message date in your timezone
3f2a91c7-5b4e-4d18-9c6f-2ae70b8d1f43
One reference
one transaction
Recorded timeline
and confirmed email alerts
Start with the reference and the original payment information. Keep the sender’s confirmation and ask your bank what has actually been reported.
Your timeline helps you review recorded transaction events. Your bank can investigate the movement of funds and explain any bank-reported delay, return or rejection.
Use the original UETR. Check the message date in your timezone and ask the operator about registration.
Ask which bank last reported the payment, what the status means, and what action is needed.
A reference-based view of registered transaction information and recorded events.
A request to the responsible bank to investigate payment routing, processing or a return.
The sending bank is your first point of contact. The receiver can also check with their bank.
| Reference | Identifies | Use it for |
|---|---|---|
| UETR | A transaction end to end | Identifying the payment when requesting updates |
| Account number / IBAN | A bank account | Identifying a sender or receiver account |
| SWIFT / BIC | A financial institution | Identifying a bank |
| Payment reference | An invoice or purpose | Reconciling a payment with an invoice |
An illustrative route. Actual routing depends on the banks involved.
Payment origin.
Sends the payment instruction.
Intermediary processing.
Connects the banks along the route.
Beneficiary account.
The destination bank for the payment.
A bank’s funds held at the correspondent.
“Our account, on their books.”The same account, from the correspondent’s view.
“Your account, on our books.”Checks may pause processing.
Each bank has its own processing windows.
Charges can affect the amount received.
A transfer may pass through an intermediary before reaching the receiving bank. Each bank has its own processing, currency and review requirements.
Use a reference to keep conversations about the same transaction. Ask for the latest bank-confirmed information when you need to know whether funds have moved.
Ask for the current status, the last reporting bank, any required action, and whether a trace or investigation is available.
A message is one part of the journey.
Different stages can be described as “sent”. A message may have been generated or submitted while further processing is still needed. Always ask which stage is actually confirmed.
Processing windows, intermediary routing, currency conversion, account details and review requirements can affect a payment. The responsible bank can explain what applies.
A completed system event describes the recorded processing outcome. It is not independent proof that funds have reached the beneficiary’s account.
Ask whether that means the message was created, accepted by the bank, or confirmed at a later stage.
Ask the sender to contact their bank with the UETR and request the latest bank-reported update.
Keep the reference and confirmations together. Ask who is handling the issue and what they need.
Anyone with the lookup details can see the public timeline. Access to the full transaction is limited to verified participants.
Share the bank-issued confirmation and UETR so your supplier can refer to the same payment. A generated document or public tracking page does not replace confirmation from your bank.
Keep sensitive account and contact information private. Full transaction details are only available to an eligible verified account.
Understand the transaction trail →Ask for the UETR and payment confirmation. Check your bank account directly and contact your bank if the expected payment is missing.
UETR.io can show registered transaction events, but receipt of money must be confirmed by your bank.
Look up the recorded status →Banks use payment tracking services to exchange information about a transfer’s progress. UETR.io is a separate transaction tracker; it does not currently query a live SWIFT gpi or bank network.
This site shows the events registered by the transaction system. For a bank-reported status, ask the bank handling your payment or use a tracking service that your bank provides.
A matched transaction record, recorded event timeline, confirmation-based email alerts and protected access to participant details.
Payment reports can describe acceptance, processing, credit or rejection. Their meaning depends on the reporting bank and the message context.
Do not treat a reference, generated message or an example diagram as evidence of settlement. Use bank-confirmed information to determine the financial outcome.
Always check who reported the event, when it was recorded and what it confirms. A system processing status is different from a bank settlement confirmation.
Banks report statuses against a UETR. This diagram illustrates the usual path.
Held for further checks
In transit between banks
A settlement leg completed
Posted to the account
A reason code usually says why (e.g. AC01).
A change will be made, such as the date.
These labels describe the events recorded for your transaction.
| Recorded status | How to read it |
|---|---|
| Generated | A transaction message was generated and registered. |
| Processing | System processing is underway according to the recorded event. |
| Review required | An operator recorded that a review is needed. |
| Completed | System processing was marked complete. This does not prove bank settlement. |
| Cancelled | The record was cancelled by an authorized operator. |
| Cancelled after fraud review | An authorized operator recorded cancellation after review. This is not an automatic bank fraud verdict. |
Use the timeframe your bank gave you. If that timeframe has passed, ask for a specific update.
Keep the original reference, date, amount and bank confirmation together.
Ask what has been confirmed, who is handling the payment and whether any action is required.
If the issue remains unresolved, ask about the bank’s trace, investigation or complaint process.
Follow the recorded transaction timeline while you ask those questions. Your bank remains the source for confirmation that funds were sent or received.
Check your transaction →A unique end-to-end transaction reference. The transaction system generates a UUID version 4 reference for each message.
Look on your transaction message or ask the person who generated it. You also need the message date in your timezone.
Transactions generated in the transaction system and successfully registered with UETR.io. An unknown reference will not create a transaction or a payment status.
Enter the UETR, message date in your timezone and your email in the form. A matching record opens the transaction timeline.
We send a confirmation link so you can activate alerts when a new transaction event is recorded.
No bank login is needed for a public lookup. Private details require an eligible, verified UETR.io account.
They come from the transaction registered by the transaction system using the original transaction details.
No. Message generation is a system event. Confirm bank submission, settlement and receipt with the responsible bank.
Check the UETR and local date. If both are correct, ask the transaction provider to confirm that registration succeeded.
System processing was marked complete in the transaction system. It does not independently confirm that funds were credited by a bank.
Use the full-details option on the result page, sign in and verify an email matching a participant email saved with that transaction.
Personal account details are excluded from the public timeline. Full details are restricted to authorized, verified participants.
After a matching lookup, use the confirmation link sent to your email and activate alerts for new recorded events.
Use the unsubscribe link in a tracking email and confirm your choice on the unsubscribe page.
No. The current integration reads transactions and events. Bank-confirmed data needs an authenticated bank integration.
No. A UETR identifies a transaction. A SWIFT/BIC code identifies a financial institution.
Use the original UETR attached to the transaction to identify the same record when asking for updates.
The site does not invent timed financial outcomes. Review and cancellation outcomes must be recorded by an authorized operator.
The current public lookup and confirmed status alerts are free. No paywall is enabled.
Contact the sending bank with your payment confirmation. For a missing transaction record, contact the transaction operator.
Read-only lookup · no login, no account details
We check transactions registered by the transaction system. This usually takes a few seconds.