Wallet passes

Ready, set, Wallet

Create the pass. Pick the audience. Send. Apple Wallet and Google Wallet in one platform — no add-on fees, no extra tools.

Phone showing a grocery loyalty pass in Wallet, fanned with a boarding pass, a bank rewards pass and a pizzeria stamp card

Everything Wallet needs, in one platform

A wallet pass puts your loyalty card, coupon, or ticket next to your customer’s bank cards — they save it without an app, and it changes when your data does. The hard part is everything around the pass: who gets it, how it reaches them, and what happens when their data changes.

New to the format? Start with What is a wallet pass and Apple Wallet vs Google Wallet.
One flow in a single platform: pass designs for Apple and Google with personal fields and a payment-to-update journey on the left, the finished bank pass on a phone in the center, and the push, email and SMS messages that deliver it on the right

Any other setup

  • Your own code or a second tool — a custom build or a pass builder bolted onto a separate sender.
  • Customer data exported by hand — the pass tool never shares a customer list with your CDP.
  • Links pasted into messages — every campaign means copying install links between tools.
  • Updates need engineering — each change goes through your own Apple and Google calls.
  • Two or more subscriptions — plus the servers behind a custom build.

Pushwoosh

  • Builder, template, or API — one place to create Apple Wallet and Google Wallet passes.
  • Personal fields filled from tags — name, points, or seat come straight from the customer profile.
  • Link lands in push, email, or SMS — or goes out automatically as a journey step.
  • Saved passes update themselves — campaign edits, tag sync, or the REST API.
  • One subscription — Wallet is part of the platform, not an add-on.

Where passes do the most work

Same pass technology, different jobs — pick your business to see the customer path and the Pushwoosh setup side by side:

Issue. Target. Send. Update.

Pushwoosh is a wallet pass creator and a messaging platform in one. Every pass belongs to a customer profile, so you never match passes to audiences in a spreadsheet.

1. Issue

Design an Apple Wallet and a Google Wallet version of the pass in the builder, or set it up once as a pass campaign with shared and personal fields. Pushwoosh signs the Apple pass with your own certificate.

2. Target

Issue each pass to a Pushwoosh User ID. Personal fields like name, points, or seat fill in from that customer’s tags or event data.

3. Send

The customer gets a push or an email and taps Add to Wallet. Your team adds an Issue Wallet Pass step to a journey, then a Send Push or Send Email step with the personal install link. For a shared pass, put one link or QR code into any push, email, or SMS.

4. Update

The customer opens Wallet and sees the new balance, seat, or offer on the same pass. Edit the campaign, let tag sync refresh passes when customer data changes, or call the API — Apple and Google update the pass on the phone.

Pass builder in Pushwoosh with boarding pass settings and a live preview of an airline pass
Pass fields editor mapping gate, origin, and destination values with per-field update messages next to the pass preview
Geozone-triggered journey in Pushwoosh that issues a wallet pass and sends iOS and Android pushes with the pass link
Flight journey in Pushwoosh that waits for a status change and sends a gate change push while the saved pass updates

Your passes come with a full crew

A pass on its own just sits in a wallet. In Pushwoosh, the channels that deliver it and the customer data behind it already live in the same account — so the price of running Wallet looks like this.

What your Wallet setup includes

  • Mobile push — sends the install link and change alerts
  • Email — an Add to Wallet button in receipts and campaigns
  • SMS — reaches customers who don’t have your app
  • Customer Journey Builder — issues a personal pass at any step
  • Segmentation & CDP — the tags and events behind personal fields
  • Personalization — each customer’s name, tier, or offer in the message
  • Analytics — how the messages carrying your passes perform

Wallet add-on fee: $0 — it’s part of the platform, your price depends on your plan.

Phone lock screen with a Wallet cashback alert, a bank push, an email statement and an SMS receipt stacked together

Safe choice

ISO 27001:2022 Certified

ISO 27001:2022

Pushwoosh meets industry standards for online security and is certified by ISO 27001:2022.

GDPR Compliant

Ensuring GDPR compliance

We maintain the highest standards of compliance with data protection regulations.

OWASP Compliant

Adhering to OWASP principles

Our platform embraces the Security by Design approach to prevent potential threats.

HIPAA Compliant

HIPAA

Pushwoosh is HIPAA compliant, ensuring the confidentiality, integrity and availability of PHI(ePHI).

SOC 2 Type 2 Certified

SOC 2 Type 2

Pushwoosh possesses a SOC 2 Type 2 report, reflecting our commitment to ensuring the utmost security of user data.

Data Privacy Framework

DPF certified

Pushwoosh is officially certified under the EU-U.S. Data Privacy Framework, including the UK extension, and the Swiss DPF.

Full certification detail on the data safety page.

Questions people ask before they start

New to Wallet

Switching from another solution