SWIFT MT103 Field 54A — Receiver's Correspondent

Last reviewed: · Curated by Ohmyfin Organisation editorial.

Field 54A identifies the receiver's correspondent — where the receiver holds its nostro account for this payment currency. Correspondent banking explained →

Payment Tracker

LIVE

Paste your UETR — we query the SWIFT GPI network in real time.

36-character UUID from your MT103 field 121 or pacs.008 <UETR> tag. Where to find it →

Receive your tracking result instantly after search
If not found, we’ll monitor for 7 days and alert you
No account needed — one-click unsubscribe
2
Trusted by 2M+ users monthly  ·  No account or card required
Encrypted | SWIFT Network Coverage | Real-time GPI
SWIFT MT103 message diagram showing fields 20, 32A, 50K, 59, 70 and 121 (UETR)
How an MT103 maps to the UETR (field 121), sender reference (field 20), value-date/currency/amount (field 32A) and beneficiary details. Source: SWIFT MT103 specification.

Details

Format: BIC (8 or 11 characters), optionally preceded by a party identifier (account number). Variants 54B (clearing code and address) and 54D (free-format name and address) also exist. Field 54A is optional, used only when the receiver of the SWIFT message needs the payment funded through a specific correspondent rather than directly. When absent, the settlement defaults to a direct account relationship between the message sender and receiver.

Field 54A is the mirror of field 53A: field 53A tells the chain where the funds come from (the sender's nostro), and field 54A tells the chain where the funds go to (the receiver's nostro). Together they describe both ends of the interbank settlement. For example: sender's bank sends USD via its JPMorgan Chase nostro (field 53A = CHASUS33) to the receiver's bank, which holds its USD nostro at Citibank (field 54A = CITIUS33). The USD funds therefore flow from JPMorgan to Citibank through the Fedwire interbank settlement system.

In many correspondent banking arrangements, both field 53A and field 54A are present simultaneously. The payment path is: sender → sender's correspondent (field 53A) → interbank settlement system → receiver's correspondent (field 54A) → receiver → beneficiary bank (field 57A) → beneficiary (field 59). The SWIFT GPI tracking trail (visible on Ohmyfin) shows all of these hops in order, each with their status update timestamp and fees.

Field 54A is optional and frequently omitted in simple bilateral payment relationships where the receiver can determine its own settlement route from the payment currency and its standard correspondent banking arrangements. Complex correspondent chains — particularly those involving non-major currencies or countries with limited banking infrastructure — are more likely to specify both field 53A and field 54A to avoid misrouting.

In ISO 20022 pacs.008, the concept maps to a combination of settlement method information and intermediate agent identification. The pacs.008 SettlmtInf element specifies the settlement method (e.g. INDA = settled via an account at the debtor agent; INGA = settled via an account at the creditor agent), and the specific nostro correspondent is identified through IntrmyAgt elements or the ClrSys (clearing system) specification.

Quick facts

SWIFT field specification
Example value:54A:RECVCORR2XXX
Valid characters / formatBIC
Required on MT103Optional
Required on MT202Optional
Required on pacs.008Optional
NotesReceiver's correspondent.

Key facts

Frequently asked questions

Field 53A vs 54A — what is the difference?

53A (Sender's Correspondent) identifies the bank where the sender holds the nostro account being debited — i.e. where the funds come from. 54A (Receiver's Correspondent) identifies the bank where the receiver holds the nostro account being credited — i.e. where the funds land. Together they describe the full interbank settlement path.

Is field 54A required if field 53A is present?

Not necessarily — they are independent optional fields. Field 53A may be present without 54A (if only the sender's funding route needs to be specified), or 54A may be present without 53A (if the receiver's nostro correspondent needs to be specified but the sender's is implied). Both can be absent in simple direct bilateral arrangements.

Why would a bank specify field 54A?

When the SWIFT message receiver does not have a direct USD (or other payment currency) account with every bank it deals with, it needs to tell the sender where to deliver the funds. By specifying its nostro correspondent in field 54A, the receiver ensures the funds are delivered to an account it can access, rather than leaving the routing to chance.

Can field 54A cause a payment to be delayed?

Yes — if field 54A specifies a correspondent that is not reachable from the sender's correspondent in the normal interbank settlement cycle, the payment may need to go through an additional hop. Also, if field 54A is incorrect or outdated (e.g. the receiver changed its nostro correspondent), the payment may be misrouted or returned.

How does field 54A appear in the SWIFT GPI tracking trail?

The receiver's correspondent identified in field 54A typically appears in the SWIFT GPI tracking trail as one of the hops before the final beneficiary bank. On Ohmyfin, each correspondent bank in the chain is listed with its BIC, timestamp, and status update. The field 54A bank will appear between the field 53A sender's correspondent and the field 57A beneficiary bank.

Get 100 free credits — track unlimited SWIFT payments

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 →
ExploreSWIFT trackerUETR trackerCurrency exchange ratesUSD → EUR rateGBP → USD rateEUR → GBP rateUSD → JPY rateWestern Union MTCN trackerMoneyGram reference trackerRia PIN trackerRemitly trackerXoom / PayPal trackerWorldRemit trackerWise trackerRevolut trackerOFX trackerZelle trackerVenmo trackerCash App trackerPayoneer trackerSkrill trackerNeteller trackerInstarem trackerTRN trackerDraft & validate hubMT ↔ MX translatorMX → MT translator@ohmyfin/swift-draft (npm)MT103 drafterMT202 drafterMT202COV drafterMT199 drafterpacs.008 drafterpacs.009 drafterpacs.002 draftercamt.053 draftercamt.054 drafterMT103 trackerWire-transfer trackerSWIFT GPI trackerBIC lookupIBAN explainedUETR explainedTRN explainedBIC explainedMT103 guideMT202 guidepacs.008 guideField 20Field 32AField 50KField 57AField 121 (UETR)Track USDTrack EURTrack GBPTrack CNYTrack INRSWIFT vs SEPASWIFT vs ACHSWIFT vs WiseUETR vs TRNBIC vs IBANMT103 vs pacs.008How long: UKHow long: USHow long: IndiaHow long: EurozoneStatus: ACSPStatus: ACCCStatus: RJCTStatus: PDNGSWIFT GPISWIFTNetOhmyfin AI AssistantSWIFT status todayBank trackersTrack HSBCTrack ChaseTrack BarclaysTrack NatWestTrack WiseTrack RevolutAsk: How to track SWIFTAsk: UETR not foundAsk: Stuck 2 weeksAsk: Get UETR from bankAsk: Is Ohmyfin freeAlliance AccessAlliance GatewaySWIFT GoKYC RegistryAbout swift.comSWIFT productsCurrency guidesPayment comparisonsPayment speedStatus codesSWIFT field referencePayments glossarySWIFT message typesSWIFT/BIC directoryCorrespondent banksKnowledge centerReject codesAC01 rejectAC04 rejectBE01 rejectCH09 rejectRR04 rejectHelp & troubleshootingPayment not receivedFind UETR on MT103Cancel SWIFT paymentFake MT103 warningMajor banksJPMorgan Chase BICHSBC BICDeutsche Bank BICCiti BICBNY Mellon BICCountry corridorsSend US → IndiaSend US → MexicoSend US → PhilippinesSend UK → IndiaSend UK → PakistanSend UAE → IndiaSend UAE → PhilippinesSend Saudi → IndiaSend Canada → IndiaSend Australia → IndiaMT message referenceMT202COVMT199MT940MT942MT900MT910MT195MT103 STPBanks by countryBanks in USBanks in UKBanks in GermanyBanks in IndiaBanks in ChinaBanks in UAEBanks in Saudi ArabiaBanks in SingaporeBanks in Hong KongBanks in JapanBanks in BrazilUse casesFreelancer paid abroadPay overseas supplierE-commerce payoutsTuition paymentReal estate abroadFamily remittanceScam alertsFake MT103 fraudMoney-transfer providersTrack WiseTrack RevolutTrack Western UnionTrack MoneyGramTrack RemitlyTrack RiaTrack XoomTrack WorldRemitTrack PayoneerTrack PayPalTrack OFXTrack SkrillTrack SendwaveTrack InstaremTrack TransferGoTrack Stripe payoutTrack AirwallexTrack HSBC Global MoneyTrack Monzo / Revolut / N26Wise vs RevolutWise vs PayPalWise vs Western UnionWise vs bank wireWestern Union vs MoneyGramRemitly vs Western UnionSend money to IndiaSend money to PhilippinesSend money to MexicoSend money to NigeriaSend money to PakistanSend money to UKAdvance-fee fraudBEC / CEO fraudPig butchering scamRomance scam wire