Chainlink unveils bridge for bank access to Swift blockchain ledger

The new framework centers on a self-signing model designed to address institutional security concerns. By deploying the Chainlink Runtime Environment (CRE), banks can coordinate data flow to and from Swift’s ledger while keeping their existing approval procedures and security controls intact. Chainlink acts as an orchestration layer, ensuring that banks maintain control over their transaction-signing keys throughout the process.

Swift’s blockchain ledger is designed to facilitate 24/7 cross-border payments using tokenized commercial-bank deposits. Under this system, deposits remain on the issuing bank’s own ledger, while Swift coordinates payment commitments between institutions before final settlement occurs through traditional mechanisms. Seventeen global banks, including Citi, HSBC, and UBS, are currently preparing live pilots to test these tokenized payment workflows across six continents.

Sergey Nazarov, CEO of Chainlink Labs, noted that the technology supports banks seeking to integrate tokenized assets into their operational models. While Swift operates the ledger—which utilizes an Ethereum Virtual Machine-compatible architecture based on Hyperledger Besu—it does not replace the organization's role as a global financial messaging network. Instead, the ledger provides a synchronized environment for payment orchestration, allowing for round-the-clock transaction movement that eventually clears through established settlement systems.