eIDAS 2.0 and Manav

eIDAS 2.0 mandates a European Digital Identity Wallet for every EU citizen and resident. Manav federates with it and extends to the agent layer eIDAS does not cover.

What eIDAS 2.0 does

The update to eIDAS requires every EU member state to make available a European Digital Identity Wallet (EUDIW) — a smartphone-based wallet for verified identity attributes (name, date of birth, government ID, professional qualifications). Member-state implementations are rolling out through. The wallet is a Layer 1 + Layer 3 construct in the HATI vocabulary: verified human plus signed claims.

What eIDAS does not cover

The agent age. eIDAS 2.0 is silent on:

• Delegation from the human to an autonomous agent.
• Scoped, time-bound authority for specific actions.
• Cryptographic proof of human supervision over AI decisions (Article 14 of the AI Act).
• Cross-platform agent identity that extends beyond EU member-state boundaries.

This is by design — eIDAS regulates electronic identification and trust services, not agent ecosystems. The two regimes are complementary.

How Manav federates with EUDIW

The Manav SDK accepts EUDIW credentials as a Layer 1 anchor. A user with an EUDIW signs into Manav using their wallet; Manav uses the wallet's verifiable presentation as the Layer 1 identity. Layers 2–5 (delegation, attestation, score, settlement) are added by Manav on top of that anchor.

The result: a user with an EUDIW can authorize an agent through Manav, satisfy Article 14 of the AI Act, and produce an audit log that EU regulators recognize at every layer. Without re-issuing identity, without abandoning eIDAS, without lock-in to a specific Manav vendor account.

Member-state pilots

EUDIW pilots have rolled out across Germany, France, Italy, Spain, the Netherlands, Sweden, and several other member states through the last few years. Adoption rates vary widely. Manav's federation pattern is the same in each: detect the wallet's PID (person identification data) format, verify the signature against the member-state trust list, mint a Manav DID anchored to that PID. We've published reference adapters for the four most-deployed wallets.

What this means for vendors selling into the EU

If your AI product accepts user identity in the EU after late, accepting EUDIW becomes an expectation. Building the Layer 1 acceptance yourself is doable but slow. Federating through Manav adds Layers 2–5 in the same project — and those layers are the ones Article 14 enforcement will check.

Common objections

Compliance teams push back with two reasonable concerns. Vendor lock-in — answered by the open-source protocol and forkable reference implementation. Audit acceptance — answered by the major auditors that have already approved the audit-trail format for SOC 2 evidence and the regulators who have reviewed the Article 14 mapping.

Frequently asked questions

What is the penalty exposure if we ignore this? Material. EU AI Act Article 14 caps fines at 7% of global revenue or €35M, whichever is higher. SOC 2 audit failures jeopardize enterprise procurement. The cost of the audit-trail layer is small relative to either.

Do we need to be in the EU for this to matter? No. Article 14 applies to any AI system placed on the EU market, including non-EU vendors selling into the EU. Most US enterprises with European customers are in scope. The same controls satisfy emerging US sectoral rules and India's DPDPA.

How long does compliance take to set up? Two weeks for an instrumented stack. Most of the work is auditing the existing agent surface — what agents run, what they touch, who authorized them — not deploying the identity layer. The protocol integrates in twelve lines; the policy work takes longer.

Where to start

Pair this with ai act article 14 playbook for the cross-jurisdictional view and how to prove human 2026 for the audit artifact your auditors expect to see. Most compliance projects we have seen succeed by reading those three together before scoping anything.

Where eIDAS 2 leaves a gap that Manav fills

eIDAS 2 specifies the European digital identity wallet — issuance, storage, verification — and stops at the human credential. The act does not address agent action. An EUDI wallet holder can prove they are who they claim to be; the wallet has nothing to say about the agent acting on the holder's behalf, the scope of that agent's authority, or the chain of accountability when the action lands wrong. Manav extends the EUDI primitives into the agent layer without contradicting them. The integration shape is straightforward: the EUDI wallet holds the human identity, the Manav layer issues the action delegation against that identity, the relying party verifies both. eIDAS 2 implementations that stop at the human credential are answering the regulator's 2024 question, not the regulator's 2027 question. The 2027 question is about agents, and the gap eIDAS leaves is the gap a complementary protocol fills.

eIDAS 2.0 issues the wallet. Manav uses the wallet to authorize the agent.