SWIFT architecture: BICs, correspondents and the message layer

A SWIFT payment runs on two layers: a messaging network that carries the instruction, and a web of accounts between institutions where the money actually moves. This article works through what that split means in practice.

In short

A SWIFT payment runs on two layers. Messages move on the SWIFT network. Money moves across accounts banks hold with each other. Confusing the two is why cross-border payments feel unpredictable.
Nostro and vostro are the same account seen from opposite sides. Your provider can only pay in a currency where it, or someone it banks with, holds one.
Under the cover method, the beneficiary's bank is told about your payment before the funds arrive. That is a feature, and it explains why a payment can show as received and unavailable at the same time.
Every payment carries a UETR. If your provider will not give you one, it cannot tell you where your money is.
Being registered with a BIC, being connected to the network, and being able to clear a given currency are three different things. Providers routinely blur them.

What are the two layers and the data flow of a SWIFT payment?

The messaging layer is a secure network with a common format: your provider transmits a structured message every receiving institution parses the same way. No money is attached to it. The message is an instruction, and it is worth exactly as much as the account relationship standing behind it.The settlement layer is that relationship. Before any institution can pay another, one of them holds an account with the other, or both hold accounts with a third party that sits in the middle. Payment then means a debit on one ledger and a credit on another.This is why a payment cannot simply be routed to wherever the message can reach. The message can reach 200 countries. The money can only travel where accounts already exist.

What is a correspondent account, and what do nostro and vostro mean?

A correspondent account is an account one financial institution holds at another so it can settle in that institution's currency or market. The two words describe one account from two sides.

Term	Whose books	Plain reading
Nostro	Yours	"Our money, held at your bank." A euro institution's USD account at a US bank.
Vostro	Theirs	"Your money, held at our bank." The same account, described by a US bank.

The practical consequence: a provider can only send you money in a currency where it holds a nostro, or where a bank it banks with does. A provider advertising 60 currencies is telling you about the reach of its correspondent network, not about software. It also explains the fees. Each institution holding a nostro in the chain runs its own compliance, funds its own liquidity and prices accordingly, which is where deductions come from. The pillar article covers the charge options that decide who absorbs them, and Narvi's own fees are on the pricing page.

Which SWIFT messages carry a payment?

ISO 20022 replaced the old MT formats for cross-border payments, and Swift's coexistence period ended in November 2025. The names changed. The functions did not.

ISO 20022	Old MT	What it does
pacs.008	MT103	Customer credit transfer. The message behind a normal business payment.
pacs.009	MT202	Transfer between financial institutions, with no underlying customer.
pacs.009 COV	MT202COV	The settlement half of a cover payment, carrying the original customer details.
pacs.002	MT199 status	Status report. Accepted, pending, or rejected, with a reason code.
pacs.004	MT103 return	Payment return. The money coming back.
pain.001	MT101	A corporate instructing its own bank to pay. Used in ERP and treasury integrations.
camt.053	MT940	End-of-day statement.
camt.052	MT942	Intraday statement.
camt.054	MT900 / MT910	Debit and credit notification.
camt.056	MT192 / MT292	Request to cancel a payment already sent.
camt.110 / camt.111	MT199 free text	Investigation request and response. Replaces the era of banks emailing each other.

The migration is not finished. From 14 November 2026, cross-border payment messages will only accept fully structured or hybrid postal addresses: town and country in their own fields, for every party in the payment. Free-text address lines get rejected. If your supplier database stores addresses as one string, that is a data project with a date on it.

What is the difference between the serial and cover methods in business logic?

This is the piece almost nobody explains to the businesses affected by it, and it is the single most useful thing in this article.Under the serial method, one pacs.008 travels the chain. Your provider sends it to a correspondent, which debits and credits and passes it on, until it reaches the beneficiary's bank. Information and money move together, in the same message, one hop at a time.Under the cover method, they separate. Your provider sends the pacs.008 straight to the beneficiary's bank as an announcement, and separately sends a pacs.009 COV along the correspondent chain to move the actual funds. Two messages, two routes, one payment.

	Serial	Cover
Messages	One pacs.008 through the chain	pacs.008 direct, plus pacs.009 COV through the chain
Beneficiary bank learns of the payment	When the message arrives with the funds	Immediately, before the funds arrive
Can the beneficiary be credited early	No	Yes, at the bank's discretion and risk
Where you see it	Shorter chains, single correspondent	Longer chains, major currency corridors

The consequence for a business: under the cover method your customer's bank can tell them a payment is coming while the money is still two institutions away. Some banks credit immediately on the announcement. Others wait for the cover to settle. Same payment, same network, completely different customer experience, and neither bank is doing anything wrong.MT202COV, the cover message's predecessor, was introduced in 2009 specifically so the settlement half would carry the originator and beneficiary details. Before that, a correspondent moving cover funds saw a bank-to-bank transfer with the underlying customer invisible, which regulators objected to. Swift's Payments Market Practice Group maintains guidance on how cover payments should be formatted, and it is the reference your provider's operations team should be working from.

What is a UETR, and how does GPI tracking work with core data?

A UETR is a 36-character reference, unique to a single payment, generated when the payment is created and carried unchanged through every message relating to it. Cancellations, status reports, returns and investigations all quote the same UETR.That reference is what makes SWIFT GPI work. Institutions on gpi report status back to a central tracker as the payment passes through them, so the sending institution can see where it currently sits, what has been deducted, and which institution is holding it.Two things follow from this that affect how you choose a provider.The tracker is visible to institutions, not to you. Whether you ever see it depends on whether your provider passes the information through, either in the dashboard, through the API, or by a human answering the question. That is a product decision, not a network capability, and the practical solution is a provider that exposes those updates clearly. How to track a payment and what to send when one stalls covers the practical side.And GPI coverage is not universal. If a payment leaves GPI coverage mid-chain, the trail goes quiet until it re-enters. A provider promising full visibility on every corridor is describing something the network does not deliver.

Why does a payment pick up intermediaries, and what shortens the chain?

Every hop is an institution that runs its own screening, applies its own cut-off, and may take its own fee. Fewer hops is faster and cheaper, and the number of hops is decided by account relationships, not by routing software.A payment goes direct when your provider holds an account with the beneficiary's institution, or both sit in the same clearing system for that currency. It gains one intermediary when they share a common correspondent. It gains two or more when they do not, which is common in thin currencies and in markets where correspondents have withdrawn.Three things actually shorten a chain, and none of them are things you can fix at the moment of payment:

Your provider's own correspondent network in the currency you use most. Ask which currencies it holds accounts in directly, not how many it can send.
Direct participation in the local clearing system. On the euro side, this is changing: the Eurosystem decided in July 2024 to open T2 and TIPS to payment institutions and electronic money institutions from April 2025, implementing the Instant Payments Regulation through an amendment to the Settlement Finality Directive. Non-bank providers that used to reach euro clearing only through a sponsor bank can now apply for direct access, subject to the same safeguards as credit institutions.
Using the right rail at all. A euro payment inside the SEPA area should never touch SWIFT. It settles over SEPA, in seconds where SEPA Instant is supported.

Note what the Eurosystem decision does and does not do. It concerns euro clearing at the central bank, not SWIFT. A provider with direct T2 access still needs correspondents for dollars. In architecture terms, that kind of constraint shapes the plan for any new feature and clarifies which task belongs in routing logic versus network access; dependency injection also improves testability in Swift applications by making scene components easier to replace in tests.

What does it take for a provider to be reachable on SWIFT at the data layer?

A registered BIC. Any eligible institution can hold one, and the public BIC directories will list it. Narvi's is NARYFIH2. Registration means the institution exists as an addressable entity. It does not mean payments flow.A connection to the network. The institution has to actually send and receive messages, either through its own SWIFT connectivity or through a service bureau. This is infrastructure and staffing, not paperwork.A correspondent that will clear the currency. This is the one that decides whether your payment happens. An institution can hold a BIC, be fully connected, and still be unable to pay in a currency where nobody will hold its account. It is also the reason some providers can send but not receive, or receive euro but not dollars.When you are comparing providers, the useful questions are the specific ones. In layered design, the data layer should expose only what inner abstractions require, not operational detail from the network edge. Clean Architecture specifies modular layers, with outer layers depending on inner abstractions. That keeps core business rules isolated from external tools like databases and networks, whether you persist state with core data or another store handling payment records. Dynamic member lookup can also support runtime dependency resolution in more advanced setups. Which currencies do you hold correspondent accounts in directly? Can my own IBAN receive an international payment, or do funds land in a pooled account and get allocated to me? Do you pass me the UETR? Who do I speak to when a payment stalls, and how quickly?That last cluster matters more than reach figures. A business refused by correspondents for reasons that have nothing to do with its own conduct hits a different problem entirely, which we cover in why correspondents say no.

FAQ

Yes. BIC stands for Business Identifier Code, and it is the address the network routes to. It is 8 or 11 characters: four for the institution, two for the country, two for the location, and an optional three for a branch. NARYFIH2 breaks down as NARY for Narvi Payments Oy Ab, FI for Finland, H2 for Helsinki. The pillar article reads one character by character.

Most often the cover method. The beneficiary's bank may hold the announcement while it waits for the cover funds to settle, or it may be running its own checks. Ask your provider for the UETR and the current gpi status: that tells you which institution is holding the payment, which is a far more useful thing to know than that it was sent.

pacs.008, the ISO 20022 customer credit transfer. Swift's MT and MX coexistence period for cross-border payments ended in November 2025. MT103 still appears in conversation and in some domestic contexts, but for cross-border traffic on the network the message is pacs.008.

No. You need it when something goes wrong, or when you are choosing between providers, because it turns marketing claims into questions with checkable answers. As in other fast-moving tech fields, examples and official documentation help people verify how a provider actually works;

Not soon, and not by any single thing. Swift itself is building alongside the existing network: in July 2026 it moved a blockchain-based shared ledger into controlled go-live with 17 banks across six continents, aimed at 24/7 settlement of tokenised deposits. Regional instant-payment schemes and stablecoin rails are taking share in specific corridors. For a European business paying suppliers in 40 countries today, SWIFT is still the rail that reaches all 40.

Getting SWIFT payments to work for your businessMost of the friction in cross-border payments comes from three places: how many correspondents your payment passes through, whether your provider gives you a real answer when something stalls, and whether your account was set up to receive international payments in the first place, since routing depends on correspondent relationships and the number of banks involved. Narvi is an electronic money institution licensed by the Finnish Financial Supervisory Authority, providing corporate customers with dedicated IBAN accounts in your company's name, local bank-style account details such as IBAN and BIC for global payments, plus SEPA and SWIFT connectivity, multi-currency wallets and API access; accurate bank account information also helps businesses using SWIFT receive funds smoothly.

See how SWIFT payments work at Narvi

Updated August 27, 2026Disclaimer
This publication is provided for general information purposes and does not constitute legal, tax, or other professional advice from Narvi Payments Oy Ab or its affiliates, and it is not intended as a substitute for obtaining advice from a financial advisor or any other professional.

SWIFT architecture: BICs, correspondents and the message layer

A SWIFT payment runs on two layers: a messaging network that carries the instruction, and a web of accounts between institutions where the money actually moves. This article works through what that split means in practice.

In short

What are the two layers and the data flow of a SWIFT payment?

What is a correspondent account, and what do nostro and vostro mean?

Which SWIFT messages carry a payment?

What is the difference between the serial and cover methods in business logic?

What is a UETR, and how does GPI tracking work with core data?

Why does a payment pick up intermediaries, and what shortens the chain?

What does it take for a provider to be reachable on SWIFT at the data layer?

FAQ

Is a BIC the same as a SWIFT code?

Does an EMI need a partner bank to send SWIFT payments?

What replaced MT103?

Do I need to understand any of this to send a payment?

Is SWIFT being replaced?

Read next: