Last reviewed: · Curated by Ohmyfin Organisation editorial.
Field 111 is the Service Type Identifier in MT103 block 3 — declares the GPI service type (001, 002, 003, etc.). Learn about SWIFT GPI → · Track any GPI payment free →
Field 111 lives inside block 3 (the User Header block) of the SWIFT MT message, alongside field 121 (UETR) and field 113 (banking priority code). The block 3 format is {block-type:value}, so field 111 appears as {111:001} for a standard GPI customer credit transfer. The five defined service type codes are: 001 (gpi Customer Credit Transfer — CCT, the standard cross-border customer payment); 002 (gpi Cover — gCOV, the GPI version of the MT202COV cover payment that carries underlying customer data); 003 (gpi Stop and Recall — gSRP, a payment that has been flagged for stop-and-recall processing); 004 (gpi Case Resolution — gCASE, used in investigation and dispute resolution messages); 005 (gpi Instant — gINS, for payments on near-instant cross-border corridors where the GPI Instant service level applies).
Field 111 is mandatory on all payments sent by SWIFT GPI member banks, which effectively means every cross-border SWIFT payment — since GPI membership now covers approximately 95% of SWIFT cross-border payment value worldwide and all major correspondent banking corridors. The service type code drives the SLAs (service level agreements) that every bank in the chain must meet. For service type 001, GPI Rulebook obligations include: same-business-day forwarding, status update within minutes of processing, and unaltered pass-through of remittance information.
The most common value by far is 001 — virtually all retail and corporate MT103 customer credit transfers use code 001. Code 002 appears on GPI Cover payments (MT202COV equivalents in GPI). Code 003 appears only when a Stop-and-Recall request (using the gSRP Stop and Recall Procedure) has been triggered by any bank in the chain — this changes the handling obligations for all subsequent banks. Code 004 is used in case-resolution workflows when a payment discrepancy needs investigation. Code 005 is used on corridors where both the sender and receiver participate in GPI Instant (sub-25-second settlement).
From the Ohmyfin tracking perspective, field 111 code 001 is the normal tracking scenario. Code 003 (Stop and Recall) changes the Ohmyfin status display to indicate that a recall has been requested — this is flagged prominently so users understand the payment may be returned. Code 005 (Instant) means the payment should have settled in under 25 seconds on a participating corridor; if Ohmyfin shows it still in ACSP after several minutes, there may be an issue with the instant payment rail.
The introduction of field 111 with the GPI Service Type Identifier was part of SWIFT's progressive rollout of the GPI programme starting from 2017. Before GPI and field 111, SWIFT messages had no standardised way to signal which service tier or SLA the payment was operating under. Field 111, together with field 121 (UETR), forms the core of the SWIFT GPI metadata infrastructure that enables end-to-end tracking and service-level enforcement across the global SWIFT network.
| Example value | :111:001 |
|---|---|
| Valid characters / format | 3 digits |
| Required on MT103 | Optional |
| Required on MT202 | Optional |
| Required on pacs.008 | Optional |
| Notes | Service-type identifier (GPI: 001 = SLA-compliant). |
Yes, for every payment sent by a SWIFT GPI member bank — which now includes effectively all banks sending cross-border payments on major corridors. The field must be populated with the appropriate 3-digit code. Absence of field 111 on a cross-border MT103 may indicate the payment is using a legacy (pre-GPI) routing, which provides no SWIFT GPI tracking guarantee.
Field 111 is in block 3 (User Header) of the SWIFT MT message, not in block 4 (the text block where most fields like 32A, 50K, 59, 70, 71A reside). It appears as {111:001} inside the {3:...} block structure. Field 121 (UETR) is also in block 3, appearing as {121:xxxxxxxx-xxxx-4xxx-xxxx-xxxxxxxxxxxx}.
Code 003 means the payment has been flagged for the GPI Stop and Recall Procedure — any bank in the chain (the originating bank, a correspondent, or the beneficiary bank) has sent a recall request. All subsequent banks in the chain must respond to the recall within one business hour during business hours. If the payment has already been credited, the beneficiary bank must ask the beneficiary for consent to return the funds.
GPI Instant (service type 005) is an extension of the standard GPI service for cross-border payments on corridors where both the sending and receiving country support near-instant payment rails (e.g. UK Faster Payments, EU SEPA Instant, Singapore FAST). Under GPI Instant, settlement should complete in under 25 seconds end to end. Not all corridors support GPI Instant.
Field 111 tells Ohmyfin which GPI service the payment is using. Code 001 payments are tracked with standard GPI status codes (ACSP, ACSC, RJCT, etc.). Code 003 (Stop and Recall) payments are flagged as "under recall" in the Ohmyfin display. Code 005 (Instant) payments are expected to show ACSC (settled) within seconds of initiation on participating corridors.
No card needed. Free for ordinary users — completely free for individuals — no daily limit, no card required. Track any international wire across 11,000+ banks.
Track a payment now — completely free Or try the tracker now →