Today, “tokenized deposits” and “stablecoins” are being treated much the same way. They’re used interchangeably in vendor pitches, trade press and board presentations. For most audiences, that’s fine. For community bank leaders, a deeper understanding is necessary.

The two instruments differ in who issues them, what backs them, how they’re regulated and what they mean for your balance sheet. Confusing one for the other doesn’t just lead to potentially awkward conversations; it can also lead to misinterpreted risk assessments and poorly evaluated vendor relationships.

Lesson 1: Two Instruments, Two Very Different Structures

Tokenized deposits are what they sound like: digital tokens that represent bank deposits. They’re issued by a regulated bank, denominated in fiat, backed 1-to-1 by funds on the bank’s balance sheet, and accessible only to customers who have completed standard KYC onboarding. They live on a permissioned network, so participation is controlled and restricted to known parties. Structurally, they’re deposits with new infrastructure.

Stablecoins are digital tokens pegged to a currency (usually USD) and issued by a non-bank entity. Stablecoins like USDC or USDT are backed by reserves such as Treasury bills or cash equivalents, but those reserves do not sit on a bank’s balance sheet and are not treated as insured deposits. They operate on public or open blockchain networks, accessible to anyone with a digital wallet, no banking required.

A February 2026 New York Fed staff report captures the structural distinction plainly: Stablecoins intermediate safe assets into a medium of exchange, while tokenized deposits allow banks to keep funding loans and supporting credit creation, just on digital rails.

It’s worth noting that bank-issued stablecoin models are beginning to emerge under frameworks like the GENIUS Act, but the comparison above reflects the common forms community bank leaders are most likely to encounter in vendor conversations today.

Takeaway for Banks: Before engaging with any “digital money” pitch, establish which instrument is actually being discussed. The answer changes the regulatory, risk and balance sheet conversation entirely — and vendors don’t always make the distinction clear on their own.

Lesson 2: How Each Functions in Practice

Tokenized deposits are built for closed, regulated environments. Their natural use cases are interbank settlement, corporate treasury management and on-network payments between known participants. Indeed, a five-bank consortium of First Horizon, Huntington, KeyCorp, M&T and Old National has already started building shared tokenized deposit infrastructure. Their network will initially move money only between their customers.

Stablecoins are built for open ecosystems. Their natural use cases are crypto trading, decentralized finance, cross-border transfers to markets underserved by traditional rails, and platform-based payments where participants may not have banking relationships at all. Stablecoins solve the portability problem by providing a form of money that can move anywhere, to anyone, without third-party permissions. They generally don’t appear on balance sheets unless the bank is directly issuing or holding them.

A 2025 estimate put cross-border stablecoin volume at $9 trillion, much of it in markets where correspondent banking is slow, expensive or unavailable. That’s a genuinely different use case from what tokenized deposits are designed to do. The two instruments are solving different problems, not competing over the same one.

Takeaway for Banks: The use cases reflect fundamentally different designs. An instrument built for open, permissionless ecosystems carries different counterparty, regulatory and operational risks than one built for closed, regulated networks. Knowing which you’re evaluating matters to every downstream question.

Lesson 3: The Regulatory Differences

Tokenized deposits sit inside existing banking law. They are deposits that remain on your balance sheet, subject to the same supervision, examination standards and consumer protections as any other deposit liability. They affect funding costs, liquidity ratios and interest expense the same way as any other deposit.

Stablecoins currently occupy a more fragmented framework. The GENIUS Act established a federal framework for payment stablecoins, but much remains unsettled, including how state money-transmitter regimes interact with federal rules and how reserve requirements will be enforced in practice.

Notably, no equivalent legislative push exists for tokenized deposits, which regulators appear to view as an evolution of existing deposit law rather than a new category requiring new rules. The Conference of State Bank Supervisors asked the Fed, FDIC and OCC for clearer guidance.

There’s also a customer and reputation dimension worth considering. Community banks don’t need to be stablecoin issuers to have exposure. If customers use stablecoin platforms that fail, face regulatory action or freeze withdrawals, they’ll bring their questions to their banker first.

Takeaway for Banks: The regulatory and balance sheet differences aren’t footnotes. They determine how examiners will view any involvement, how risk should be categorized internally, and what governance your institution must put in place before engaging with either instrument in any capacity.

Lesson 4: Putting the Distinction to Work

Understanding these differences is only useful if it changes how community bank leaders operate on a day-to-day basis. Here are three concrete applications:

Interpreting Vendor and Fintech Pitches
The terminology in vendor decks is often imprecise by design. After all, “digital assets,” “tokenized money,” and “blockchain-based payments” can refer to very different things.

A short checklist of questions cuts to the chase: Are you describing a tokenized deposit, a stablecoin or something in between? Where do the liabilities sit — on our balance sheet, yours or a third party’s? Which regulators oversee this activity, and under what framework?

These questions should be the baseline due diligence that any bank should apply before conversations go further.

Framing Board and Customer Conversations
When these topics come up in the boardroom or across the counter, clear language matters. Tokenized deposits can reasonably be described as an evolution of existing deposits. They fall within the existing regulatory perimeter.

Certain stablecoins warrant a more cautious approach due to different issuers, different regulatory status and reserves that don’t carry deposit insurance. The distinction gives board members and customers a coherent mental model without requiring a deep technical explanation.

Building a Monitoring Habit
Neither instrument requires immediate action from most community banks, but both certainly require ongoing attention. A standing quarterly or biannual agenda item is a low-cost way to stay current and keep the topic going among your leadership team and board.

Track what your correspondents and core providers are building. Watch for any regulatory guidance that specifically mentions bank involvement with stablecoins or tokenized deposit networks. The landscape is moving fast enough that a six-month gap in attention can mean missing something material.

A Clearer Lens for the Next Conversation

The Reserve Primary Fund didn’t fail because money market funds were inherently dangerous. It failed in part because its similarity to bank deposits led too many participants — institutional and retail alike — to treat them as the same. The confusion itself was part of the risk.

That same tension is playing out today with tokenized deposits and stablecoins. They share enough surface similarities (e.g., digital, dollar-denominated, blockchain-based, etc.) that many are bound to mix them up. For community bank leaders, that isn’t an option. 

These instruments differ in structure, regulation, risk profile and strategic implications. Understanding these differences doesn’t require becoming a blockchain expert; it just requires a consistent conversation.