Topic starter
11/11/2026 6:01 pm
TL;DR: Device changes, status changes and over-collection can break a valid digital identity transaction later, according to Hopae. Wallet and verifier workflows need lifecycle governance because device changes, status changes and over-collection can break a valid transaction later.
Editorial analysis by NHI Mgmt Group, based on content published by Hopae: “Digital identity risk assessment: what happens after eID verification?”.
Key questions
Q: Why does wallet recovery create identity risk after a phone change?
A: Wallet recovery can create identity risk after a phone change because recovery often relies on the old number, SMS codes, or help desk verification, any of which can be hijacked when the number is reassigned or ported.
Q: How should organisations govern selective disclosure in digital identity systems?
A: They should define which attributes are allowed for each transaction type, who can request them, and how consent is recorded and revoked.
Q: What should teams do first when a credential appears in a breach check?
A: The first action is to reset the password for the affected account and replace it with a strong unique value.
Practitioner guidance
- Define post-verification state handling Document how your relying party responds to valid, revoked, suspended, stale and unknown credential states before any production rollout.
- Treat recovery as re-issuance Require a named owner for re-authorization, old-device invalidation and status propagation whenever a wallet credential is moved or replaced.
- Minimise data across the full flow Review analytics, debugging, support tickets and logs to ensure they do not retain more identity data than the transaction requires.
Bottom line: Digital identity risk does not end at verification, because recovery, revocation and status changes can still create incidents after acceptance succeeds.
Glossary terms: Digital Identity Risk Universe, Selective Disclosure, Credential Lifecycle, Federation
Explore further
View Full Forum → | NHI Foundation Course → | Our Services → | Read the full analysis →
11/11/2026 6:07 pm
Post-verification risk is the real control boundary: identity assurance is not finished when the credential first passes validation. The system still has to manage device change, status updates, revocation and consent withdrawal across multiple parties. That is the point where responsibility becomes distributed, and distributed responsibility is where gaps appear. Practitioners should design the lifecycle boundary as a governance control, not a user convenience feature.
A question worth separating out:
Q: Does a verified credential stay trusted after status changes?
A: A verified credential does not stay trusted if its status changes. Trust depends on current validity, issuer status, revocation, expiry, and any updates to the holder’s attributes or assurance level, so relying parties must check status at presentation or through an online status service before accepting it.
👉 Read our full editorial: Digital identity risk assessment must cover recovery and revocation