Skip to main content
The last step of enrollment is adding the pass to the customer’s wallet. Which buttons appear — Add to Apple Wallet, Add to Google Wallet, or both — and what happens on tap depends on your program’s setup and on the customer’s device and browser. This page is the reference for both, and the same rules apply to the wallet button widget on your own site.
This behavior comes with the experiences Stell hosts: the enrollment flow and the wallet button widget. Passes delivered another way — wallet links in emails, or an integration your developers build on the Stell API — don’t include the QR code hand-off. The pass link an API integration sends shows the right wallet button for the pass, but on a computer it offers the link to copy rather than a QR code.
Pick the customer’s device:
What the customer sees: the Add to Apple Wallet button — in Safari, Chrome, or any other browser. Google Wallet is never offered on iPhone (there is no Google Wallet app on iOS).What tapping does: the pass opens straight in Apple Wallet. One tap on Add and it’s done.
If your program offers only Google Wallet, an iPhone visitor instead sees “No compatible wallet is available for your device” with a suggestion to try an Android device.
Two things hold on every device:
  • The pass is created the moment the customer taps a wallet button. The button shows a spinner while the pass is prepared.
  • Each pass belongs to exactly one wallet. A customer who picks Apple Wallet gets an Apple Wallet pass, not a copy in both.
Wallet-specific enrollment links (for example from your emails) can preselect one wallet, but the device and program checks still apply — a link asking for a wallet the device can’t hold falls back to whatever is available.
A customer stuck on this step? See enrollment troubleshooting for the situations support staff hear about and how to resolve them.