What Is Swift GPI? UETR, Tracking and What It Means for Indian Exporters

Swift GPI stands for Global Payments Innovation, and it has been live since 2017. It is a set of rules plus a central tracking service sitting on top of the existing Swift network.

The practical effect is that a cross-border payment can be followed from the sending bank to the beneficiary's account.

Every payment under it carries a UETR, a single reference that stays attached to the money for the whole journey, much like a courier tracking number. Your bank can look that reference up and tell you where the payment is right now.

Swift GPI in five lines:

• Full form - Global Payments Innovation, live since 2017
• What it is - a rules and tracking layer on the existing Swift network, not a new network
• UETR - a 36-character reference that stays with the payment end to end
• Speed - per Swift's published data, nearly 60% of payments are credited within 30 minutes and almost all within 24 hours
• Fee transparency - deductions and the FX applied are disclosed at each stage

Waiting on a payment right now? Skip to what to ask your bank for the four things to request, in order.

GPI made the payment visible while leaving the underlying plumbing alone.

Before 2017, an international wire went dark the moment it left your bank. Nobody could say where it was, what had been deducted, or when it would land.

Swift's own Swift gpi product page frames the fix the same way. Two things it is, and two it is not:

• It is - a rulebook that member banks sign up to, plus a central database called the Tracker that every bank in the chain writes status updates into
• It is not - a new payment network, or faster rails. The money still hops through the same correspondent and intermediary banks

There is no such thing as a "GPI code" you enter somewhere.

That confusion comes from the SWIFT code, which is your bank's BIC and a separate thing. GPI is a service standard, not an identifier.

Four commitments sit in the gpi Rulebook, and every feature people list traces back to one:

• End-to-end tracking - every payment carries a UETR and its status is visible at each hop
• Speed - same-day use of funds, within the time zone of the receiving member's local business day
• Fee transparency - deducted fees and the FX applied must be disclosed at each stage, not silently removed
• Unaltered remittance information - the invoice reference and payment details reach the beneficiary as sent, rather than being truncated in transit

Credit confirmation follows from the first of those. Because every hop is written to the Tracker, the final credit is written back too.

Under the old model, a sender learned a payment had arrived when the beneficiary emailed to say so.

Three supporting pieces sit around the rulebook, all of them bank-facing:

• The gpi Directory - tells a member bank which institutions are reachable and how
• Observer - how Swift measures whether members are meeting the rulebook
• Case Resolution - the formal route for querying a stuck payment, and the thing to ask your bank for when one stops moving

Older service labels also circulate (gCCT, gCOV, gpi Instant and others). These are historic 2017-era branding. Swift has since folded gpi into a baseline standard, so treat any of them you meet as legacy naming rather than a current product.

The mechanism is a push model: each bank reports its own leg, and Swift holds one live record.

1. The sending bank assigns a UETR to the payment and transmits it over Swift.
2. Each bank in the correspondent chain writes a status update, tagged to that UETR, to Swift's central Tracker as it processes the payment.
3. The Tracker holds one continuously updated record for that UETR, visible to every member bank in the chain.
4. The beneficiary's bank writes the final credit confirmation back, and it becomes visible up the chain to the originating bank.

That gap is why third-party "free UETR tracker" sites exist. None of them is Swift's own service, and where their status data comes from is not documented.

You get the UETR, give it to your bank, and your bank reads the Tracker for you.

What a UETR Looks Like, in a Code Block

Recognising the format on sight saves an email. An illustrative example, not a real transaction:

UETR (Unique End-to-End Transaction Reference)
└── 97ed4827-7b6f-4491-a06f-b548d5a7512d
    ├── 97ed4827  ── 8 hex digits
    ├── 7b6f      ── 4
    ├── 4491      ── 4
    ├── a06f      ── 4
    └── b548d5a7512d ── 12
    = 32 hexadecimal digits + 4 hyphens = 36 characters
    Carried in Field 121 of the payment message

The pattern is 8-4-4-4-12 and the total length is 36 characters. In the legacy MT103 message it travels in Field 121. In ISO 20022 it is the PmtId/UETR element, which the CBPR+ market-practice guidelines make mandatory on the main value messages.

Some published guides say a UETR is 32 characters, counting only the hexadecimal digits and leaving out the four hyphens. Both describe the same reference. If you are checking yours against a field-length limit, use 36.

Where to Get Your UETR

There are two places to get it:

• Your client's payment confirmation - the advice their bank issued usually carries the UETR alongside the value date and amount. This is normally the quicker route for a freelancer, because the client is one message away
• Your own bank - on an inward remittance the UETR arrives in the incoming message, so the trade finance or forex desk can read it out. A branch manager may need to escalate to that desk

Keep the UETR with the invoice record. A payment that goes quiet weeks later is far quicker to trace when the reference is already on file.

What Each GPI Status Means

Your bank will report the payment in one of a handful of states:

Behind those descriptions, bank systems use ISO 20022 status codes such as ACSP, ACSC, ACCC and RJCT, plus reason codes explaining why a payment is pending.

Those are genuine ISO 20022 codes rather than a customer-facing glossary Swift publishes, so your bank may describe the same state in its own words.

Tracking an MT103, and What ISO 20022 Changed

Ask for the UETR and the message-format question stops mattering, because the reference is the same either way.

For years, the SWIFT MT103 carried Field 121, and "send me the MT103" became shorthand for proof a payment had gone out. Swift completed the migration of FI-to-FI cross-border traffic to ISO 20022 on 22 November 2025.

A further deadline follows on 14 November 2026, when unstructured postal addresses are removed, leaving structured or hybrid formats. MT103 is not dead in everyday usage, and many banks still issue an MT103-style advice to customers.

Swift's own figures have moved over time, which is why other guides quote different numbers. Treat any speed statistic carrying an older date as superseded.

For corridor-by-corridor comparisons, our guide to SWIFT transfer time goes wider than this page.

Why Same-Day Use of Funds Can Still Mean Next Week

The commitment is same-day use of funds within the time zone of the receiving member's local business day. It is a service-level commitment, not a promise of instant credit, and that distinction matters if you invoice US clients.

A payment released late on a Friday in New York can meet its commitment and still reach your Indian account the following week. Indian banking hours, weekends and public holidays all sit inside the elapsed time you experience.

Why the Last Mile Is Where the Time Goes

The international leg is rarely the slow part.

Industry analysis from The Global Treasurer and Deutsche Bank, alongside Swift's own last-mile work, puts the concentration of elapsed time on the receiving-bank leg:

• Local processing - the beneficiary bank's own queues and cut-off times
• FX conversion - booking the rate and crediting the rupee amount
• Beneficiary-side compliance - documentation and screening at the receiving end

Percentages get quoted widely for this. Treat the direction as sound and any specific split as an estimate.

GPI is a visibility layer. Every fee in the chain becomes legible, and the total stays exactly where it was.

Take a $10,000 invoice paid by a US client into an Indian bank account.

• What gpi makes visible - the amount that left, what each intermediary bank deducted, and what arrived, disclosed at each stage under the rulebook
• What it does not touch - the receiving bank's FX spread, which is a commercial decision by that bank and is not governed or capped by the rulebook

The spread is priced separately from every fee gpi discloses, which is the gap most guides skip.

A deduction is a stated amount you can add up. A conversion is a rate, and its cost only surfaces when you compare what you were given against the mid-market rate that day. Only the first shows up in a Tracker record.

Six things GPI leaves exactly as it found them.

• The intermediary chain stays - GPI tracks the hops, it does not remove them, and each one can still deduct
• No tracker of your own - Swift runs none for customers, so you see status only through your bank
• Visibility depends on your bank - if your bank does not surface Tracker status to customers, the data exists and you still cannot see it
• Last-mile delay persists - beneficiary-side processing and compliance are outside the tracked speed commitment in practice
• Participation is not universal - if a bank in the chain is not a gpi member, the tracked record has a blind spot
• It does not touch your FX spread - disclosure is not a price control

Same payment, same correspondent chain, before and after the rulebook. What changed is what you and your bank can see while it is in flight.

Table A. A traditional Swift payment against a gpi payment:

Where Swift Go Fits

Swift Go is the sibling product, launched in 2021, for low-value cross-border payments up to $10,000 equivalent. It runs on the same tracked infrastructure.

What it adds on top is price certainty. Participating banks agree fees and FX upfront under their own service rulebook.

For an exporter invoicing small, frequent amounts, knowing the cost before sending can matter more than watching the status. On a large one-off receivable, the tracking detail is what you want.

GPI Versus the Other Ways an Exporter Gets Paid

GPI is bank infrastructure and a payment platform is a way of receiving money. They are not substitutes, so read the table as orientation rather than scoring.

Read the first row against the other two and the trade becomes visible. Of these three routes, only the bank wire shows you the whole correspondent chain, and only there is the conversion cost absent from the table's "what you pay" column.

Xflow's scope is narrower than that row may suggest. It covers receiving export earnings into India, with payment status and compliance documentation in one place.

It has no view of the Tracker, so it changes nothing about what gpi shows you on a bank wire.

For the wider question of which rails an exporter can use instead of a bank wire, see SWIFT payment alternatives.

Everything above describes the system. This is what you do inside it on the Tuesday your money has not landed.

Three moves, in order: establish whether your bank is on the network at all, ask for the right four things, then keep the payment reference separate from your Reserve Bank of India (RBI) paperwork.

Is My Bank on GPI, and How Would I Check?

Banking trade press reported 11 Indian banks signing up to gpi during the India rollout, ICICI, HDFC and Axis among them. Other banks may be members without having said so publicly, so treat any list, this one included, as incomplete.

The gpi Directory itself is member-access, so the reliable check is to ask your bank.

Put it to the trade finance or forex desk rather than the branch counter, and ask two things:

• Is the bank a gpi member? - membership is what puts your payment on the Tracker at all
• Will it share Tracker status on inward remittances? - this second answer decides how useful any of it is to you

Membership and customer-facing visibility are separate things, and a bank can have the first without offering the second.

Your Inward Payment Has Stalled: What to Actually Ask For

Ask for these four things, in this order.

1. The UETR - the reference for this specific payment, in full
2. The current Tracker status - what Swift's record says right now, not what the branch assumes
3. Which party holds it - the bank in the chain the payment is sitting with, and since when
4. Whether a case has been raised - Case Resolution is the formal Swift process for querying a stuck payment, and "we have emailed our correspondent" is not the same thing

Freelancers without a trade finance desk to call can put the same four questions to a relationship manager, who escalates rather than answering on the spot.

Ask for all four in writing, so the status is something you can forward to your client.

The UETR Is Not Your FIRA or eBRC Paperwork

The UETR and the FIRA solve different problems, and conflating them costs time.

The eBRC is the electronic Bank Realisation Certificate you file with the Directorate General of Foreign Trade (DGFT). Both run on separate tracks from the UETR:

The two are separate records and neither depends on the other. Our FIRA page covers the document itself, and FIRC vs FIRA sets out which one you need.

So ask for both, for different reasons: the UETR to find the money, the FIRA to prove it arrived.

Four periods have applied since late 2025, and an export from November 2025 onwards may still be inside its own:

The shortest window belongs to the middle band. From 1 October 2026 the RBI's new FEMA (Export and Import of Goods and Services) Regulations, 2026 supersede the 2015 Regulations.

The period has moved three times inside a year, so confirm it against the notification in force for your own export date.

GPI is worth different things depending on how often you invoice.

Either way, the UETR is what lets the bank look the payment up rather than search for it.