SWIFT — Tokenized Asset Transfer Experiments

SWIFT: Connecting 11,500+ Institutions to Tokenized Assets

SWIFT processes over 45 million messages daily for 11,500+ financial institutions across 200+ countries — and its tokenized asset transfer experiments aim to extend this network to blockchain-based settlement without requiring institutions to replace their existing infrastructure. SWIFT — the Society for Worldwide Interbank Financial Telecommunication — has completed multiple phases of tokenized asset transfer experiments demonstrating that SWIFT’s existing messaging infrastructure can coordinate cross-border tokenized asset transactions across multiple blockchain networks, potentially eliminating the need for institutions to build bilateral blockchain integrations.

Tokenized Asset Experiments

SWIFT’s tokenization experiments have progressed through multiple phases with increasing scope and sophistication:

Phase 1 (2022-2023): Demonstrated that SWIFT messaging could trigger and confirm tokenized asset transfers on blockchain networks. The proof-of-concept connected SWIFT’s messaging platform with tokenized asset settlement, establishing the technical feasibility of using existing SWIFT message types (MT and ISO 20022) to initiate blockchain transactions.

Phase 2 (2024): Expanded to multi-chain asset transfers, atomic settlement across different blockchains, and integration with Canton Network and Chainlink CCIP for cross-chain interoperability. This phase demonstrated that a single SWIFT message could coordinate settlement across multiple blockchain platforms — enabling a tokenized bond on one chain to settle against payment on another chain through SWIFT orchestration.

Phase 3 (2025-ongoing): Production-grade experiments with selected institutions testing SWIFT-mediated tokenized asset settlement in live environments. This phase moves beyond proof-of-concept to operational validation with real institutional participants and real (or near-production) transactions.

The experiments involved 15+ major financial institutions including BNY Mellon, Citi, DTCC, HSBC, and Euroclear. SWIFT’s approach preserves the existing institutional workflow — banks continue using SWIFT for communication — while adding blockchain-based settlement as a new execution layer beneath the familiar messaging interface.

Strategic Position

SWIFT’s position is unique in the tokenization ecosystem. It does not issue tokens, operate a blockchain, or provide custody. Instead, it provides the messaging coordination that enables existing institutions to participate in tokenized asset markets without replacing their back-office systems. For the 11,500+ SWIFT member institutions — the vast majority of which will never operate blockchain nodes or maintain DLT infrastructure — SWIFT connectivity provides the simplest on-ramp to tokenized asset settlement.

The strategic significance is quantitative: there are approximately 100-200 institutions actively building or operating DLT infrastructure for tokenized assets. There are 11,500+ institutions connected through SWIFT. The gap between these numbers — roughly 11,300 institutions — represents the addressable market for SWIFT-mediated tokenized asset access. These institutions cannot practically build DLT capabilities but need access to tokenized markets as counterparties demand it.

SWIFT’s position also carries systemic importance. As the messaging backbone of the global financial system, SWIFT’s adoption or rejection of tokenized asset messaging effectively determines whether tokenized markets remain isolated (accessible only to institutions with direct DLT connectivity) or connected (accessible to any SWIFT member). The commitment to tokenized asset messaging signals that SWIFT intends to include rather than exclude tokenized markets from the global financial messaging network.

ISO 20022 Integration

SWIFT’s ISO 20022 messaging migration (the industry-wide transition from legacy SWIFT MT messages to structured ISO 20022 XML messages) creates a strategic opportunity to embed tokenized asset data in standard financial messages. The migration — affecting all SWIFT messaging categories — provides a once-in-a-generation opportunity to incorporate digital asset data fields into the global messaging standard.

A SWIFT payment message (pacs.008) could include tokenized asset transfer instructions alongside traditional payment data, enabling dual-rail settlement where the cash leg settles through traditional payment systems and the security leg settles on blockchain. This dual-rail approach eliminates the “big bang” migration risk — institutions can continue processing traditional settlements through existing infrastructure while gradually adding tokenized settlement capabilities.

The ISO 20022 standard’s extensibility enables tokenized asset-specific data elements: blockchain network identifier, token contract address, settlement finality confirmation, and on-chain transaction hash. These data elements can flow through existing SWIFT message processing infrastructure (message queues, validation rules, archiving systems) without requiring institutions to deploy new messaging technology.

For tokenized bond settlement specifically, ISO 20022 securities messages (sese.023 for settlement instructions, sese.024 for settlement confirmations) can incorporate tokenized settlement data alongside traditional CSD-based settlement instructions. This enables a transition period where the same bond can settle through both traditional (Euroclear/Clearstream) and tokenized channels, with SWIFT messages coordinating both settlement paths.

Integration with Institutional Infrastructure

SWIFT’s experiments connect directly with other institutional tokenization infrastructure, creating a coordination layer that links purpose-built DLT platforms:

DTCC integration: SWIFT messages can trigger DTCC’s tokenized collateral management operations. A SWIFT-initiated margin call could automatically trigger the pledge of BUIDL tokens from a participant’s custody account to DTCC as margin collateral — connecting the messaging layer with the settlement layer through existing institutional processes.

BNY Mellon custody: SWIFT instructions can initiate digital asset custody operations at BNY Mellon — deposit instructions, withdrawal requests, position reporting — through the same SWIFT message types used for traditional securities custody. This means institutional clients can manage tokenized assets through the same operational processes used for traditional assets.

Canton Network connectivity: SWIFT experiments have demonstrated connectivity with Canton Network, enabling SWIFT messages to initiate transactions across Canton-connected platforms (GS DAP, Broadridge DLR, BNY Mellon). This positions SWIFT as the external access layer for institutions that are not direct Canton Network participants.

Central bank coordination: For CBDC-settled tokenized bond transactions — such as the EIB bond settled against Banque de France wholesale CBDC — SWIFT messaging coordinates between the security token platform, the CBDC payment platform, and the institutional participants, providing the multi-party orchestration that atomic settlement requires.

Competitive Dynamics

SWIFT’s tokenized asset messaging occupies a different layer from purpose-built interoperability protocols:

SWIFT and Canton Network are complementary rather than competitive. Canton provides the application-level interoperability for institutions with direct DLT deployment. SWIFT provides the messaging layer for institutions that access tokenized markets through existing SWIFT infrastructure. A complete institutional tokenization stack likely includes both — Canton for deep platform integration and SWIFT for broad institutional reach.

Practical Significance

The practical significance of SWIFT’s tokenization work extends beyond technical capability to institutional adoption dynamics. Institutional adoption of blockchain-based settlement does not require institutions to replace SWIFT with blockchain messaging. Instead, SWIFT evolves to include blockchain-based settlement as one of multiple execution methods — preserving the institutional connectivity that has taken decades to build while enabling new settlement capabilities.

For the $130 trillion global bond market and the $100+ trillion global equity markets, SWIFT-mediated tokenized settlement provides the most realistic path to broad institutional adoption. The alternative — requiring 11,500+ institutions to independently deploy DLT infrastructure — is neither economically feasible nor operationally practical for the vast majority of financial institutions.

According to BIS analysis, SWIFT’s tokenized asset messaging represents a critical enabler for institutional tokenization at scale, particularly for cross-border transactions where the current infrastructure involves multiple correspondent banking hops, CSD-to-CSD links, and settlement timing mismatches. The G20 tokenization roadmap has identified cross-border settlement infrastructure — including SWIFT connectivity — as a priority area for international coordination, and SWIFT’s experiments directly address this priority.

Implementation Timeline and Institutional Readiness

SWIFT’s tokenized asset messaging roadmap progresses from experimentation to production availability:

2022-2024 (Completed): Proof-of-concept and expanded experiments demonstrating technical feasibility across multiple blockchain networks and institutional participants. These phases validated that SWIFT messaging can coordinate blockchain-based settlement without architectural changes to SWIFT’s core messaging platform.

2025-2026 (Current): Production pilot with selected institutions processing live or near-live tokenized asset settlements through SWIFT. This phase focuses on operational validation — testing message formats, error handling, reconciliation processes, and regulatory reporting in production environments.

2027-2028 (Planned): General availability of tokenized asset messaging as a standard SWIFT service, accessible to any SWIFT member institution. This phase would enable any of the 11,500+ SWIFT members to participate in tokenized asset settlement through standard SWIFT connectivity, without requiring direct DLT deployment.

The implementation timeline is governed by institutional readiness more than technical capability. The messaging technology works — the experiments proved this. The challenge is ensuring that institutions’ back-office systems, regulatory compliance frameworks, and operational procedures can accommodate tokenized asset message types alongside traditional securities messages. SWIFT’s phased approach provides institutions with time to prepare while establishing the technical foundation for broad deployment.

For cross-border tokenized bond settlement, SWIFT provides the messaging layer connecting issuer platforms (GS DAP, HSBC Orion) with investor custodians across jurisdictions. This messaging function — seemingly mundane but operationally essential — determines whether tokenized bonds can be distributed, traded, and settled across the global institutional network or remain confined to the DLT-enabled subset of institutions.

SWIFT’s connectivity to the total RWA tokenization market ($20 billion in TVL (excluding stablecoins)) positions it as the messaging backbone through which the vast majority of institutional participants will access tokenized capital markets infrastructure, including DTCC settlement ($2.4 quadrillion annually) and Broadridge DLR’s $385 billion average daily tokenized repo operations.

Contact for institutional inquiries: info@capitaltokenization.com