Insight

Stablecoins Are Multiplying. So Are the Records.

Sibos 2026 settled that money will move across more coins, ledgers and rails. The harder question comes next: when those systems hold different records of the same payment, who makes them agree?
Cordant
Written by
Cordant
Sibos 2026 spent the week talking about how money will move across more coins, ledgers and payment rails. The harder operating question comes one step later: when those systems hold different records of the same payment, who makes them agree?

Sibos made one thing clear: digital money is not converging onto a single rail. Deutsche Bank's Ciarán Byrne warned of "a series of digital islands rather than a connected ecosystem." BNP Paribas's Wayne Hughes said the industry is "unlikely to converge on a single blockchain." The ECB's Holger Neuhaus described fragmentation across models and infrastructures as a limit on interoperability and scale. And on Tuesday, a day after Wells Fargo joined Project Agorá, its CFO Mike Santomassimo put it in four words: "Single bank solutions don't work."

The count is going up regardless. Swift now has 17 banks participating in its blockchain-based ledger for tokenised deposits, and Oracle, IBM, Cosmos and Chainlink each announced a route into it during Sibos week. Twenty-one financial institutions have committed to a separate venture targeting a dollar stablecoin in 2027, with the euro next, and a ten-bank euro consortium is seeking approval on its own. At a Sibos breakfast on Tuesday, Kraken's Mark Greenberg said fragmentation will be permanent, with hundreds of stablecoins, and that "we only work in USDC will not hold." He added that Kraken signs a new payment service provider almost every week.

The industry is responding with interoperability: shared ledgers, common standards and infrastructure designed to move value between different forms of money. That is necessary. It also solves only half the problem. A connector can tell one network how to interact with another. It does not tell an operator why the blockchain, internal ledger, treasury system and counterparty statement now show different things. Interoperability moves the money. Reconciliation establishes what happened.

Every new rail creates another version of the payment

Take a stablecoin payment received by a payment provider. The blockchain records the transfer when it is confirmed. The provider's internal ledger records it when its systems ingest and post the transaction. The treasury system reflects the position differently again. If the stablecoin is redeemed into fiat, the bank records that movement on another rail and on another clock.

None of those records has to be wrong. They are recording different stages of the same economic flow. But the customer asks one question: what happened to my money? Someone inside the operation has to connect those records into one answer.

Tokenised deposits make the problem even easier to see. Swift's new ledger enables participating banks to move tokenised deposits 24/7 while final settlement can still happen through existing payment systems. Swift describes the ledger as an orchestration layer that operates before final settlement through existing infrastructure. That means a payment can have one state on the shared ledger and another in the systems responsible for final settlement.

Again, neither record is necessarily wrong. The problem is knowing which state the payment is in, what was supposed to happen next, whether it happened, and who owns the exception if it did not. That is an operations problem, not an interoperability problem.

The fragmentation moves inside the institution

When a new rail goes live, it does not replace the systems already recording money. It gets added to them. The chain gets added to the processor. The shared ledger gets added to the core. The stablecoin issuer gets added to treasury. A new counterparty gets added to the contracts, statements and settlement processes already in place. So a new rail does not create one new record. It creates a new set of relationships between records that now have to be understood, and those systems were not built to explain one another.

The blockchain can prove that a transfer happened on-chain. It cannot tell you whether the provider posted it correctly. The internal ledger can show what was booked. It cannot tell you whether the issuer met the redemption terms in your agreement. The bank statement can show that dollars arrived. It cannot tell you whether they arrived when the network rules said they should. Every system knows its part. Operations has to know the whole payment.

The missing layer is not another rail

This is why the next infrastructure problem is different from the one getting most of the attention. The industry is building ways for value to cross networks. What institutions also need is a way to understand what happened across those networks.

Before the next stablecoin or tokenised deposit rail goes live, take a single payment and write down every place that will record some part of it: the chain or shared ledger, the processor, the internal ledger, the core, treasury, the bank account and the counterparty. Then ask four questions. What does each system believe happened? When should each record appear? What agreement or rule determines what should happen? And who knows when the difference between two records is a legitimate timing difference versus an exception?

Today, the answer to that last question is usually a person. They know that one status means initiated while another means settled. They know the issuer has until the next business day to redeem. They know which bank statement should match which ledger entry and which exception matters enough to investigate. That knowledge is what keeps a fragmented payment operation coherent, and every new rail gives that person more relationships to hold in their head.

Where Cordant sits

Cordant is the command center for modern financial infrastructure. It sits above the systems an institution already runs and connects two things that normally live apart: what actually happened and what was supposed to happen.

For a stablecoin or tokenised deposit payment, Cordant follows the event across the chain, ledger, processor, bank and counterparty rather than treating each record as an unrelated transaction. It also understands the agreements, policies and network rules governing that payment: when settlement was due, what fee should have been charged, what finality means and what should happen when something goes wrong. When actual behavior diverges from expected behavior, the exception arrives with the evidence and cause attached, handed to a person, queue or agent who can act on it.

Cordant does not move the money. It does not hold the keys. And it does not replace any of the systems underneath it. The chain stays the chain. The ledger stays the ledger. The bank stays the bank. Cordant makes the operation across them understandable, and that becomes more important, not less, as digital money fragments.

Sibos showed an industry getting much better at connecting the islands. Now somebody has to make their records agree. Money already moves in real time. The decisions should too.

‍

‍

‍

‍

‍

Sources -
‍

‍

‍

‍

Continue reading
September 28, 2026
Insight
AI agents can only follow the operating rules an institution has written down
The consistency an AI agent needs before it can run financial operations does not come from the model. It comes from knowing, explicitly, what the operation expects to happen, and in most institutions that knowledge is spread across contracts, policies, systems and the people who reconcile the gaps between them.
Read article
A man works with a laptop and notebook.
September 22, 2026
Insight
Put The Command Center in Place Before the AI Operating System
Before an institution gives agents authority over financial operations, it needs a command center that can tell them what actually happened, what should have happened and which record is right when the systems disagree.
Read article
A man considers his work beside a laptop in an office.
September 21, 2026
Insight
Money Moves in Seconds. Finding Out What Happened to It Still Takes Days
Payments now settle in a quarter of the time they took five years ago, yet finding out what went wrong with one still takes as long as it always did, and this year's research shows why.
Read article