SWIFT gpi Explained: Tracking, UETR, and ISO 20022

SWIFT gpi, explained simply, is the Global Payments Innovation standard that governs how cross-border wire transfers move through the banking network. Member banks commit to crediting funds the same business day, disclosing every fee and exchange rate deducted along the way, tracking each payment in real time using a unique reference, and confirming to the sender when the money has been credited to the beneficiary. Before gpi, an international wire passed through a chain of correspondent banks with no shared rules on any of that, and the sender was largely in the dark.

How Fast a gpi Payment Moves

Participating banks agree to credit funds the same business day a payment arrives, as long as it reaches the beneficiary’s bank before that bank’s local cut-off. Anything landing after cut-off must be credited the next business day. These timing rules come from the SWIFT gpi Rulebook, which every member institution signs up to when it joins.¹

In practice, gpi transfers move much faster than the old multi-day norm. SWIFT has reported that roughly half of gpi payments reach the beneficiary within 30 minutes, and nearly all arrive within 24 hours.² Banks that consistently miss the timing commitments face consequences within the network, including restricted access to certain features or a declined renewal of their gpi validation.³

One caveat: the speed and tracking commitments hold only when every bank in the chain is on the gpi network. If a transfer routes through a local payment system or a non-participating bank, the gpi Tracker flags the handoff, and from that point the payment is processed as a standard transaction. The sender loses real-time visibility, and the same-day credit rule no longer applies.⁴ Worth knowing if you regularly send money to countries where smaller banks may not yet participate.

Fee and Exchange Rate Transparency

A common complaint about traditional wires was that the recipient got less than expected with no clear accounting of the difference. Under gpi, every bank that touches a payment must disclose the fees it deducted and the exchange rate it applied. That information travels with the payment through standardized messaging, so the sender can see the cost breakdown from origination to delivery.¹

Intermediary banks, which sit between the sender’s bank and the recipient’s bank, historically deducted processing charges without documentation. The gpi rules end that practice by requiring each intermediary to record its charges in the payment message. The recipient’s arrival amount should therefore match the amount projected after all disclosed costs. The same transparency also makes it easier to spot a bank that is overcharging relative to what was agreed.

The UETR and Real-Time Tracking

Every gpi payment is stamped at creation with a Unique End-to-End Transaction Reference, or UETR. It’s a 36-character alphanumeric string generated using the UUID specification under RFC 4122 (version 4), which makes it globally unique with no risk of collision.⁵ The UETR stays attached to the payment from origination through every intermediary until final delivery. Think of it as a tracking number for a parcel, except it works across the global banking system.

Banks feed UETR data into the SWIFT gpi Tracker, a cloud-hosted database that shows real-time status. At each stage, the handling bank updates the Tracker when it receives and forwards the funds. The Tracker reports three core statuses: settlement in progress, settlement completed, or rejected. If a payment is held by compliance screening or a sanctions check, the Tracker reflects that hold in near real-time, so no one is left guessing.¹

Sometimes a payment stalls because of missing or malformed information, such as a wrong account number format or an incomplete address. SWIFT’s gCase service lets banks resolve those issues in-flight, using the Tracker to identify where the hold-up is and exchanging the needed information directly with that institution rather than returning and restarting the payment.⁶

Confirmation That Funds Were Credited

Since the end of 2020, every customer payment sent over SWIFT requires a confirmation that funds have been credited to the beneficiary’s account.³ The beneficiary’s bank sends this to the gpi Tracker using an MT 199 message, an ISO 20022 XML message, or an API confirmation.⁷

If the payment cannot be completed because of incorrect account details, a regulatory block, or any other reason, the bank must send a rejection notice instead. That creates a closed loop that was entirely absent before gpi, when senders often had no way to know their money had arrived until the recipient manually confirmed it. Now the network itself provides definitive proof of delivery or a clear reason for failure. Banks that fail to meet confirmation requirements risk having their gpi validation declined or not renewed.³

Stopping or Recalling a Payment

Sending money to the wrong account, or discovering fraud after the wire has gone, is the nightmare scenario. The Stop and Recall service (gSRP) gives banks a structured way to try to recover the funds. The originating bank sends a cancellation request tied to the same UETR as the original payment. If the funds haven’t yet reached the beneficiary bank, the service can stop the payment in transit.⁸

Once funds have landed at the beneficiary bank, things change. A cancellation request does not force the beneficiary bank to return the money. It provides information the bank can use to make a risk-based decision about whether to freeze the funds pending investigation.⁹ The beneficiary bank responds with one of several standardized status codes:

Cancelled as requested (CNCL), meaning the funds are being returned.
Pending (PDCR), meaning the bank is still reviewing the request.
Rejected (RJCR), meaning the bank has declined the cancellation, with a reason code.

Rejection reasons range from regulatory restrictions preventing return, to the account holder refusing to release the funds, to the original transaction never having been received. In some cases the beneficiary bank will require a formal indemnity agreement from the originating bank before proceeding.⁹ Speed matters enormously. Once funds are credited and the beneficiary withdraws them, recovery becomes a legal matter rather than a network-level fix.

Catching Errors Before You Send

A growing complement to gpi is SWIFT’s Payment Pre-validation service, which checks whether a payment will succeed before it’s sent. Through APIs, the service verifies beneficiary account details and confirms that the payment information meets the destination country’s requirements. If the beneficiary’s bank subscribes to the service, it checks the account information directly; if not, SWIFT validates what it can using centralized reference data and local payment rules.¹⁰

Incorrect beneficiary details are one of the most common reasons cross-border payments get delayed or rejected. Catching an error before the payment enters the banking chain avoids the fees, delays, and frustration of a failed transfer and a later recall attempt. The service works with both legacy MT message formats and ISO 20022.

What gpi Looks Like for Corporate Treasuries

Businesses that keep accounts at several banks across different countries face a fragmentation problem: five banks, five portals, inconsistent data, different status language. SWIFT’s gpi for Corporates (g4C) standardizes gpi data flows between banks and corporate systems, so a single treasury or ERP platform can show a unified view of every payment’s status, fees, and delivery confirmation.¹¹

There are two useful visibility features. For outgoing payments, “pay and trace” lets the corporate generate its own UETR at initiation and then receive in-flight notifications. For incoming payments, inbound tracking provides advance notice of funds arriving, with data on the sender, remittance details, and near real-time status. That inbound view is particularly valuable for cash forecasting, since treasury teams no longer have to wait for end-of-day bank statements to know what has landed.¹² Banks that offer g4C must also provide dashboards so business users can analyze payment performance by currency, country corridor, and bank.¹¹

The Shift to ISO 20022

The messaging backbone underneath gpi is changing. SWIFT’s legacy MT message formats, including the MT 103 for customer transfers and the MT 199 for tracker confirmations, are being replaced by ISO 20022, a richer XML-based standard that carries far more structured data. The coexistence period, during which banks could send either format, ended in November 2025. As of January 2026, any institution still sending legacy MT messages faces additional charges from SWIFT.¹³

For gpi tracking specifically, SWIFT still supports MT 199 messages sent to and from the gpi Tracker, with no end date announced. However, the MT 199 format is officially deprecated, and all new tracking features will only be built for ISO 20022 and API formats. SWIFT recommends that banks not start new implementations using MT 199 and that existing users migrate.¹³

For senders and recipients, the impact is mostly behind the scenes. ISO 20022’s richer fields let payment instructions carry more detailed remittance information, more complete beneficiary addresses, and more structured purpose codes. Over time, that means fewer payments rejected for missing or ambiguous data, and better straight-through processing across the network.

1
Swift. Swift GPI
2
Swift. Swift GPI Reduces Cross-Border Payment Times to Minutes, Even Seconds
3
Swift. Swift gpi for Financial Institutions – Label Criteria 2024
4
SWIFT. SWIFT gpi – How Payment Market Infrastructures Can Support gpi Payments
5
SWIFT. SWIFT gpi for Financial Institutions – Label Criteria 2023
6
Swift. Swift Launches New Frictionless Case Resolution Service to Speed Up Cross-Border Payments
7
Swift. Universal Confirmations – Answers to Your Key Questions
8
Deutsche Bank. SWIFT gpi – Time for Action
9
SWIFT. Market Practice Guidelines for the Cancellation of Suspected Fraudulent Transactions
10
Swift. Payment Pre-validation
11
Swift. Swift Compatible Application – Swift GPI for Corporates – Label Criteria 2024
12
Swift. Bringing the Swift GPI Experience Directly to Your Customers
13
Swift. ISO 20022 – Implementation