BNP Paribas and HSBC completed a live Siemens treasury payment from a BNP Paribas euro account in France to an HSBC sterling account in the UK using tokenized deposits on Swift’s shared ledger. Swift’s ledger is designed to validate and synchronize interbank payment commitments, with an initial focus on 24/7 cross b...
Published byEdited with GPT-5.6 TerraImages generated with GPT Image 2
Research answer

Create a landscape editorial hero image for this Studio Global article: How did BNP Paribas and HSBC complete the first live corporate treasury payment on Swift’s blockchain-based shared ledger for Siemens—transf. Article summary: BNP Paribas debited Siemens’ euro deposit in France and HSBC credited Siemens’ sterling deposit in the UK, with the banks using tokenised deposits recorded and synchronised through Swift’s shared blockchain ledger rather. Topic tags: general, general web. Style: premium digital editorial illustration, source-backed research mood, clean composition, high detail, modern web publication hero. Use reference image context only for broad subject, composition, and topical grounding; do not copy the exact image. Avoid: logos, brand marks, copyrighted characters, real person likenesses, fake screenshots, UI text, readable text, watermarks, charts with fake numbers, clic
BNP Paribas and HSBC have completed a live corporate treasury payment for Siemens using Swift’s blockchain-based shared ledger. The transaction moved funds from Siemens’ euro account at BNP Paribas in France to its sterling account at HSBC in the UK, using tokenized deposits to support the cross-bank, cross-currency transfer. 1
4
The milestone matters less as a claim that blockchain has replaced cross-border banking and more as evidence that regulated banks can test tokenized commercial-bank money on shared infrastructure for a real corporate treasury flow.
The two banks executed a payment for Siemens from a euro-denominated account held with BNP Paribas in France to a sterling-denominated account held with HSBC in the UK. Reports describe it as the first live corporate treasury payment on Swift’s ledger and as a test of whether tokenized deposits could work across bank systems while preserving commercial-bank money used by corporate customers. 1
2
4
That distinction is important. A tokenized deposit is intended to represent a bank deposit within the regulated banking system. The initiative is therefore different from asking a corporate to move treasury cash into a privately issued cryptoasset or to abandon its existing bank relationships. 2
6
Swift describes the ledger as a shared orchestration layer for interbank payments. It records, sequences, validates and synchronizes payment commitments involving tokenized deposits, including checks that funds are available before execution. 6
9
In practical terms, the goal is a common, synchronized transaction state among participating institutions instead of a process that depends solely on passing messages between separate records. The banks continue to perform their regulated roles; the ledger is infrastructure intended to coordinate the transfer and its status. 6
13
Swift says the first use case is 24/7, real-time cross-border payments. Its initial live pilot involved 17 banks across six continents, including BNP Paribas and HSBC. 9
13
A transfer between accounts at two banks in two countries is more demanding than an internal transfer within one bank. The Siemens transaction also involved two currencies: euros at the sending bank and sterling at the receiving bank. 1
4
That makes it a useful demonstration of interoperability—the ability for tokenized deposits issued and managed by different regulated institutions to be used in a coordinated cross-border payment process. Earlier in August 2026, Standard Chartered and HSBC announced a live cross-border tokenized-deposit transaction on the same Swift ledger, focused on bank-to-bank interoperability. 8
The Siemens use case adds a corporate treasury application: moving liquidity between a multinational’s own bank accounts.
For a multinational company, knowing the precise state of a cross-border transfer matters as much as initiating it. A synchronized ledger could give participating banks and their corporate clients faster confirmation of whether a payment has been validated, executed and settled.
That may reduce the operational burden of matching payment messages, bank records and internal treasury systems. It could also improve cash visibility and liquidity management when funds move between entities, regions or currency accounts. These are expected operational benefits, not independently proven outcomes from a single transaction. 3
6
Swift’s stated objective is also to support payment availability around the clock, rather than limiting processing to traditional cut-off windows. 9
13
A shared and validated transaction record can reduce uncertainty between a payment instruction and confirmed settlement. In principle, that can shorten the period in which a party is waiting to know whether funds are available or a corresponding transfer has completed.
However, faster technical coordination does not remove the core requirements of cross-border finance. The actual risk and speed of a transaction still depend on FX execution, liquidity, legal settlement finality, sanctions and anti-money-laundering controls, local regulation, and operational resilience. The Siemens transaction is a live proof point, not a guarantee of instant or risk-free settlement at scale.
Swift announced plans to add a blockchain-based shared ledger to its infrastructure at Sibos in Frankfurt on September 29, 2025. 24
25 It completed the ledger’s design phase on March 30, 2026 and moved into minimum-viable-product implementation.
16
On July 9, 2026, Swift said the ledger was ready for initial use, with 17 banks preparing to pilot live transactions using tokenized deposits. 13 The Siemens payment, reported on September 4, shows the initiative being applied to a live corporate treasury transfer after that initial activation.
1
4
The central proposition is not that a new form of money must displace bank deposits. It is that existing regulated deposits may be represented as tokens and made interoperable through common infrastructure. Swift is working with more than 40 financial institutions on the initiative, with cross-border payments as the first use case. 9
That approach could make tokenization more relevant to mainstream corporate finance because it works through the institutions that already manage corporate deposits, compliance and international payments. But broad adoption remains contingent on participation by banks and corporates, shared standards, workable economics, legal certainty and reliable liquidity across currencies.
The Siemens transfer is therefore best viewed as an early, concrete validation of the model: regulated banks have used Swift’s shared ledger for a live corporate, cross-currency payment. The larger question—whether the model can scale into a widely used 24/7 cross-border settlement network—remains open.
Studio Global AI
This page includes a source-backed answer you can continue inside Studio Global.
BNP Paribas and HSBC completed a live Siemens treasury payment from a BNP Paribas euro account in France to an HSBC sterling account in the UK using tokenized deposits on Swift’s shared ledger.
BNP Paribas and HSBC completed a live Siemens treasury payment from a BNP Paribas euro account in France to an HSBC sterling account in the UK using tokenized deposits on Swift’s shared ledger. Swift’s ledger is designed to validate and synchronize interbank payment commitments, with an initial focus on 24/7 cross border payments using tokenized deposits.
For corporate treasurers, the potential value is a more synchronized view of payment status and liquidity, though legal finality, FX, compliance, liquidity and adoption still determine the real world outcome.