A SWIFT message is an instruction, not a transfer

A cross-border payment often begins with a bank sending a standardized, authenticated message through SWIFT, a network banks use to exchange financial instructions. The message identifies the payment, the parties involved, and where the funds should be credited. Authentication helps the receiving institution verify that the instruction came from an authorized sender; it does not, by itself, move or guarantee the money.

The banks settle through accounts and payment systems

To carry out the instruction, banks adjust balances they hold with one another. If the two banks do not have a direct relationship, one or more intermediary banks may relay the payment through their own accounts. The banks update their ledgers as the transaction is processed, while settlement—the actual discharge of what the banks owe—takes place through those account relationships or through other payment systems.

The route depends on the banks, currencies, and payment arrangements involved. A SWIFT message can therefore be part of a payment that takes time to complete: the instruction may arrive before the banks have finished checks, passed funds through intermediaries, or settled their obligations.

Why the distinction matters

SWIFT is infrastructure for communicating financial instructions, not a global pool of money or a single system that settles every transaction. Its reach comes from giving financial institutions a common, secure way to describe payments across borders. The message coordinates the bookkeeping; the banks and settlement arrangements make the balances real.