Skip to main content
Passlet doesn’t put passes into wallets directly. Every issued pass exposes add-to-wallet links, and you deliver those links through whatever channel reaches your holders: email, SMS, a confirmation page, or your own app. Each pass has three: A smart link detects the platform it was opened on and redirects to the Apple or Google link for the same pass. One URL works in an email, on a printed QR code, or in a chat message, with no branching on your side. When the platform can’t be determined (a desktop browser, an unusual user agent, a link scanner), the smart link shows a small page with the Add to Apple Wallet and Add to Google Wallet buttons so the holder can pick. It only offers the wallets the pass actually has, so a template with one wallet switched off never shows a dead button.
Smart links respect the same rules as the links they redirect to. A revoked, voided, or not-yet-issued pass shows the same status page it would on a direct link.
  • Console: on the Passes list, use the row action Copy wallet link (Smart link, Apple Wallet, or Google Wallet), or open the pass detail page where all three are listed with copy and QR-code actions.
  • CSV export: the passes export includes Smart Link, Apple Link, and Google Link columns.
  • API: pass objects include their hosted link URLs under hostedLinks. See the API reference.
Opening a link on a phone adds the pass to that wallet. The same pass can be added from both wallet links if the template supports both wallets. If a holder lost the original email or you suspect a link leaked, use Resend links on the pass detail page. This regenerates fresh add-to-wallet links and invalidates the previous ones, smart link included. Passes already added to a wallet stay in the wallet; only the links change. Revoke wallet links invalidates all three hosted links without voiding the pass. Use it when links were shared too widely but the already-installed passes should keep working. To kill the pass itself, void it instead.

​
Grace period for barcode changes

If you edit a pass’s barcode payload (the variable your template’s Scanner properties declare as the scan code), previously distributed payloads keep scanning successfully for a grace period, so holders whose wallets haven’t refreshed yet don’t get rejected at the door. Workspace owners configure this wallet update tolerance (default 8 hours) under Settings → General.