SWIFT GPI Payment Tracking: How to Follow Your International Transfer

Before 2017, international wire transfers were effectively invisible once they left your bank. You submitted a payment, waited several days, and hoped it arrived. SWIFT GPI (Global Payments Innovation) changed that by introducing end-to-end tracking, speed commitments, and transparency into the SWIFT correspondent banking network. This guide explains how GPI works, how to use it, and what to do when a tracked payment stalls.

What Is SWIFT GPI?

SWIFT GPI is an enhanced international payment service layered on top of the existing SWIFT correspondent banking network. It was launched in 2017 and is now the standard for most institutional and commercial international wire transfers. By 2026, more than 4,000 banks across 200 countries are GPI members, and the majority of SWIFT cross-border payment value flows through GPI-enabled rails.

Key improvements GPI introduced over classic SWIFT transfers:

• Unique End-to-end Transaction Reference (UETR): Every GPI payment gets a 36-character UUID that travels with the payment through every correspondent bank. This is the primary tracking identifier.
• Real-time status updates: Each bank in the chain must update the payment status in the SWIFT GPI Tracker within a defined time window.
• Speed commitments: GPI banks commit to same-day processing for payments received before their cut-off time.
• Fee transparency: Deductions made by intermediary banks are disclosed, so the beneficiary and sender both know exactly what fees were charged.
• Funds confirmation: The receiving bank confirms when funds have been credited to the beneficiary's account, providing genuine end-to-end confirmation rather than just a dispatch receipt.

How Does the UETR Work?

The UETR (Unique End-to-end Transaction Reference) is a version 4 UUID generated by the sending bank at the moment the payment instruction is created. It looks like: 97ed4827-7b6f-41d2-b41e-b0f1c63ab78a

Every financial institution that touches the payment — originating bank, correspondent banks, receiving bank — is required to pass the UETR along unchanged and record a status event in the SWIFT GPI Tracker database. This creates an immutable audit trail of the payment's journey.

To track your payment, you need the UETR. Your originating bank should provide it in the payment confirmation or receipt. It may also appear in your online banking transaction details under labels like "Reference", "GPI Reference", or "End-to-End ID".

How Do You Track a SWIFT GPI Payment?

There are three main ways to check the status of a GPI payment:

• Your bank's online banking portal: Most major banks surface GPI tracking data in their transaction detail screens. Look for a "Track payment" or "Payment status" link next to international wire transactions. This is the simplest option.
• SWIFT's gpi Tracker (bank access only): SWIFT operates a central tracker database that GPI member banks query via API. Corporate customers can access this indirectly through their bank's treasury management system (TMS) or through SWIFT's corporate access programme.
• Bank API integration: For finance teams processing high volumes of international payments, many banks expose GPI tracking via ISO 20022 APIs. Your ERP or payment platform can query these APIs using the UETR to display live status without manual intervention.

What Do the GPI Status Codes Mean?

SWIFT GPI uses standardised status codes that appear in tracking screens:

• ACSP (Accepted Settlement in Process): The payment has been accepted and is being processed, but has not yet reached the final bank.
• ACCC (Accepted Credit to Customer): Funds have been credited to the beneficiary's account. This is the final success state.
• RJCT (Rejected): The payment was rejected — often due to a compliance check failure, sanctions screening hit, or invalid account details.
• PDNG (Pending): The payment is queued and has not yet been processed by the current bank in the chain.
• CANC (Cancelled): The payment was cancelled, either by the sender or due to a processing error.

What Happens if a GPI Payment Stops Moving?

If a GPI payment has been in ACSP status for more than 24 hours without progressing to ACCC, it has stalled at an intermediary bank. This typically happens because:

• The beneficiary's IBAN or account details are incorrect or failed the receiving bank's validation
• The receiving bank requires additional compliance documentation (common for large or unusual amounts)
• A correspondent bank in the chain has flagged the transaction for manual review
• The beneficiary bank is in a different time zone and has not yet processed within its operating hours

Contact your bank's international payments team with the UETR. They can query the GPI Tracker to identify which bank last updated the status and initiate a trace or cancellation request. GPI banks are contractually obligated to respond to trace requests within one business day.

Does a Valid IBAN Guarantee GPI Success?

A valid IBAN is a necessary but not sufficient condition for a successful GPI payment. The IBAN must pass MOD-97 validation and belong to a real account at the receiving bank. Structurally valid IBANs can still reference closed accounts, frozen accounts, or accounts that have been renumbered after a bank migration.

Before submitting a high-value international wire, validate the beneficiary IBAN at ibanchecker.cash to confirm the IBAN format and retrieve the corresponding bank name and BIC code. Cross-reference the bank name with the beneficiary's stated bank — a mismatch is a red flag for potential fraud.

For teams processing multiple international payments, the bulk IBAN checker validates up to 10,000 IBANs simultaneously and returns the BIC for each, which you can pre-populate into your payment file before submission.

GPI Instant and ISO 20022 Migration

SWIFT is actively migrating the GPI network to ISO 20022 message formats, completing a multi-year transition that runs through 2026 and into 2027. ISO 20022 provides richer data fields — structured remittance information, legal entity identifiers (LEIs), and purpose codes — which improve straight-through processing rates and reduce compliance delays. Banks adopting ISO 20022 alongside GPI see meaningfully fewer payment rejections from compliance screening, because the richer data reduces false positives.

Last updated: June 2026