- HSBC and Standard Chartered have completed the first live cross-border transaction on Swift’s new blockchain-based ledger.
- What moved was a deposit: a claim on money already sitting in a bank account, recorded on a shared ledger.
- The ledger is permissioned and bank-only. No public is involved, and nothing here is buyable.
Two of Britain’s biggest banks have just sent money to each other across a border using a blockchain. That sounds like the thing crypto has been promising for fifteen years. It isn’t, quite, and the difference is the whole story.
Almost every time a big bank touches blockchain technology, the story reaches ordinary readers as evidence that crypto is being adopted, and often as a reason a particular coin should go up. This one has no coin attached to it at all. Knowing which bank blockchain stories connect to the market you can actually buy into, and which are closed systems you’ll never touch, saves you from acting on the wrong ones.
The second reason it matters: both banks are UK-headquartered, and if this works, it eventually becomes the plumbing your own international transfers run through.
What actually happened
HSBC and Standard Chartered exchanged payment messages over Swift’s blockchain-based ledger and recorded the settlement on it. Swift describes this as the move from the system being ready for initial use to it having handled a genuine interbank transaction. One transaction, two banks, live money.
Lewis Sun, HSBC’s head of digital currencies, called it “a landmark moment for the promise of tokenised deposits”. Mark Willis, who runs emerging payments at Standard Chartered, said it was “an important step towards more seamless, always-on financial services”. Both lines come from the banks’ joint announcement, so read them as the framing the banks want rather than an account of what was built.
Swift has been working towards this for a while. It said in July that the ledger was ready for initial use, with seventeen banks across six continents lined up to try live transactions on it. This is the first of those to actually happen.
Swift, for anyone who has only ever seen the name on a bank transfer form, is the messaging network that international payments run on. It doesn’t move money itself. It carries the instructions between banks, and the actual funds shuffle between accounts the banks hold with each other. That’s why a transfer to another country can take days: it’s a chain of messages and reconciliations, and everyone involved is keeping their own separate record.
A tokenised deposit is not a stablecoin
The phrase turns up in every version of this story, usually unexplained.
A tokenised deposit is money you already have in a bank account, represented as an entry on a shared ledger so it can be moved and settled there. The deposit itself does not change. It remains a claim on that bank, covered by the same protections it had this morning. What changes is the record-keeping.
That makes it different from a , which is a token issued by a company that says it holds matching reserves somewhere, and different again from a cryptocurrency like bitcoin or ether, which isn’t a claim on anybody. Tokenised deposits are the most conservative version of the idea. The bank stays the bank.
The awkward part: Swift is the one building it
The original pitch for public blockchains, going back to bitcoin’s launch, was that you could move value between countries without the correspondent banking network, without Swift, without waiting for anyone’s business hours.
What’s been built instead is Swift running the ledger. The banks keep their customers and their compliance checks, and they decide who is allowed to connect. The blockchain part is a shared database that removes some of the reconciliation work between institutions that already trust each other.
That isn’t a criticism of the engineering. Shaving days off cross-border settlement is a genuinely useful thing to do, and if it works at scale it will show up as faster and cheaper international transfers for ordinary customers. But it’s the opposite of disintermediation. The intermediary built the rails.
Why there’s no read-across to any coin you can buy
The ledger is permissioned, meaning access is restricted to approved participants. In this case, banks. You can’t hold a wallet on it, you can’t buy a token that represents it, and no public cryptocurrency is used to pay fees or secure it.
So when you see this story framed as institutional adoption, be precise about what’s being adopted. Banks are adopting a database structure. They are not buying XRP, or XLM, or anything else that has historically been marketed on the promise of replacing Swift, and the existence of a bank-run alternative arguably makes that promise harder rather than easier to keep.
Bank blockchain pilots are announced regularly. They are almost always permissioned, and the price moves that sometimes follow them are usually built on a misreading.
What to watch
Three things would turn this from a pilot into infrastructure. Whether more banks join: two participants is a demonstration, twenty is a network. Whether the volume becomes routine rather than announced, because the point at which nobody publishes a press release about a transaction is the point at which it’s real. And whether it runs outside banking hours, since 24/7 settlement is the actual prize here and the reason the whole exercise exists.
For UK readers there’s a narrower thing to watch: whether either bank extends any of this to retail customers, or whether it stays wholesale plumbing between institutions. On current form, expect the latter for a long while. If you want the practical picture of how UK banks handle crypto-related payments today, that’s a separate and much more immediate problem, and we’ve covered it in our guide to UK banks and crypto.