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. Here is what separates them under the GENIUS Act, and the bank ledger, wallet and interoperability architecture it takes to put deposits on-chain.
GENIUS Act explained
4 bank models compared
5-component architecture
Pre-launch test plan
Key takeaways
A tokenized deposit is a bank deposit liability on blockchain rails. A payment stablecoin is an issuer's redemption obligation.
The GENIUS Act excludes tokenized deposits from its payment stablecoin definition, so banks build on existing deposit rules.
JPMorgan, Citi, HSBC and The Clearing House show four different network models already in motion.
The hard part is architecture: core banking sync, wallet governance, chain choice and interbank interoperability.

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.

Diagram · Who stands behind the token
TOKENIZED DEPOSIT · BANK MONEY Holder Tokenized deposit Bank deposit liability Core ledger holds claim on on books PAYMENT STABLECOIN · ISSUER MONEY Holder Payment stablecoin Issuer redemption obligation Reserve assets holds claim on backed by
Same dollar on a blockchain, two different claims: one on a bank's balance sheet, one on an issuer's reserves.

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.

Put the deposit first. Build the blockchain around it.
The design principle behind every section of this guide
01 · DEFINITIONS

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.

Bank money
Tokenized deposit
Represents a deposit liability of a bank. The token is a digital representation of money recorded on the bank's books and transferred through distributed ledger technology.
Issuer money
Payment stablecoin
An issuer's obligation to redeem the token for a fixed monetary value. Its backing comes from permitted reserve assets under the applicable regulatory framework.

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.

Area
Tokenized deposits
Payment stablecoins
Issuer
Depository institution (bank)
Permitted payment stablecoin issuer
Underlying claim
Bank deposit liability
Issuer's redemption obligation
Regulatory framework
Applicable banking and deposit rules
GENIUS Act framework
Interest
Can pay interest, like other deposits
Issuers may not pay interest or yield to holders
Deposit insurance
Treated as deposits under the Federal Deposit Insurance Act
Not deposit-insured
Ledger model
Bank-controlled or interoperable ledger
Public or permissioned blockchain
Access
Usually restricted to eligible bank customers and participants
Depends on issuer and transfer controls
Integration
Bank core, deposit ledger and token platform
Issuer, reserve, redemption and wallet infrastructure

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.

System of record: core ledger
Tokenized deposit
Mirrors a balance held in a customer account. The token moves; the core banking ledger stays the source of truth.
System of record: chain
Deposit token
More digitally native. The on-chain record is the primary record, without a mirrored credit in a corresponding account.
The question that matters
For architecture purposes, the question is simple: which ledger is the system of record?
02 · REGULATION

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.

Important
The exclusion does not remove existing banking, prudential, AML or other applicable obligations. Tokenized deposits stay inside the bank's regulatory perimeter.

Two practical consequences follow for builders:

Interest. The Act bars permitted payment stablecoin issuers from paying interest or yield to holders. Tokenized deposits remain deposits, so banks keep the ability to pay interest on them, as the Federal Reserve Bank of Richmond has noted.
Deposit insurance. In April 2026, the FDIC proposed a rule clarifying that tokenized deposits meeting the statutory definition of "deposit" would be treated no differently under the Federal Deposit Insurance Act than any other deposit.
Deposit insurance does not depend on the technology a bank uses to record its deposit liabilities.
The FDIC's position in its April 2026 proposed rule

For institutions looking to put bank dollars on-chain, tokenized deposits therefore offer a route that builds on the existing bank-deposit relationship.

03 · MARKET

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.

300+ financial institutions on Citi's 24/7 USD Clearing network
50+ markets that network connects
5 markets where HSBC's Tokenized Deposit Service is available
H1 '27 planned availability of The Clearing House network
JPMJPMorgan
Live
Public chain · Base
JPMD, a permissioned deposit token for institutional clients on an Ethereum Layer 2.
CCiti
Live
Private permissioned chain
Citi Token Services, now integrated with 24/7 USD Clearing for cross-border payments.
HSBCHSBC
Live
Interop via Swift ledger
Tokenized Deposit Service in the US, plus a live interbank transaction with Standard Chartered.
TCHThe Clearing House
H1 2027
Shared bank network
On-Chain Money Initiative connecting tokenized deposits to RTP and CHIPS.

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.

October 2024
Citi Token Services for Cash moves from pilot to live commercial solution.
June 2025
JPMorgan launches the JPMD proof of concept on Base.
July 18, 2025
GENIUS Act enacted, excluding tokenized deposits from the payment stablecoin definition.
November 2025
JPMD becomes available to JPMorgan's institutional clients.
April 2026
HSBC brings its Tokenized Deposit Service to the US. The FDIC proposes its tokenized deposit clarification.
June 2026
The Clearing House announces its On-Chain Money Initiative.
July 2026
Siam Commercial Bank goes live on Citi's 24/7 USD Clearing and Citi Token Services.
August 2026
HSBC and Standard Chartered complete the first live tokenized deposit transaction on Swift's ledger.
September 2026
The Clearing House selects Quant for its interoperability layer.
First half of 2027
Planned availability of The Clearing House network to participating institutions.

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.

Free assessment
Mapping your first tokenized deposit use case?
Get a free review of your core banking connectivity, wallet model and chain options before you commit to a network.
Book the Free Assessment
04 · ARCHITECTURE

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.

Diagram · Reference architecture
Permission & identity layer KYC, wallet ownership, eligibility Core banking system accounts and balances Tokenization platform mint, transfer, redeem Blockchain network smart contracts, records Reconciliation service token supply must equal deposit liabilities approves API events token ops balances on-chain events
The tokenization platform runs alongside the core, not in place of it. Reconciliation checks both ledgers continuously.

A typical tokenized deposit architecture has five components:

1
Core banking system Maintains customer accounts, deposit balances and account ownership.
↓
2
Tokenization platform Creates, transfers, redeems and manages tokenized deposit representations.
↓
3
Permission and identity layer Verifies eligible participants, wallet ownership and transaction permissions, including the KYC and AML compliance checks the bank already runs.
↓
4
Blockchain network Records token movements and executes approved smart contract operations.
↓
5
Reconciliation service Matches ledger events with bank records and identifies discrepancies, much like sub-ledger accounting does for embedded finance.
✓
Each component depends on the one above it staying in sync.

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.

A token transfer should not become an independent financial event disconnected from the bank's books.

The system needs a controlled process for issuance, transfer, redemption and reconciliation.

05 · CHAIN CHOICE

Public vs Permissioned Blockchain for Tokenized Deposits

The choice between a permissioned and a public blockchain affects access, privacy, interoperability and operational responsibility.

Controlled participation
Permissioned chain
Restricts participation to approved institutions or entities. The operator defines who validates transactions, who can access information and who can initiate transfers.
Suits institutional treasury
Suits internal liquidity movement
Suits interbank settlement
Example: Citi Token Services
Broader infrastructure
Public chain
Provides established blockchain infrastructure, smart contract environments and access to external applications, with the asset itself kept under bank controls.
Wider network reach
Established tooling
Controls must be designed in
Example: JPMD on Base

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:

Q.01
How are eligible wallet addresses approved?
Q.02
Can tokens be transferred to unauthorized wallets?
Q.03
How are transaction fees funded?
Q.04
What happens when a wallet is compromised?
Q.05
How are erroneous or suspicious transfers handled?
Q.06
Can the bank freeze, block or recover assets where legally and contractually permitted?

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.

06 · WALLETS

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:

Identity binding Associate wallet addresses with verified customer and institutional identities.
Access controls Apply role-based permissions for treasury teams, operators and authorized signatories.
Key management Use hardware security modules (HSMs) or institutional custody arrangements to protect signing keys.
Transaction policies Set limits, approval thresholds, destination restrictions and multi-party authorization rules.
Lifecycle management Support wallet creation, suspension, key rotation, recovery and closure.

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.

MakerPrepare transfer
CheckerSecond approval
PolicyLimits & destination
HSMSign
ChainSubmit
07 · INTEROPERABILITY

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.

Diagram · Interbank orchestration model
Sending bank own tokenized deposit ledger debits customer Receiving bank own tokenized deposit ledger credits customer Orchestration layer matches and nets Existing rails final settlement obligation matched net positions settled settled
The pattern behind the HSBC and Standard Chartered transaction on Swift's ledger: each bank keeps its own ledger, a shared layer matches obligations.

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:

01 Transaction formats Network-specific message and transaction structures.
02 Participant verification Identity checks for both counterparties.
03 Asset mapping Asset and denomination mapping between issuers.
04 Status events Transaction status and confirmation events.
05 Settlement coordination Agreement on when and how final settlement happens.
06 Exceptions Exception handling and reconciliation.
Watch out
Avoid assuming that tokens issued by different banks are interchangeable simply because both represent US dollars. Each token has its own issuer, redemption process and eligibility conditions.
08 · TRANSACTION FLOW

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:

Customer requests payment Through the bank's channel or API
Bank authenticates customer Identity and session checks
Wallet and destination verified Both wallets eligible and permitted
Balance and limits checked Deposit balance and policies
Token transfer authorized Approvals collected, transfer signed
Blockchain records transaction The token moves on-chain
Bank ledgers reconciled On-chain events matched with core
Payment confirmed Once settlement is final
Read left to right, row by row. Nothing reaches the chain without passing the approval gate.
Engineering note
The workflow should also account for failed transactions, duplicate requests, network interruptions and delayed confirmations. Idempotency controls are essential to prevent a retry from creating an unintended second payment.

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.

09 · BEFORE LAUNCH

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:

Internal liquidity movement
Treasury transfers between subsidiaries
Cross-border payments
Supplier payments

Define the participants, transaction limits, wallet model and settlement process. Then test the following:

Ledger consistency Can the bank reconcile token balances with deposit liabilities?
Smart contract security Have issuance, transfer and redemption contracts undergone independent testing?
Wallet governance Can the institution enforce approvals and revoke compromised access?
Transaction finality What event confirms that the payment is complete?
Interoperability Can the system handle transfers involving another bank or blockchain?
Operational recovery What happens during a chain outage, failed transaction or reconciliation mismatch?

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.

Pre-launch review
Is your core banking ready for 24/7 token events?
We test ledger consistency, wallet governance and recovery paths before your first live transfer.
Talk to a Blockchain Specialist
10 · SEAFLUX

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.

AWS Select Consulting Partner
Ethereum
Hyperledger
Polygon
Solana

Here is where we support tokenized deposit and blockchain payment projects:

Tokenization platform development
Design and build issuance, transfer and redemption flows on Ethereum, Hyperledger, Polygon or Solana, drawing on our work in multi-chain token development.
Core banking and blockchain payment integration
Build the APIs and event pipelines that keep core banking systems, deposit ledgers and on-chain balances in sync.
Smart contract development and audits
Write and review the contracts that control minting, transfer restrictions and redemption.
Blockchain wallet development
Implement identity-bound wallets, custody and HSM integration, and multi-party approval workflows for treasury teams.
Cross-chain interoperability solutions
Connect tokenized deposits across permissioned and public networks and to existing payment rails.
Compliance and reconciliation engineering
Build KYC, AML and audit trail controls into the platform, following the fintech compliance architecture patterns we use across regulated projects.
Cloud infrastructure for 24/7 operations
Run always-on payment systems on secure, scalable infrastructure through our cloud computing services.
Case study
Our blockchain payments experience includes a crypto debit card payment platform that connects digital assets with card payments.
11 · NEXT STEPS

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.

Free Blockchain & Fintech Architecture Assessment
If your bank launched a tokenized deposit tomorrow, where would the first integration bottleneck appear?
Seaflux offers a Free Blockchain & Fintech Architecture Assessment to help teams evaluate these decisions across banking systems, blockchain infrastructure and payment integrations.
Wallet governance
Core banking connectivity
Cross-chain settlement

Frequently Asked Questions (FAQ): Get the Answers You Need

Krunal Bhimani

Krunal Bhimani

Business Development Executive

Claim Your No-Cost Consultation!

Let's Connect