> For the complete documentation index, see [llms.txt](https://docs.thewalletcrew.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.thewalletcrew.io/guides-monitoring/monitor/pass-details.md).
# Pass details
To find a specific pass, see [Pass list](/guides-monitoring/monitor/pass-list.md).
The pass detail page gives a complete view of one pass — its current state, the data it holds, its notification history, and its full event log. It also makes it possible to trigger a pass update or send a notification directly from this page.
Real-world examples
* A support agent checks whether a customer's pass is still installed and re-sends the QR code.
* An operations manager reviews the event history after a push update.
* A programme administrator verifies metadata and notification history before escalating a case.
## The four tabs
The detail page is organised into four tabs. Each tab answers a different operational question.
### General
The **General** tab shows the current state of the pass. It is the fastest place to confirm the main operational details.
The tab includes:
* **Template** — which pass template this pass was created from.
* **Title / Subtitle** — the values currently shown in the pass header fields.
* **Creation date** — when the pass record was created on the platform.
* **Last updated** — when the pass was last modified.
* **Installation status** — whether the pass is installed in Apple Wallet, Google Wallet, both, or neither. Apple and Google installation status appear separately.
* **Active installations** — the number of wallets where the pass is currently installed. For Apple, this counts individual devices, including Apple Watch. For Google, this counts Google accounts.
{% hint style="info" %}
An active installation count of `0` means the pass has been removed from all wallets. The pass record still exists on the platform — it has not been deleted.
{% endhint %}
### Data
The **Data** tab shows all data associated with the pass. This is useful when the visible pass content needs to be checked against the underlying record.
The data is grouped into three categories:
* **Additional data** — information stored directly on the pass record. These values are usually set when the pass is created or updated.
* **External data** — information pulled in from connected source systems. This shows the latest data available when the pass was last refreshed.
* **Metadata** — extra fields attached to the pass, such as `storeId`, `programmeId`, or any custom field used for filtering and reporting.
### Notifications
The **Notifications** tab lists every push notification sent to this pass. Use it to confirm what message was sent and when it was sent.
Each row shows:
* **Date** — when the notification was sent.
* **Message** — the notification content that was sent.
* **Device type** — Apple or Google.
{% hint style="info" %}
Delivery confirmation is not available. Apple and Google do not expose whether a notification was received by the device.
{% endhint %}
### History
The **History** tab shows the complete event log for this pass. Use it to understand what happened, in which order, and with which recorded data.
All platform events for this pass are listed, including:
| Event | What it means |
| --------------------- | ---------------------------------------------------------- |
| Pass:Created | The pass record was created on the platform |
| Pass:Installed | A customer added the pass to Apple Wallet or Google Wallet |
| Pass:Uninstalled | A customer removed the pass from their wallet |
| Pass:Updated | The pass data was changed |
| Pass:UpdateSent | A push update was delivered to a device |
| Pass:Scanned | The pass barcode was scanned at a reader |
| Pass:NotificationSent | A push notification was sent to this pass |
Each event row shows the event timestamp and all data recorded with the event.
The history is complete. All events are shown with no time-limit cutoff.
For bulk export across many passes, use [Report](/guides-monitoring/monitor/report.md).
## Actions
Three actions are available from the top of the pass detail page. These actions help resolve common support and operations cases without leaving the page.
### Push update
**Push update** refreshes the pass using the latest available data. It always updates the pass record on The Wallet Crew.
A confirmation toast appears when the update is queued.
#### Push notification behavior
A pass update has two separate outcomes: a backend update and a device notification.
The backend always updates the pass, whether or not it is installed. Pass identifiers, metadata, and timestamps are updated and stored on The Wallet Crew.
A device notification is sent only when the pass is currently installed in Apple Wallet or Google Wallet. No device notification is sent when the pass is uninstalled.
Backend updates persist. If the pass is installed again later, the wallet receives the latest version stored on The Wallet Crew.
Use [Pass:Installed and Pass:Uninstalled events](/developers-guides/integration-guides/wallet/pass-lifecycle.md#wallet-removal) to track wallet installation and removal.
### Send notification
**Send notification** sends a push notification to all devices where this pass is installed. Use this to alert the customer, for example to inform them of a balance change or a new offer.
This action does not rebuild the pass content.
### View QR code
**View QR code** displays the pass's Add-to-Wallet QR code. Use this to re-send the install link to a customer, for example by screenshot or email.
## FAQ
When should the General tab be checked first?
Start with **General** when the goal is to confirm whether the pass exists, which template it uses, when it changed last, and whether it is still installed.
What is the difference between Data and History?
**Data** shows the current values attached to the pass. **History** shows the sequence of events that happened to that pass over time.
When should Report be used instead of Pass details?
Use **Pass details** for one-pass investigation. Use [Report](/guides-monitoring/monitor/report.md) when event data is needed in bulk across many passes.
Can I use failed updates to detect uninstalled passes?
No. Updates never fail because a pass is uninstalled. The backend update always succeeds. Device notification is conditional on an active Apple Wallet or Google Wallet installation.
Use [Pass:Installed and Pass:Uninstalled events](/developers-guides/integration-guides/wallet/pass-lifecycle.md#wallet-removal) to track wallet removal.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.thewalletcrew.io/guides-monitoring/monitor/pass-details.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.