For the past two years, digital identity wallets have lived largely in the safe space of pilots. EU Digital Identity Wallet (EUDI) projects, national schemes, and cross-border proofs of concept have focused on citizen services, onboarding flows, and controlled demonstrations of interoperability under ideal conditions.

That phase is ending.

As digital wallets move from public-sector experimentation into enterprise environments, a more demanding reality emerges. Enterprises are not interested in identity as an idea. They care about identity as infrastructure — something that must work under load, survive failure, and remain auditable when things go wrong.

This is where digital wallets stop being policy instruments and start colliding with Enterprise Identity and Access Management (IAM).

From Citizen Credential to Enterprise Trust Input

In pilot environments, wallets are often framed as self-contained trust mechanisms: cryptographically secure, user-controlled, privacy-preserving. All of that may be true — but none of it is sufficient once the wallet becomes part of an enterprise access decision.

Enterprises do not authenticate identities in isolation. They operate layered trust systems that combine:

• identity proofing
• directory services
• role and attribute management
• multi-factor authentication
• device posture
• policy engines
• audit and compliance tooling

Within this environment, a wallet is not a replacement for IAM. It is a new trust input.

That distinction matters. Because once wallets are treated as inputs rather than endpoints, they are judged by the same criteria as every other IAM component: reliability, revocability, fallback, liability, and operational continuity.

Why Pilots Succeed — and Production Is Less Forgiving

Pilots are designed to succeed.
Production systems are designed to fail safely.

In pilot phases, assumptions are tolerated. Dependencies are known. Volumes are controlled. Everyone involved wants the project to work. Enterprise environments do not offer that luxury.

When a digital wallet is used to access corporate systems, the enterprise must be able to answer questions that pilots rarely confront:

• What happens if the wallet provider is unavailable?
• How quickly can access be revoked?
• How is liability handled if credentials are misused?
• What audit trail exists outside the wallet itself?
• Can access continue if the wallet cannot be used?

These questions are not theoretical. They define whether a wallet can be deployed at scale, across borders, and under regulatory scrutiny.

Wallets and IAM: Coexistence, Not Replacement

There is a persistent misconception that digital wallets will “replace” enterprise IAM. In practice, the opposite is happening.

IAM platforms are absorbing wallets as federated identity signals, much like smart cards, certificates, or external identity providers before them. The wallet becomes one factor in a broader policy decision, not the decision itself.

This has two important consequences.

First, enterprises will demand interoperability on their terms. Wallets must integrate cleanly with existing IAM stacks, not require architectural reinvention.

Second, wallets inherit enterprise expectations around control. User sovereignty may be a policy goal, but enterprise access decisions remain enterprise responsibilities.

The result is a pragmatic compromise: wallets enhance trust, but they do not override governance.

The Real Friction Points: Revocation, Fallback, and Audit

As wallets move closer to production, three friction points consistently emerge.

Revocation

Enterprises need immediate, provable revocation. If an employee leaves, a contractor’s role changes, or a credential is compromised, access must stop — now, not “after the next sync”.

Wallet-centric revocation models must therefore align with enterprise lifecycle management, not sit beside it.

Fallback

No enterprise can afford a single point of failure in its access layer. Wallets must coexist with alternative authentication paths, whether that is hardware tokens, certificates, or emergency access procedures.

A wallet that works only when everything else is functioning is not enterprise-ready.

Auditability

IAM decisions are audited long after they occur. Enterprises need to demonstrate who accessed what, when, under which policy, and based on which attributes.

Wallets that cannot feed structured, verifiable data into enterprise audit systems will struggle to move beyond pilots.

Identity Is Becoming Infrastructure

The deeper shift is not technological, but conceptual.

Identity is no longer just about authentication. It is becoming critical infrastructure, embedded in operational workflows, compliance regimes, and business continuity planning.

That shift brings digital identity wallets into direct contact with regulatory expectations around resilience, governance, and risk management. Once identity becomes infrastructure, it becomes subject to the same scrutiny as networks, platforms, and services.

This is where many wallet discussions become uncomfortable — because infrastructure is expected to be replaceable.

Trust Only Matters When You Can Remove It

One of the defining characteristics of mature enterprise systems is not how well they work when everything is available, but how they behave when something is removed.

Can access decisions still be made if a component fails?
Can the organisation continue to operate under constraint?
Can governance be demonstrated under stress?

These questions apply just as much to identity inputs as they do to servers or services.

A wallet that cannot be bypassed, substituted, or revoked cleanly is not a trust anchor — it is a dependency.

From Identity Pilots to Governance Reality

The move from pilot to production forces a reframing of digital wallets. They are no longer evaluated primarily on cryptographic elegance or user experience, but on how they behave inside real organisations, under real constraints.

This is not a failure of the wallet model. It is a sign of maturity.

But it also signals something larger: European trust frameworks are entering a phase where operational reality matters more than architectural intent.

Identity is only one layer in that stack.

What Comes Next

As digital identity becomes embedded in enterprise IAM, regulators are also sharpening their focus on the trustworthiness of the systems organisations depend on — not just who accesses them, but what they are built on.

The next phase of European digital governance will test whether organisations truly understand their dependencies, or whether trust has been assumed rather than engineered.

Identity may be the front door.
But resilience depends on what happens deeper inside the building.

Part 2 will examine how Germany’s implementation of NIS2 turns this question into enforceable reality — and why supply-chain governance is about to become operational, not theoretical.