SWIFT / Learning brief
SWIFT gpi and payment tracking
Your notes
In simple terms / 01
What this means in plain language
SWIFT gpi (global payments innovation) is a set of standards that made cross-border correspondent payments faster and more transparent, adding fee visibility and end-to-end tracking through a unique reference and a central Tracker.
SWIFT gpi (global payments innovation) is a service, launched in 2017, that set out to fix long-standing complaints about cross-border payments: they were slow, their fees were hard to see, and no one could say where a payment had reached. gpi is a set of business rules that member banks agree to follow, and it improves three things. Speed: participating banks commit to processing a payment quickly and making funds available the same day within the correspondent chain. Transparency: the fees deducted and any currency conversion are recorded and shared, so the sender can see what was taken. Tracking: every payment is given a UETR (unique end-to-end transaction reference), a 36-character code that stays with it from start to finish. Banks report each step against that reference to a central system called the Tracker, so a payment can be followed like a parcel. gpi also supports stop-and-recall, a way to request that a payment be halted or returned.
Complete lesson / 02
Understand the full idea, step by step
When you post a parcel today, you get a tracking number and a page that says where it is — collected, in transit, out for delivery. For a long time, a cross-border bank payment had no such page. You sent it, and then you waited. SWIFT gpi is, more than anything, the story of how cross-border payments got their tracking page.
The payment at a glance
- Payer
- Asha Traders — account at Bank Alfa
- Beneficiary bank
- Nordbank (abroad)
- Correspondent
- Meridian Bank
- Amount sent
- EUR 48,250.00
- Tracking reference
- UETR eb6305c9-1f7f-49de-aed0-16487c27b42d
A service layer, not a new message
It is tempting to imagine gpi as a new kind of payment message. It is not. A gpi payment travels in the same message types banks already used — the money still moves through the same correspondent chain, each bank still debiting and crediting its own books. What gpi adds sits *around* those messages: a set of rules the member banks promise to follow, and a shared place to record what happened. gpi does not replace correspondent banking; it disciplines it. Because the improvement is agreed behaviour rather than a new network, it spread across the existing system without every bank rebuilding.
SWIFT gpi — global payments innovation
A service layer over the correspondent-banking network in which member banks commit to service levels: process a cross-border payment the same business day where the receiving side allows, be transparent about the fees and any currency conversion they apply, and confirm to a shared record once the beneficiary has been credited. It is a rulebook plus a tracking backbone — not a message format and not a settlement system.
You may be wondering: if it is not a new message, what actually makes tracking possible?
One reference that never changes. When the first bank creates the payment, it stamps on a UETR — a single identifier that every bank in the chain then quotes without altering. Because all the separate messages carry the same reference, a central record can stitch them into one timeline. The parcel-tracking page works the same way: it is not the box that reports its position, it is the barcode every depot scans.
UETR — Unique End-to-End Transaction Reference
A 36-character identifier, generated to be globally unique, assigned to a payment at its start. In a legacy MT (Message Type) message it rides in a dedicated field of the user header; in an ISO 20022 (International Organization for Standardization standard 20022) message it has its own element. Its one job is identity: the same UETR appears on the customer instruction and on every related bank-to-bank message, so the payment keeps a single name from first instruction to final credit.
Read the steps as text
- 01MessageThe customer orders a USD transfer abroadOrdering customer → Bank Alfa (ordering bank)
The ordering customer instructs Bank Alfa to pay a supplier banked at Cassia Bank in another country. Bank Alfa has no direct account relationship with Cassia — that is why correspondents exist.
- 02ProcessingBank Alfa validates and screensBank Alfa (ordering bank)
Format and balance checks plus sanctions screening. Cross-border payments face stricter screening because more jurisdictions are involved.
Screening checkpoint: Outbound cross-border screening — Ordering and beneficiary parties, banks, and remittance text are screened before the payment leaves.
- 03PostingThe customer's account is debitedBank Alfa (ordering bank)
Bank Alfa books the debit and, per the charge option, any fees.
- DR Ordering customer's account at Bank Alfa — USD 250,000.00
- 04MessageThe MT103 goes to Bank Alfa's USD correspondentBank Alfa (ordering bank) → Meridian Bank (correspondent) · MT103
In the serial method the payment instruction itself travels through the account chain. Meridian holds Bank Alfa's USD account (Bank Alfa's nostro), so Meridian can debit it.
- 05ProcessingMeridian validates and screens in the middleMeridian Bank (correspondent)
Every bank in the chain screens independently. Meridian also checks that Bank Alfa's account has cover for the debit.
- 06SettlementMoney moves across the books of MeridianMeridian Bank (correspondent)
Both Bank Alfa and Cassia hold USD accounts at Meridian. Settlement here is a book transfer in commercial bank money: Meridian debits one account it holds and credits the other.
No clearing house is involved — the correspondent's ledger is the settlement venue. This is settlement in commercial bank money, not central bank money.
- DR Bank Alfa's USD account at Meridian (vostro) — USD 250,000.00
- CR Cassia's USD account at Meridian (vostro) — USD 250,000.00
- 07MessageCassia is advised its nostro was creditedMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT910
The MT910 credit confirmation lets Cassia's reconciliation match expected funds against its nostro account movement.
- 08MessageThe MT103 continues serially to CassiaMeridian Bank (correspondent) → Cassia Bank (beneficiary bank) · MT103
Meridian forwards the payment instruction to the beneficiary bank with the full ordering and beneficiary details intact.
- 09ProcessingCassia validates the incoming paymentCassia Bank (beneficiary bank)
Account checks and inbound screening. Only when funds are confirmed on the nostro and checks pass is the beneficiary credited.
- 10PostingThe beneficiary is creditedCassia Bank (beneficiary bank)
Cassia credits its customer, net of any beneficiary-side charges the charge option allows.
- CR Beneficiary's account at Cassia — USD 250,000.00
How Maya finds the answer
- INSTRUCTION
Bank Alfa assigned the payment its UETR at the outset. Maya starts from that single reference — she does not need to know the route in advance.
- MESSAGE
As the payment passed each bank, that bank reported a status against the UETR: received, fees charged, forwarded. The Tracker — a central record SWIFT operates — collects these like a parcel's scan history.
- VALIDATION
Maya opens the Tracker on the UETR. She can see the payment reached Meridian Bank, which applied a fee and forwarded it, and is now sitting at Nordbank pending credit — not lost, just not yet posted.
- NOTIFICATION
Under the network-wide confirmation rule, Nordbank will report the final outcome — credited — back to the Tracker. Maya tells Asha Traders exactly where the payment is and what was deducted, without sending a single enquiry message.
COMMON CONFUSION
“The Tracker holds the money while the payment is in flight, like an escrow account.”
The Tracker holds only status information against the UETR — where the payment is and what each bank did. The money itself always sits in a bank's books along the correspondent chain, moving by debit and credit as before. Tracking reports on value; it never holds it.
Why transparency of cost falls out for free
Because each bank records the fee it took and any exchange rate it applied against the same UETR, the Tracker can show how the amount sent became the amount received. When Asha Traders' supplier receives less than EUR 48,250.00, Maya can now say which bank deducted what, rather than guessing. The deduction is visible and attributed. This is the same design paying off twice: one shared reference makes both the location and the cost of a payment answerable.
STRICTLY SPEAKING
Strictly speaking, gpi also lets a bank ask to halt or recover a payment using its UETR — but a recall is a request, not a command. The bank currently holding the funds must check whether they are still available and whether the beneficiary agrees to release them, then report the outcome. It is the orderly, traceable way the system tries to undo a payment, not a guarantee that money can be pulled back once credited.
FOR NOW, REMEMBER
- gpi is a service layer over correspondent banking — agreed service levels plus a shared tracking record — not a new message type or a settlement system.
- The UETR is one unchanging 36-character reference every bank quotes, giving the payment a single identity end to end.
- The Tracker collects each bank's status against the UETR, so anyone in the chain can see where a payment is and what fees were taken.
- Tracking reports on value; the money still moves by debit and credit along the correspondent chain.
TRY IT YOURSELF
Maya opens the Tracker and sees Meridian Bank forwarded the payment with a fee deducted, and Nordbank has reported it as pending credit. What is the most accurate thing to tell Asha Traders?
You have followed one gpi payment and its single reference. But a cross-border payment is really several messages doing different jobs — and gpi has a named variant for each. That is the next lesson.
KEEP GOINGKey takeaways / 03
Three things to remember
- 01
SWIFT gpi (global payments innovation) improves cross-border payments on three fronts: speed, fee and currency transparency, and end-to-end tracking.
- 02
A UETR (unique end-to-end transaction reference) stays with a payment through every bank, giving it one identity that can be tracked.
- 03
Banks report each step to a central Tracker, and a stop-and-recall request can halt or return a payment already sent.
Practical use cases / 04
Where you would use this
A customer service team quotes a payment's UETR to tell a corporate client which bank in the chain is currently holding a transfer.
A treasury operation checks the Tracker to confirm funds were credited and to see the fees deducted along the route.
An operations desk sends a stop-and-recall request when a payment was sent in error or is suspected to be fraudulent.
Worked example / 05
Put the idea into a real situation
Illustrative example: a fictional bank, Meridian Trust, sends a cross-border payment of USD 48,000.00 for a customer to a beneficiary at a fictional bank, Kestrel Union Bank, through one intermediary. At initiation Meridian Trust assigns the payment a 36-character UETR (unique end-to-end transaction reference), such as 97ed4827-7b6f-4491-a06f-b548d5a7512d, and records it in the message. Each bank updates the Tracker as it processes the payment, so when the customer calls after 25 minutes, Meridian Trust can see the funds were credited to the beneficiary 12 minutes earlier, with total fees of USD 30.00 deducted along the way. The next day the customer reports the payment was a mistake, so Meridian Trust sends a stop-and-recall request quoting the same UETR, and Kestrel Union Bank confirms the USD 48,000.00 is still available and returns it within 2 business days.
Operational sequence / 06
Follow the message and decision path
This compact sequence is a learning model. Exact routing and rulebook behavior can vary by scheme, participant, and implementation.
Read the steps as text
- 01MessageBank Alfa sends the MT103 carrying a UETRBank Alfa (originator bank) → Meridian Bank (correspondent) · MT103
Asha Traders, a customer of Bank Alfa, is paying a supplier banked at Nordbank. Bank Alfa generates a UETR — a 36-character unique end-to-end transaction reference — embeds it in the MT103, and sends the instruction to its USD correspondent, Meridian Bank, which holds Bank Alfa's nostro account.
- 02MessageBank Alfa opens the trail on the gpi TrackerBank Alfa (originator bank) → gpi Tracker (Swift)
Keyed to that UETR, Bank Alfa writes the first status to the cloud-based gpi Tracker. From this moment the payment can be followed end to end, unlike an opaque legacy correspondent chain where the originator saw nothing after sending.
- 03SettlementCover moves across the nostro relationshipBank Alfa (originator bank) → Meridian Bank (correspondent)
gpi adds tracking on top of correspondent banking; it does not change how money moves. Meridian debits the USD nostro account Bank Alfa holds with it, providing cover for the onward payment in commercial bank money.
No clearing house is involved — the correspondent's ledger is the settlement venue, in commercial bank money rather than central bank money.
- DR Bank Alfa's USD nostro account at Meridian — USD 40,000.00
- 04MessageMeridian forwards the MT103 to NordbankMeridian Bank (correspondent) → Nordbank (beneficiary bank) · MT103
Meridian passes the payment instruction on to the beneficiary bank, Nordbank, with the ordering and beneficiary details intact and the same UETR carried through — the tracking key stays constant along the whole chain.
- 05MessageMeridian updates the gpi TrackerMeridian Bank (correspondent) → gpi Tracker (Swift)
As it processes the payment, Meridian posts its own status against the UETR to the Tracker, adding to a continuous status trail that Bank Alfa can see in near real time.
- 06SettlementMoney moves from Meridian to NordbankMeridian Bank (correspondent) → Nordbank (beneficiary bank)
Meridian settles with Nordbank across the accounts they hold between them, so the value is with the beneficiary bank before it credits its customer. This is the same correspondent settlement gpi leaves untouched.
- CR Nordbank's USD account at Meridian (vostro) — USD 40,000.00
- 07PostingNordbank credits the supplierNordbank (beneficiary bank)
With funds confirmed and checks passed, Nordbank books the credit to the supplier's account — the point at which the beneficiary actually has the money.
- CR Supplier's account at Nordbank — USD 40,000.00
- 08MessageNordbank confirms the credit on the TrackerNordbank (beneficiary bank) → gpi Tracker (Swift) · MT103
Nordbank sends a gpi confirmation of credit against the UETR to the Tracker, closing the trail. Bank Alfa and Asha Traders can now see end-to-end status and proof that the supplier was paid — the transparency gpi is built to deliver.
Evidence & review / 07
Evidence & review
SWIFT gpi over the correspondent-banking network; cross-border payments in FIN MT and ISO 20022.
What this brief simplifies: Correspondent chain shortened to one intermediary; the UETR shown is synthetic; exact service-level timings and stop-and-recall behaviour depend on the current gpi rules and participants.
Sources for this brief3
- Scheme-specific rule
Swift gpi (global payments innovation) ↗ — Swift · gpi service levels; UETR; Tracker; stop-and-recall
Only public summaries are used here; the full service definition and rulebook sit behind a swift.com account.
- Market practice
ISO 20022 Standards (Swift ISO 20022 adoption programme) ↗ — Swift · UETR carriage in MT and ISO 20022 messages
Programme milestones change over time; the coexistence period for in-scope cross-border payment instructions ended in November 2025. Check swift.com for the current timeline.
- Simplified educational illustration
Payments Signal editorial teaching models — Payments Signal
Used wherever diagrams, scenarios, figures, or example values are didactic constructions rather than sourced facts; every such use carries a simplifications disclosure. All people, companies, banks, and list entries in examples are fictional.