Enterprise payment tracking for modern cross-border operations.
Globalinvests Tracker gives operations, treasury, and client-service teams a branded visibility layer for UETR, TRN, sender references, route milestones, and onboarding-led API expansion.
Reference overview
Coverage
UETR, TRN, sender reference, and internal tracking code lookup
Visibility
Route milestones, counterparties, timestamps, fees, and status chronology
Rollout
Operator-managed tracking today with API onboarding and connectivity rollout pathways
Reference code
c1f7ab21-6f62-4bd5-9bd3-0abf298fd501
Use this reference to review the current Globalinvests Tracker layout, route presentation, and transaction detail structure.
Open reference viewPlatform overview
Built for teams that need structured visibility across cross-border payment activity.
What the platform delivers
tracker.globalinvests.uk centralizes transaction references, routing visibility, and payment status context so operations teams can manage payment investigations and client follow-up from one workspace.
API & connectivity rollout
Enterprise onboarding can extend the platform with API access, workflow connectivity, and institution-specific rollout paths aligned to operational, treasury, and corridor requirements.
How it works
A simple reference-first workflow for route visibility and status review.
Search a reference
Use a UETR, TRN, sender reference, or internal code to open the latest transaction view.
Review route intelligence
Follow route milestones, counterparties, timestamps, and the current status to understand where action is needed.
Extend through onboarding
Use the platform as the operational visibility layer today, then expand through API onboarding and workflow integrations as rollout progresses.
Common status codes
Read transaction states with more confidence.
Created
The 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 actively progressing within the current processing path.
Pending Compliance Review
Additional documentation, validation, or review may still be required.
Rejected RJCT
The transfer was rejected and requires operational investigation before resubmission.
Completed
The record is marked as completed in the current transaction chronology.
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 corridor-specific business hours
Compliance, documentation, or sanctions review requirements
Beneficiary detail mismatches or follow-up clarification requests
Funding checks, currency conversion, or settlement dependencies
Weekends, public holidays, or internal routing dependencies between institutions
Enterprise access
Ready to review a transaction reference or present a route update?
Start from the public lookup flow to review route milestones, status chronology, and transaction details. Operator access remains available through the direct internal admin address.