Notifications
Clear all
Topic starter
21/08/2026 4:50 pm
TL;DR: EU Digital Identity Wallets will become mandatory in 2026, and KOBIL argues that businesses must be able to process state-verified wallet identities across login, contracts, KYC, and service workflows or risk losing customers. The governance problem is not adoption alone, but whether existing systems can securely ingest, tokenize, and authorise wallet data at scale.
NHIMG editorial — based on content published by KOBIL: EUDI-Wallet-ready identity integration for business workflows
By the numbers:
- 90% of IT leaders say properly managing NHIs is essential for a successful zero-trust implementation.
- Only 5.7% of organisations have full visibility into their service accounts.
- 97% of NHIs carry excessive privileges, increasing unauthorised access and broadening the attack surface.
Questions worth separating out
Q: How should organisations integrate EUDI wallet identities into customer workflows?
A: Start by mapping the exact workflows that will consume wallet data, then define where state-issued assertions are verified, transformed, and stored.
Q: Why do EUDI wallets change customer IAM governance?
A: They shift part of identity assurance outside the enterprise, so internal controls no longer own the full credential lifecycle.
Q: What breaks when wallet data is copied into backend systems without purpose limits?
A: The organisation turns a high-assurance identity assertion into reusable personal data, which weakens both privacy and access control.
Practitioner guidance
- Define the wallet trust boundary Map where state-issued wallet assertions enter your environment, where they are transformed, and which system becomes the control owner for each step.
- Separate authentication from attribute release Do not let a successful wallet login automatically expose all available identity data.
- Review backend systems for wallet data reuse Check whether wallet attributes are copied into CRM, booking, payment, or case-management systems beyond the original purpose.
What's in the full article
KOBIL's full article covers the operational detail this post intentionally leaves for the source:
- Step-by-step workflow examples for e-commerce, banking, insurance, and mobility use cases
- Specific integration guidance for encryption, tokenisation, and access rights around wallet data
- Practical processing flows for login, contract execution, payment, and check-in scenarios
- The vendor's view of how monitoring and future wallet updates are expected to affect implementation
👉 Read KOBIL's analysis of EUDI wallet integration for customer identity workflows →
EUDI wallet integration: what it means for customer identity controls?
Explore further
21/08/2026 5:09 pm
Wallet acceptance creates a new identity governance boundary, not just a new login method. The article frames the wallet as a bridge between state-issued identity and business processes, which is the right place to think about control failure. Once identity is asserted outside the enterprise, the question becomes who governs the handoff, the attribute scope, and the audit trail. Practitioners should treat this as a federation boundary that needs explicit policy ownership.
A few things that frame the scale:
- Only 5.7% of organisations have full visibility into their service accounts, according to Ultimate Guide to NHIs.
- 96% of organisations store secrets outside of secrets managers in vulnerable locations including code, config files, and CI/CD tools, according to Ultimate Guide to NHIs.
A question worth separating out:
Q: Who is accountable when wallet-based identity processing fails a compliance check?
A: Accountability sits with the organisation that receives, stores, and acts on the wallet data, even if the identity originates from a state ecosystem. Legal, IAM, and application owners all need a shared control model for authentication, consent, retention, and auditability.
👉 Read our full editorial: EU digital identity wallets will reshape customer access governance
