US Regional Banks Launch Tokenised Deposit Network

Table of Contents


Regional banks develop regulated tokenised deposit network

  • Five US regional banks are piloting a permissioned blockchain platform for tokenised deposits called the Cari Network.
  • The pilot is slated for the third quarter, with a customer rollout planned for Q4.
  • The initial use case is moving money between customers of the participating banks.
  • Unlike stablecoins, the deposit tokens mirror normal bank liabilities and are intended to remain within bank regulation and FDIC insurance.

Digital Dollar Terms Explained
A quick primer on the “digital dollar” terms that often get mixed together:
– Tokenised deposits: a bank deposit represented as a token; the token mirrors a normal deposit liability of the bank.
– Stablecoins: typically a non-bank issued token designed to track a fiat currency; protections depend on the issuer’s reserves, legal structure, and oversight.
– CBDC: a digital form of central bank money (a direct liability of a central bank), not a commercial bank deposit.
Cari is positioning itself in the first category: bank-issued deposit claims represented in token form, moved on a permissioned network.

Overview of the Cari Network Initiative

A group of five US regional banks has joined forces to build a permissioned, blockchain-based platform designed to bring tokenisation into everyday banking deposits. The project—called the Cari Network—is positioned as a way for regional and community banks to offer clients functionality that resembles stablecoins, but within the traditional, regulated banking perimeter.

The core idea is straightforward: instead of relying on a non-bank issuer to create a digital dollar-like instrument, the network would enable banks to represent deposits as tokenised deposits—digital tokens that mirror standard bank deposit liabilities.

In other words, the “token” is a new representation of an existing bank deposit claim, rather than a separate, privately issued form of money. That distinction matters because it ties the digital instrument directly to the existing banking framework rather than creating a parallel system.

According to Finextra’s reporting (which cites Bloomberg), the network’s early focus is practical rather than expansive. Over time, the network could potentially connect to other networks, suggesting an ambition to expand interoperability beyond the founding group—though the first phase is deliberately contained.

The initiative arrives amid broader experimentation in digital assets and payments infrastructure, but Cari’s framing is explicitly conservative in one key respect: it aims to modernise payments while keeping insured deposits at the centre of economic activity, rather than shifting activity to non-bank money substitutes.

Tokenised Deposit Transfer Flow
How “deposit → token → transfer → redemption” typically works in a bank-led tokenised deposit model:
1) A customer holds a normal deposit at Bank A (no new money is created).
2) Bank A represents that deposit claim as a token inside the network (a digital representation of the same liability).
3) The token is transferred on the permissioned network to a recipient associated with Bank B.
4) Bank B credits the recipient’s deposit balance (and the network records the movement between member banks).
5) The tokenised representation is extinguished/updated so the customer experience remains “I sent dollars; they received dollars.”
Key checkpoint: the token is meant to track an underlying deposit claim at all times—so reconciliation, controls, and member-bank rules matter as much as the blockchain layer.

Participating Banks in the Tokenised Deposit Project

The founding participants in the Cari Network are:

  • First Horizon
  • Huntington Bancshares
  • KeyCorp
  • M&T Bank
  • Old National Bancorp

Together, these institutions represent a coordinated move by regional banks to develop shared infrastructure—rather than waiting for large national banks, card networks, or non-bank crypto-native firms to define the rails for tokenised money.

The collaboration is notable because it is explicitly designed to serve the needs of regional and community banks, which often face a strategic dilemma: customers increasingly expect faster, more digital payment experiences, but building new infrastructure independently can be costly and slow. A shared network can spread development and operational effort across multiple institutions while still keeping activity within the regulated banking system.

That starting point suggests a focus on immediate utility—bank-to-bank movement of funds within a defined membership—rather than an open-ended system where any participant can join without controls.

While the longer-term possibility of connecting to other networks has been raised, the early-stage design choice—permissioned access and a limited set of banks—signals a preference for controlled rollout, governance, and compliance alignment among known institutions.

Participating bank (as named) Role in initiative (per article) Notes readers often look up (not provided here)
First Horizon Founding participant / pilot bank Ticker, asset size, and HQ not specified in the article
Huntington Bancshares Founding participant / pilot bank Ticker, asset size, and HQ not specified in the article
KeyCorp Founding participant / pilot bank Ticker, asset size, and HQ not specified in the article
M&T Bank Founding participant / pilot bank Ticker, asset size, and HQ not specified in the article
Old National Bancorp Founding participant / pilot bank Ticker, asset size, and HQ not specified in the article

Timeline for the Cari Network Pilot and Rollout

The Cari Network’s timeline, as described by its leadership, is staged across two key milestones in 2026:

  • Pilot in the third quarter (Q3)
  • Planned rollout for customers in the fourth quarter (Q4)

This sequencing reflects a typical pattern for regulated financial infrastructure: test in a constrained environment first, then expand to customer-facing availability once operational readiness, controls, and user experience are validated.

The pilot phase is expected to involve the participating banks using the network. That limited scope can help isolate variables—such as transaction flows, settlement processes, and operational procedures—before scaling access more broadly.

The Q4 customer rollout target indicates that the project is not positioned as a distant research effort; it is being framed as near-term infrastructure intended for real-world use. At the same time, the initial rollout is not the end state, but rather a foundation that could be extended once the core model is proven.

In practical terms, the timeline also underscores the project’s emphasis on execution: a permissioned blockchain network for tokenised deposits is being treated as a deployable payments modernisation initiative, not merely an exploratory digital-asset experiment.

Phase (2026) What’s stated What that usually implies operationally
Q3 — Pilot Pilot among the five participating banks Controlled volumes, tighter participant set, heavier monitoring and reconciliation
Q4 — Customer rollout Planned rollout for customers Customer-facing UX, support processes, and clearer rules for exceptions/disputes
Beyond initial rollout Potential to connect to other networks (per Finextra citing Bloomberg) Interoperability work, governance expansion, and more complex risk/ops coordination

Regulatory Framework and Insurance for Deposit Tokens

Cari’s central differentiator—at least as described by the project—lies in how it treats the digital instrument itself. The network aims to provide stablecoin-like functionality, but with deposit tokens that mirror normal banking liabilities. That means the tokens are intended to be treated as bank deposits, not as a separate category of privately issued digital cash.

Two implications follow from that framing:

  1. Subject to bank regulations
    Because the tokens mirror standard deposit liabilities, they sit inside the regulatory expectations that apply to banks. The project’s messaging emphasises that innovation should strengthen the regulated banking system rather than displace it.

  2. FDIC insured
    The deposit tokens are described as FDIC insured, aligning them with the protections associated with insured deposits in the US banking system. This is a key contrast with many stablecoin structures, where the nature and extent of protections depend on the issuer’s reserves, legal structure, and oversight—factors that can vary widely.

The network’s permissioned design also fits this regulatory posture. A permissioned blockchain typically restricts participation to approved entities, which can support governance, compliance, and operational controls. In this context, permissioning is not just a technical choice; it is part of how the network aligns tokenised money movement with regulated banking norms.

In short, Cari is being positioned as a way to deliver digital-asset-style payment capabilities while keeping the legal and supervisory foundations of deposits intact—especially the concept that insured deposits remain “at the core of economic activity.”

Interpreting Key Claims in Practice
What the project’s key claims mean in practice (and what they don’t automatically guarantee):
– “Mirrors normal bank liabilities”
– Means: the token is intended to represent a standard deposit claim on a bank.
– Doesn’t automatically answer: how exceptions are handled (returns, disputes, mistaken payments) across multiple banks.
– “FDIC insured”
– Means: the project is positioning tokens as deposits eligible for the same insurance concept as insured deposits.
– Doesn’t automatically answer: how coverage is communicated in-app, how pass-through/ownership records are maintained, or how edge cases are treated.
– “Permissioned network”
– Means: only approved participants can validate/transact; governance can be aligned among known institutions.
– Doesn’t automatically answer: how quickly new members can join, or how interoperability is managed if/when other networks connect.

Initial Functionality of the Cari Network

The Cari Network’s initial functionality is intentionally narrow: it will first be used to move money between the participating banks’ own customers. That starting point matters because it defines the network as a payments and transfer rail—at least at launch—rather than a broad platform for trading, investing, or open-ended digital-asset activity.

By focusing on transfers among customers within the participating institutions, the network can deliver a stable, controlled environment for tokenised deposit movement. It also suggests that early success will be measured in operational reliability and customer experience, not in speculative adoption.

The network is also described as aiming to let banks offer clients similar functionality to stablecoins. While the project does not spell out feature-by-feature comparisons, the implication is that tokenised deposits could provide a digital representation of money that can move efficiently within the network—without stepping outside the banking system.

That suggests the architecture is being designed with potential interoperability in mind, even if the first deployment is restricted to the founding banks. If such connections materialise, they could expand the reach of tokenised deposit transfers beyond the initial group—though the project’s early emphasis remains on intra-network movement.

For now, the message is pragmatic: start with a defined set of banks, enable customer-to-customer money movement across those institutions, and build outward only after the core model is proven.

Initial Transfer Rail Requirements
Questions that clarify “initial functionality” for a customer-to-customer transfer rail (useful to confirm as details emerge):
– Who can send/receive on day one (retail, business, both)?
– Settlement expectations: real-time vs near-real-time vs batch windows?
– Operating hours: 24/7 transfers or bank-hours with cutoffs?
– Limits: per-transaction and daily caps, and whether they differ by customer type.
– Reversals and disputes: what happens with mistaken payments, fraud claims, or compliance holds?
– Fees and FX: any network fees, and whether cross-currency is in scope (often not at launch).
These checkpoints don’t change the core claim (bank customers moving money across member banks), but they determine how “stablecoin-like” the experience feels in practice.

Leadership and Vision Behind the Cari Network

The Cari Network is led by Gene Ludwig, its CEO and a former Comptroller of the Currency. That background is significant for a project that is explicitly positioning itself inside the regulated banking system rather than at its edges.

In a LinkedIn post, Ludwig framed the initiative’s philosophy in direct terms:

“Innovation in digital assets should strengthen, not displace, the regulated banking system. Tokenised deposits, built on sound blockchain infrastructure, can modernize payments while keeping insured deposits at the core of economic activity.”
Gene Ludwig, CEO of the Cari Network and former Comptroller of the Currency

This statement captures the network’s strategic stance: it is not pitching tokenisation as a replacement for bank deposits, but as a modernisation layer for how deposits can be represented and moved.

Ludwig’s emphasis on “sound blockchain infrastructure” and “insured deposits” also signals a balancing act. On one side is the push for innovation in payments and digital assets; on the other is the insistence that the foundation remains the existing banking model—regulated liabilities and deposit insurance.

That vision aligns with the choice of a permissioned blockchain platform and a consortium of regional banks. Rather than pursuing a permissionless approach associated with many crypto networks, Cari is being built as a bank-led system where participation, governance, and the nature of the money instrument are designed to fit established banking expectations.

Ludwig’s Regulatory Credibility Anchor
Why Ludwig’s background is central to Cari’s positioning:
– As a former Comptroller of the Currency, Ludwig is closely associated with bank supervision and the practical realities of operating inside US banking rules.
– That makes his “strengthen, not displace” framing more than marketing language: it signals the project is aiming for a design that can live comfortably within bank governance, controls, and supervisory expectations.

The Future of Banking: Embracing Tokenization

Understanding Tokenized Deposits

Tokenised deposits, as described in the Cari Network model, are digital tokens that mirror normal banking liabilities. The key point is not simply that money is represented digitally—bank balances already are—but that the representation is structured as a token on a blockchain-based platform, intended to move within a defined network.

Cari’s pitch is that this can deliver stablecoin-like functionality while remaining anchored to insured deposits and bank regulation. In that framing, tokenisation is less about creating a new kind of money and more about changing the rails and representation used to move existing bank money.

The Role of Regional Banks in Financial Innovation

The Cari Network highlights a particular dynamic in US banking: regional and community banks want to offer modern digital payment experiences without ceding the future of digital money to non-bank issuers or only the largest institutions.

By collaborating, the participating banks are effectively pooling effort to build shared infrastructure. The initiative suggests that innovation in payments is not solely the domain of global banks or technology firms; regional institutions can also coordinate to shape new models—especially when those models are designed to fit within existing regulatory and insurance frameworks.

Regulatory Considerations for Tokenized Assets

Cari’s approach is built around the idea that tokenised deposits should remain within the regulated banking system. The deposit tokens are described as being subject to bank regulations and FDIC insured, positioning them differently from many stablecoins.

The permissioned nature of the network also reflects regulatory realities: controlled participation can support governance and compliance expectations in a way that open networks may struggle to match. In this model, regulation is not treated as an obstacle to route around, but as a design constraint to incorporate from the start.

Benefits of a Permissioned Blockchain Network

A permissioned blockchain platform is designed for a known set of participants rather than the general public. For a consortium of banks, that can be a feature: it enables a shared ledger-like infrastructure while maintaining control over who can transact and under what rules.

In the Cari context, permissioning aligns with the network’s stated goal of strengthening the regulated banking system. It also fits the initial rollout plan—moving money between customers of participating banks—where the priority is likely predictable operations and governance rather than open access.

Challenges and Opportunities Ahead

Cari’s near-term opportunity is clear: prove that tokenised deposits can support real money movement between customers of multiple banks.

The longer-term opportunity—connecting to other networks—could expand reach and utility, but it also raises questions of coordination and integration that typically become more complex as networks grow. For now, the project’s staged approach suggests it is prioritising execution and controlled scaling.

What stands out is the broader signal: tokenisation is increasingly being framed not only as a crypto-native concept, but as a tool banks themselves can use to modernise payments—while keeping insured deposits and regulation at the centre of the system.

Tokenised Deposits: Gains and Gaps
What tokenised deposits can improve—and what remains hard:
– Potential upsides
– Faster, more programmable movement of bank money within a governed network.
– Bank-led model keeps deposits and supervision central (rather than shifting activity to non-bank instruments).
– Shared infrastructure can reduce “each bank builds alone” duplication for regional institutions.
– Open questions / trade-offs
– Interoperability: connecting networks can multiply complexity (rules, messaging standards, settlement conventions).
– Governance: permissioning helps control risk, but can slow expansion and requires strong member alignment.
– Operations: disputes, reversals, fraud handling, and customer support often determine real-world success more than the ledger technology.
– Adoption: customers may only notice value if speed, availability, and user experience beat existing rails.

From the weidemann.tech editorial perspective, this kind of bank-led, permissioned approach is most interesting when evaluated through real payments operations—how governance, dispute handling, and risk controls hold up once customer flows move from pilot to production.

This article reflects publicly available information at the time of writing. Some operational details—such as limits, hours, reversals, and interoperability—were not disclosed and may evolve as the pilot progresses. Updates should be guided by what participating banks and the network publish as the rollout moves toward customer availability.

Scroll to Top