← All use cases

Events & access

Verify ticket and eligibility at event entry.

Use a separate ticket credential or ticket-system lookup for admission, and request a wallet attribute only when the event needs it.

The challenge

Ticket resale, manual identity checks, and separate age or membership checks can slow entry and frustrate guests.

How it works

A simple flow.
A verifiable result.

  1. 01

    Keep admission rules in the ticket system

    Define how the organizer issues, transfers, revokes, and redeems each ticket.

  2. 02

    Request only an extra attribute if needed

    Use a wallet presentation for a permitted age threshold, membership, or eligibility fact.

  3. 03

    Validate and redeem at the gate

    Check both the credential result and the ticket’s current state before admitting the guest.

Wallet attributes plus separate ticketing controls

  • Keep ticket validation separate and clear
  • Avoid collecting identity details for every guest
  • Support a faster check for required eligibility

EUDI Wallet does not by itself issue event tickets, stop resale, or guarantee anonymous entry. Ticket uniqueness, transfer rules, redemption, and any selective-disclosure design belong to the event ticketing system.

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.