
Chainlink has partnered with Bottomline to offer blockchain-based cross-border settlement to more than 600 banking customers, while allowing institutions to continue using their existing payment messaging systems. The collaboration introduces Chainlink technology into a major slice of global payments infrastructure.
Bottomline Integrates Blockchain Rails for Bank Clients
Bottomline, a provider of services for banks that use the Swift network and other payment platforms, announced the integration as a way to bridge traditional messaging with onchain settlement. According to company materials, Bottomline’s network underpins payment flows totaling roughly $16 trillion annually.
The partnership is designed to let banks initiate and reconcile payments through familiar channels, with final settlement executed on blockchain infrastructure. The approach aims to reduce integration friction by preserving existing workflows and compliance processes, while enabling access to tokenized settlement and other onchain capabilities.
Why It Matters for Cross-Border Payments
- Banks gain optionality to settle cross-border transactions on blockchain networks without overhauling front-end messaging systems.
- The integration targets operational continuity for institutions and their corporate clients, potentially improving settlement speed and transparency.
- By connecting established payment rails to onchain settlement, the collaboration seeks to advance interoperability between traditional finance and digital asset infrastructure.
Context: Chainlink’s Role in Financial Infrastructure
Chainlink is a decentralized oracle network that connects blockchains with real-world data and external systems. The company has worked with major financial institutions and market infrastructures on projects exploring tokenized assets and cross-chain interoperability, including pilots involving Swift’s messaging standards.
Outlook
The move highlights growing interest among payment providers and banks in leveraging blockchain for settlement while maintaining existing operational frameworks. Specific timelines, supported networks, and technical details were not disclosed.