Privacy-preserving identity integration
The EUDI Wallet creates a new integration market between national credential issuers and private services that need a fact, signature, or entitlement without collecting a complete identity document.
The commercial gap is not another speculative identity chain. It is a reliable relying-party layer that asks for the minimum attribute, supports the current EU profiles, and produces defensible evidence about what was requested and retained.
Initial product
A narrow SDK and implementation service could provide:
- same-device and cross-device presentation flows
- policy templates for one attribute, such as an age threshold
- wallet and protocol compatibility tests
- a minimal verification receipt without storing the underlying credential
- consent and privacy-notice components
- failure handling for unsupported wallets
- an auditable map of every field retained after verification
EU age verification framework 2026 is the first concrete profile. It should not be generalized into named identification when a yes-or-no threshold is sufficient.
Buyers
Early buyers may include age-restricted ecommerce, online communities, employment and education services, or regulated customer portals. The best first buyer has a real 2026 deadline, engineering capacity, and a reason to avoid identity-document storage.
Revenue can combine implementation, verification volume, compatibility testing, and policy updates. The SDK should remain replaceable and avoid becoming a universal identity graph.
Risks
Standards and national implementations are moving. Certification, liability, wallet availability, revocation, accessibility, and platform support may change the product surface. A technically selective proof can still become linkable when the relying service stores it beside an account, IP address, payment, or device identifier.
The business should therefore sell data minimization and integration evidence, not a claim of complete anonymity.
First test
- Interview ten Swedish or Nordic relying parties.
- Identify one repeated proof request and one binding deadline.
- Implement the Commission reference flow in a sandbox.
- Test at least two wallet implementations and both same-device and cross-device paths.
- Obtain privacy and identity-law review before production verification.
This is a higher-complexity opportunity than Privacy migration and continuity, but it has a regulatory distribution event that a generic consumer privacy application lacks.