Identity Is Becoming the Next Capital Routing Layer

Identity is moving into the transaction path. In May 2025, the World Wide Web Consortium made Verifiable Credentials 2.0 a standard. The format lets an issuer sign a claim, a holder carry it, and a machine verify it. EU member states plan to offer digital identity wallets by the end of 2026.

This is not a better login system. It is a new control layer for finance. A credential can decide who may hold an asset, enter a pool, or draw credit. It can also decide who may sign for a company or send funds across a border.

The structural signal is control migration. Banks once kept identity inside closed customer files. Programmable markets can bind identity to wallets, accounts, assets, and transaction rules. The party that defines accepted credentials can shape capital access before execution begins.

The legacy model starts with document collection. Each bank, broker, exchange, and custodian checks the same party again. The result sits in a private database and cannot move with the client.

A portable model splits the system into four parts. An approved issuer creates a signed credential. A person or company holds it in a wallet. A verifier checks the proof. It also checks the proof’s current status. A policy engine then turns the result into a financial permission.

That last step creates the leverage. The policy engine can allow a token transfer, set a credit limit, release collateral, or block settlement. Identity stops being a record. It becomes executable market logic.

This design already exists in regulated token standards. ERC-3643 links token transfers to an identity registry and a compliance contract. A transfer can fail when the receiving wallet lacks the needed claims. It can also fail when a rule returns false. Identity therefore sits inside the asset, not only inside the broker.

Organizational identity follows the same path. GLEIF’s verifiable Legal Entity Identifier can prove which entity exists and which person may act for it. That can compress checks around trade approval, payment release, reporting, and collateral movement.

The cost moves as well. Less money goes to repeated document review. More money goes to credential issuance and revocation. Wallet security and policy code also take a larger share. Fees move toward the software that grants or denies access.

Legacy finance has legal reach and balance-sheet support. Banks can absorb liability, reverse some errors, and work inside known rules. Their identity systems also create a distribution moat because clients must enter through each bank’s own process.

The weakness is speed. Data is copied across firms. Reviews repeat. Capital waits while trust is rebuilt.

Autonomous systems use reusable proofs and rules that run before a transaction settles. A wallet can prove that it meets a condition. It does not need to send the full source file to each venue. Zero-knowledge tools can also prove a fact while hiding the raw data behind it.

But autonomy does not remove trust. It moves trust into credential issuers, revocation lists, wallet keys, contract upgrades, and rule makers. A bad credential can spread across many venues. A flawed policy contract can block good capital or admit bad capital at machine speed.

Institutions will therefore fight to control the trust list. Banks want credentials tied to accounts. Custodians want them tied to controlled wallets. Protocols want them tied to open execution rules. Regulators want them tied to the legal perimeter.

Capital first accepts identity friction where access is scarce. It then moves toward venues that can reuse trusted proofs, clear checks faster, and settle with fewer manual stops. The gain is lower cost and more time in use.

BIS Project Mandala showed how policy rules and proof engines can sit inside cross-border payment flows. That model turns compliance from a review after instruction into a condition of instruction. The same logic can govern token trades, collateral transfers, and credit lines.

The first margin pressure lands on firms paid to repeat the same checks. The next pressure lands on venues that use closed identity records to hold clients in place. Portable credentials weaken that moat. Approved capital can move without restarting the full process.

New toll booths will form. Credential issuers can charge for trust. Wallet providers can control presentation and consent. Policy engines can control routing. Asset issuers can decide which proofs unlock transfer rights.

The prize is not identity data. It is the power to turn identity into action. That power decides which capital may enter, act, and settle.

Financial infrastructure once moved value after identity checks were complete. Programmable markets merge the check with the movement. Permission, compliance, execution, and settlement become one machine-readable path.

Identity is therefore becoming a financial rail. The winning architecture will verify rights once, reuse them across venues, and enforce them at transaction speed. Control will shift toward whoever owns the credential standard, the wallet, the policy engine, and the final permission to move capital.

Sources: World Wide Web Consortium, European Commission, Bank for International Settlements, Global Legal Entity Identifier Foundation, Ethereum Improvement Proposals, Ethereum.org