Trusted independent reportCross-border relevantPublication date verified
PYMNTS
Bottomline partners with Chainlink on cross-chain, cross-border payment access
WHAT HAPPENED
PYMNTS reports that Bottomline partnered with Chainlink to connect Bottomline's existing payment software with public and private blockchains. The announced design keeps ISO 20022 messaging in place while Chainlink's CCIP moves tokenized value between chains and its Runtime Environment coordinates workflows. The cited 600-plus banks are Bottomline customers that could receive access, not banks confirmed to have adopted or used the integration.
PUBLISHED September 4, 2026SOURCE PYMNTSLANE Payment infrastructure
KEY FIGURES
600+ (not confirmed adopters)
Bottomline bank customers potentially reachable
More than USD 16 trillion
Annual value moved across Bottomline platforms, as claimed in the announcement
WHAT TO WATCH NEXT
Watch whether follow-up sources disclose named launch markets, supported currencies, live customers, and transaction volume.
Readable PYMNTS report based on a Chainlink announcement and additional secondary reporting. The partnership is announced, but no corresponding Bottomline release or customer adoption was located; the 600-plus banks and USD 16 trillion describe Bottomline's broader customer base and platform activity, not live usage of this integration.
The page already presents the summary and analysis. This section keeps only the copy, download, and technical source record without repeating the same reading view.
View technical text
# Bottomline partners with Chainlink on cross-chain, cross-border payment access
> Evidence tier: B1
> Evidence type: Independent payments-trade report based on Chainlink's partnership announcement
> Source: [PYMNTS](https://www.pymnts.com/blockchain/2026/bottomline-partners-with-chainlink-to-connect-600-banks-to-blockchain-settlement)
> Published: 2026-09-04
> Captured: 2026-09-04T17:52:25.912Z
## Source summary
PYMNTS reports that Bottomline partnered with Chainlink to connect Bottomline's existing payment software with public and private blockchains. The announced design keeps ISO 20022 messaging in place while Chainlink's CCIP moves tokenized value between chains and its Runtime Environment coordinates workflows. The cited 600-plus banks are Bottomline customers that could receive access, not banks confirmed to have adopted or used the integration.
## Why it matters
Connecting an established Swift-service provider to blockchain settlement could let participating banks test onchain cross-border flows without replacing familiar messaging systems. This is an announced integration path, not production adoption: no bank customer, go-live date, transaction, supported asset, corridor, compliance model, payment volume, fee or measured settlement result is disclosed.
## Key numbers
- **Bottomline bank customers potentially reachable:** 600+ (not confirmed adopters)
- **Annual value moved across Bottomline platforms, as claimed in the announcement:** More than USD 16 trillion
## Topics and entities
- Industry lane: Payment infrastructure
- Entities: Bottomline / Chainlink
- Web3 payments
- Cross-border payments
- Payment infrastructure
## Evidence and credibility note
Readable PYMNTS report based on a Chainlink announcement and additional secondary reporting. The partnership is announced, but no corresponding Bottomline release or customer adoption was located; the 600-plus banks and USD 16 trillion describe Bottomline's broader customer base and platform activity, not live usage of this integration.
Date evidence: PYMNTS page is dated September 3, 2026; article metadata records 2026-09-04T01:45:49Z, which is September 3 in U.S. Eastern time
## First-party corroboration
- [https://x.com/chainlink/status/2095497430473007387](/en/items/https://x.com/chainlink/status/2095497430473007387)
## Original-source traceback
[Open the original PYMNTS report](https://www.pymnts.com/blockchain/2026/bottomline-partners-with-chainlink-to-connect-600-banks-to-blockchain-settlement)
---
This is a structured Payments Hot Markdown source summary derived from external reporting. Use the original link above to read the publisher's article; copyright remains with the original publisher.