Chainlink said on September 28 that it was enabling financial institutions to connect their systems and transaction-signing infrastructure to Swift’s blockchain ledger through the Chainlink platform, targeting institutions that use tokenized deposits.
The arrangement keeps transaction-authorizing keys under each institution’s control while Chainlink orchestrates workflows between the institutions’ ledgers and Swift’s ledger. It forms part of Swift’s effort to coordinate cross-border payments: Swift has said deposits remain on participating banks’ own ledgers, with its ledger coordinating the workflow and final settlement continuing through agreed mechanisms such as real-time gross settlement systems.
Chainlink adds self-signing access to Swift’s blockchain ledger
Chainlink said in its September 28 announcement that financial institutions can connect their internal systems and key-signing infrastructure to Swift’s blockchain ledger through Chainlink.
The setup uses the Chainlink Runtime Environment, or CRE, and its self-signing model, according to a Chainlink recap. CRE orchestrates workflows between an institution’s own ledger and Swift’s ledger, while the institution retains control of the keys authorising transactions.
The disclosures present this as workflow connectivity with institutional signing authority preserved—not deposits moving onto a common Chainlink ledger.
Swift’s tokenized-deposit ledger
Swift’s blockchain ledger is built to coordinate 24/7 cross-border payment workflows involving tokenized deposits issued by banks. Those deposits remain recorded on the ledgers of participating banks, Swift said, preserving the underlying location of the deposit even as payment instructions and workflow coordination are handled through the ledger.
The blockchain ledger is intended to coordinate a cross-border payment process across institutions, not to complete final settlement automatically. Swift says that settlement continues through mechanisms agreed by participating parties, such as real-time gross settlement systems; in practical terms, established settlement arrangements still complete the transfer.
Swift set out that model in its July announcement that its ledger was ready for use. The design matters because it frames tokenized deposits as bank-issued liabilities operating within bank-ledger and settlement arrangements, rather than as a separate asset that displaces them. Swift’s description of the ledger also makes clear that its stated purpose is the coordination of payment workflows.
Seventeen banks prepare live pilots
Swift said the blockchain ledger moved from concept to activation in nine months. At the time of its July 9 release, 17 banks across six continents were preparing to pilot live tokenized-deposit transactions.
The pilot group provides the immediate institutional context for Chainlink’s connection. It does not establish that all 17 banks will use Chainlink’s integration, but it indicates the scale of the initial live-tokenized-deposit testing cohort that Swift had identified.
Swift says its broader network connects more than 11,500 financial institutions and corporates across more than 200 markets. That network footprint is considerably wider than the initial pilot group, although the July announcement describes the 17-bank effort as a preparatory pilot stage rather than a network-wide deployment.
Earlier Swift-Chainlink interoperability tests
The ledger connection follows earlier work between Swift and Chainlink on interoperability. In 2023, the organisations used Chainlink’s Cross-Chain Interoperability Protocol, or CCIP, alongside Swift messaging standards to demonstrate how traditional financial systems could interact with public and private blockchains.
Those earlier experiments involved more than a dozen financial institutions and market infrastructures, according to a joint Swift and Chainlink report. They were demonstrations of interoperability, whereas the current announcement concerns connecting institutional systems and signing infrastructure to Swift’s blockchain ledger.
The progression from messaging and interoperability tests to a ledger connection highlights the practical issue the new design seeks to address: how banks can coordinate tokenized-deposit workflows while maintaining control of their own ledgers and transaction-authorising keys.
Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.
