How to Distribute Wallet Passes: 7 Methods Compared

Getting a wallet pass designed and issued is the easy part. Getting it onto a customer's phone is where most implementations stall. There are seven distinct distribution methods, each suited to a different context. Some require almost no technical work; others integrate deeply with your existing systems. This guide covers all seven, with honest assessments of where each one shines and where it falls short.

1. Email with an Add to Wallet link

The most widely used method. You generate a personalised pass URL for each customer and include it as an “Add to Apple Wallet” or “Add to Google Wallet” button in a transactional email — confirmation, welcome or post-purchase message.

How it works: The button links to a hosted pass URL. On iOS, tapping the Apple Wallet button downloads the .pkpass file, which iOS opens directly in Wallet. On Android, tapping the Google Wallet button redirects to the Wallet save flow.

Pros: Reaches your entire existing customer list. No additional infrastructure beyond your normal email sending. Works for both platforms with two buttons or one universal URL that detects the device.

Cons: Dependent on email open rates. Customers must be on a mobile device when they open the email — clicking on desktop does not add the pass to a phone wallet without extra steps.

Best for: Post-signup confirmation emails, post-purchase loyalty card issuance, membership welcome sequences. Any situation where you already have the customer's email address and they expect a confirmation message.

2. SMS link

An SMS containing a short URL to the pass. When the customer taps the link on their phone, they are taken directly to the Add to Wallet flow.

How it works: You send an SMS via a provider such as Twilio or MessageBird with a shortened pass URL. The URL resolves to the platform-appropriate wallet save flow.

Pros: Extremely high reach — SMS open rates exceed 90%. The customer is almost certainly on a mobile device when they read it. Particularly effective for customers who rarely check email.

Cons: SMS costs money per message, which adds up at scale. Some customers find unsolicited SMS intrusive. Requires phone number collection at the point of sign-up.

Best for: High-value customers where pass adoption is worth the SMS cost. Re-engagement campaigns for customers who did not engage with the welcome email. Event-day distribution where immediacy matters.

3. QR code on a website, receipt or poster

A QR code that encodes the pass distribution URL. The customer scans it with their phone camera, which opens the Add to Wallet prompt.

How it works: For anonymous distribution (same pass template for everyone), the QR code links to a page that creates a new pass on the fly and redirects to the wallet save flow. For personalised passes, the QR code is generated per customer and printed on receipts, letters or membership packs.

Pros: Works in physical environments where a phone number or email is not yet known. No data plan needed — the QR code scan works over any connection. Inexpensive to produce: print on a receipt or display on a screen.

Cons: Requires the customer to proactively scan. Lower conversion rate than a direct link delivered to an inbox. Anonymous QR codes produce passes without personalisation unless the customer signs in first.

Best for: In-store loyalty card sign-up at point of sale. Posters at venue entry points. Printed membership packs. Website confirmation pages.

4. NFC tag tap

An NFC tag programmed with the pass URL. The customer taps their phone to the tag and the Add to Wallet prompt appears.

How it works: NFC tags (NTAG213 or similar) store a URL record. When a compatible phone — which is essentially every modern smartphone, given that 94% have NFC — touches the tag, iOS and Android read the URL and either open a pass or trigger the wallet save flow.

Pros: Frictionless for the customer. No scanning required — just a physical tap. Works reliably in low-light environments where QR scanning is difficult. Tags can be embedded in membership cards, desk stands or entry barriers.

Cons: Has a hardware cost (tags cost approximately 20–50p each in bulk). Requires physical deployment at the point of use. Not suitable for remote or online-only distribution scenarios.

Best for: Venue front desks, gym reception areas, conference badge handouts, retail point of sale. Any physical touch point where speed of pass adoption matters.

5. In-app Add to Wallet button

For businesses with an existing iOS or Android app, an in-app button is the smoothest possible user experience.

How it works: On iOS, use the PassKit framework. A PKAddPassesViewControllerpresents the pass preview and “Add” button natively inside your app. On Android, use the Google Wallet API's save-to-wallet flow with a PayClient. Both platforms provide official UI components that match the wallet's native design.

Pros: Best possible user experience — no browser redirect, no email to open. The add flow is one tap from within your app. High conversion rate because the customer is already authenticated and engaged.

Cons: Requires an existing native app. App development and maintenance cost is significant. Not available for businesses that are web-only.

Best for: Fintech apps issuing loyalty or payment cards. Retail apps with a high-engagement customer base. Any business where the app is the primary customer interface.

6. CRM automation (e.g. HubSpot)

Trigger pass creation automatically from within your CRM when a deal closes, a form is submitted or a contact reaches a particular lifecycle stage.

How it works: Issuepass connects directly to HubSpot. When a trigger fires — a deal moves to Closed Won, a contact's membership tier changes, a form submission completes — Issuepass creates the pass and sends the distribution email automatically. No manual step is required. Pass data (name, tier, member ID) is pulled directly from CRM fields.

Pros: Zero manual work after setup. Scales to any volume. Pass issuance happens at exactly the right moment in the customer journey. CRM data stays in sync with pass data automatically.

Cons: Requires a CRM integration setup. HubSpot-specific at present, though other CRMs can be connected via Zapier or webhook.

Best for: Membership organisations managing their member lifecycle in a CRM. SaaS businesses issuing passes when a customer upgrades to a paid plan. Any team that wants pass issuance to be a fully automated part of their sales or onboarding workflow.

7. Zapier or webhook trigger

The most flexible method. Connect Issuepass to any application that can fire a webhook or integrate with Zapier — which covers thousands of tools.

How it works: Your application sends a webhook to the Issuepass API when a relevant event occurs. The payload contains the customer's details and the template ID to use. Issuepass creates the pass and returns the Add to Wallet links, which your application can then include in an email or display on screen. With Zapier, you connect Issuepass as an action in a Zap triggered by any supported app — Typeform, Shopify, Stripe, and so on.

Pros: Works with any tool that supports webhooks or Zapier. No custom integration code required for common platforms. Can be set up in minutes for straightforward use cases.

Cons: Webhook-based flows require some technical setup. Zapier adds a monthly cost if you are on a paid plan. Debugging failures requires access to your webhook logs.

Best for: Businesses using non-HubSpot tools. Teams that want to prototype a pass distribution flow quickly without committing to a full API integration. Multi-step automations that combine pass issuance with other actions (send Slack notification, update a spreadsheet, and so on).

Recommendation matrix

No single method is universally best. The right choice depends on your infrastructure, your customers' context and your team's technical capacity.

• Start here if you have an email list: Email with Add to Wallet link. Low effort, immediate reach.
• Start here if you have a physical venue: QR code at point of sale plus NFC tags at the front desk. Cover both scanning preference and tap preference.
• Start here if you use HubSpot: CRM automation. Set it up once, issue passes forever.
• Start here if you use a different tool: Zapier or webhook. Connect in minutes.
• Add later when volume is established: SMS for re-engagement campaigns targeting customers who have not yet added their pass.

Most businesses end up using two or three methods in combination — for example, email on sign-up, QR code on printed receipts and CRM automation for tier upgrades.

Start free and distribute your first wallet pass in minutes.