Accept EU Digital Identity Wallets with institutional confidence.
Arbiter gives regulated health and finance organizations one controlled API for EUDI Wallet verification, selective disclosure, and pan-EU identity acceptance.
Wallet acceptance dossier
Status: implementation planning
27
Member states
2
Credential formats
1
API surface
Deadline context: EU member states must issue EUDI Wallets by December 2026. Private-sector acceptance obligations follow in 2027 for selected relying parties.
Compliance challenge
Wallet acceptance is not a front-end feature.
Regulatory interpretation
eIDAS 2.0 introduces mandatory wallet acceptance for selected private-sector relying parties. Arbiter keeps implementation aligned with the evolving Architecture Reference Framework and implementing acts.
Credential complexity
Relying parties must support multiple credential formats, protocol profiles, trust anchors, and disclosure models. Arbiter presents these differences through one stable API.
Implementation lead time
Member states must issue EUDI Wallets by December 2026, with private-sector acceptance obligations following in 2027. Identity infrastructure requires early technical preparation.
Protocol coverage
Built for the EU digital identity stack.
Arbiter translates wallet ecosystem complexity into a stable relying party integration.
OIDC4VP presentation flows
SD-JWT selective disclosure
ISO/IEC 18013-5 mdoc credentials
Trust List synchronization
Same-device and cross-device verification
Level of Assurance policy controls
Priority sectors
Designed for organizations where identity risk is material.
Health
Authenticate patients, members, and policyholders for sensitive workflows where verified identity and data minimization must coexist.
Finance
Use wallet-based identity for regulated onboarding, Strong Customer Authentication, and cross-border account access.
Operating model
One integration, three controlled steps.
Request verified attributes
Your application asks Arbiter for the assurance level and attributes required for a specific workflow.
Verify wallet presentation
Arbiter validates the presentation, credential format, issuer trust status, disclosure policy, and protocol requirements.
Return a normalized result
Your system receives a concise verification response, without taking custody of unnecessary identity data.
Controls
Built to support legal, security, and product review.
Privacy by design
Selective disclosure lets relying parties request only the attributes needed for a workflow, reducing unnecessary data exposure.
Pan-EU readiness
One integration can support national wallets and issuer trust models across all 27 EU member states as the ecosystem rolls out.
API abstraction
Product teams work with a stable API while Arbiter handles protocol translation, credential parsing, and policy updates.
Audit posture
Verification events can be structured for audit trails, incident review, and internal compliance reporting.
FAQ
Questions for implementation planning.
What is eIDAS 2.0?
eIDAS 2.0 is the updated European digital identity regulation. It establishes EU Digital Identity Wallets and creates acceptance obligations for selected relying parties in regulated sectors.
Why not build wallet support internally?
An internal build requires protocol expertise across OIDC4VP, SD-JWT, mdoc, trust management, issuer metadata, and changing ARF specifications. Arbiter reduces that work to one maintained integration.
Does Arbiter store personal identity data?
Arbiter is designed around selective disclosure and data minimization. The relying party receives only the verification outcome and attributes required for the transaction.