Table of Contents
- 1. Stablecoins and tokenised deposits reshape banking services
- 2. Step 1: Understanding Tokenised Deposits and Stablecoins
- 3. Step 2: The Importance of Regulatory Compliance
- 4. Step 3: Addressing Cross-Border Payment Challenges
- 5. Step 4: Meeting Client Needs with Combined Solutions
- 6. Step 5: Exploring Use Cases for Financial Institutions
- 6.1 Real-Time Cash Concentration
- 6.2 Instant Delivery-Versus-Payment
- 7. Step 6: Recognizing the Demand from Market Participants
- 8. Step 7: The Risks of Not Adopting Digital Solutions
- 9. Step 8: Navigating Regulatory and Policy Considerations
- 10. Conclusion: The Future of Digital Money in Banking
- 10.1 Embracing Innovation
- 10.2 Navigating Regulatory Landscapes
Stablecoins and tokenised deposits reshape banking services
Banking Shifts in Digital Assets
What changed in 2024–2026 (and why banks care):
- Regulation moved from “grey area” to clearer rulebooks in major markets (e.g., EU MiCA effective 2024; US GENIUS Act in 2025), making product design and go-to-market decisions less speculative.
- Expectations shifted to 24/7/365 settlement and liquidity visibility, not just faster messaging—pushing banks to rethink cut-offs, intraday liquidity, and operational controls.
- Digital-asset venues and payment networks increasingly expect interoperable rails, so “can you connect?” is becoming as important as “what’s your price?” in mandates.
- Tokenised deposits sit inside a bank’s regulated balance sheet and KYC perimeter, enabling programmable liquidity and operations.
- Stablecoins can do what deposits can’t: move value across borders, including across capital-control boundaries.
- Banks building only one rail risk serving only “half” of client needs—especially for multinational treasury flows.
- Demand is rising from clients and correspondents/counterparties, turning digital-money connectivity into an RFP requirement.
Step 1: Understanding Tokenised Deposits and Stablecoins
By 2026, “digital money” in banking increasingly means two instruments with different strengths: tokenised deposits and stablecoins. Tokenised deposits are traditional bank deposits represented on a distributed ledger. They remain liabilities of the issuing bank, typically within existing banking regulation and—depending on jurisdiction—within deposit insurance frameworks. Because they sit inside the regulated balance sheet and the bank’s KYC perimeter, they are a natural fit for controlled, programmable operations.
Stablecoins, by contrast, are digital tokens typically pegged 1:1 to fiat currency and issued by private entities (though banks may also issue them). Their design goal is stable value and easy transfer, which has made them attractive for payments and cross-border movement of funds. In practice, stablecoins have also become a bridge between traditional finance and digital-asset venues.
The key point for strategy is that these are not perfect substitutes. Tokenised deposits are built for regulated banking workflows and liquidity management; stablecoins are built for reach and portability—especially across borders and across networks that don’t share the same banking rails.
| Dimension | Tokenised deposits | Stablecoins |
|---|---|---|
| Issuer / liability | Liability of the issuing bank (a deposit claim) | Liability of the issuer (bank or non-bank, depending on model) |
| Where it “lives” operationally | Inside the bank’s regulated balance sheet and KYC perimeter | Often designed to circulate across networks/venues beyond a single bank perimeter |
| Best-fit strengths | Programmable treasury operations, internal liquidity orchestration, controlled workflows | Cross-border reach, portability across venues, faster movement across networks |
| Typical constraints to plan for | Interoperability across banks/ledgers; integration with core banking and intraday liquidity | Regulatory fragmentation; reserve/issuer requirements; venue and chain risk controls |
| Good first questions | “Which internal flows are slowed by cut-offs/manual reconciliation?” | “Where do clients need reach we can’t provide on bank-to-bank rails?” |
Step 2: The Importance of Regulatory Compliance
Regulation is not a footnote in digital money—it is the product boundary. Tokenised deposits generally fall under existing banking rules because they are bank liabilities. That gives them a compliance “home”: prudential oversight, established risk management expectations, and operation inside the KYC perimeter. For banks, that alignment is precisely why tokenised deposits are positioned as the natural instrument for programmable treasury operations.
Stablecoins face a more explicit and fragmented regulatory landscape. By 2026, major jurisdictions have moved from ambiguity to frameworks: the EU’s MiCA regime (effective 2024) sets requirements such as EU-based reserves and includes caps on non-euro stablecoins (€200 million per day). In the US, the GENIUS Act (July 2025) created a federal framework for payment stablecoins, shifting them toward regulated financial infrastructure.
Even with progress, global fragmentation remains. Definitions, backing requirements, and issuer obligations vary across markets, creating compliance complexity for banks and multinational corporates operating across multiple jurisdictions.
Build-Time Compliance Essentials
Build-time compliance checkpoints (practical, not theoretical):
- Define the instrument clearly: tokenised deposit vs stablecoin (and whether the stablecoin is bank-issued or third-party).
- Map the perimeter: who can hold/transfer (KYC’d clients only, whitelisted wallets, permitted venues).
- Confirm reserve/segregation expectations (where applicable) and how attestations/reporting will be produced.
- Specify AML/sanctions controls for on-chain activity: screening, monitoring, and escalation paths.
- Decide operating model for 24/7: staffing, incident response, and cut-off replacement controls.
- Document redemption and dispute handling: how clients exit back to deposits, and what happens on failed/returned transfers.
- Validate cross-border legal enforceability: which jurisdiction’s rules govern issuance, transfer finality, and claims.
Step 3: Addressing Cross-Border Payment Challenges
Cross-border payments are where the split between tokenised deposits and stablecoins becomes most visible. Retail banking wants payments that clear across a border in real time. Stablecoins are positioned to answer that demand because they can move value across networks without requiring every step to be a traditional bank-to-bank settlement hop. They can also traverse capital-control boundaries that can strand local-currency balances.
Tokenised deposits, meanwhile, are designed for programmable liquidity inside the bank’s regulated perimeter. They can reduce idle liquidity across entities and enable conditional movement of funds, but they are not inherently built to solve the “last mile” of cross-border reach—especially when capital controls and non-convertible currencies complicate flows.
This is why a bank building only tokenised deposits may still leave clients dependent on external rails for cross-border execution, while a bank building only stablecoin capability may miss the operational advantages of programmable deposits for treasury and transaction banking.
The strategic implication is straightforward: cross-border is not just a payments problem; it is a liquidity, operating-hours, and interoperability problem—one that often requires more than one instrument.
| Cross-border constraint | Tokenised deposits (typical fit) | Stablecoins (typical fit) | Trade-off to make explicit |
|---|---|---|---|
| Need for strict bank-perimeter controls (KYC’d participants, bank liability) | Strong | Varies by issuer/model | More control can mean less reach/interoperability |
| Reach to non-bank venues/counterparties | Often limited unless networks interconnect | Stronger by design | More reach increases the need for venue/chain risk controls |
| Capital controls / non-convertible currency corridors | Often constrained | Often used as a workaround rail (subject to local rules) | Regulatory and policy constraints can still override technology |
| 24/7 settlement expectations | Strong for internal/on-network flows | Strong across always-on networks | 24/7 operations requires new monitoring, liquidity, and incident response |
| Treasury visibility and internal liquidity optimisation | Strong | Indirect | Optimising internal liquidity doesn’t automatically solve external execution |
Step 4: Meeting Client Needs with Combined Solutions
The combined proposition is increasingly framed as “owning the whole flow.” Tokenised deposits can deliver programmable operations: real-time cash concentration, conditional disbursement, atomic settlement, and liquidity that stops sitting idle across entities. Stablecoins can deliver cross-border movement, including across the boundaries that traditional banking rails and capital controls impose.
For a multinational treasurer operating across convertible and controlled currencies alike, offering only one instrument can mean solving only one leg of the journey. Offer both, and the bank can cover the end-to-end lifecycle: internal liquidity orchestration (tokenised deposits) plus external reach and cross-border clearing (stablecoins).
End-to-End Tokenised Payment Flow
A simple “whole-flow” way to design the combined proposition:
1) Origination (inside the bank): client funds are held as deposits and represented as tokenised deposits for programmable control.
2) Orchestration (treasury logic): rules-based sweeps, conditional releases, limits, and approvals run within the KYC perimeter.
3) Execution (outside reach): when the beneficiary/corridor requires broader interoperability, value is routed via stablecoin rails.
4) Settlement & reconciliation: confirm finality, reconcile on-ledger events to bank books, and provide client reporting across entities.
5) Return path: redemption back into deposits (and into local rails) is designed as a first-class user journey, not an exception.
This is not theoretical. Use cases described as moving into production include settlement outside traditional banking hours, delivery-versus-payment that clears instantly instead of settling days later, and treasury visibility across entities without manual reconciliation. Used together, tokenised deposits and stablecoins can reduce operational friction while expanding where and when money can move.
Step 5: Exploring Use Cases for Financial Institutions
Banks evaluating digital money in 2026 are not just chasing novelty; they are responding to concrete operational demands: 24/7 settlement expectations, reduced reconciliation, and better liquidity utilisation. Tokenised deposits are positioned for programmable liquidity inside regulated banking. Stablecoins are positioned for cross-border and multi-network value transfer.
The most compelling use cases tend to share three traits: they compress settlement time, reduce manual processes, and improve visibility across entities and counterparties. They also reflect a shift in expectations—settlement and liquidity management are no longer assumed to be constrained by traditional banking hours.
Two examples frequently cited in production-oriented discussions are real-time cash concentration and instant delivery-versus-payment. Both highlight why programmability and atomicity matter, and why banks are increasingly considering multi-rail strategies rather than single-instrument bets.
Qualify and Prioritise Use Cases
A repeatable way to qualify and prioritise digital-money use cases:
- Value: What measurable outcome improves (cut-off removal, trapped liquidity reduced, reconciliation hours removed, settlement risk reduced)?
- Feasibility: Can it run inside today’s KYC/booking model, and can core systems support 24/7 posting and exception handling?
- Risk: What new exposures appear (issuer/credit, chain/venue, operational, legal enforceability), and what control closes each one?
- Interoperability: Which counterparties/venues must connect on day one, and what’s the fallback rail if they can’t?
- Time-to-production: What is the smallest “live” scope that still proves the outcome (not just a pilot)?
Checkpoint: If you can’t name (1) the control owner and (2) the operational runbook for failures, it’s not production-ready yet.
Real-Time Cash Concentration
Real-time cash concentration is a transaction-banking use case built around programmable liquidity. In traditional setups, cash pooling and concentration across entities can be slow, operationally heavy, and dependent on cut-off times—leaving balances idle and forcing treasurers into workarounds.
Tokenised deposits are positioned to change that by enabling liquidity to move within the bank’s regulated perimeter with conditions attached: funds can be swept, allocated, or restricted based on predefined rules. The goal is not just speed, but control—reducing idle cash across subsidiaries and improving treasury visibility without manual reconciliation.
In a multinational context, this also supports a clearer view of liquidity across entities, helping treasurers understand where cash sits and how quickly it can be mobilised. The broader promise is that “programmable operations” become a standard feature of transaction banking rather than a bespoke integration project.
Instant Delivery-Versus-Payment
Delivery-versus-payment (DvP) is a settlement pattern where delivery of an asset and payment happen together. Traditional market infrastructure can involve multi-day settlement cycles, creating counterparty and operational risk, and tying up liquidity.
Instant DvP aims to clear the exchange immediately—asset delivery and payment occur atomically. Discussions in 2026 increasingly point to DvP that clears instantly instead of settling days later, including settlement that runs outside traditional banking hours.
Tokenised deposits can support the payment leg inside a regulated banking framework, while stablecoins can extend reach to venues and counterparties that operate across borders or outside conventional rails. The practical outcome is faster settlement, reduced reconciliation, and a pathway to more continuous markets—where “banking hours” are less determinative of when value can move.
Step 6: Recognizing the Demand from Market Participants
Demand is not coming only from end clients. Correspondents, counterparties, and market infrastructure participants are also pushing for greater efficiency and interoperability. That matters because it changes the competitive dynamic: digital-money capability becomes not merely a product feature, but a connectivity requirement.
Correspondents increasingly expect connection, turning tokenised deposit and stablecoin capability into a mandate requirement. In practical terms, banks that cannot connect risk losing RFPs to those that can. This is a subtle but powerful shift: adoption pressure moves from “nice-to-have innovation” to “table stakes” for participating in certain flows.
On the client side, adoption signals are also strengthening. Stablecoin wallet growth has expanded dramatically since 2020, with hundreds of millions holding stablecoins via mainstream apps. Institutional intent is rising as well: a 2025 EY-Parthenon survey found that 54% of institutional non-users planned to adopt stablecoins within 6–12 months.
Stablecoin Adoption Signals and Momentum
Concrete demand signals (public estimates; directionally useful, not exact):
- Stablecoin market size: ~US$308B total market capitalisation as of Aug 2026 (Reap Global, 2026).
- Usage quality matters: Deutsche Bank (2026) estimates that while total stablecoin transaction volume can look very large, a smaller subset reflects “real payments” once non-economic activity is excluded.
- Adoption intent: EY-Parthenon (2025) survey cited above—54% of institutional non-users planned adoption within 6–12 months.
- RFP pressure: correspondents/counterparties increasingly treat digital-money connectivity as a qualifier, not an experiment—shifting the decision from product teams to mandate strategy.
Taken together, these signals suggest that banks are being pulled into digital money from both directions: clients seeking better service levels and market participants demanding interoperable rails.
Step 7: The Risks of Not Adopting Digital Solutions
The risk of inaction in 2026 is not simply “missing a trend.” It is losing relevance in flows where speed, programmability, and 24/7 operations are becoming expected. Stablecoins, in particular, do not require bank adoption to reach customers. That creates a new competitive threat: banks can be bypassed for certain payment and settlement use cases even when the underlying demand is mainstream (cross-border payments, treasury movement, settlement outside banking hours).
There is also a commercial risk tied to mandates. If correspondents and counterparties increasingly treat digital-money connectivity as an RFP requirement, banks without tokenised deposit and/or stablecoin capability may be screened out before pricing or relationship strength even comes into play.
Operationally, banks that remain bound to legacy cut-offs and multi-day settlement cycles may struggle to serve clients who are building always-on businesses. The direction of travel is toward real-time visibility, reduced manual reconciliation, and liquidity that does not sit idle across entities. If competitors can offer those outcomes—whether via tokenised deposits, stablecoins, or both—then “not adopting” becomes a measurable disadvantage rather than a philosophical stance.
Risks of Delayed Action
Cost of inaction (risk → impact → leading indicators to watch):
- Disintermediation in cross-border flows → fee and deposit leakage → clients routing value via non-bank rails; declining share in FX/payment corridors.
- Mandate exclusion → lost RFPs before pricing → more “must-have connectivity” questions in RFPs; shorter shortlists.
- Operational mismatch with 24/7 commerce → client churn in high-velocity segments → rising exception volumes around cut-offs; increased manual reconciliation headcount.
- Fragmented digital-asset strategy → higher future integration cost → duplicated pilots; multiple incompatible vendor stacks; unclear ownership of controls/runbooks.
Step 8: Navigating Regulatory and Policy Considerations
No technology alone can overcome regulatory and policy constraints. Even as frameworks mature, the global picture remains fragmented. Stablecoin rules differ across the US, EU, and Asian financial centres; tokenised deposits may be treated as familiar bank liabilities in one jurisdiction and as a novel instrument requiring new oversight in another.
Policy considerations also intersect with settlement safety. Central bank money remains the safest settlement asset because it eliminates credit risk at the point of settlement. Both stablecoins and tokenised deposits introduce commercial-bank or issuer credit exposure, which can be mitigated by settlement layers anchored in central bank reserves. This is one reason discussions about wholesale settlement infrastructure continue alongside private digital money adoption.
For banks, the practical navigation challenge is multi-dimensional: compliance design (KYC/AML and governance), prudential treatment, cross-border legal enforceability, and interoperability across networks and venues. The strategic takeaway is that “multi-rail” is not only a product strategy; it is also a risk strategy—matching instruments to jurisdictions, use cases, and settlement expectations.
| Jurisdiction / theme | Stablecoins (2024–2026 snapshot) | Tokenised deposits (2024–2026 snapshot) | Practical implication for banks |
|---|---|---|---|
| European Union | MiCA effective 2024; requirements for issuers and reserves; caps on certain non-euro stablecoin activity (Deutsche Bank, 2026 summary of MiCA constraints) | Often treated as bank liabilities under existing regimes, but implementation details vary | Design EU distribution, reserves, and reporting early; don’t assume a “global” stablecoin model ports cleanly |
| United States | GENIUS Act (July 2025) created a federal framework for payment stablecoins (as cited in industry summaries) | Typically fits within existing banking oversight when structured as deposits | Product teams need a clear issuer model and supervisory alignment; avoid mixing models without governance clarity |
| Key Asia financial centres (e.g., HK/SG/JP) | Distinct regimes with different issuer and reserve expectations (Reap Global, 2026 overview) | Treatment can vary; some markets view as familiar deposits, others as novel instruments (Fnality, 2026) | Plan for jurisdiction-by-jurisdiction rollout and controls; “one compliance design” rarely works |
| Settlement safety (cross-cutting) | Introduces issuer credit exposure at settlement | Introduces bank credit exposure at settlement | Where possible, align settlement design to safer anchors and strong risk controls (Fnality, 2026) |
Conclusion: The Future of Digital Money in Banking
Embracing Innovation
By 2026, tokenised deposits and stablecoins are increasingly framed as complementary building blocks rather than competing ideologies. Tokenised deposits bring programmability inside the regulated balance sheet; stablecoins bring cross-border reach and real-time movement across networks. Banks that combine them can cover more of the client journey—from internal liquidity orchestration to external settlement and payments—rather than owning only one leg of the flow.
Navigating Regulatory Landscapes
Regulatory clarity has improved in key markets, but fragmentation persists. MiCA in the EU and the GENIUS Act in the US illustrate momentum toward formal frameworks, while other jurisdictions continue to evolve their approaches. For banks, success depends on treating compliance, governance, and settlement design as core product features—not afterthoughts.
Building a Competitive Edge
The competitive bar is rising. Demand is being driven by clients and by market participants who increasingly expect interoperable digital-money connectivity. As tokenised deposits and stablecoins move into production for use cases like real-time cash concentration and instant DvP, the question for banks becomes less about whether digital money matters—and more about whether they can deliver it safely, compliantly, and at the service levels modern finance now expects.
Signals to Revisit Strategy
As of 2026, what to watch next (signals that strategy needs an update):
- Interoperability: whether tokenised deposit networks become meaningfully multi-bank/multi-venue rather than closed loops.
- Operating model maturity: which banks can truly run 24/7 with clear liquidity, controls, and incident runbooks.
- Regulatory convergence (or not): whether cross-border stablecoin rules become more harmonised—or remain corridor-specific.
- “Real payments” growth: whether stablecoin usage continues shifting from trading/venue activity toward measurable commercial payment flows.
This perspective is informed by Martin Weidemann’s work building and scaling technology-driven businesses in regulated environments—particularly across payments and digital transformation—where interoperability, settlement design, and operational risk are practical constraints, not abstract concepts.
This article reflects publicly available information as of 2026. Regulatory frameworks and market practices for stablecoins and tokenised deposits are evolving quickly and may differ materially by jurisdiction and use case. Any market figures cited are best read as directional estimates rather than precise measurements, and details may change as new information emerges.
I am MartĂn Weidemann, a digital transformation consultant and founder of Weidemann.tech. I help businesses adapt to the digital age by optimizing processes and implementing innovative technologies. My goal is to transform businesses to be more efficient and competitive in today’s market.
LinkedIn

