Tokenized Deposits vs Stablecoins: A Builder's Guide to Bank Dollars On-Chain
A dollar on a blockchain can represent two very different financial relationships.
It could be a stablecoin issued by a payment stablecoin issuer and backed by reserve assets. Or it could be a tokenized deposit representing money a customer holds with a bank.
Both can move across blockchain networks. Both can support programmable payments. But when you compare tokenized deposits vs stablecoins, the institution behind the asset, the legal claim it represents and the infrastructure required to move it are different.
The distinction became more important on July 18, 2025, when the United States enacted the GENIUS Act 2025. The law established a federal framework for payment stablecoins and expressly excluded deposits recorded using distributed ledger technology (DLT) from its definition of payment stablecoins.
For banks and fintech builders, this creates room to develop blockchain-based payment systems around existing commercial bank deposits. If you are building on the stablecoin side instead, our guide to stablecoin payment infrastructure and GENIUS Act compliance covers that path.
The engineering challenge is making those deposits usable across wallets, ledgers, banking systems and blockchain networks without losing control over ownership, settlement and reconciliation. This guide walks through the tokenized deposit architecture, chain choices, wallet design and interoperability work involved.
What Are Tokenized Deposits, and How Do They Differ from Stablecoins?
A stablecoin and a tokenized deposit may both be designed to maintain a dollar value, but they represent different liabilities.
In other words, tokenized bank deposits are still bank deposits. Only the recordkeeping and the transfer rails change.
This distinction affects the entire system design. Whether you frame it as stablecoins vs tokenized deposits or the other way around, the table below shows where the two differ.
Deposit Tokens vs Tokenized Deposits
The two terms are often used interchangeably. Where a distinction is drawn, a tokenized deposit mirrors a balance that still sits in a customer account on the bank's core ledger. A deposit token is more digitally native: the on-chain record acts as the primary record rather than mirroring a credit in a corresponding account. The FDIC describes the terms in the same way in its 2026 proposed rule.
What the GENIUS Act Means for Tokenized Deposits
The GENIUS Act excludes deposits, including tokenized deposits, from the statutory definition of payment stablecoins. It also preserves banks' ability to issue tokenized deposits and use distributed ledger technology.
Two practical consequences follow for builders:
For institutions looking to put bank dollars on-chain, tokenized deposits therefore offer a route that builds on the existing bank-deposit relationship.
Tokenized Deposits in Banking: The Market Has Moved Beyond Experiments
Several financial institutions are already building or operating tokenized deposit infrastructure. Their approaches reveal different ways to connect traditional banking systems with blockchain networks.
JPMorgan: JPMD Deposit Token on Base
JPMorgan introduced JPMD in June 2025 as a proof of concept on Base, an Ethereum Layer 2 public blockchain. In November 2025, the bank made the USD deposit token, branded JPM Coin, available to its institutional clients. B2C2, Coinbase and Mastercard completed test transactions with it.
JPMD is a permissioned deposit token. Although Base is a public network, access to the token is restricted to eligible institutional participants. This shows that public-chain infrastructure does not have to mean unrestricted access to the underlying financial product.
Citi: Tokenized Deposits on a Private Network
Citi Token Services uses a private permissioned blockchain, owned and managed by Citi, to tokenize deposits within its global network. Its cash service moved from pilot to a live commercial solution in October 2024, and clients do not need to hold or manage tokens to use it.
In July 2026, Siam Commercial Bank became the first financial institution client to go live with Citi's integrated 24/7 USD Clearing and Citi Token Services solution. Because Citi's 24/7 USD Clearing network connects more than 300 financial institutions across over 50 markets, the implementation links tokenized deposits with cross-border payment infrastructure.
HSBC: Connecting Bank Deposits Across Networks
HSBC expanded its Tokenized Deposit Service to the United States in April 2026, adding to its availability in Hong Kong, Singapore, Luxembourg and the UK. In August 2026, HSBC and Standard Chartered completed the first live cross-border tokenized deposit transaction on Swift's blockchain-based ledger.
Swift's ledger acted as an orchestration layer. It matched and netted the payment obligations recorded on each bank's own tokenized deposit system before final settlement through existing systems. That is a useful pattern for builders: interoperability without forcing both banks onto a single ledger.
The Clearing House: A Shared Bank Network
The Clearing House announced its On-Chain Money Initiative in June 2026. In September, it selected Quant to provide the network's interoperability, orchestration and transaction-management layer.
The initiative aims to connect tokenized deposits with established payment infrastructure, including RTP and CHIPS. Its planned availability to participating institutions is in the first half of 2027.
These implementations show that banks are exploring different network models. The common requirement is connecting on-chain transfers with the systems that record and settle actual bank deposits.
Tokenized Deposit Architecture Starts with the Bank Ledger
How do banks issue tokenized deposits? Every approach to bank deposit tokenization starts in the same place: a reliable relationship between the token supply and the bank's deposit records.
The blockchain may record token transfers, but the bank remains responsible for the underlying deposit liability. The token platform must therefore maintain a consistent relationship between on-chain balances and the corresponding customer accounts.
A typical tokenized deposit architecture has five components:
The critical design decision is how these components communicate. Most banks deploy the tokenization platform as a layer alongside the existing core rather than replacing it, which makes API integration and event handling central to the design.
The system needs a controlled process for issuance, transfer, redemption and reconciliation.
Public vs Permissioned Blockchain for Tokenized Deposits
The choice between a permissioned and a public blockchain affects access, privacy, interoperability and operational responsibility.
Permissioned Chains: Controlled Participation
Citi's private blockchain implementation demonstrates this approach. Participating clients use the service through the bank's infrastructure without independently managing blockchain tokens.
The trade-off is network reach. Connecting institutions across separate permissioned environments requires agreed standards, governance and interoperability mechanisms. For a closer look at how public and permissioned platforms differ, see our comparison of Ethereum vs Hyperledger.
Public Chains: Broader Infrastructure, Controlled Assets
JPMD's deployment on Base demonstrates how a bank can use a public blockchain while maintaining restrictions around an institutional deposit token. However, public-chain integration introduces additional questions:
A public chain does not automatically provide the privacy or transaction controls a bank requires. These must be designed into the token, the wallet and the supporting infrastructure, including the smart contracts that enforce transfer rules. Our guide to smart contract best practices covers the security basics.
Tokenized Deposit Wallet Architecture: More Than a Private Key
Wallet integration is one of the most important parts of a tokenized deposit system.
For institutional applications, a wallet should connect the blockchain address to a verified customer or organization. The bank needs to know who controls the address, what permissions apply and whether the participant remains eligible to transact.
A production wallet architecture should include:
For example, a corporate treasury team may allow one employee to prepare a transfer while requiring a second authorized employee to approve it. The wallet should enforce that policy before a transaction reaches the blockchain.
Tokenized Deposits Interoperability Between Banks
A bank may successfully issue deposits on its own ledger, but that does not mean another bank can receive them.
Blockchain interoperability requires more than connecting two networks. Institutions need agreement on identity, asset representation, settlement finality, transaction validation and redemption.
Consider a payment between two banks operating separate tokenized deposit systems. The sending bank needs to validate the customer and debit the relevant deposit account. The receiving bank needs to recognize the incoming asset and credit the correct account. Both institutions need evidence that the transaction has completed under their agreed settlement model.
A shared network or interoperability layer can coordinate these operations. The HSBC and Standard Chartered transaction on Swift's ledger is one model, where each bank keeps its own ledger and a shared layer matches obligations. The Clearing House initiative is another, designed to connect tokenized commercial bank money with existing payment rails such as RTP and CHIPS.
For builders, the integration layer should handle:
How Tokenized Deposits Work: A Practical Transaction Flow
A tokenized deposit payment needs to connect the customer's bank account, wallet and blockchain transaction. A typical flow looks like this:
Where both legs of a trade sit on the same ledger, smart contracts can also support atomic settlement, also called delivery versus payment (DvP), in which the asset and the cash move together or not at all.
How to Build a Tokenized Deposit Platform: What to Get Right Before Launch
A tokenized deposit platform should be tested against operational scenarios, not just successful transfers.
Start with a limited institutional use case. The most practical tokenized deposits use cases today are:
Define the participants, transaction limits, wallet model and settlement process. Then test the following:
API integrations are equally important. Core banking platforms, identity providers, wallet services and blockchain networks need secure interfaces with clear ownership of transaction states.
For fintech teams exploring programmable payments, this infrastructure also creates opportunities for agent-driven transactions. We have covered the payment architecture behind x402 AI agent payments and the settlement requirements of agentic commerce.
How Seaflux Helps Banks and Fintechs Build Tokenized Deposit Infrastructure
Seaflux is a blockchain development company and fintech software development partner, and an AWS Select Consulting Partner, with teams in Austin, Texas and Ahmedabad, India. Our blockchain development services and fintech software development teams help banks and fintechs connect blockchain networks to the banking systems that already run their business, delivering banking blockchain solutions that fit existing controls rather than replacing them.
Here is where we support tokenized deposit and blockchain payment projects:
Put the Deposit First. Build the Blockchain Around It.
The GENIUS Act gives tokenized deposits a distinct position outside its payment stablecoin definition. That distinction creates room for banks to extend deposit-based payment services onto blockchain infrastructure, while remaining subject to the banking rules that govern their activities.
For builders weighing tokenized deposits vs stablecoins, the priority is connecting the token to a real bank liability. Wallet permissions, ledger synchronization, chain selection and interoperability must work as one controlled system.
The most useful starting point is to choose one payment journey and map every system involved, from the customer's deposit account to the receiving institution's ledger.
Frequently Asked Questions (FAQ): Get the Answers You Need
What are tokenized deposits?
Tokenized deposits are digital representations of commercial bank deposits recorded on a blockchain or other distributed ledger. They remain a deposit liability of the issuing bank, so the customer's claim is against the bank, just like a traditional account balance.
Tokenized deposits vs stablecoins: what is the difference?
A tokenized deposit is a bank deposit on blockchain rails, issued by a depository institution and governed by banking rules. A payment stablecoin is a separate token issued by a permitted payment stablecoin issuer, backed by reserve assets and governed by the GENIUS Act framework.
Are tokenized deposits stablecoins under the GENIUS Act?
No. The GENIUS Act expressly excludes deposits, including deposits recorded using distributed ledger technology, from its definition of payment stablecoins. Tokenized deposits remain subject to existing banking, prudential and AML obligations.
Are tokenized deposits FDIC insured?
Under a rule the FDIC proposed in April 2026, tokenized deposits that meet the statutory definition of a deposit would be treated the same as any other deposit under the Federal Deposit Insurance Act. Standard coverage rules and limits would still apply.
Can tokenized deposits pay interest?
Yes. Because tokenized deposits are bank deposits, banks can pay interest on them. Permitted payment stablecoin issuers, by contrast, cannot pay interest or yield to stablecoin holders under the GENIUS Act.
Should a bank use a public or permissioned blockchain for tokenized deposits?
It depends on the use case. Permissioned chains give tighter control over participants and data and suit internal liquidity and interbank settlement. Public chains offer broader reach, but the bank must build its own controls for wallet eligibility, transfer restrictions and asset recovery.
How do tokenized deposits work between two banks?
The sending bank debits its customer's deposit account and initiates the token transfer, and the receiving bank recognizes the asset and credits the correct account. A shared network or interoperability layer usually coordinates identity, transaction status and final settlement between the two institutions.

Krunal Bhimani
Business Development Executive