What happens after a Wallet pass is installed

A signed pass can include a web-service URL, serial number, pass type identifier, and authentication token. Together they let Wallet register the device for future changes without exposing your normal API credential.

When a user adds the pass, Wallet sends its device library identifier and push token to the pass web service. Eventlayer associates that registration with the pass so it knows which devices to notify when the ticket changes. Downloading a pass and installing it are distinct steps; a download alone is not evidence of a device registration.

A ticket update and a notification to Apple have different failure modes. Eventlayer queues the update work so a slow push service does not have to block the ticket change. Your application can keep working with the ticket while the device update follows.

The push notification carries no pass content. It tells Wallet to query the web service, where authentication and an update tag determine whether the latest signed pass should be returned.

That is why a push being sent and a phone showing the new pass are not the same moment. The device must be reachable and fetch the update. At the door, use the ticket’s current server state for admission rather than trusting the details still visible on a phone.