Tokenized deposits have passed the proof-of-concept phase. Banks now know they can put deposits on a blockchain. We now have enough precedents for [tokenized deposits](https://www.zeeve.io/use-cases/tokenized-deposits-digital-cash/) to be used as a valid payment rail globally. But the critical challenge is selecting the production infrastructure.
The decision is not easy because tokenized deposits will still be the banks’ balance-sheet liabilities and must retain all existing legal, regulatory, and risk characteristics. Plus, add new capabilities like real-time settlement and programmable automation.
A pilot can be launched on almost any ledger. But a production-grade system requires a long-term view. A dedicated enterprise deployment partner, like [Zeeve](https://www.zeeve.io/), can deliver [banking-grade blockchains](https://www.zeeve.io/industry/banks-capital-markets/), absolute data privacy, and global interoperability without leaving banks’ legacy systems.
This article helps banks make that decision more easily. It will answer all their queries, break down infrastructure decisions into 5 layers, and give architecture diagrams for tokenized deposit programs undertaken by banks.
# What are tokenized deposits?
A tokenized deposit is our standard, commercial bank deposit represented on a bank’s blockchain. Economically and legally, it is identical to off-chain deposits and maintains a 1:1 par exchange rate with fiat currency.
Source: [Federal Register](https://www.federalregister.gov/d/2026-06974/p-366)
Hence, they are a direct claim on the balance sheet of the issuing commercial bank and fall under standard deposit insurance schemes such as the FDIC in the United States. Unlike [stablecoins](https://www.zeeve.io/use-cases/stablecoins-cbdc-style-digital-money/), they support the bank’s fractional-reserve policy and credit creation.
The benefit is that by wrapping these liabilities in a [blockchain](https://www.zeeve.io/managed-custom-blockchain/) interface, banks can make commercial money programmable and highly mobile. It becomes capable of settling peer-to-peer 24/7/365 (atomic settlement) without relying on centralized, batch-processed clearinghouses like the Federal Reserve’s ACH, which pauses on weekends and holidays.
# For a deeper dive into who it benefits, the use cases where tokenized deposits bring more value, and the regulatory readiness worldwide, visit our detailed article:
[Why Banks Need to Tokenize Deposits? Who Benefits?](https://www.zeeve.io/blog/why-banks-need-to-tokenize-deposits-who-benefits/)
# What does a tokenized deposit infrastructure actually mean?
In a traditional bank, our balance sits inside a private SQL database or mainframe system called a Core [Banking Platform](https://www.zeeve.io/industry/banks-capital-markets/). This system cannot naturally read, see, or interact with a blockchain. The [tokenized deposit infrastructure](https://www.zeeve.io/use-cases/tokenized-deposits-digital-cash/) is the multi-layered technology stack built to bridge this specific gap, along with addressing the key concerns that arise because of blockchain introduction. For example, privacy & compliance, custody, [interoperability](https://www.zeeve.io/blog/superchain-erc20-simplifying-asset-interoperability-in-layer2-rollups), etc.
Tokenized deposit infrastructure refers to the blockchain, middleware, [compliance](https://www.zeeve.io/blog/could-digital-product-passport-for-textiles-be-the-biggest-compliance-trend-this-year), privacy, integration, and operations stack required to issue, manage, and govern tokenized commercial [bank](https://www.zeeve.io/blog/why-the-stablecoin-vs-tokenized-deposits-war-is-a-costly-distraction-for-banks/) deposits.
So if a bank asks what are the main infrastructure requirements for a tokenized deposit program, the answer is not limited to token issuance, custody, or settlement alone. It includes the network architecture, [smart contract](https://www.zeeve.io/blog/a-comprehensive-guide-for-smart-contract-and-sovereign-rollups/) logic, participant controls, privacy mechanisms, compliance workflows, interoperability rails, integration with core banking systems, and the operational [layer](https://www.zeeve.io/blog/what-are-layer-2-rollup-networks-everything-you-need-to-know/) required to run the system reliably.
# We can divide the entire tokenized deposit infrastructure into 2 primary building blocks and 5 subcategories
# Architectural Archetype:
1. Network Infrastructure (Private Chains/permissioned, Public chains, Hybrid Networks
2. Ledger Model / Data Structure
3. Smart Contract & Token Architecture
# Other Infrastructure Decisions:
1. Privacy & Compliance: Selective Disclosure, ZK
2. [Integration](https://www.zeeve.io/integrations/) Layer: with legacy core banking system through APIs + other enterprise connectivity (like Oracle, Digital asset custody stack like MPC, HSM, Account Abstraction, etc.), and interoperability with other banks and financial networks using [Hyperlane-like integrations](https://www.zeeve.io/hyperlane-integration/).
Now lets look into each of them one by one.
# Network infrastructure:
Network infrastructure is the most important decision. Banks can use private or permissioned chains, public chains with institutional controls, or other hybrid models that combine public verifiability with private execution.
Each model has a different tradeoff between control, interoperability, cost, and ecosystem access.
1. Complete Public chains
Public networks offer open infrastructure, broad developer ecosystems, liquidity, and composability. They are attractive when the bank wants to support multi-party [settlement](https://www.zeeve.io/blog/fizit-testnet-goes-live-real-time-b2b-settlements-built-for-the-industrial-world), tokenized securities, institutional [DeFi](https://www.zeeve.io/blog/how-appchains-fits-on-depins-vision-of-redefining-physical-infrastructure), or open network connectivity.
The challenge here is control. Tokenized deposits cannot behave like permissionless bearer assets by default. Banks need allowlists, identity checks, sanctions screening, transaction limits, and issuer controls.
MAS Project Guardian showed that even when deposit tokens are used on a public blockchain, banks can restrict interactions to known addresses and require verifiable credentials.
Source: Onyx by J.P. Morgan Analysis
So, Public chains can work when controls are built at the token, application, wallet, and RPC layers. They are best suited when interoperability and [ecosystem ](https://www.zeeve.io/blog/key-defi-ecosystem-pitfalls-solutions/)reach matter more than full infrastructure ownership. But banks must plan for transaction fee volatility, public metadata exposure, chain governance risk, and finality assumptions.
A public-chain strategy should never start with the chain alone. It should start with the permissioning model.
1. Private and permissioned chains
Private and permissioned chains give banks more control over participants, validators, access rules, and [data](https://www.zeeve.io/blog/blockchain-data-indexing-navigating-its-working-and-challenges/) visibility. These networks are easier to align with internal risk, audit, and [compliance](https://www.zeeve.io/blog/a-guide-to-blockchain-security-and-compliance) requirements. They also give more predictable performance and cost.
This model works well for internal treasury settlement, closed-loop corporate payments, interbank consortium networks, and wholesale settlement among known institutions. Single-bank ledgers can support intra-bank transfers, and shared ledgers allow multiple institutions to interact on common rules and assets.
The tradeoff is network reach. A private network may solve the bank’s internal settlement problem. It may not solve cross-bank interoperability unless other banks join or external bridges are built.
Private infrastructure is the safest starting point for many banks. It is not always the best end state. The end state depends on how much external settlement the bank expects.
1. Hybrid networks / Custom-built public-permissioned chains
Hybrid networks try to combine institutional control with broader connectivity.
So a hybrid chain could be
* Public chains with permissioned applications,
* Private execution with public anchoring,
* Privacy nodes connected to public liquidity, or
* Institutional networks with selective disclosure.
J.P. Morgan’s JPMD/JPM Coin rollout on Base is a useful example. The asset runs on a public Ethereum [Layer 2](https://www.zeeve.io/blog/what-are-layer-2-rollup-networks-everything-you-need-to-know/), but is available to institutional clients and designed for regulated, permissioned use.
Source: JP Morgan
Let’s take an example of privacy-first public chains like Midnight or Hyli, which combine public-chain verifiability with confidentiality. They use [zero-knowledge](https://www.zeeve.io/zk-infrastructure/) proofs, selective disclosure, or proof-based settlement to let institutions prove validity without revealing underlying data like balances, counterparties, business logic, or transaction metadata.
Most of the examples in the market point in this direction.
Another example could be public chains with private institutional nodes like the Canton network or Rayls. These architectures give institutions private execution, private ledgers, or controlled nodes, but also connect them to a broader shared settlement or [interoperability layer](https://www.zeeve.io/blog/superchain-erc20-simplifying-asset-interoperability-in-layer2-rollups/).
For tokenized deposits, hybrid infrastructure is useful when banks need privacy, auditability, and institutional governance, but also want future connectivity to public ecosystems. This can be a strong fit for interbank settlement, tokenized securities settlement, [cross-border](https://www.zeeve.io/blog/blockchain-in-cross-border-payments-a-game-changer/) liquidity, and regulated digital cash networks.
If you want to understand how any of these models works or which could be best suited for your bank, schedule a no-cost discussion [call with Zeeve experts](https://www.zeeve.io/talk-to-an-expert/).
# Ledger model and data structure:
They are primarily two types. ‘
1. Account-based ledgers
Account-based ledgers are best for regulatory simplicity. Identity is attached to balances at the ledger or account layer. This maps well to existing [banking ](https://www.zeeve.io/blog/banking-the-unbanked-defi-promoting-financial-inclusion/)records, account ownership, customer due diligence, reconciliation, reporting, and internal controls.
This model is useful when the bank needs every balance to map cleanly to a customer, corporate account, omnibus structure, or internal ledger. It is also useful for closed networks where participants are known and permissioned.
2. Token-based or UTXO-style ledgers
Token-based ledgers represent value more directly in the token. In UTXO-like models, settlement can be structured around discrete spendable units. These models can be better for atomic settlement, DvP, PvP, and complex multi-party workflows where counterparties do not share the same account architecture.
Blockchain deposits can also be native or non-native. Native records are blockchain records that act as the primary source of truth. Non-native records are on-chain mirrors of off-chain records. Native deposit [tokens](https://www.zeeve.io/blog/a-simple-and-comprehensive-guide-on-non-fungible-tokens) are promising because they are not limited by [off-chain](https://www.zeeve.io/blog/zeeve-partners-with-redstone-oracles-to-power-layer2-rollups-with-off-chain-data-integrations/) reconciliation processes and can use new blockchain functionality.
A bank architecture may need both patterns. They can start with account-based issuance, where regulatory clarity matters most. Add token-based settlement where DvP, PvP, or cross-network atomicity matters.
# Smart Contract & Token Architectures:
The smart contract layer defines how tokenized deposits behave. They are not simple fungible [token deployments](https://www.zeeve.io/blog/introduction-to-token-standards-erc-20-erc-721-erc-777-and-erc-1155/).
For tokenized deposits, smart contracts should support pre-settlement controls. These may include KYC status, sanctions results, wallet eligibility, transaction value, velocity limits, user role, geography, product type, and issuer approval.
They must also support operational controls. These include maker-checker approvals, emergency pause, audited upgrades, key rotation, admin role separation, contract monitoring, and formal review.
# What token standard should a bank use?
The following [token standards](https://www.zeeve.io/blog/introduction-to-token-standards-erc-20-erc-721-erc-777-and-erc-1155/) can be used but one thing we need to keep in mind is, there is no universal token standard for tokenized deposits. The right standard depends on the use case type.
# ERC-20
Good for simple fungible transfers, but compliance must be added through custom controls.
# ERC-1400
More suitable for regulated financial instruments because it supports partitions, operator controls, and forced transfers.
# ERC-3643 / T-REX
Useful where identity-linked transfer restrictions are required.
Custom permissioned token contracts
Often appropriate for bank-led or consortium-led networks where the participant set is closed, and role-based controls are more important than public composability.
# Other Infrastructure Decisions
# Privacy and compliance Infrastructure
Privacy and data localization are one of the biggest corporate adoption challenges and one of the hardest parts of tokenized deposit infrastructure. Because,
* Banks cannot expose sensitive metadata of counterparties, volumes, pricing, and [supply chain](https://www.zeeve.io/industry/supply-chain/) information. Jurisdictions may restrict also where data can reside and who can see it.
* At the same time, regulators, auditors, compliance teams, and internal control teams need visibility.
That creates a design dilemma.
The infrastructure must keep [transaction](https://www.zeeve.io/blog/whats-driving-the-massive-op-superchain-transaction-growth/) data confidential from unauthorized parties and also make the right data available to the right supervisory and control functions.
For tokenized deposits, privacy must operate across multiple surfaces.
It has to cover
* asset transfers.
* balances.
* smart contract execution.
* identity checks.
* API access.
* RPC endpoints.
* observability logs and dashboards.
* disclosure workflows.
This is the right framing because institutional privacy cannot be solved only at the token level.
[Zeeve’s Privacy Layer](https://www.zeeve.io/zeeve-privacy-layer/) is a perfect solution to institutional privacy and compliance challenges. It treats privacy as modular middleware and can be integrated with any blockchain type below your application layer.
Learn More: [how confidential transactions (ZK), role based access, selective disclosure and private smart contracts work in Zeeve Privacy Layer.](https://www.zeeve.io/blog/what-does-privacy-in-blockchain-mean-for-financial-institutions/)
These features of Zeeve privacy layer are useful here to keep sensitive data [private ](https://www.zeeve.io/blog/what-does-privacy-in-blockchain-mean-for-financial-institutions)without losing on-chain utility of tokenized deposits.
Because a private chain is not automatically a private workflow, privacy must be designed across the full system. Because even if your network is private, the [validators](https://www.zeeve.io/blog/everything-you-need-to-know-about-validator-nodes-a-deep-dive/) can still see the transactions and participants.
# Integration layer
# Core banking integration infrastructure
Tokenized deposit infrastructure does not replace core banking. It integrates with it.
The core banking system remains the system of record for deposit liabilities, customer accounts, interest treatment, [regulatory](https://www.zeeve.io/blog/web3-and-blockchain-gaining-traction-in-india-startups-seek-regulatory-clarity) reporting, treasury management, and balance sheet controls. The blockchain layer becomes the programmable [settlement ](https://www.zeeve.io/use-cases/cross-border-settlement-rails/)environment.
This needs [API](https://www.zeeve.io/blog/shared-apis-vs-dedicated-nodes-which-is-a-viable-option-for-your-dapp)\-based integration with legacy systems like, FIS, Finastra, Temenos, Mambu, in-house cores, treasury platforms, and compliance systems. REST APIs, webhooks, message queues, and event streams can connect [on-chain](https://www.zeeve.io/blog/how-enterprises-can-leverage-sui-blockchain-for-on-chain-asset-optimization/) actions with off-chain banking records.
Every mint, transfer, and burn needs a corresponding entry in the bank’s system of record. This reconciliation architecture can take longer to design and test than the [smart contract](https://www.zeeve.io/blog/a-comprehensive-guide-for-smart-contract-and-sovereign-rollups/) layer.
This is why banks should design reconciliation before choosing token standards.
# Integration with external enterprise tools
Tokenized deposits also need enterprise connectivity beyond core banking.
* For example, institutional custody is critical. Banks need MPC, HSM, remote signing, key rotation, quorum approval, transaction policies, and recovery workflows.
* For corporate users, account abstraction can improve wallet usability, delegated approvals, role-based signing, and pre-programmed payments.
* The policy engine should do KYC/AML screening before any [transaction ](https://www.zeeve.io/blog/parallel-transaction-execution-a-sneaky-update-in-hyperledger-besu-v24-7-1)settlement. The rules may include sender identity, receiver identity, balance, value threshold, velocity, sanctions result, jurisdiction, instrument type, business purpose, and approval status.
* [Oracles](https://www.zeeve.io/blog/decentralized-oracles-supercharging-the-enterprise-rollup-adoption/) can be important when payment depends on external data like, any rates or prices, delivery confirmation, securities settlement status, collateral values, or any corporate workflow events.
* Observability also matters. Banks need dashboards, logs, alerts, SLA monitoring, incident runbooks, transaction tracing, audit exports, and compliance evidence.
And all these together builds the regulated [financial infrastructure](https://www.zeeve.io/industry/fintechs-and-payments/) for tokenized deposits.
# Interoperability with other banks and financial networks
Tokenized deposits create the most value when they can move across counterparties.
A single-bank token can improve internal treasury movement. A shared ledger can improve settlement within a consortium. A broader interoperable network can support cross-bank [payments](https://www.zeeve.io/blog/blockchain-in-cross-border-payments-a-game-changer), tokenized securities settlement, [cross-border](https://www.zeeve.io/use-cases/cross-border-settlement-rails/) treasury, collateral mobility, and liquidity management.
Interoperability will be needed between traditional finance systems and blockchains, across different chains, and with other assets on a given blockchain. But multiple bridging and wrapping can introduce operational and technical risk.
This is where [Hyperlane-like integration](https://www.zeeve.io/hyperlane-integration/) concepts become relevant. Hyperlane is an interoperability framework that supports asset bridging and message passing across many chains and virtual machines and Zeeve enable this for its enterprise customers.
A bridge that moves value but breaks compliance is not bank-grade interoperability. A messaging layer that carries instructions without legal finality is not enough either.
KYC, AML, privacy and control has to be there in every layer.
Banks should ask early whether every new counterparty requires a [custom integration](https://www.zeeve.io/managed-custom-blockchain/) or whether the platform supports standardized connectivity from the start.
# A decision table: What Questions Banks Should Ask a Tokenized Deposit Blockchain Infrastructure Provider?
So when banks evaluate tokenized deposit infrastructure, they are really evaluating a full-stack infrastructure requirements:
# How Zeeve helps banks deploy tokenized deposit infrastructure
[Zeeve](https://www.zeeve.io/) helps banks design, deploy, and operate [tokenized deposit settlement infrastructure](https://www.zeeve.io/use-cases/tokenized-deposits-digital-cash/) across private, permissioned, public-permissioned, and hybrid architectures.
The value starts with infrastructure advisory. Banks do not need to choose a stack in isolation. They need to match [architecture](https://www.zeeve.io/blog/how-3-layer-architecture-of-polygon-works-in-ethereum) with use case, privacy needs, regulatory obligations, transaction volume, finality needs, and interoperability goals.
Zeeve can support banks across the full stack.
* Multi-stack advisory across permissioned, public-permissioned, [rollup](https://www.zeeve.io/rollups/), [appchain](https://www.zeeve.io/appchains/), and hybrid architectures
* Managed [blockchain network deployment](https://www.zeeve.io/blockchain-protocols/) and operations
* [Zeeve Privacy Layer](https://www.zeeve.io/zeeve-privacy-layer/)
* API and event integration with core banking, treasury, custody, and compliance systems
* Interoperability support with other banks, financial networks, and [cross-chain](https://www.zeeve.io/blog/what-are-cross-chain-bridges-a-detailed-guide/) messaging layers
* 24 by 7 monitoring, upgrades, observability, SLAs, and operational support
The goal is to help banks launch tokenized deposits without forcing them into a single chain, a single architecture, or a disruptive replacement of core systems. If your bank is looking to launch a tokenized deposit program, [connect with Zeeve](https://www.zeeve.io/talk-to-an-expert/) to discuss how we can help!
Show full