Swift Does Not Move Your Money. So What Does?

A Swift message is an instruction, not a suitcase

People say a payment went through Swift as if Swift were a pipe full of pounds. Swift describes its own role more narrowly: it exchanges standardised financial messages and does not hold funds or manage customer accounts. The instruction and the settlement it triggers are related, but they are not the same event.

A message identifies the institutions, amount, currency and parties. Banks then settle using accounts they hold directly or through correspondents. Swift's tracker can show progress because a unique reference follows the instruction. Tracking a parcel does not drive the van, and tracking a payment does not provide the receiving bank with money.

Domestic systems combine the layers differently. CHAPS instructions settle one by one across accounts in the Bank of England's RTGS service. Faster Payments gives customers near-real-time credits, while the participating institutions' net positions settle in RTGS at scheduled points during the day. Similar front-end speed can hide a different settlement design.

ISO 20022 gives the instruction better fields

ISO 20022 defines structured financial messages. It is not a network and does not choose the bank route. Its value is the ability to carry consistent fields rather than squeeze important detail into short free-text lines. Better data can improve sanctions screening, reconciliation and automated repairs.

The names look forbidding until they are translated. A pacs.008 carries a customer credit transfer between financial institutions. A pacs.009 covers an institution's own credit transfer. A pacs.002 reports payment status, while camt messages handle jobs such as statements and debit or credit notifications. The code identifies a business purpose, not a faster class of money.

Swift ended the general CBPR+ coexistence period for old MT and ISO 20022 payment instructions in November 2025. The work continues. From November 2026, town and country must sit in designated fields for relevant cross-border messages, and fully unstructured addresses will no longer be supported. A cleaner message still depends on clean customer data.

Settlement is where the promise becomes final

RTGS means real-time gross settlement. Each accepted payment is settled individually rather than included in a later net total. Central-bank money is used between participants, removing the commercial-bank credit exposure from that final settlement asset. The Bank of England's renewed RT2 ledger went live in April 2025.

Net settlement takes another route. A retail system can process thousands of customer payments, offset what each member owes and submit the remaining positions for settlement. This economises on liquidity. It also requires rules for failed participants and enough funds when the settlement cycle arrives.

The European Central Bank's TIPS service settles instant payments in euros, Swedish kronor and Danish kroner continuously. Settlement is final in central-bank money. Access still comes through eligible payment service providers or reachable arrangements, so a British transfer app does not gain a direct European rail merely by using ISO 20022.

How the plumbing reaches a £200 quote

Structured purpose and address data can keep an ordinary payment away from manual review. The recipient bank's yes or no comes back in its own status message. Standard identifiers make repairs less like comparing two faxed forms. Every repair avoided saves work. With luck, a little of that saving shows up in the price or arrival time.

APIs are not here to push those messages into retirement. A bank may accept a customer instruction through an API, translate it into an ISO 20022 payment and receive status events back. Another provider may expose the same journey as one developer endpoint. The neat request at the top can still fan out into several network-specific instructions below.

Standards cannot remove a missing correspondent, a closed local market or an empty payout account. Nor do they decide the exchange rate. The BIS keeps returning to liquidity, access and legal differences because a technically perfect message may still reach a system where the sender cannot settle directly.

When a provider advertises a new protocol, ask which layer improved. Is the company connected to a domestic payment system, sending richer messages through a partner or merely offering better tracking? That narrower answer can still describe a useful improvement. It should be more precise than saying the money now uses modern rails.