> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getstell.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Adding the pass to a wallet

> Which wallet buttons customers see on each device, and what happens when they tap them

The last step of [enrollment](/enrollment/how-enrollment-works) 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](/enrollment/wallet-button-widget) on your own site.

<Note>
  This behavior comes with the experiences Stell hosts: the enrollment flow
  and the [wallet button widget](/enrollment/wallet-button-widget). Passes
  delivered another way — wallet links in
  [emails](/enrollment/wallet-button-widget#in-your-emails), or an
  integration your developers build on the [Stell
  API](/api-reference/integration/add-to-wallet) — don't include device
  detection or the QR code hand-off.
</Note>

Pick the customer's device:

<Tabs>
  <Tab title="iPhone" icon="mobile">
    **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.

    <Note>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.</Note>
  </Tab>

  <Tab title="Android phone" icon="mobile-screen-button">
    **What the customer sees:** the **Add to Google Wallet** button — Apple Wallet passes can't open on Android, so that button is never offered here.

    **What tapping does:** Google's save page opens and the pass lands in Google Wallet.

    <Note>If your program offers only Apple Wallet, an Android visitor instead sees "No compatible wallet is available for your device" with a suggestion to try an iPhone or Mac.</Note>
  </Tab>

  <Tab title="Computer" icon="desktop">
    **What the customer sees:** every wallet your program offers. A program with both shows **Add to Apple Wallet** and **Add to Google Wallet** side by side, and the customer chooses.

    <Frame caption="On a computer, a program that offers both wallets lets the customer choose.">
      <img src="https://mintcdn.com/stell/Ty7Bh0WRcITPBqum/images/enrollment/wallet-choice-desktop.png?fit=max&auto=format&n=Ty7Bh0WRcITPBqum&q=85&s=d14dec97c6fa2339729694c1099bb90d" alt="The wallet step on a computer with the Add to Apple Wallet and Add to Google Wallet buttons side by side" width="2880" height="720" data-path="images/enrollment/wallet-choice-desktop.png" />
    </Frame>

    **What tapping Add to Apple Wallet does** depends on the browser:

    * **Safari on a Mac** — the Wallet app on the Mac opens with the pass.
    * **Any other browser** (Chrome, Edge, or Firefox on a Mac; any browser on Windows) — a **Scan to add your pass** dialog shows a QR code. The customer points their iPhone camera at it and the pass opens in Apple Wallet on the phone. The pass is never downloaded as a file.

    <Frame caption="The QR code moves the pass from the computer to the iPhone that can hold it.">
      <img src="https://mintcdn.com/stell/Ty7Bh0WRcITPBqum/images/enrollment/qr-dialog.png?fit=max&auto=format&n=Ty7Bh0WRcITPBqum&q=85&s=48a4a36a6d909bd5f72993fc23214fab" alt="The Scan to add your pass dialog showing a QR code to scan with an iPhone" width="2880" height="1426" data-path="images/enrollment/qr-dialog.png" />
    </Frame>

    The pass link behind the QR code is time-limited. If the customer waits too long, the code stops working — closing the dialog and tapping **Add to Apple Wallet** again produces a fresh one.

    **What tapping Add to Google Wallet does** is the same in every browser: Google's save page opens, the customer signs in to their Google account, and the pass appears in Google Wallet on their Android phone.
  </Tab>
</Tabs>

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.

<Tip>
  A customer stuck on this step? See [enrollment
  troubleshooting](/enrollment/troubleshooting) for the situations support
  staff hear about and how to resolve them.
</Tip>