1. Bring the original details
You need the complete 36-character UETR, the message date in your timezone and an email address. Use the date associated with the original message, rather than today’s date or a hoped-for arrival date.
You do not enter the amount or currency. Those values come from the registered transaction. A format check can catch some copying mistakes before you search.
2. Match a registered transaction
The lookup searches this service’s records for the reference and message date. A match opens a signed transaction link displaying the recorded amount, bank names and timeline. Events appear with the latest first; time displays use your browser’s timezone.
Keep a signed link private. It is an access link, not an ordinary public article URL. A missing match means the service found no corresponding record—not that the payment failed.
3. Confirm email updates
After a successful lookup, a new alert request receives a confirmation email. Follow the link and confirm on the page to activate updates. An unconfirmed address does not receive ongoing event alerts.
Updates are sent when further events are recorded. They are not scheduled predictions of what a bank will do next. Use the unsubscribe link in an update to stop that subscription.
4. Sign in only when private details are needed
Public lookup does not require an account. Full transaction details require a signed-in account with a verified email matching a sender or receiver email recorded for that transaction. Creating an account alone does not grant access to someone else’s details.
If a participant email is missing or incorrect, ask the transaction provider to review the original record. See Security & Data Access for the access boundary.
Keep the bank question separate
A recorded event is information about the service’s record. Ask your bank to confirm submission, settlement, any return and the actual account entry. For a search that produces nothing, follow the no-result checklist.