Skip to content
    hazBasehazBaseDocs
    USE CASES
    All use cases

    Cinema and venue passes

    Connect eligibility, validity periods, reservations and entry in one access flow.

    Culture & venue accessExample architecture

    The scenario

    ForCinemas, theaters, event venues and subscription services

    Issue a monthly cinema pass and use it for eligible screenings. Manage pass ownership separately from reserving a particular seat.

    What this makes visible

    Members can check validity and reservations; venues reconcile access eligibility with actual attendance.

    Token and business-data roles

    Represented by tokens

    Use PrivilegeNFT for individual passes. Manage screening reservations and usage limits in business rules linked to member ID and tokenId.

    Managed in business systems

    Member ID, pass type, screening ID, reservations/seats, validity and attendance history.

    Map project, asset or order IDs to chainId, contract address and tokenId where applicable. Link the operation ID to the confirmed transaction so the application can trace the result.

    Contract composition

    ContractRole in this use case
    PrivilegeNFTIdentify each pass and its holder.
    WhitelistProvide eligibility records for members or users.

    Follow each contract for its key operations, SDK and source. Select the components your workflow needs and connect them to business approvals and records.

    User and processing flow

    1. Define the plan

      Define validity, eligible screenings, usage limits and guest policies.

    2. Issue the pass

      Verify enrollment/payment, issue the pass and link the member to tokenId.

    3. Verify reservation and entry

      Reconcile ownership, validity and reservation, then record entry.

    4. Handle renewal or expiry

      Update the pass and application access state under renewal or cancellation rules.

    Operating considerations

    Capacity and seating

    Issuing a pass does not reserve a seat. Integrate reservation capacity and entry with existing systems.

    Transfer policy

    Distinguish personal passes from transferable tickets and define how reservations follow ownership changes.

    Review approvals, reconciliation and recovery

    Implement this use case

    These implementation patterns provide architectures, data models, processing steps and SDK examples. Start with the capabilities this use case requires.