How the concept is used

A wallet can participate in an ecosystem of issuer, holder and verifier. The issuer establishes information and issues a digital credential. The holder uses a wallet to manage or present it. The receiving service checks the evidence and decides whether it is suitable for the intended purpose. A technically valid presentation is therefore only one part of the overall journey.

A practical example

Imagine a person holding a digital proof of age. An online shop requests evidence for a particular threshold, and the user presents an appropriate credential through a wallet. The shop must support the format and have a basis for trusting the issuer. If it needs a different attribute, possession of a credential answering an unrelated question does not solve that requirement.

Important distinctions

A digital identity wallet is not automatically the EU Digital Identity Wallet, Denmark’s AltID or a payment wallet. Those names refer to particular initiatives or other uses, whereas wallet is the broader concept. Different wallets and credentials offer different sharing, recovery and correlation protections. A business should check support and data flows instead of assuming that an app will be accepted everywhere. This explanation does not claim that IDguard currently supports identity wallets.

Sources

  1. World Wide Web Consortium: Verifiable Credentials Data Model v2.0 Checked
  2. NIST: NIST SP 800-63C-4: Federation and Assertions Checked

These explanations were prepared with AI assistance and draw on the sources listed.