Bank Readiness: The Supply Side of Stablecoin Adoption
What U.S. banks are planning, prioritizing, and waiting on — the view from inside the institution.
POC Version 0.6 — May 13, 2026. Based on American Banker’s 2026 Value of On-Chain Survey (199 banking professionals, Feb 2026) and the Finzly/American Banker Setting the Stage for Tokenized Money white paper (105 institutions, April 2026, drawn from the same survey). Findings checked against the full text of all three American Banker parts and the Finzly white paper (October 2026). Additional sources needed to complete this section — see “What This Section Still Needs.”
The Use Cases section of this guide covers demand — the corporations, treasury teams, and fintechs evaluating or deploying stablecoin rails for cross-border payments, supplier settlement, and liquidity management. This page covers the other side of the equation: supply. Specifically, what are U.S. financial institutions doing internally to build, pilot, or position for on-chain infrastructure? How far along are they? What is stopping the ones that haven’t moved yet? And what does their planning posture look like heading into the second half of 2026?
The distinction matters in ways that go beyond taxonomy. A bank moving from “pilot” to “production” with a stablecoin product is a fundamentally different event than a corporate treasurer switching settlement rails. The bank action creates new institutional infrastructure — rails that other companies and individuals can then use. Both signals matter for assessing adoption trajectory, but they operate on different timelines and with different risk calculus. American Banker’s 2026 Value of On-Chain Survey — fielded in February 2026 among 199 banking professionals across banks, credit unions, online-only bank divisions, and neobanks — provides the most comprehensive contemporaneous snapshot of institutional planning posture available. February 2026 was also the month the GENIUS Act’s final rulemaking timeline became clear and the OCC issued its proposed rulemaking on stablecoin activities, making the survey a genuine moment-in-time reading of where banks stood as regulatory clarity approached. [AB]
Adoption Status by Institution Size
The headline figure from the American Banker survey: about 30% of respondents’ institutions have already implemented or are piloting on-chain technology, and another 15% are in early internal discussions. [AB] The remaining majority are at some stage of awareness, planning, or deliberate waiting. On its face, 30% sounds like a minority — but the number requires context to interpret correctly.
The largest banks are the biggest users of on-chain technology, while community banks and credit unions remain in early planning stages. [AB] This means the 30% implementation and pilot figure is heavily weighted toward the top of the asset distribution. The institutions that have moved are disproportionately large by assets under management — so even if 70% of institutions by count are still watching, the institutions that are moving likely represent the significant majority of U.S. banking assets. The 30% number is not a measure of how many banks have moved; it is a measure that the banks with the most resources and the most client relationships at scale have moved first, which is the expected adoption pattern for capital-intensive infrastructure investments.
National banks are the most eager to issue stablecoins; community banks and credit unions are the least likely. [AB] The hesitation among smaller institutions is structural, not simply cultural. Building or buying on-chain infrastructure requires upfront investment in technology, compliance, and staff training — costs that are harder to justify without the transaction volumes and client scale to generate returns. Community banks and credit unions also face a more ambiguous regulatory path under the GENIUS Act, where the $10 billion asset threshold separates federal from state licensing requirements, adding uncertainty and cost for smaller institutions considering issuance.
Despite the size gap, competitive pressure is registering as a real motivator across institution types. [AB] The survey found that failing to participate in on-chain technology could mean losing a competitive edge — a finding consistent with how prior payment rail shifts (ACH adoption, real-time payments, mobile banking) played out. First movers build client habits and vendor relationships that are difficult to displace later. About half of respondents felt their clients are already ready for on-chain products, suggesting that demand-side pressure is visible to bankers even where internal readiness lags. [AB]
Top Use Cases: What Banks Are Building
Cross-border payments are the leading on-chain use case for individual consumers, and cross-border functionality is simultaneously a high priority for business client-facing applications. [AB] This convergence across both retail and B2B segments is notable: it suggests banks are not segmenting their on-chain investment thesis by customer type but are instead identifying cross-border payment friction as a universal pain point that a single infrastructure investment can address across segments.
For business clients, the use cases most often enabled, piloted or planned within 12 months are cross-border payment rails (41%), payout and disbursement rails (37%), merchant payments (34%), wholesale payments (34%) and tokenized deposits (30%). [AB] These map directly onto what corporate treasurers and finance teams identify as their highest-friction workflows — creating a genuine supply-demand alignment that is often absent in early-stage payment technology cycles. Payments and settlement efficiency is seen as the greatest near-term and long-term value from on-chain adoption — the same thesis holds across both time horizons, which is unusual and suggests this isn’t speculative positioning but a more durable conviction. [AB]
Retail and mass-market customers are the most common focus of institutions’ on-chain strategies (35%, ahead of institutional investors at 24% and small businesses at 20%), and faster payments (82%) and lower transaction costs (73%) are the top expected consumer benefits. [AB] Banks see on-chain rails as a way to compete on speed and cost in consumer payments, where non-bank fintechs and neobanks have made inroads precisely by reducing friction and fees.
The near-term return case is concentrated but not unanimous. Payments and settlement efficiency is the top expected near-term return (40%), well ahead of client retention or acquisition (18%), a new revenue stream (12%), back-office automation (10%) and cost reduction (9%); 8% expect no near-term value. [AB] Over the long term, payments and settlement efficiency (67%) narrowly leads cost reduction (65%) and client retention (62%). Cross-border payments lead the use-case lists for both consumers (43%) and businesses (41%), a plurality rather than a majority.
These bank-prioritized use cases align closely with the Field Guide’s five demand vectors. The top use cases banks are building for — cross-border payments, treasury management, and settlement efficiency — map directly onto Vector 1 (Cross-Border Payment Friction), Vector 2 (Treasury and Liquidity Efficiency), and Vector 3 (Merchant and Commerce Settlement). The convergence between supply-side bank priorities and demand-side corporate pain points is a meaningful signal: when what banks are building matches what corporate clients say they need, the adoption curve tends to accelerate once infrastructure reaches baseline reliability and regulatory clarity arrives.
What Is Holding Banks Back
Regulatory uncertainty is the top blocker. The survey is unambiguous: regulatory clarity is the single change executives most need before they will advance on-chain adoption internally. [AB] This is a solvable problem with a known timeline. The GENIUS Act passed committee in early 2025 and its rulemaking process accelerated through late 2025 and into 2026. The OCC issued proposed rules on bank stablecoin activities in February 2026 — the same month the survey was fielded. Final OCC rules are expected mid-to-late 2026. Many of the institutions that cited regulatory uncertainty as a blocker in February were almost certainly waiting specifically for that rulemaking to complete before greenlighting internal deployments. The blocker is real, but it has a resolution timeline that is now measurable in months rather than years.
Legacy systems are the second major blocker. [AB] This is structurally harder than the regulatory question. Core banking systems at many U.S. institutions were built for batch processing and are not natively compatible with the real-time, atomic settlement model that on-chain rails require. Integrating on-chain capabilities into existing infrastructure requires either middleware layers, core system upgrades, or wholesale platform migration — all of which involve multi-year timelines and significant operational risk. The legacy systems blocker is one reason the “unified money platform” thesis discussed in the next section is gaining traction: rather than bolting on-chain capabilities onto legacy cores, some institutions are choosing to rebuild the underlying infrastructure with multi-rail support from the ground up.
Risk concerns present a nuanced picture. While on-chain payment rails reduce costs, many respondents feel that higher levels of risk are introduced by the technology. [AB] The risks in question span smart contract security, key management, counterparty risk in digital asset settlement, and the operational risk of running systems that are less mature than decades-old ACH infrastructure. These are legitimate engineering and operational concerns, not reflexive conservatism, and they suggest that banks moving to production will invest heavily in risk controls before exposing client assets to on-chain rails.
Client demand creates a productive tension with these blockers. The survey found client demand is the top motivator for public digital-asset services such as loyalty tokens (62%) and business custody (61%), while long-term revenue potential leads for tokenization, including tokenized deposits for business clients (63%). [AB] Banks are facing pull from corporate clients and, in some segments, retail customers who are already using stablecoin or crypto rails outside the banking system. The dynamic mirrors earlier payment technology cycles: banks that were slow to offer real-time payment options watched fintech competitors capture transaction volume. Regulatory clarity arriving in 2026 is likely to compress the window between “watching” and “deploying” for institutions that are otherwise ready.
Infrastructure Convergence: The Unified Money Platform
The Finzly/American Banker white paper draws on a subset of the same survey: 105 respondents at institutions at least in early discussions about on-chain technology, surveyed in January and February 2026. Its headline finding is intent: 79% agree that handling traditional and tokenized money on a single unified platform is important, from 72% at community banks to 82% at credit unions. [FZ] The paper’s readiness measure is not used here because its text (“only one in four” prepared to support tokenized deposits) and its own chart (53% overall) disagree. The survey’s firmer readiness measure is the 30% implemented or piloting reported above. [AB]
The intent points away from bolt-on point solutions, which the paper says many institutions used for instant payment rails, and toward a single ledger and money-movement layer for fiat and tokenized value. [FZ] That is a different investment thesis than “add a stablecoin product.” It is a thesis about rebuilding how a financial institution moves and accounts for money. Readiness lags well behind that intent.
Finzly, a payments infrastructure vendor, sets out four requirements for that layer on its summary page for the report [FZ]:
- Real-time ledgering across all accounts and assets — a single ledger that reflects positions in fiat, tokenized deposits, and digital assets in real time, without reconciliation lag.
- Payment orchestration across rails — a routing and execution layer that spans ACH, RTP, FedNow, wire transfers, card networks, and on-chain rails, selecting the optimal rail per transaction rather than routing through a default.
- Atomic processing of transactions, balances, and settlement — the ability to execute, settle, and update the ledger in a single operation, eliminating the settlement window risk that exists in batch-processed systems.
- Interoperability between fiat systems and digital value — the plumbing to move value between traditional account infrastructure and on-chain environments without manual intervention or multi-day settlement cycles.
Dean Nolan, Head of Payment Strategy at Finzly, framed the relationship between the “what” and the “how” directly: “If tokenized deposits are the ‘what,’ then real-time ledgering and payment orchestration are the ‘how.’” [FZ]
The gap between 79% intent and about 30% implementing or piloting has a direct implication for stablecoin adoption timing. Once a bank has a unified ledger that handles ACH, FedNow, and on-chain rails in the same system, adding stablecoin or tokenized-deposit settlement becomes an incremental product decision rather than an infrastructure overhaul. Most institutions evaluating on-chain technology have reached the same architectural conclusion, but most have not yet built the precondition. [FZ] [AB]
Stablecoin Issuance Intent by Institution Type
National banks are the most eager to issue stablecoins; community banks and credit unions are the least likely to do so. [AB] The divergence reflects differences in scale, regulatory positioning, and strategic incentive. Large national banks have the transaction volume to justify the compliance infrastructure, technology investment, and liability management that proprietary stablecoin issuance requires. They also have the most to gain from controlling a stablecoin instrument that sits at the center of their clients’ payment workflows.
The GENIUS Act’s $10 billion asset threshold is directly relevant to the issuance calculus. Institutions above $10 billion would be regulated under a federal framework; those below would navigate state-level licensing requirements. For the large number of U.S. banks and credit unions below that threshold, the state-level path adds regulatory fragmentation and cost that makes proprietary issuance a harder business case to justify.
The OCC’s conditional charter approvals for Circle, Ripple, Paxos, and BitGo in December 2025 changed the competitive environment in ways that affect the build-vs.-partner calculus for banks of all sizes. Non-bank stablecoin issuers are now being brought into a regulated framework, which means banks considering proprietary stablecoin issuance are no longer simply competing with unregulated crypto entities — they are competing with regulated, OCC-chartered issuers that have years of stablecoin operations experience and established market share. This raises the bar for proprietary bank issuance while simultaneously making partnership with a licensed issuer a more credible and strategically defensible option.
For the largest national banks, the picture is one of proprietary intent. JPMorgan has moved JPMD from pilot to production-scale use. Wells Fargo has trademarked WFUSD. Bank of America has a stablecoin product in development. These institutions have made their positioning clear. For community banks, credit unions, and mid-size regional banks, the more likely path is accessing on-chain rails through infrastructure providers — Finzly, Zero Hash, Ripple Payments, and similar platforms — rather than issuing proprietary instruments. The issuance intent data from the AB survey maps onto this structural reality: the institutions that are eager to issue are the ones with the scale and regulatory positioning to make it work; the institutions that are hesitant are the ones for whom the partnership model is the rational alternative.
What This Section Still Needs
This page is a POC. The following gaps are identified transparently for reviewers and potential contributors:
- Full AB survey data. The full text of all three American Banker articles is now on file and the figures on this page are checked against it. The underlying dataset, with breakdowns for every question by institution type and size, is not published; the articles report selected breakdowns only.
- McKinsey on-chain banking analysis. The AB ON-CHAIN conference site references a McKinsey estimate that global banks hold over $10 trillion in trapped capital across nostro accounts that on-chain settlement could free. The primary McKinsey source has not been independently located and verified. This figure, if sourced, would anchor the treasury and liquidity section with authoritative third-party data that is independent of the AB and Finzly surveys.
- OCC charter tracking data. Circle, Ripple, Paxos, and BitGo received OCC conditional banking charter approvals in December 2025. A systematic tracking page — showing which institutions have received approvals, which have applied, and which have declined — would quantify the “regulatory clarity arriving” thesis with primary regulatory data rather than reported summaries.
- Community bank and credit union perspective. Both the AB survey and the Finzly report skew toward institutions that are actively exploring on-chain technology. A complementary data source covering institutions that have explicitly evaluated and decided not to pursue on-chain technology — and their stated reasons — would complete the picture and prevent selection bias from distorting the bank readiness narrative.
- International comparison. How does U.S. bank readiness compare to EU banks operating under the MiCA framework, or to banks in Singapore, the UAE, and Hong Kong where stablecoin regulatory frameworks are further along and in some cases already producing live production deployments? The GENIUS Act debate is frequently framed as a U.S. competitiveness issue; data on comparable institutions in more advanced regulatory jurisdictions would make that argument concrete.
Three specific sources worth prioritizing for the next version:
- McKinsey “Global Payments Report” 2025 or 2026 — for nostro account capital data and cross-border payment economics that would independently corroborate the treasury efficiency thesis.
- FDIC or OCC supervisory data on bank on-chain technology filings, no-action letters, or supervisory guidance issued — to document the regulatory environment from the regulator’s perspective rather than the industry’s.
- SWIFT data on correspondent banking volume trends — as baseline context for the displacement thesis. If correspondent banking volume is declining, that is independent evidence of structural pressure on the legacy cross-border payment model that on-chain rails are positioned to replace.
Sources
- [AB] American Banker (Arizent) — 2026 Value of On-Chain Survey, 3-part series. 199 banking professionals, February 2026. Frank Gargano, Data Reporter. Parts published March 24, 27 and 31, 2026. Part 1 (paywall) · Part 2 (paywall) · Part 3 (paywall)
- [FZ] Finzly / American Banker (Arizent) — Setting the Stage for Tokenized Money, white paper, April 2026. 105 respondents at banks, credit unions, online-only bank units and neobanks at least in early discussions about on-chain technology, surveyed January–February 2026 as part of The Value of On-Chain 2026. Finzly summary
Page History
8 reader-facing changes since 2026-05-29; last change 2026-10-13 (v1.0).
Show all changes
| Date | Release | Change |
|---|---|---|
| 2026-10-13 | v1.0 | Finzly entry 8 segment figures per Figure 1; drop readiness figure (text and Figure 2 disagree) |
| 2026-10-13 | v1.0 | Finzly/American Banker (entry 8) checked against white paper PDF: 79% not 80%, 105 respondents, April 2026, same survey as entry 7; add 25% readiness figure |
| 2026-10-13 | v1.0 | American Banker survey (entry 7) and Bank Readiness checked against full article text; remove two unsupported claims, add survey figures |
| 2026-07-12 | v0.8 refresh | Added Use Case Overview, Updated Use Case pages, and a Roadmap section. |
| 2026-07-10 | v0.8 refresh | Updated main page data |
| 2026-07-01 | v0.8 | v0.8: Batch 4 content integration — 57-company directory, regulatory, history, use cases, digest, research sources |
| 2026-06-06 | v0.8 | v0.7: [describe your changes] |
| 2026-05-29 | v0.7 | v0.6: initial commit - 1st MkDocs build, all docs as of 05-14-2026 |
Infrastructure and formatting commits are omitted. Release-level detail is in the Release Notes.