Cross-border payment tracking with clearer reference visibility.
Search by UETR, TRN, sender reference, or internal tracking code. Review route checkpoints, status chronology, and transaction context from a single operator-managed interface.
Reference overview
Lookup paths
UETR, TRN, sender reference, or tracking code
Visibility
Route checkpoints, timestamps, counterparties, and notes
Operations
Manual transaction entry today, API-ready presentation layer next
Example reference
fa89d0f3-f4f0-4b29-a8ad-0123456789ab
Use the sample UETR above to preview the current transaction layout and route presentation.
Open example statusPayment tracking context
Understand the reference layer behind cross-border payment status checks.
What is UETR / GPI tracking?
UETR is the unique end-to-end transaction reference used to identify a payment across its lifecycle. GPI-style tracking focuses on reference continuity, intermediary visibility, and status clarity across the transfer path.
Why teams use it
Operations, treasury, and client-service teams use transaction references to answer where a payment is, which bank last touched it, and whether a transfer is still moving, pending review, or complete.
How it works
A simple reference-first workflow for route visibility and status review.
Start with a reference
Use a UETR, TRN, sender reference, or internal tracking code to open the transaction record.
Review the route
Follow the route path, counterparties, timestamps, and latest status to understand where attention is needed.
Act with context
Use the status chronology and operational notes to coordinate with the relevant bank, team, or counterparty.
Common status codes
Read transaction states with more confidence.
Created
Record has been created and is ready for route and status updates.
Sent to Correspondent
The transfer has been forwarded to the next institution in the route.
ACSP Processing
The transaction is being processed and remains in the settlement path.
Pending Compliance Review
Additional review or supporting information may still be required.
Rejected RJCT
The transfer was rejected and needs investigation before resubmission.
Completed
The record is marked as completed in the current tracking history.
Why payments get delayed
Delays often come from review, routing, or corridor-specific controls.
Even when a transaction reference is available, the next meaningful update can depend on cut-off times, intermediary handling, documentation checks, or operational dependencies between institutions.
Intermediary bank cut-off times and local business hours
Compliance, sanctions, or documentation review
Beneficiary detail mismatches or clarification requests
Currency conversion, corridor controls, or funding checks
Weekends, public holidays, or internal routing dependencies
Operations access
Need to search a record or review a transaction reference?
Start from the public lookup flow to review the current route, status, and payment reference details. Restricted operator access remains available only through the direct internal admin address.