Jack Henry & Associates announced on October 16, 2026 that it had become the first core technology provider to integrate its platform with Google Cloud Universal Ledger, a permissioned blockchain purpose-built for institutional settlement. The move opens tokenized deposit capabilities to more than 7,200 community and regional banks and credit unions that rely on Jack Henry’s core banking software — institutions that have largely watched large-bank experiments in programmable money from the sidelines.
Jack Henry’s collaboration with Google Cloud dates to 2022, when the company began migrating its core infrastructure to the cloud. That partnership expanded in June 2026 with a broader fintech development agreement. The October 16 announcement takes that collaboration into settlement infrastructure, giving community banks a credible path to deploy tokenized deposits without building proprietary blockchain systems.
What Tokenized Deposits Are — and Why Community Banks Have Been Locked Out
Tokenized deposits are digital representations of existing bank deposits recorded on a distributed ledger. They are not stablecoins. Stablecoin holders do not receive deposit insurance under the current federal framework; tokenized deposits, by contrast, remain liabilities of the issuing bank, sit on the bank’s balance sheet, and are expected to carry FDIC insurance as conventional deposits do. The GENIUS Act stablecoin framework, signed in July 2025, governs payment stablecoins and explicitly does not apply to tokenized deposits, which remain governed by existing banking law.
The distinction matters commercially. Community banks already hold their customers’ deposits. Tokenizing those deposits does not require a new instrument or a new regulatory license — it requires infrastructure. That infrastructure has, until now, been inaccessible to most institutions below the top tier of global banking. State banking regulators, through the Conference of State Bank Supervisors, formally requested clarification from the FDIC, the Federal Reserve, and the OCC in November 2025 on seven open questions about tokenized deposits, acknowledging that the gap between the regulatory framework for stablecoins and the one for tokenized deposits creates uncertainty that has slowed community bank adoption.
JPMorgan began testing JPM Coin institutional deposit functionality in 2019. Since then, large bank experiments in programmable settlement have proliferated. Community banks—which collectively manage trillions in deposits and serve most small-business lending relationships in the United States—have had no comparable entry point. The core problem is structural. Traditional interbank settlement requires institutions to pre-fund positions for every bilateral relationship they maintain, tying up capital as a prerequisite for participation. Tokenized deposit networks built on multilateral netting eliminate that drag — but only if the underlying infrastructure is connected to the institutions that need it.
How Google Cloud Universal Ledger Actually Works: Permissioned Layer-1, Python Smart Contracts, No Pre-Funding Required
GCUL is a permissioned Layer-1 blockchain — a distributed ledger with access controls that restrict participation to approved institutional counterparties. Unlike public blockchains such as Ethereum, GCUL does not require participants to interact with a native cryptocurrency or manage cryptographic wallets in the consumer sense. It operates on Python-based smart contracts, a deliberate design choice that lowers the technical barrier for financial institutions whose developers work in Python rather than Solidity.
The settlement architecture eliminates pre-funded account requirements through multilateral netting. Rather than requiring Bank A to pre-position funds at Bank B before a transaction can settle, GCUL offsets claims across all participating institutions before final settlement occurs. The net settlement amount — often a fraction of the gross transaction volume — then moves through existing payment rails. This design materially reduces the liquidity cost of participation, which is the primary economic reason community banks have found bilateral correspondent banking arrangements burdensome.
Google Cloud has positioned GCUL as an infrastructure layer rather than a competing financial product. The platform operates by leveraging existing commercial bank money rather than introducing a new form of value. Because Google Cloud itself has no competitive conflict to manage with bank deposit franchises, it can serve as a neutral substrate in a way that bank-operated platforms cannot. CME Group signed on as an early institutional partner and announced in March 2025 plans to use GCUL for tokenized asset settlement in capital markets.
Why Jack Henry’s 7,200-Institution Network Is the Missing Ingredient
Jack Henry’s platform serves more than 7,200 community and regional financial institutions. That scale transforms the commercial calculus for GCUL. A settlement network’s value is proportional to the number and diversity of institutions that can transact on it. A permissioned blockchain with three participating banks is a proof of concept. One with 7,200 institutions behind a single integration point is a viable settlement rail.
Ben Metz, Jack Henry’s Chief Technology Officer, said in the October 16 announcement that the integration is intended to give community banks access to programmable money capabilities that have previously been available only to larger institutions. James Tromans, Google Cloud’s director of Web3 and Digital Assets, framed Jack Henry’s network scale as a precondition for GCUL achieving meaningful settlement volume.
Google Cloud’s commercial strategy for GCUL centers on the network density thesis. According to Blockworks’ reporting on GCUL’s architecture and market positioning, the platform’s design as a credibly neutral infrastructure is intended to generate the broad institutional participation — across many currencies and institution types — that transforms a proof-of-concept network into a viable settlement rail. Network density — the number and variety of institutions participating on a shared ledger — determines whether programmable money becomes a live commercial capability or remains a perpetual pilot.
What This Means for a Community Bank — and Its Business Customers
For a community bank using Jack Henry’s core platform, this integration means access to tokenized deposit infrastructure without a separate procurement process or technology build. Jack Henry is offering tokenized deposit capabilities through its existing platform relationship, meaning the bank’s core system becomes the entry point to GCUL participation.
The commercial cases that become possible are ones that community banks have struggled to serve with conventional payment infrastructure: near-real-time settlement for business customers who currently wait days for ACH transactions to clear; programmable payment logic that can release funds automatically when delivery conditions are met; and intraday liquidity management that does not require correspondent bank relationships for every counterparty. The announcement describes Jack Henry as paving the way for tokenized deposits to reach community banking customers, signaling that live deployments are a target outcome rather than a distant aspiration.
What Regulators Have Not Yet Decided — and Why It Matters
The regulatory environment for tokenized deposits remains unsettled. The GENIUS Act, signed in July 2025, resolved the federal framework for payment stablecoins but left tokenized deposits in a statutory gap — governed by existing bank regulation but without specific guidance on the novel questions raised by programmable deposit infrastructure. Regulators have not yet clarified whether existing reserve requirements apply to tokenized deposits in the same way they apply to demand deposits, how smart contract-based payment logic interacts with Regulation E’s consumer protection rules, or what examination standards apply to banks offering tokenized deposit products.
The Conference of State Bank Supervisors submitted a formal comment letter to the three federal banking agencies in November 2025, identifying seven specific areas where joint guidance is needed. As of October 2026, that guidance has not been issued. Community banks considering GCUL integration through Jack Henry will need to navigate this uncertainty through their primary regulators and, in many cases, seek informal guidance before offering tokenized deposit products to customers.
Is This Ready to Cross Ledgers? The Interoperability Question
One limitation of any single-network tokenized deposit infrastructure is interoperability. A community bank’s business customer may have counterparties at institutions that do not participate in GCUL. DBS Bank and JPMorgan’s Kinexys division announced a cross-chain interoperability framework for interbank tokenized deposit transfers across multiple blockchains in late 2025, demonstrating that the industry recognizes network fragmentation as a structural problem. GCUL has not yet published a formal interoperability protocol.
The parallel development of tokenized deposit infrastructure across multiple networks and jurisdictions makes interoperability a medium-term commercial requirement for any tokenized deposit platform that aspires to be more than a closed-loop settlement system.
The Larger Picture
The Jack Henry announcement arrives as several competing infrastructure plays are emerging in institutional settlement. As Blockworks has documented, Stripe’s Tempo product and Circle’s Arc platform are also pursuing institutional tokenized settlement use cases. The competitive differentiation GCUL is pursuing — credibly neutral infrastructure controlled by a cloud provider with no deposit franchise — is a distinct positioning that may be particularly relevant for community banks whose relationship with large-bank-operated payment networks is structurally competitive.
Jack Henry’s 7,200-institution distribution network is the clearest near-term test of whether that thesis holds. If community banks adopt tokenized deposit capabilities at meaningful scale through the Jack Henry integration, GCUL will have demonstrated that the network density required for viable programmable settlement can be assembled through a single core banking integration rather than years of institution-by-institution negotiation.
Frequently Asked Questions
Are tokenized deposits the same as stablecoins?
No. Tokenized deposits and stablecoins are legally and structurally distinct instruments. A tokenized deposit remains a liability of the issuing bank, is recorded on the bank’s balance sheet, and is expected to carry FDIC insurance coverage in the same way a conventional deposit does. A stablecoin is typically a separate instrument issued by a non-bank entity. State banking regulators have CSBS formally requested guidance from the FDIC, Federal Reserve, and OCC specifically to clarify these distinctions in the context of emerging tokenized deposit products.
What regulatory guidance exists for community banks that want to offer tokenized deposits?
Federal joint guidance from the FDIC, Federal Reserve, and OCC on tokenized deposits has not yet been issued as of October 2026. The GENIUS Act, which established the federal stablecoin framework in July 2025, explicitly excluded tokenized deposits from its scope. The Conference of State Bank Supervisors has formally requested from regulators a joint guidance document addressing seven specific open questions, including reserve treatment, consumer protection rule application, and examination standards. Community banks will need to engage their primary regulators and likely seek informal guidance before launching tokenized deposit products.
What is Google Cloud Universal Ledger, and how is it different from a public blockchain?
GCUL is a permissioned Layer-1 blockchain operated by Google Cloud for institutional financial use. Unlike public blockchains such as Ethereum, GCUL restricts participation to approved institutional counterparties and does not require participants to hold or transact in a native cryptocurrency. It uses Python-based smart contracts for institutions, which lowers the technical barrier for financial institutions whose development teams work in Python. Settlement occurs through multilateral netting, which offsets claims between participants before final settlement, eliminating the pre-funded account requirements that characterize bilateral correspondent banking.
Why hadn’t community banks been able to access tokenized deposit infrastructure before this Jack Henry announcement?
Community banks lacked a distribution channel. Large banks such as JPMorgan built proprietary tokenized deposit infrastructure for their own institutional clients, but those networks were closed to competitors. Technology providers serving community banks had not built GCUL integrations, leaving smaller institutions without an access point. Jack Henry’s announcement is significant precisely because its 7,200-institution customer base means that a single integration now puts GCUL participation within reach of a large portion of US community and regional banks, none of which could have replicated this access independently before this Jack Henry announcement.
