How the concept is used

An attribute, its issuance and its presentation are different stages. A trusted participant can establish the information and issue evidence; the user can later present that evidence to a service. The service needs to check whether it comes from an accepted issuer, remains valid and answers the question being asked. An image displaying the word “approved” does not, by itself, offer those verification properties.

A practical example

Imagine a service that only needs to know whether someone is at least 18. Suitable evidence could answer that question without disclosing an address or precise birth date. If the service requires a different threshold, it must establish that the proof actually covers it. Evidence for one threshold should not be silently reinterpreted as evidence for every other threshold.

Important distinctions

Proof of age is not necessarily a universally accepted digital identity document. Format, issuer, verification mechanism and receiving-service support all matter. The EU’s age verification work illustrates digital proofs, but an initiative or app does not automatically make every online shop capable of accepting them. Check the actual integration and applicable local requirements before incorporating a proof into a purchase journey.

Sources

  1. European Commission: Blueprint for an age verification solution Checked

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