Field note

Tokenized money is a 2025 architecture problem, not a 2030 one

The BIS just blueprinted a tokenized unified ledger and JPMorgan put a deposit token on a public chain - in the same week. The hard part for banks was never the blockchain. It is retrofitting core banking to carry programmable money without a big-bang migration.

Jul 2, 2025 · Navin Agrawal · Architecture · 2 min read

Tokenized money is a 2025 architecture problem, not a 2030 one

Visual brief

Visual brief

Tokenized money is a 2025 architecture problem, not a 2030 one

As of July 2025

Most banks are still planning tokenized-deposit strategy like it is 2019. The reference points moved this year - and the gap is architectural, not conceptual.

Two events landed within days of each other, and together they turned tokenized money from a 2030 slide into a 2025 design constraint for payment architects.

The BIS put it on paper

On 24 June 2025 the Bank for International Settlements released, in its Annual Economic Report 2025, a blueprint for a “tokenized unified ledger” - central bank reserves, tokenized commercial-bank deposits, and securities settling side-by-side on one programmable platform. It is the central-bank establishment describing programmable money as the next-generation system, not a fringe experiment.

JPMorgan put it in production

Days earlier, JPMorgan’s Kinexys unit began piloting a USD deposit token, JPMD, on Coinbase’s Base - an Ethereum public layer-2. After years running only on its private chain, it was the bank’s first step onto a public blockchain. A proof-of-concept, but a real one, on a public network.

The 2025 trigger and the foundations

The two June-2025 events that made tokenized money current, and the three architecture patterns that let a bank absorb it without a big-bang migration.

As of July 2025: the BIS Annual Economic Report (24 June 2025) blueprinted a tokenized unified ledger of reserves, deposits, and securities on one programmable platform, and JPMorgan Kinexys began piloting its JPMD deposit token on Coinbase's Base public layer-2. The architectural foundations that matter: money-model decoupling, a universal connector for ISO 20022 and smart-contract calls, and real-time liquidity engines for 24/7/365 settlement.
The blockchain is the easy part. The architecture underneath it is the work.

The 2025 trigger and the foundations

The 2025 trigger and the foundations

As of July 2025: the BIS Annual Economic Report (24 June 2025) blueprinted a tokenized unified ledger of reserves, deposits, and securities on one programmable platform, and JPMorgan Kinexys began piloting its JPMD deposit token on Coinbase's Base public layer-2. The architectural foundations that matter: money-model decoupling, a universal connector for ISO 20022 and smart-contract calls, and real-time liquidity engines for 24/7/365 settlement.

From modernizing payment platforms, the pattern is consistent: the blockchain technology is rarely the bottleneck. The bottleneck is retrofitting core banking architectures to support programmable money without breaking what already runs. Three design choices keep showing up as the ones that decide whether a bank is ready.

Money-model decoupling

No big bang

Separate what a dollar represents from the ledger that stores it, so a new standard plugs in without another core migration.

Universal connector

One API

Handle ISO 20022 messages and smart-contract calls through the same payment layer, with swappable AML, sanctions, and FX modules.

Real-time liquidity

24/7/365

Tokenized cash settles around the clock; stream intraday positions instead of managing liquidity in batch.

The complexity is not in understanding blockchain. It is in retrofitting core banking to carry programmable money without breaking existing operations.

Was this useful?

Choose once.

Related Posts

View All Posts »
The broker pattern is older than the agentic-commerce headline

The broker pattern is older than the agentic-commerce headline

Stripe Shared Payment Tokens are the agentic-commerce headline, but anyone who ran a card tokenization rollout in 2014 recognizes the shape in five seconds. A scoped surrogate credential with a thin stable interface in front and brokered complexity behind is not new. Visa Token Service shipped it twelve years ago, and the architects who see the pattern early build the right systems instead of rebuilding every eighteen months.

Consumer auth patterns fail the bank exam

Consumer auth patterns fail the bank exam

Authentication that works for web scraping becomes a compliance problem the moment an AI agent moves real money. Enterprise payment systems need certificate identity, scoped service accounts, and short-lived tokens - the things a banking examiner expects to see.

Cross-platform integration: the patterns that actually hold

Cross-platform integration: the patterns that actually hold

Fiserv, Bottomline, and a core banking system each work fine alone. Wiring them into one payment chain is where projects go to die - and the difference between the ones that survive and the ones that become expensive lessons is a handful of boring resilience patterns.