This documentation is currently under development. Certain sections are not yet complete and will be added shortly.
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Pass list

Find a pass quickly by identifier, template, metadata, or date, then open its detail page.

The pass list shows every pass in a programme. Use it to find a pass by any identifier, filter by template or date, and open the pass detail page for a full view of that pass's history.

Real-world examples
  • A support agent searches a loyalty number to answer a customer query.

  • An operations manager filters by template and creation date to check a batch issue.

  • A programme administrator opens a pass to verify its current state and history.

How to open the pass list

The pass list is the starting point for finding and checking a pass. It brings every pass available in the account into one view.

1

Open the back-office

Sign in to The Wallet Crew back-office.

2

Go to Wallet > Passes

The list loads all available passes. By default, the newest updates appear first.

Finding a pass

The search and filter controls at the top of the list narrow the result set quickly. Start with the identifier already available in the customer case, then add template or date filters if needed.

Filters available:

  • Pass ID — the internal platform identifier for the pass.

  • External ID — any external identifier linked to the pass, such as a CRM customer ID, a loyalty number, or a booking reference. This is the most common way support teams locate a specific customer's pass.

  • Pass template — narrows the list to passes created from one template.

  • Metadata fields — filters by any metadata field defined on the passes, such as storeId or programmeId. These fields depend on the programme setup and can vary from one programme to another.

  • Creation date — shows only passes created within a date range.

  • Last updated — shows only passes updated within a date range.

To find a pass for a specific customer, filter by External ID using the identifier sent when the pass is created — for example, a CRM ID, loyalty number, or booking reference.

Columns

The default columns give a quick operational view of each pass.

Column
What it shows

Pass ID

The internal platform identifier

Creation date

When the pass record was created

Last updated

When the pass was last modified or updated

Template

Which pass template the pass was created from

External ID

The external identifiers linked to this pass

Installation status

Whether the pass is currently installed in a wallet

Use the column selector to add or remove columns. Metadata fields are available as extra columns, and the selected layout is saved in the browser.

Opening a pass

Click any row in the list to open the pass detail page for that pass.

For what can be reviewed once the pass is open, see Pass details.

FAQ

Which filter should be used first for a customer case?

External ID is usually the fastest starting point. It matches the identifier sent from the source system when the pass was created.

Why does filtering by External ID show several rows for the same identifier?

The back-office shows every pass created with that External ID. An External ID does not guarantee a one-to-one match with a pass.

Multiple rows usually result from test enrolments or repeated API calls. To identify the active pass, check the Installation status column, then compare the most recent Last updated value.

For the technical model behind external identifiers and data retrieval, see Pass data and sync.

Why do metadata filters differ between programmes?

Metadata fields come from each programme's pass setup. One programme may use storeId, while another may use eventId or membershipTier.

Why do the visible columns look different on another browser?

The column setup is saved in the local browser. A different browser or device can show a different saved layout.

Last updated