The History of SWIFT and How the Network Works

International Banking Before SWIFT

Cross-border banking once depended heavily on telex.

Telex allowed banks to transmit written instructions electronically across long distances, which represented a major advance over earlier communication methods. By the 1960s, however, international banking volumes were expanding rapidly and the limitations of free-text communication had become expensive.

Bank employees had to interpret messages written by counterparties using different terminology, formats and operating practices.

That increased manual intervention.

Authentication required procedures agreed between correspondent banks. Payment instructions had to be interpreted and re-entered into internal systems. Differences in abbreviations or formatting could create operational errors.

International banking needed more than a faster communication line.

It needed a common financial language.

239 Banks Created SWIFT in 1973

The solution came from the banking industry itself.

In 1973, 239 banks in 15 countries created a cooperative utility that would eventually become SWIFT.

The structure mattered.

Rather than allowing one commercial bank to own the principal communications system used by its competitors, participating institutions created shared infrastructure.

The network would provide common messaging standards, routing technology and secure communications available across institutions and jurisdictions.

SWIFT was established under Belgian law and remains headquartered in Belgium.

The cooperative model continues today. Financial institutions form the core of the ownership and governance structure, making SWIFT industry infrastructure rather than a conventional technology vendor selling a proprietary communications network to banks.

SWIFT Went Live in 1977

Building the network took several years.

SWIFT needed operating centers, communications links, bank interfaces and standardized message formats capable of supporting real financial transactions.

The network went live in 1977.

By launch, participation had increased from the original 239 banks to 518 institutions across 22 countries.

The response from the banking market came quickly.

Within the first year of operations, the network had already processed around 10 million messages.

The reason was structural. Every additional institution joining the network increased the number of counterparties another bank could reach through one standardized infrastructure.

A Short History of SWIFT

The Bigger Innovation Was Standardization

SWIFT's communications network gets much of the attention, but standardization created much of its economic value.

Banks need to understand what another institution is asking them to do.

A payment instruction requires structured information about the ordering party, beneficiary, amount, currency, banks and accounts involved.

A documentary letter of credit requires entirely different information: applicant, beneficiary, expiry, shipment terms, documents, amount, confirmation instructions and availability.

A securities settlement instruction needs another data structure.

SWIFT created standardized message families so participating systems could interpret those transactions consistently.

This eventually produced the familiar MT message architecture used throughout international banking.

Why Standardization Changed International Finance

Consider two banks processing thousands of cross-border instructions each day.

Without a shared format, operations teams must determine where key information appears in every incoming communication.

With standardized messages, specific fields have defined purposes.

Software can validate messages, identify counterparties, extract structured information and send transactions into downstream processing systems.

That supports straight-through processing.

It also makes larger transaction volumes economically manageable.

What SWIFT Actually Does

SWIFT provides secure infrastructure through which participating institutions send standardized financial messages.

Its users include banks, securities firms, market infrastructures, investment institutions and large corporates.

The network carries the information required to initiate and administer financial transactions.

SWIFT also develops and maintains standards, identification systems, interfaces, transaction-management capabilities, payment tracking and other infrastructure used by the financial community.

The fundamental role remains messaging.

SWIFT Messages and Money Movement Are Separate Layers

This distinction clears up one of the most persistent misconceptions about international banking.

Imagine a customer of Bank A sending USD 1 million to the customer of Bank B.

Bank A can send the relevant payment instruction through SWIFT.

The financial settlement takes place through correspondent accounts, clearing systems, central-bank money or another appropriate settlement arrangement.

If the banks maintain nostro and vostro accounts with each other, the transaction can result in the appropriate accounts being debited and credited.

If intermediary banks are required, the payment instruction may travel through a correspondent chain.

SWIFT provides the standardized communications layer connecting those institutions.

Why Correspondent Banking Still Matters

A bank in one country rarely maintains a direct account relationship with every bank in every other country.

Correspondent banking solves that problem.

One institution maintains an account with another bank capable of providing access to a foreign currency or financial market.

SWIFT allows the banks in that chain to exchange standardized instructions securely.

The network effect is enormous. One bank can communicate with institutions across a large part of the international financial system without building bespoke communications infrastructure for every relationship.

The BIC and the “SWIFT Code”

Most businesses first encounter SWIFT through a bank's SWIFT code.

The formal term is Bank Identifier Code, or BIC.

The code identifies the financial institution within standardized messaging and payment workflows.

A BIC can contain information identifying the institution and location, with an optional branch identifier.

This is why international payment instructions commonly request both an IBAN or account number and a SWIFT/BIC.

The account identifies where the funds ultimately belong. The BIC identifies the institution involved in routing the financial message.

SWIFT and Cross-Border Payments

Payments remain the use case most closely associated with SWIFT.

Banks exchange instructions covering customer transfers, financial-institution transfers, confirmations, returns, investigations and other parts of the payment lifecycle.

For decades, the industry relied heavily on MT formats such as MT103 for customer credit transfers and MT202 for financial-institution transfers.

That messaging environment has now moved into ISO 20022 for cross-border payment instructions.

The underlying principle remains familiar: one institution communicates standardized payment information to another institution through trusted infrastructure.

SWIFT and Trade Finance

Trade finance became another important part of the SWIFT network because international trade depends heavily on bank-to-bank communication.

An importer in one country may request its bank to issue a documentary letter of credit in favor of an exporter using a bank in another jurisdiction.

Those banks need a reliable method for exchanging the credit, amendments, reimbursement instructions and documentary information.

Category 7 SWIFT messages provide much of that architecture.

Examples include:

Financely covers this architecture in our MT700 documentary credit, MT799 and broader letter of credit material.

SWIFT Made Global Trade Easier to Automate

Before standardized electronic bank messaging, every additional international counterparty created another communications problem.

A letter of credit issued in Japan, advised in Switzerland and payable to a Brazilian exporter required the banks to understand the same transaction terms.

SWIFT gives the institutions a structured communication environment.

The contractual rules still come from frameworks such as UCP 600, ISP98 and URDG 758 where incorporated into the relevant instrument.

SWIFT handles the banking message.

The ICC rules govern the relevant documentary or guarantee practice.

SWIFT Expanded Beyond Payments

International finance extends far beyond cash transfers.

Securities firms, custodians, asset managers, central securities depositories and other market infrastructures need to exchange instructions concerning trades, settlement, custody and corporate actions.

SWIFT expanded to support these workflows as financial markets became more automated.

The same economic principle applies.

Standardized communications reduce manual translation between institutions and make straight-through processing possible across large transaction volumes.

Treasury and Foreign Exchange

Bank treasury operations also rely on standardized communication.

Foreign exchange, money-market transactions, confirmations and related settlement activity require institutions to reconcile counterparties, currencies, values and settlement instructions.

As transaction volumes increased, standardized electronic messages became core infrastructure for those workflows.

SWIFT GPI Changed Payment Tracking

Traditional correspondent banking often left corporate treasurers with limited visibility after a payment left the originating bank.

SWIFT launched its Global Payments Innovation service, commonly called SWIFT GPI, in 2017.

GPI introduced greater end-to-end visibility into cross-border payments.

Its features included payment tracking, improved fee transparency, transfer of remittance information and faster processing among participating institutions.

This moved the customer experience closer to parcel tracking: banks and eligible users could see where a cross-border payment sat in the chain rather than relying entirely on manual investigations among correspondent institutions.

Why Payment Tracking Was Important

The messaging network itself could move information quickly.

Delays often occurred elsewhere in the transaction chain.

A payment could encounter compliance screening, foreign exchange conversion, local clearing windows, missing information or beneficiary-bank processing.

Tracking makes those frictions visible.

That distinction remains important today when assessing cross-border payment speed. A SWIFT message can reach another institution rapidly while the underlying payment still awaits further processing.

ISO 20022 Changed the Language Again

The original MT architecture helped standardize global finance for decades.

Modern financial institutions require substantially richer data.

ISO 20022 provides a more structured financial-messaging methodology and data model capable of carrying granular information about parties, accounts, transactions, remittance and other payment attributes.

The SWIFT community decided in 2018 to migrate cross-border payments and reporting toward ISO 20022.

The migration culminated in a major milestone on 22 November 2025, when the MT and ISO 20022 coexistence period for cross-border payment instructions ended.

ISO 20022 is now the standard language for cross-border payment instructions on the network.

Why Richer Data Matters

Better payment data affects several parts of bank operations.

Structured party information can improve sanctions and compliance screening. Detailed remittance data can improve invoice reconciliation. Better standardized information reduces the need for manual repair.

It also creates more usable information for treasury systems, analytics and transaction monitoring.

SWIFT's history therefore follows a consistent pattern: banks create greater value by agreeing how financial information should be structured before sending it across the network.

Why Banks Trust SWIFT

A financial messaging network becomes valuable only when institutions trust the source and integrity of the messages they receive.

Security and operational resilience therefore sit at the center of SWIFT's role.

The network combines controlled institutional access, secure messaging infrastructure, standardized identities and operational controls.

Banks also maintain their own authentication, approval, sanctions, fraud and transaction-monitoring controls around incoming and outgoing messages.

SWIFT reported network availability above 99.99% in 2024, illustrating how closely the financial system depends on continuous operation.

SWIFT Authentication Is Different From Credit Approval

A properly authenticated SWIFT message establishes that a communication came through the relevant banking channel.

Creditworthiness requires separate analysis.

A valid MT760 issued by a small regional bank remains an undertaking of that regional bank.

A valid MT700 issued by a highly rated international bank carries that bank's documentary-credit obligation.

The message network authenticates communications. Beneficiaries and other financial institutions still assess issuer credit, transaction risk and instrument wording.

SWIFT Became a Target for Fraud Narratives

The prestige associated with SWIFT also made its terminology attractive to fraudsters.

Expressions such as MT799, MT760, MT103 and “bank-to-bank SWIFT” appear frequently in fabricated transaction procedures.

The codes themselves are ordinary banking message formats.

The relevant questions remain straightforward:

• Which regulated institution sent the message?
• Which institution received it?
• What does the actual message say?
• Which underlying transaction generated it?
• Has the receiving bank authenticated it?
• Which legal or credit obligation sits behind it?

A message code alone provides few answers.

How SWIFT Became Geopolitically Important

For most of its history, SWIFT attracted little attention outside banking and financial operations.

That changed when access to the network became part of international sanctions policy.

SWIFT is incorporated in Belgium and operates under applicable Belgian and European Union law.

In 2012, it disconnected specified Iranian banks after an EU regulation prohibited specialized financial-messaging services for sanctioned institutions.

Similar attention returned in 2022 when selected Russian banks were disconnected following sanctions adopted after Russia's invasion of Ukraine.

These events demonstrated the strategic importance of financial messaging infrastructure.

What Disconnection From SWIFT Actually Means

Removing a bank from SWIFT removes its access to that widely used standardized communication network.

The bank then faces much greater friction communicating with international counterparties through ordinary global banking workflows.

The action differs from confiscating a bank's assets or automatically blocking every payment involving that institution.

Those effects come from separate legal sanctions, correspondent-bank decisions, asset freezes and payment-system restrictions.

SWIFT access concerns the communication layer.

SWIFT Is a Cooperative

SWIFT's ownership structure separates it from many other global technology networks.

It operates as a cooperative owned and governed by its financial-institution shareholders.

This model reflects the original reason for its creation.

Competing institutions needed common infrastructure in an area where interoperability produces greater value than proprietary fragmentation.

The participating financial community therefore shares the network rather than allowing one competitor to control the basic language used for communication.

How Large Is SWIFT Today?

SWIFT now connects more than 11,500 institutions across more than 200 countries and territories.

Those users include banks, financial institutions, market infrastructures and corporate customers.

Average daily FIN traffic exceeds 53 million messages.

The scale gives SWIFT a powerful network effect.

A newly connected financial institution gains access to standardized communication with a large existing community. Existing institutions benefit each time the network becomes more comprehensive.

This is one reason financial messaging infrastructure becomes difficult to replace through a single competing platform.

SWIFT's Role Today Goes Beyond Sending Messages

The Future of SWIFT

Financial infrastructure is changing again.

Instant-payment systems are expanding. Stablecoins and tokenized deposits are entering institutional finance. Central banks continue to study digital currencies. Distributed-ledger networks can move tokenized assets and cash representations directly between participants.

SWIFT's strategic question therefore resembles the one banks faced in 1973.

Different institutions, systems and asset networks need to communicate with one another.

Interoperability may become more important as financial infrastructure fragments across conventional accounts, instant-payment rails and tokenized networks.

SWIFT has already explored interoperability across distributed-ledger networks and has continued developing shared-ledger and digital-asset capabilities.

The technology underneath global finance may change considerably while the need for trusted common standards remains.

SWIFT's Real Product Is Financial Interoperability

It is tempting to describe SWIFT as a payments network.

That captures only part of its role.

Its deeper contribution has been creating a common communications environment in which institutions using different internal systems, currencies, languages and jurisdictions can exchange financial instructions with a shared understanding of what those instructions mean.

That is why the network expanded from payments into trade finance, securities, treasury and other institutional workflows.

The history of SWIFT is ultimately the history of financial institutions agreeing to speak the same operational language.

From Telex to ISO 20022

The technology has changed dramatically since the first SWIFT messages were exchanged in 1977.

The original problem remains recognizable.

A bank in Singapore needs to communicate reliably with a bank in London. A trading company in Dubai needs a documentary credit advised to its supplier. A custodian needs settlement instructions. A multinational treasury needs visibility over a cross-border payment.

Every transaction depends on information reaching the right institution in a format its systems and people can understand.

Telex addressed communication.

SWIFT added structure, security and scale.

ISO 20022 is adding richer data to that architecture.

More than fifty years after its creation, the underlying proposition remains remarkably durable.