Before 2017, cross-border SWIFT payments were essentially fire-and-forget. The sender bank pushed an MT103 to the first correspondent and prayed. GPI changed everything by adding a mandatory UETR and a real-time central tracker.
Classic SWIFT (pre-GPI) used MT103 messages with bank-local references only. There was no end-to-end identifier, no central status board, and no SLA on speed or fees. Tracing a payment meant chains of MT199 / MT195 messages between banks — slow and expensive.
GPI introduced four innovations: a mandatory UETR (field 121) on every payment, a central tracker hosted by SWIFT that every member bank reports to, transparency of fees deducted at each hop (field 71F), and SLA commitments on speed.
Today, "classic SWIFT" still exists technically — a bank can send an MT103 without joining GPI. But fewer than 5% of cross-border payments by value go this route. Most non-GPI traffic is on minor corridors or via small regional banks.
If your payment goes through a single non-GPI hop, end-to-end tracking breaks at that point. The UETR is still in the message, but the non-GPI bank does not publish status updates, so the tracker shows the last known GPI status before the gap.
Customer experience differs sharply. GPI customers can see "credited at HSBC London 14:32 GMT, charges 12.50 USD, FX 1.2845". Classic SWIFT customers see nothing until the beneficiary calls. For high-value commercial flows this difference is decisive — most corporates contractually require GPI.
Ohmyfin and other public trackers query the GPI network — non-GPI payments simply will not return data because there is no data to return.
Not formally, but in practice yes. ISO 20022 migration plus GPI adoption mean classic MT103-only flows are vanishing. SWIFT plans to retire MT category 1, 2 and 9 messages on November 22, 2025.
Yes — SWIFT publishes the GPI directory. Or simply check: if the wire confirmation shows a UETR and the GPI tracker returns data, your bank is GPI.
No additional retail charge in most banks. The bank absorbs the GPI membership fee because GPI reduces their support costs (fewer "where is my payment" calls).
Different layers. GPI is a service (UETR + tracker + SLA). pacs.008 is a message format (ISO 20022 XML successor to MT103). A payment can be GPI on either format.