Banks now know that deposits can live on a blockchain. Enough precedents exist for tokenized deposits to work as a valid payment rail. The open question now is which infrastructure a bank should build on for production.
This decision is harder than it looks. A tokenized deposit remains a liability on the bank’s balance sheet. It must keep every existing legal, regulatory, and risk characteristic of a normal deposit. On top of that, it must add new capabilities such as real-time settlement and programmable payments. A pilot can run on almost any ledger. A production system needs a long-term view.
First, a quick definition
A tokenized deposit is a standard commercial bank deposit represented on a blockchain. It is economically and legally identical to an off-chain deposit and holds a 1:1 par exchange rate with fiat currency. It has a direct claim on the issuing bank and sits under standard deposit insurance schemes. Unlike stablecoins, tokenized deposits support fractional-reserve banking and credit creation.
By placing this liability on a blockchain interface, banks make commercial money programmable and mobile, which can settle around the clock without waiting for batch-processed clearing systems that pause on weekends and holidays.
Infrastructure means more than picking a chain
Many executives see this as a blockchain selection problem. It is not. Tokenized deposit infrastructure is a full stack. It covers the network selection, the ledger model, the smart contract and token architecture, the privacy and compliance layer, and the integration layer that connects everything to core banking, custody, and other financial networks.
The core banking platform will remain the system of record and continues to hold deposit liabilities, customer accounts, and other regulatory and compliance responsibilities. The blockchain only becomes a programmable settlement environment on top. Every mint, transfer, and burn on-chain needs a matching entry in the bank’s books. This reconciliation process has to be carefully designed between these two ledgers and often takes longer than the smart contract work itself.
The network decision, and how adoption will happen
The network layer is the most consequential choice. Banks can build private tokenized deposit networks, shared/ consortium networks, use institutional public chains, or adopt hybrid models that combine private execution with public connectivity. Each carries a different balance of control, reach, and cost.
Here is a more useful way for leaders to think about it. The market will not adopt one model. It will adopt in waves, and each wave will favor a different architecture. By “waves,” I don’t mean chronological waves. They are four adoption patterns developing at the same time.
- The first wave has already happened. The five to seven largest global banks have launched their own private tokenized deposit networks. JPMorgan, Citi, and HSBC are the visible examples. These banks had the client volumes, the treasury flows, and the budgets to justify owning the full stack.
- The second wave belongs to the remaining G-SIBs. These institutions face the same client expectations as the first movers. They serve the same multinational corporates. They are the most likely group to launch private tokenized deposit networks next, because their scale supports it and their clients will demand parity.
- The third wave is for large regional banks, which will likely pursue both choices at once. Some will launch private chains for their own corporate treasury settlement. Others will need shared networks to meet wholesale settlement demand from clients. Corporate treasury is the segment with the highest near-term ROI for banks, so the choice depends on how much of that business each bank holds. Regional leaders can also form shared tokenized deposit networks with peer banks. These consortiums are regional and purpose-built. They are different in character from global coordination networks like SWIFT.
- The fourth category is global consortium participation. Most banks will not build. They will join. Existing global bodies built for specific purposes are strong candidates to launch consortium blockchains. Think of settlement networks like SWIFT, clearing platforms like The Clearing House, or depositories like DTCC. These organizations already hold the membership, the trust, and the rulebooks. Launching a consortium chain lets them deliver cost savings, efficiency, and client retention to existing members. This could turn out to be one of the biggest categories.
One bank, multiple networks
There is a second insight leaders should internalize. No serious bank should believe it needs only one chain.
Look at JPMorgan. It runs Kinexys as a private network. It is a founding shareholder of Partior. It is part of the planned Clearing House consortium with its G-SIB peers. And it is integrating with the Canton Network for asset settlement. Four different networks, four different purposes, one bank.
HSBC shows the same pattern on a smaller scale. It is preparing its own corporate tokenized deposit product while also sitting inside the UK Regulated Liability Network pilot alongside five other British banks.
Large banks with significant treasury and wholesale settlement books are the most likely to end up running this kind of portfolio. A private chain handles internal flows and single-client relationships where the bank wants full control. A domestic consortium handles cost-efficient settlement with close peers. A global network handles cross-border reach without building bilateral connections to every counterparty bank. Small and mid-tier banks are more likely to skip the private chain altogether and simply join two or three consortia that together cover most of their client demand.
This is not unusual in banking. Banks already connect with several payment systems, correspondent networks, card schemes and securities infrastructures. Tokenized finance is likely to develop in a similar way.
This changes how the infrastructure decision should be framed inside a bank. The question is not “which chain should we build.” It is “which of these four layers do we need a presence in, and in what order.”
The decisions underneath the network choice
Once the network strategy is clear, four further layers deserve executive attention.
- The blockchain ledger model matters for regulatory fit. Account-based ledgers attach identity to balances and map cleanly to existing banking records and due diligence processes. Token-based or UTXO-style models handle atomic settlement and multi-party workflows better. Many banks will end up using both, starting with account-based issuance and adding token-based settlement where delivery-versus-payment matters.
- Token standards are use-case dependent. There is no universal standard for tokenized deposits. ERC-20 works for simple transfers with added compliance controls. ERC-1400 suits regulated instruments. ERC-3643 helps where identity-linked restrictions are required. Closed consortium networks often justify custom permissioned contracts.
- Privacy is the hardest problem. Banks cannot expose counterparty identities, volumes, or pricing to other network participants. Regulators and auditors still need visibility. A permissioned chain does not automatically deliver a private workflow, because validators can still see transactions, and apart from these network-level access controls, workflow privacy is also necessary. Zero-knowledge proofs, confidential transactions, selective disclosure, or role-based access make this possible, but only if privacy is treated as a stack-wide design goal.
Read More: How Banks Can Enable Selective Privacy and Compliance for Tokenized Deposits?
Integration is the last decision, and it determines time to production. Beyond core banking connectivity, banks need oracles or institutional custody with MPC and HSM controls, policy engines that screen every transaction before settlement, and interoperability layers that will bring universal connectivity with custom networks as required.
If any of these considerations is missing, that infrastructure cannot be called bank-grade infrastructure.
We have covered this section in great detail in a separate article. Read it here.
How to choose the right blockchain infrastructure for tokenized deposits?
The questions worth asking now and how Zeeve helps
Financial leaders evaluating this space should press their teams and vendors on a short list. The more useful questions are which networks their largest clients are already asking to use, which consortiums their closest peers are joining, whether there are any 3rd party tool/services it is using that could lead to vendor lock-in, and whether your blockchain infrastructure partner has multi-stack expertise that can handle migration if at any point it becomes necessary.
The technology has been proven. The competitive question now is who builds infrastructure that can grow with the market. Working with an experienced enterprise deployment partner can compress that learning curve considerably, but the strategic choices described here belong to the bank’s leadership.
If your institution is weighing tokenized deposit infrastructures, Zeeve can help. We have worked with a big US bank in their tokenization initiative. Connect with Zeeve to discuss your roadmap.
