What is an Apple Wallet pass?

An Apple Wallet pass is an event credential that lives in the iPhone’s Wallet rather than inside an app. For an attendee at a check-in desk, that is the difference between a swipe from the lock screen and unlocking, finding an app and navigating to a code.

In practice at an event

The organizer issues a pass carrying the attendee’s name, the event details and a scannable code. The attendee adds it once. Because passes are remotely updatable, the issuer can push a change — a corrected session time, a new code — to a pass somebody added last week.

Issuing passes requires a signing certificate from Apple, which is a real setup step rather than a switch. A vendor’s wallet feature is therefore available rather than always on, and the certificate is worth confirming before you promise passes to attendees.

What to look for

Ask whether passes are updatable after issue or are a one-time snapshot, because the update mechanism is most of the value.

Ask about Android, where Google Wallet is the equivalent and support is not automatic.

And confirm the signing certificate is in place for your event specifically, not just supported in principle.

One practical note for the desk. A wallet pass and an in-app code are two routes to the same check-in, and attendees will arrive with either. Brief the desk to accept both rather than to insist on one, because insisting is how a queue forms.

How event67 handles it

event67 issues an Apple Wallet pass to attendees from the event record, refreshed by the backend while the event runs. It requires a signing certificate to be configured, so the feature is available rather than always on — treat it as something to confirm during setup. iOS Live Activities are driven by the same dispatcher.