Ticket security without mystery

How MetaPass verifies a ticket.

A QR image alone is not the decision. Entry depends on the private credential, the current stored ticket state, and organiser permission. An optional on-chain record is advisory and never replaces the database ticket.

From checkout to check-in

1. Purchase recorded

After a confirmed CHF card or free-ticket checkout, MetaPass creates the durable database ticket and its private QR credential.

2. QR becomes entry-ready

The ticket page makes the private QR available when the signed-in owner and durable ticket state are valid.

3. Optional technical record

A background worker may create an advisory on-chain record. It is shown separately and does not replace the database ticket or delay entry by default.

4. Organiser scans at the door

The access tool checks the private credential, event permission, and current database ticket state before recording check-in.

What scanner results mean

Door staff should follow the displayed result and avoid manually changing ticket records.

Entry accepted: The credential and ticket identity passed verification and the ticket is now marked used.
Already checked in: The ticket was consumed previously. Staff should not override it without the event’s support process.
Wrong event: The organiser account is not responsible for this ticket’s event.
Technical record preparing: The optional technical record is not ready. This advisory state does not make an otherwise valid database ticket fraudulent.
Temporarily unavailable: MetaPass could not safely complete the scan. The ticket was not consumed; check connectivity and retry.
Invalid or refunded: The permanent ticket state or credential does not qualify for entry.

During a temporary outage

Do not ask the buyer to pay again and do not mark the ticket used manually. Confirm connectivity, retry verification, and contact the event’s support owner if the delay continues.

Information that must stay private

Never post a QR token, private key, wallet recovery phrase, authority secret, card details, or service-role credential in a support message or screenshot.