Sending Wallet Passes via Email: Best Practices and Templates

Email remains the most universal distribution channel for wallet passes. Every smartphone user has an email address; not everyone is on the same social platform or messaging app. A well-structured pass delivery email achieves two things: it gets opened, and it converts the open into an add-to-wallet action. Most pass delivery emails fail at one or both. This guide covers what works.

How Pass Delivery via Email Works

Apple Wallet and Google Wallet use fundamentally different mechanisms for pass delivery, which means a single email needs to handle both gracefully.

Apple Wallet: passes are distributed as .pkpass files or via a Universal Link (a standard HTTPS URL). When the recipient taps the link on an iOS device, Safari recognises the file type and prompts them to add it to Apple Wallet. The Universal Link approach is preferred over attaching the file directly to the email — more on why below.

Google Wallet: passes use a “Save to Google Wallet” URL — a Google-hosted URL that, when tapped on Android, opens the Google Wallet app and prompts the user to save the pass. This URL is generated by Issuepass and included in the distribution email automatically.

A single distribution email from Issuepass includes both an Add to Apple Wallet button and a Save to Google Wallet button, so recipients on any device can act immediately. Issuepass email templates handle the button formatting and URL generation — you do not need to build this yourself.

Why Not Attach the .pkpass File Directly?

A common mistake is attaching the raw .pkpass file to the email as an attachment. This fails in two important ways. First, Gmail strips .pkpass attachments for security — Gmail treats unknown file types as potential threats and removes them before delivery. Second, even where the attachment survives, email clients on Android have no native handler for .pkpass files.

The correct approach is always a hosted link — an HTTPS URL that serves the pass. Issuepass hosts all passes and generates the appropriate link for each platform. The Add to Wallet button in your email points to this hosted URL, not to a file attachment. This works across all email clients including Gmail, Outlook and Apple Mail.

Subject Lines That Get Opened

Subject line copy determines whether the email gets opened at all. Several patterns consistently perform well for pass delivery emails:

• “Your [Brand] loyalty card is ready” — clear, personal, implies something waiting for action.
• “Add your membership card to Apple Wallet” — specific to platform, works well for iOS-heavy audiences.
• “Your event ticket is here” — urgency and relevance for event tickets.
• “[Name], your VIP pass is ready to add” — personalisation increases open rates measurably.

Keep subject lines under 50 characters — anything longer gets truncated on mobile lock screens and in-app previews. Avoid the words “coupon”, “promotion” or“discount” in the subject line — these trigger spam filters and are more likely to land in the Promotions tab in Gmail or Outlook's focused inbox alternative. Use“your card”, “your pass” or “your ticket”instead.

Preheader text — the preview line visible in the inbox list — should complement rather than repeat the subject. If the subject is “Your loyalty card is ready”, the preheader might read“Tap to add it to Apple Wallet or Google Wallet.”

Email Body Structure

The goal of the email body is to get the recipient to tap a button. Everything else is secondary. An effective structure has four elements:

1. One-sentence introduction: “Your [Brand] membership card is ready to add to your wallet.” Do not write three paragraphs explaining what a wallet pass is. Assume the recipient understands or is curious enough to tap.
2. Add to Apple Wallet button: prominent, above the fold, using Apple's approved button artwork (black with the Apple Wallet logo). This is for iOS recipients.
3. Save to Google Wallet button: below the Apple button, using Google's approved button artwork. This is for Android recipients. Including both buttons means the email works for any device without device detection.
4. Fallback text: a short sentence for recipients who do not use a wallet app —“Not using a wallet app? Your card details are shown below.” — followed by the key pass fields as plain text. This ensures the email is not a dead end for anyone.

Issuepass email templates follow this structure by default. Customise the header image, button colours and introductory copy to match your brand. Do not move the wallet buttons below the fold — conversion drops sharply when the action requires scrolling.

Device Detection: When to Show One Button vs Both

If your email service provider supports device-based conditional content — showing different HTML blocks based on the user agent — you can hide the Apple button for Android recipients and the Google button for iOS recipients. This produces a cleaner email with a single clear action.

In practice, many email clients and corporate mail servers strip user-agent data, making reliable device detection difficult. The safer approach is to show both buttons with a brief label: “On iPhone: add to Apple Wallet. On Android: save to Google Wallet.” Recipients understand which button applies to them.

Issuepass distribution emails handle this automatically. When you know a recipient's device preference — for example, from a previous pass add event — the system can suppress the irrelevant button for a cleaner experience.

Personalisation Builds Trust

A pass delivery email that greets the recipient by name and shows their specific details — their member number, their event date, their loyalty tier — converts significantly better than a generic send. The customer sees their name on the pass preview and knows it is theirs before they tap the button.

Issuepass populates pass fields from your template data, and the distribution email includes a preview of the pass face. This combination — personalised email, personalised pass preview, one-tap action — achieves the highest add-to-wallet conversion rates.

Gmail and Outlook Behaviour

Gmail on Android may render the Add to Apple Wallet button but it will have no effect when tapped on Android. This reinforces the importance of the Google Wallet button placement. In Outlook, button rendering depends on the Outlook version — always include a plain text fallback link below your buttons for clients that strip HTML button formatting.

For organisations sending to mixed corporate email environments, Issuepass supports a plain text version of the distribution email that includes direct links rather than styled buttons. Plain text emails bypass most corporate email gateway filters and reach inboxes that HTML-rich emails may not.

Automated Delivery with Issuepass

When you create a pass in Issuepass — whether through the dashboard, the API or an automated Zap — the distribution email is sent automatically. You do not need to configure a separate email campaign. The email uses your brand's logo, colours and introductory copy from your workspace settings, and it is sent from your custom domain if configured.

For bulk issuance (importing a CSV of members, for example), Issuepass sends distribution emails in batches to avoid triggering spam rate limits. Each recipient receives their email within minutes of the import completing.

Getting Started

Configure your distribution email template in the Issuepass workspace settings — upload your logo, set your brand colour and write your introductory line. Then create your first pass: the email goes out immediately. Measure add-to-wallet conversion in the Issuepass analytics dashboard and iterate on your subject line and body copy from there.

Start free and send your first pass via email today.