Skip to main content
A pass is an individual wallet credential issued from a published template version. This guide covers issuing from the admin console; for automation see the Create a pass API.

Issue from the console

Go to Passes → Issue passes (or click Issue Pass in the template editor).
1

Pick a template

Only templates with a published version can issue passes. The pass will be pinned to the latest published version at issue time.
2

Fill in the rows

The issue screen is a spreadsheet-style grid with one row per pass:
  • External Pass ID: your system’s reference for this pass. Toggle Auto-generate External Pass IDs if you don’t have one. External IDs are unique per workspace and make issuance idempotent, so re-sending the same ID never creates a duplicate pass.
  • Label: the holder’s display name.
  • One column per template variable.
Add rows with Add pass, or bulk-load them with Import from CSV (append to or replace the grid). A live preview shows the pass as you type.
3

Issue

Click Issue pass (or Issue N passes). Issuance runs asynchronously; large batches are queued and processed in the background.
Passes inherit their project from the template, shown read-only on the issue screen. Organize with projects before issuing if you need separation.

Pass statuses

The console shows a friendly label for each status; the API uses the uppercase value. Every column of the Passes list can be sorted and filtered from its header: label (contains or exact match), project (including uncategorised), template, pinned version (up to date / upgrade available / a specific version), revision, status, and created date (today, rolling windows, or a custom range). The Quick filters button covers the common one-click cases (statuses, upgrade available, and recent creation windows), and every active filter shows as a dismissable pill in the Filtered by row, with Clear all beside it. Free-text search by label or external ID sits in the toolbar. Download CSV (next to the quick filters) exports the list with the current filters and sorting applied. The file contains the displayed columns plus each pass’s Apple and Google Wallet links, and covers up to 10,000 passes per export.

The pass detail page

Open any pass to see its status and template version in the page header, with an upgrade prompt when a newer published version exists, and five tabs:
  • Overview: a live preview beside a Revisions timeline (every data update or version upgrade is a snapshot you can step through), plus the add-to-wallet links for each wallet, with copy and QR-code actions and the Resend / Revoke controls.
  • Notifications: messages sent to this pass, with a Send notification action. See the Notifications guide.
  • Pass data: the pass’s stored variables and pinned template version, with Edit, Upgrade to vN, and Void pass actions.
  • Scan history: every scan decision recorded for this pass.
  • Audit history: the pass’s lifecycle event log.
Row and bulk actions on the list cover the common lifecycle operations: Copy wallet link, Update data, Upgrade to vN, Notify, and Void.

Voiding passes

Void pass permanently voids a credential: its links are revoked and the pass is flagged for removal from wallets (removal can take up to 24 hours to propagate). Voiding is available on issued passes, individually or in bulk, and cannot be undone. A pass can also void itself automatically when its last allowed scan is used, if the template’s redemption rule has Auto-void after reaching limit turned on.