Why Banks Are Tokenizing: The Business Case Beyond the Hype

The narrative around bank tokenization has consistently overstated the ideological and understated the commercial. Banks have not adopted blockchain because they found the technology philosophically compelling or because they wanted to participate in the decentralised finance revolution. They have adopted it because specific, quantifiable business problems — settlement risk, collateral inefficiency, compliance overhead, distribution cost — have become large enough, and the DLT solutions credible enough, that the cost-benefit calculation shifted.

Understanding why banks are tokenizing is not an academic exercise. It determines the compliance requirements that the tokenized financial market will generate, the platforms and infrastructure that will receive regulatory investment, and the standards that programmes operating in this market must meet.

There are four genuine business reasons. This analysis examines each, with the specific bank programmes that validate them and the compliance implications that follow.

Reason One: Settlement Efficiency — From T+2 to T+0

The conventional securities settlement cycle — T+2, meaning trades settle two business days after execution — is not a technological constraint. It is a legacy of the paper-era processing times that the DTCC and its predecessors were designed to handle. In a world of electronic trading, T+2 settlement creates costs that are large, systemic, and widely underestimated by those outside the securities operations function.

The primary cost is settlement risk: the two-day window between trade execution and settlement creates bilateral exposure between counterparties that must be collateralised through margin. In the US equity market alone, the aggregate daily margin requirement at DTCC runs to tens of billions of dollars. This collateral serves no economic function except hedging a risk that exists only because settlement is slow.

DLT-based settlement enables T+0 — or more precisely, delivery-versus-payment simultaneous with trade execution — eliminating the settlement lag and with it the margin requirement that it generates. The SEC’s mandate for US equity markets to move to T+1 settlement (implemented May 2024) was a step toward this goal using conventional infrastructure. DLT-based settlement goes further, enabling programmable, atomic settlement where the transfer of securities and cash occurs simultaneously and irrevocably.

Broadridge DLT Repo: Broadridge’s Distributed Ledger Repo (DLR) platform is the most scaled validation of DLT settlement efficiency in the market. The platform enables bilateral repo transactions to be executed, settled, and unwound intraday on a DLT rail, providing settlement finality faster than conventional tri-party repo processes. Over 20 major financial institutions — including Goldman Sachs, HSBC, and Société Générale — participate. Cumulative notional has exceeded $1 trillion.

The compliance implication of DLT-based settlement efficiency is underappreciated. Faster settlement reduces settlement risk, which reduces the margin requirement, which reduces the collateral obligation. But it also compresses the window in which compliance checks — sanctions screening, AML monitoring, transaction reporting — must be completed. A T+0 settlement system requires compliance checks to be completed in near real-time, not in a batch process run overnight. Compliance infrastructure must be designed for atomic settlement if it is to be fit for purpose in a DLT settlement environment.

JPMorgan Kinexys: Kinexys (formerly Onyx) processes intraday repo transactions and cross-border FX payments for JPMorgan institutional clients at $2 billion+ daily volume. The system’s primary value proposition is intraday settlement finality — enabling firms to reuse collateral multiple times within a single day, rather than having it locked in a single overnight transaction. Kinexys demonstrates that the settlement efficiency argument is not theoretical; it is generating $2 billion in daily transaction volume for a single bank’s institutional clients.

Reason Two: Collateral Mobility — The $10 Trillion Opportunity

Collateral management is one of the largest operational challenges in institutional finance. Global regulatory requirements — Basel III, EMIR margin rules, Dodd-Frank variation margin requirements — have driven the total collateral obligation in the financial system to tens of trillions of dollars. A material portion of this collateral is misallocated: high-quality liquid assets (HQLA) sitting in one entity that needs collateral elsewhere in the financial system, with mobilisation delayed by settlement cycles, operational friction, and geographic constraints.

The Bank for International Settlements has estimated that collateral mobilisation inefficiency costs the global financial system billions of dollars annually in excess margin, idle assets, and operational overhead. The problem is structural: collateral is posted before settlement cycles confirm receipt; cross-border collateral transfers face multiple-day delays; different market segments (equity repo, derivatives variation margin, securities lending) operate in parallel collateral silos that cannot easily be connected.

DLT resolves the mobility problem by enabling near-instantaneous transfer of tokenized assets as collateral, with delivery-versus-payment mechanics that eliminate the timing mismatch between collateral posting and confirmation. A tokenized money market fund share that serves as repo collateral at 9:00 AM can be returned, re-tokenized, and reposted as derivative variation margin at 2:00 PM on the same day — a transaction that would take two business days in a conventional settlement environment.

JPMorgan Token Collateral Network (TCN): JPMorgan’s $215 million pilot using tokenized BlackRock MMF shares (BUIDL) as intraday repo collateral between JPMorgan and Goldman Sachs was the first institutional validation of this use case at a material scale. The transaction used BUIDL tokens — held in Securitize’s infrastructure on Ethereum — as collateral in a Kinexys-settled repo, creating a bridge between public blockchain assets and JPMorgan’s permissioned settlement network.

The compliance implications of cross-platform collateral mobility are significant. When a tokenized asset moves from the Ethereum public chain to JPMorgan’s Kinexys network as collateral, the compliance metadata — investor eligibility verification, AML status, sanctions screening — must travel with it or be independently verified at each platform boundary. The absence of a universal compliance metadata standard for cross-platform asset transfers is one of the most significant open compliance architecture problems in institutional tokenization.

Reason Three: Programmable Compliance — ERC-3643 and the End of Manual Transfer Restriction

The third business reason is less frequently cited in banking press releases but is arguably the most consequential for the compliance profession: tokenization enables compliance rules to be encoded directly into the asset, rather than enforced through manual processes and contractual obligations.

This is what “programmable compliance” means in practice. Consider the conventional mechanism for enforcing a transfer restriction on a private placement security. A US Regulation D offering imposes resale restrictions on purchased shares — they cannot be resold to non-accredited investors, and they are subject to a six-month holding period. In a conventional offering, these restrictions are enforced by:

1. A legend on the stock certificate (or book-entry note)
2. A contractual representation from the buyer
3. The transfer agent’s manual review of each proposed transfer
4. Legal counsel opinion for non-exempt transfers

This process is expensive (legal opinion costs), slow (days to clear), error-prone (manual review misses edge cases), and dependent on counterparty compliance (contractual restrictions are only as good as the counterparty’s willingness to comply).

Token standards like ERC-3643 — the open standard for compliant tokenized securities — enable transfer restrictions to be enforced by the smart contract itself. The contract maintains an on-chain identity registry of verified, whitelisted wallets. A transfer instruction to a non-whitelisted wallet is rejected automatically, at the protocol level, with zero processing cost and zero possibility of human error. The transfer restriction is not a contract term dependent on counterparty compliance; it is a technical fact of the asset’s architecture.

This has several compliance implications:

Transfer restriction enforcement becomes auditable and immutable. Every attempted and completed transfer of a restricted token is recorded on-chain, creating an immutable compliance audit trail. Regulators examining compliance with transfer restrictions can query on-chain data rather than depend on paper records maintained by a transfer agent.

KYC/AML can be performed once, not at every transfer. If the whitelisting process includes rigorous KYC/AML verification of each wallet address, the compliance burden at each subsequent transfer is reduced to confirming that the destination wallet is on the whitelist — a check performed automatically by the smart contract. This does not eliminate ongoing AML monitoring obligations (which are perpetual), but it reduces the per-transaction compliance overhead significantly.

Compliance rules can be updated without document amendments. If a fund’s distribution policy changes — the eligibility criteria for investors are modified, a new jurisdiction is added or removed — the whitelist can be updated by the transfer agent without requiring amendment of subscription agreements or re-execution of legal documentation. The compliance change is immediate and effective across all existing token holders.

BlackRock BUIDL uses this model — Securitize’s compliance infrastructure maintains the whitelist, and the ERC-3643-compatible smart contract enforces it. This is the institutional compliance template described in our BUIDL analysis; its significance for the compliance profession is that it shifts compliance burden from per-transaction manual review to per-investor one-time verification with automated enforcement thereafter.

Reason Four: New Revenue — Fund Distribution, Structured Product Access, and the Wealth Management Channel

The fourth reason is the most commercially significant at the corporate strategy level: tokenization creates new revenue opportunities that do not exist in the conventional financial infrastructure.

Fund distribution efficiency: The global private markets — private equity, private credit, infrastructure, real estate — have historically been accessible only to institutional investors (pension funds, endowments, sovereign wealth funds) and the highest tier of high-net-worth individuals. Minimum investments of $1-10 million, quarterly redemption windows, and manual subscription processes create a distribution architecture that cannot serve the wealth management channel at scale.

Tokenized fund shares reduce minimum investments to $10,000-$50,000 while eliminating the manual processing overhead through automated subscription, KYC, and transfer management. For alternative asset managers — Hamilton Lane, Ares, Apollo, KKR — this unlocks a wealth management channel that represents tens of trillions of dollars in addressable assets. The compliance architecture of Reg D + Securitize transfer agent + smart contract transfer restrictions enables this distribution at scale without requiring proportional increases in fund administration headcount.

Structured product democratisation: Structured products — principal-protected notes, leveraged equity participation, yield enhancement strategies — have historically required minimum investments of $100,000-$250,000, limiting their availability to institutional and ultra-high-net-worth investors. Tokenized structured products can be issued in minimum denominations of $1,000 or less, dramatically expanding the distribution addressable market.

Several European banks — Société Générale Forge, DZ Bank in Germany — have issued tokenized structured products for distribution via digital wealth platforms at reduced minimums. The compliance architecture for these issuances requires careful structuring: reduced minimums do not reduce regulatory obligations; retail-accessible structured products face more stringent suitability, disclosure, and margin requirements than institutional products.

On-chain yield and DeFi integration: Banks with BUIDL-equivalent products or tokenized deposit products can access the DeFi ecosystem as yield infrastructure. Institutional DeFi protocols — Ondo Finance, MakerDAO’s RWA programme — have deployed billions in capital into tokenized Treasury products as collateral. For banks issuing tokenized deposits or money market funds, the DeFi ecosystem represents a new distribution channel with institutional capital depth.

The Compliance Architecture Banks Are Building

The four business reasons produce a convergent compliance architecture requirement. Examining the programmes at JPMorgan, Goldman Sachs, HSBC, Deutsche Bank, and BNY Mellon, the common elements are:

Regulated custody as the foundation. Every institutional tokenization programme is anchored to regulated custody — either the bank’s own balance sheet custody, a registered trust company, or a qualified custodian in the relevant jurisdiction. The tokenized asset is not a replacement for regulated custody; it is a layer on top of it. BNY Mellon’s digital asset custody programme, Deutsche Bank’s Taurus partnership, and HSBC Orion all anchor their token infrastructure to conventional regulated custody frameworks.

Identity and eligibility infrastructure. The most significant infrastructure investment in institutional tokenization compliance is identity — maintaining and verifying a database of investors whose wallets are eligible to hold specific tokens. This is the whitelist, implemented through KYC verification processes that comply with FATF standards and jurisdiction-specific AML rules. Investment in identity infrastructure — both the technology systems and the legal frameworks — is the compliance cost that most institutional programmes have underestimated.

Settlement layer interoperability. Institutional tokenization programmes are not building isolated DLT systems; they are building interoperability layers between existing financial infrastructure and DLT settlement rails. The compliance coverage must extend across both layers — conventional settlement system compliance for the conventional infrastructure elements, and on-chain AML and transaction monitoring for the DLT elements.

For bank-specific programme details, see /tracker/institutional-adoption/. For related editorial analysis, see /analysis/blackrock-changed-everything/.