As your pass offerings evolve, you may want to retire old templates or prevent outdated passes from being used. Our platform gives you two options:
Archive a pass template to tidy up your workspace
Void passes to deactivate them in your customers’ wallets
Let’s break down what each one does—and how it affects end users.
📁 What Does Archiving a Pass Template Do?
Archiving a pass template helps keep your workspace organized.
Moves the template into your “Archived” folder
Prevents new passes from being created from it
Keeps all historical data and pass records intact
Does not affect any passes already issued to users
✅ Use this to clean up your workspace when a pass template is no longer in use.
🚫 What Does Voiding a Pass Do?
Voiding a pass deactivates it in the user's wallet.
The QR code or barcode becomes inactive
The pass may appear as Expired, Inactive, or grayed out
The user will not receive future updates or push notifications
The pass is no longer usable or valid
⚠️ Voided passes can’t be reactivated. To give access again, create a new pass and share a fresh download link.
✅ How to Archive (and Optionally Void)
Navigate to the Pass Template
Go to the pass template you'd like to archive.Click “Archive Template”
This removes the template from your active list.Choose Whether to Void Passes
When archiving, you’ll see the option:
“Void all passes associated with this template”
Check this to ensure no one can continue using outdated passes.
🔄 You can archive a template without voiding passes. But if you need to stop usage, make sure to void.
🔔 What Customers See When a Pass is Voided
Apple Wallet:
Voided or expired passes are moved to the “Expired Passes” section. They’re no longer visible in the main wallet view and cannot be used or updated. Barcodes may appear grayed out or removed.Google Wallet:
Voided passes may disappear entirely from the user’s wallet or become marked as inactive. The pass is no longer linked to their device and cannot receive updates or display notifications.
📣 We recommend notifying your users before voiding passes to prevent confusion and maintain trust.
📘 Summary
Action | Affects End User’s Wallet? | Can Be Reversed? |
Archive | ❌ No | ✅ Yes |
Void | ✅ Yes – disables the pass | ❌ No |
Still not sure which option is right for your use case? Reach out to our team →