Last reviewed: · Curated by Ohmyfin Organisation editorial.
SWIFT GPI brings end-to-end UETR tracking, same-day SLAs, and fee transparency to cross-border SWIFT payments. Classic SWIFT had none of that. Track any GPI payment free by UETR on Ohmyfin →
Before SWIFT GPI, international bank wires were genuinely opaque. A sender initiating an MT103 had no way of knowing where their money was after it left their bank. Banks had to conduct inter-bank investigations via MT192 (request for cancellation) or MT199 (free-format queries), a process that could take days. Beneficiaries would complain to the sender, who had to go back to their bank, who would then call the correspondent, who called the next bank — a chain of phone calls and SWIFT messages that often took 3–5 business days to resolve a simple "where is my payment?" question.
SWIFT GPI (Global Payments Innovation) solved this with three key additions: (1) a UETR (Unique End-to-end Transaction Reference) — a 36-character UUID assigned at origination and carried by every bank in the chain; (2) the SWIFT Tracker — a real-time database updated by every GPI bank as it processes the payment; and (3) four service-level rules that every GPI bank must agree to: same-day processing, fee transparency (each bank must declare its charges), unaltered remittance data (no truncation of field 70 information), and confirmed final credit with time-stamped confirmation. The UETR is the public-facing key that links a sender to the SWIFT Tracker.
SWIFT GPI status codes: the core status codes used in the GPI tracker are ACSP (AcceptedSettlementInProcess — payment is progressing through the chain), ACCC (AcceptedCreditSettlementCompleted — payment has been credited to the beneficiary's account, final), RJCT (Rejected — payment was rejected by a bank in the chain, with a reason code), and the legacy-compatible ACSP with sub-status for various in-chain states. Ohmyfin surfaces these statuses in plain English so you know immediately whether your payment is in progress, complete, or rejected — and if rejected, which bank rejected it and why.
Classic SWIFT traffic: as of 2025, an estimated 5% or less of cross-border SWIFT volume still runs on classic (pre-GPI) SWIFT. This is mostly legacy low-volume corridors, payments processed by banks that have not yet joined GPI, or some specialised financial institution traffic. Classic SWIFT payments do not have a UETR in field 121 — the field is either absent or zero. They cannot be tracked by Ohmyfin or any GPI-based tracker. If you send to or from a bank in a developing-country corridor that is not yet GPI-enabled, your payment may still be classic SWIFT.
GPI Stop-and-Recall (gSRP): one of the most powerful features of GPI is the ability to stop and recall a payment in transit. With classic SWIFT, cancelling a payment once sent required manual bank-to-bank communication and could take days or weeks. With GPI's Stop-and-Recall Protocol (gSRP), the originating bank can send a stop instruction that propagates to every bank in the chain within minutes. Each GPI bank must acknowledge and act on the stop request within their SLA. This dramatically reduces fraud losses and accidental wire misdirection. The UETR is the key that makes gSRP possible — without it, there is no way to identify the payment across banks.
SWIFT GPI and Ohmyfin: Ohmyfin is an independent service that uses direct banking relationships and the SWIFT GPI infrastructure to look up payment status by UETR in real time. You do not need to be a bank customer of any specific institution — simply paste your UETR into Ohmyfin and the service returns the latest known GPI status, including which bank is currently holding the payment, the timestamps of each hop, and whether the payment has been finally credited. This replaces the old process of calling your bank, waiting on hold, and hoping they escalate to the right correspondent.
| SWIFT GPI | Classic SWIFT | |
|---|---|---|
| Launched | 2017 | Pre-2017 |
| UETR / tracking | Yes — live status | No tracking |
| Speed commitment | Same-day for most G20 | Best-effort |
| Fee transparency | Per-hop fees disclosed | Opaque |
| Remittance data | Unaltered end-to-end | May be truncated |
| Share of 2025 volume | ~95% | ~5% (legacy corridors) |
Almost every G20 major bank is. If your MT103 has a UETR (field 121) — a 36-character hyphenated code — the payment is GPI-eligible. Over 4,500 financial institutions across 170 countries are active GPI members. If your bank operates in the US, UK, EU, Canada, Australia, Japan, China, Singapore, Hong Kong or most other developed markets, it is almost certainly on GPI.
Look for the UETR in your payment confirmation. On an MT103, the UETR is in block 3 field 121 — it looks like xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx (36 characters with hyphens). If field 121 is present, your payment is GPI. If it is absent or zero, it may be classic SWIFT (or a domestic payment that does not use SWIFT at all).
ACSP stands for AcceptedSettlementInProcess — the payment has been accepted and is being processed. It is currently in transit somewhere in the chain. The specific bank holding it is shown in the Ohmyfin status details. ACSP is normal for a payment that is still moving between correspondents; it typically resolves to ACCC (final credit) within the same business day on major GPI corridors.
ACCC (AcceptedCreditSettlementCompleted) means the payment has been finally credited to the beneficiary's account. This is the terminal success state — the payment is complete. If Ohmyfin shows ACCC but the beneficiary says they have not received the funds, contact the beneficiary's bank — the credit was confirmed to SWIFT but may be pending internal posting at their bank.
If the payment is still in transit (ACSP, not yet ACCC), the GPI Stop-and-Recall Protocol (gSRP) allows the originating bank to send a stop instruction that every GPI bank in the chain must honour within their SLA. Contact your bank immediately if you suspect fraud — they need to act within hours. Once the payment shows ACCC (final credit to beneficiary), recovery requires the beneficiary's cooperation and legal action.
Ohmyfin uses direct banking relationships and the SWIFT GPI infrastructure to query live payment status by UETR. The service returns the latest known SWIFT GPI status at each bank in the chain — the same data that GPI banks see in the SWIFT Tracker — without requiring you to have a relationship with any specific bank.
No card needed. Free for ordinary users — completely free for individuals — no daily limit, no card required. Track any international wire across 11,000+ banks.
Track a payment now — completely free Or try the tracker now →