technologybriefs
8:46in productionCh. 1 · Syntax, not infrastructure/ 8:46 · ceiling 15 min
Systems · Tech history

SWIFT

1973

SWIFT standardised syntax—not money, not speed, not trust.

SWIFT standardised the grammar of financial messages. It enabled parsing across heterogeneous systems—but only at the syntactic level. It did not replace telex or create a global payments network. Its success lies in what it refused to be.

SystemsTech historyBankingInfrastructureInformationBanking across the network →
Chapters & takeaways4
  1. 0:49
    Syntax, not infrastructure

    SWIFT is a syntax standard, not a network or payment rail.

  2. 2:09
    Transport-agnostic parsing

    Interoperability works even when messages bypass SWIFT’s own network.

  3. 3:30
    Cooperative standard-setting

    Standardisation emerged through collaboration, not unilateral mandate.

  4. 5:02
    URNs, not URLs

    RFC 3615 formalises SWIFT FIN as a namespace—not a protocol.

Worth your time?

Yes. Study the whole thing.

4.5/ 5
What works
  • decouples syntax from transport
  • enables cross-vendor message parsing
  • anchors ISO financial messaging standards
  • supports URN-based identification (RFC 3615)
What does not
  • guarantee message delivery
  • enforce semantic correctness
  • operate as a real-time network
  • define settlement rules
Study it if
  • financial software architects
  • standards compliance officers
  • interoperability engineers
Skip it if
  • payment operations teams
  • cybersecurity analysts
  • central bank policy designers
The written brief1 min read

What it is and the problem it solves

SWIFT is a syntax standard for financial messages. It solves the problem of incompatible message formats across banks and processing systems.

How it works

SWIFT operates via a centralized store-and-forward mechanism. It defines and maintains syntax standards for financial messages. It functions as a registration authority for key ISO financial messaging standards. It collaborates with international organizations to define message format and content standards.

What works

Messages formatted to SWIFT standards are processable by many well-known financial processing systems, regardless of transmission network. It became the industry standard for syntax in financial messages.

What does not

SWIFT does not transmit messages by default. Messages formatted to SWIFT standards need not travel over the SWIFT network to be processed. It does not govern semantics, execution logic, or real-time behaviour—only syntax.

What it changes

It decouples message syntax from transport medium. Financial systems no longer need bespoke parsers for every counterparty. Interoperability becomes a function of conformance, not bilateral integration.

Is it worth your time

Yes—if your work depends on cross-system interoperability of financial message syntax, not transmission infrastructure. SWIFT does not move money or guarantee settlement. Its value is in standardisation, not speed, security, or network control.

Same field · Systems4 of 157
10:36
SES (company)1985SES is a satellite infrastructure company built on orbital economics—not bandwidth alone. Its innovations are logistical: co-location, digital transmission, and now multi-orbit consolidation. Its value lies in guaranteed beam placement, not raw speed.
9:44
Apache CassandraFacebook · 2008Cassandra is a distributed, wide-column database built for write-heavy, multi-datacentre workloads. It prioritises availability and scalability over consistency. It requires upfront schema design aligned to access patterns. It was developed at Facebook for inbox search and released open-source in July 2008.
10:00
Apache HadoopYahoo · 2006Hadoop is not a database or a query engine. It is a fault-tolerant batch-processing substrate built for scale, not speed or simplicity.
10:55
International Bank Account NumberInternational Organization for StandardizationIBAN is a validation layer—not a payment rail, not a registry, not a protocol. It catches human input errors in account identifiers before they trigger costly rejections downstream. Its mechanism is simple: a fixed-position country code, two check digits, and a national account identifier, all validated via MOD-97-10. It works where people type numbers. It fails where logic, intent, or authority is required.
Up next in Technology

System on a chip

· 9:18

SoCs shrink computers—but lock in obsolescence the moment they’re fabricated.

Play nextBack to Systems
9:18