← All use cases

E-commerce & age assurance

Verify an age threshold with less data.

Ask for the age predicate your service needs, such as age_over_18, instead of requesting a date of birth or identity image when the supported credential allows it.

The challenge

Collecting full identity documents to answer a yes-or-no age question can create unnecessary privacy and security exposure.

How it works

A simple flow.
A verifiable result.

  1. 01

    Choose the relevant threshold

    Request the minimum age condition your product or local rules require.

  2. 02

    Let the customer approve

    Present the request through a wallet-supported link, QR code, or in-person flow.

  3. 03

    Use the verified result

    Continue your age-gated journey based on the verified predicate and your own policy.

Selective disclosure of an age claim

  • Ask for a threshold rather than a full birth date
  • Keep identity photos out of the age-check flow
  • Record an auditable verification outcome

The exact age proof and selective-disclosure format depend on the credential issuer and wallet. Applicable age-assurance rules and relying-party registration still apply.

DLBR EID verifies supported wallet presentations and returns a verification result. Credential issuance, the relying party’s decision, and sector-specific processes stay with the relevant organization.

See the EUDI Wallet Architecture and Reference Framework Opens in a new tab

Start with a wallet flow

Explore a verification in your sandbox.

Test the gateway with sample credentials, then confirm issuer and wallet support for your production use case.