The Pre-SWIFT Moment

Stablecoins can transfer value across public networks in seconds. The wallet address is visible, but the legal identity, regulatory status, and acceptance policy of the counterparty often are not. For a regulated institution, those are different questions.

The Travel Rule illustrates the gap. FATF reported in June 2025 that 99 jurisdictions had passed or were in the process of passing Travel Rule legislation. FATF’s Recommendation 16 requires consistent originator and beneficiary information in payment messages, yet implementation remains uneven across jurisdictions and providers.

So the paradox is not that blockchains are anonymous in every sense. It is that a technically observable transaction can still arrive without the standardized institutional context required to process it safely. Speed solved the movement of tokens. It did not solve the coordination of institutions.

The useful comparison is not a neat sequence of 1975, 1995, and 2025. The real dates are more instructive.

1973: 239 banks from 15 countries formed Swift because bilateral Telex relationships could not scale. 1977: Swift went live with 518 institutions in 22 countries. It did not move the underlying money; it standardized trusted messaging and coordination.

1982: RFC 821 formalized the Simple Mail Transfer Protocol. SMTP did not create every email service, but it defined a common way for independent systems to relay messages across networks.

Today: stablecoin markets have many issuers, chains, custody stacks, Travel Rule providers, exchanges, banks, and payment firms. Each component can work on its own. The missing layer is a common institutional protocol that lets them work together without forcing every participant into the same chain, issuer, or vendor.

Five blockers repeatedly appear when a regulated institution tries to turn a stablecoin transfer into a dependable cross-border payment. They are coupled: solving one in isolation does not produce an operational corridor.

Gravity. Every incumbent optimizes the part of the stack it owns. Issuers want their stablecoin to be the default. Foundations want activity on their chain. Custody and orchestration platforms deepen their own integrations. Banks protect existing client relationships and control frameworks.

That behavior is rational, but it does not automatically create a neutral network. Tether and Circle have little incentive to collapse their products into one shared operating standard. Chains compete for settlement activity. VASPs satisfy licensing requirements inside their immediate commercial perimeter. The result is a set of capable components with no universal institutional handshake.

For four years I built a VASP in Europe. Each new remittance corridor meant finding another partner, negotiating another operating model, integrating another API, and tuning another exception process. The roadmap filled with plumbing rather than product innovation.

That is the operational meaning of “pre-SWIFT.” Before a shared network, every institution builds bilateral relationships. The cost grows roughly with the number of counterparties, and every new corridor adds a different combination of legal, technical, treasury, and compliance work.

Swift’s 2026 ledger makes the analogy more—not less—relevant. Swift says the ledger coordinates bank payment commitments, supports tokenized deposits, and uses existing settlement infrastructures. In July 2026, it announced that 17 banks were preparing initial use. This is a serious institutional network, not a straw man.

But its initial boundary is also clear: participating banks, bank-issued tokenized deposits, and settlement controlled through existing systems. Stablecoin corridors need an adjacent coordination layer for non-bank payment institutions, VASPs, multiple public chains, multiple issuers, local payout partners, and Travel Rule exchange. The opportunity is not to “replace Swift” with a faster database. It is to build the interoperability layer for the part of digital money that Swift’s first ledger does not cover.

A useful network cannot be “chain-agnostic” by pretending chains are identical. It has to preserve their differences while giving institutions one operating contract. The same applies to issuers, fiat rails, and compliance rules.

The most important control is a pre-flight check. Before money moves, the recipient should be able to express the geographies, institutions, customer types, compliance levels, assets, limits, and evidence it accepts. The network resolves those policies against the proposed payment and returns a green light, a red light, or a request for additional information.

That changes compliance from a post-transaction investigation into a routing input. It also makes interoperability practical: participants do not need identical risk appetites; they need a standard way to describe and evaluate them.

The pre-SWIFT moment is not a promise that one startup will replace a global bank network. It is a diagnosis: stablecoin infrastructure has reached the stage where bilateral integrations become the constraint.

The durable opportunity is a shared institutional layer—one that lets different regulated firms discover one another, exchange the right data, match policies, select a viable route, and prove settlement without surrendering control of their assets or risk decisions.

That is how global money movement becomes more like messaging: not because every participant uses the same provider, but because independent systems agree on how to communicate.

For the compliance mechanics behind this coordination model, continue with the Travel Rule explainer.