97% of wallet passes are still on guests’ phones after 30 days. For apps, it’s 25%. That one stat explains why every restaurant loyalty platform is racing to add wallet integration.
Wallet passes turn a guest’s phone into a persistent reminder of your restaurant. No app download. No account creation. No storage complaints. The pass sits alongside credit cards and boarding passes, pushes notifications to the lock screen, and triggers alerts when the guest walks nearby. This guide breaks down what wallet integration actually means for restaurants, how Apple Wallet and Google Wallet differ, and how 6 platforms compare on features, pricing, and setup complexity. The goal: help you pick the right tool without wading through marketing pages.
What wallet integration actually means
A wallet pass is a digital card saved to Apple Wallet (iPhone) or Google Wallet (Android). It’s the same technology behind boarding passes and event tickets. For restaurants, wallet passes typically serve as coupon cards, loyalty stamps, or reward certificates.
The power isn’t in the card itself. It’s in what happens after the guest saves it.
Pass types
Coupon, loyalty stamp card, event ticket, or generic pass. Each type has a different layout and behavior. Coupons show a barcode and expiry date. Loyalty cards can display a stamp or point balance. Event tickets support date-based lock screen surfacing.
Push notifications to lock screen
When you update a pass (new offer, balance change, expiry warning), the guest gets a lock screen notification. No app required. No push permission prompt. The notification just appears, exactly like an app notification would.
Geofence alerts
Set GPS coordinates and a radius (100-300 meters works best for restaurants). When the guest enters that zone, their phone buzzes with your pass. “You’re near Mario’s Cafe — your 10% coupon is waiting.” This works without the guest opening any app.
Real-time pass updates
Change the offer, update the balance, swap the message. The update pushes to every guest who holds the pass. No app version review, no waiting for store approval. Changes go live in seconds.
Works on every smartphone
Apple Wallet is pre-installed on every iPhone sold in the last decade. Google Wallet runs on Android 5.0+ devices (released 2014). Between them, you reach 99%+ of smartphone users without asking anyone to download anything.
Apple Wallet vs Google Wallet: key differences
| Feature | Apple Wallet | Google Wallet |
|---|---|---|
| Pass types supported | Coupon, loyalty, event ticket, boarding pass, generic | Loyalty, offer, gift card, event ticket, transit, generic |
| Push notifications | Yes — on pass update | Yes — on pass update |
| Location triggers | Yes — GPS + WiFi + cell tower | Yes — GPS-based |
| NFC support | Limited to Apple Pay NFC | Full NFC support for passes |
| Update mechanism | Push via APNs (Apple Push Notification service) | Push via Google API |
| Market share by region | ~55% US/UK/AU, ~27% SEA | ~72% SEA/global, ~44% US |
| Setup complexity | Requires Apple Developer certificate ($99/yr) or platform | API-based, no developer certificate needed |
| Pass expiration | Built-in relevant date field | Built-in expiration support |
| Offline access | Full offline — pass stored locally | Full offline — pass stored locally |
For restaurants in the US, UK, and Australia, Apple Wallet reaches the majority of guests. In Southeast Asia, the Middle East, and most of Europe, Google Wallet has higher penetration. A good loyalty platform generates passes for both automatically — so you don’t have to choose.
6 platforms compared: wallet integration for restaurants
Features, pricing, and honest trade-offs:
| Feature | SpiniX | Stamp Me | Square Loyalty | Como Sense | PassKit | Loopy Loyalty |
|---|---|---|---|---|---|---|
| Apple Wallet | Yes | Yes | No | Yes | Yes | Yes |
| Google Wallet | Yes | Yes | No | Yes | Yes | Yes |
| Push notifications | Yes | Yes | In-app only | Yes | Yes | Yes |
| Geofence alerts | Yes | Limited | No | Yes | Yes | No |
| Real-time updates | Yes | Yes | N/A | Yes | Yes | Yes |
| QR trigger | Yes — gamified | Yes — stamp scan | Yes — POS-based | Yes — POS-based | Yes — scan | Yes — scan |
| Setup time | ~15 minutes | ~30 minutes | ~10 minutes (if on Square) | 1-4 weeks (custom) | ~1 hour | ~20 minutes |
| Monthly pricing | From EUR 29/mo | From $49/mo | From $45/mo | Custom ($200-500+/mo est.) | From $35/mo | From $15/mo |
| Best for | Gamified rewards + review collection | Digital stamp cards | Square POS users | Enterprise multi-location | Developers / custom pass flows | Budget passes only |
Notes:
- Square Loyalty does not support Apple or Google Wallet passes. It works through the Square app ecosystem. Strong choice if you already run Square POS, but no wallet pass functionality.
- Como Sense has the deepest POS integration of any platform listed. If you operate 10+ locations with a major POS system (Oracle, NCR, Lightspeed), Como’s custom pricing may be justified by the integration depth.
- Loopy Loyalty is the most affordable option, but it’s a pass management tool, not a loyalty engine. You get wallet passes with push notifications, but no gamification, no email capture, no review collection.
- PassKit is developer-friendly with strong API documentation. Best for teams that want full control over the pass flow. Not ideal for restaurants without technical staff.
Setup complexity compared
SpiniX — 3 steps (~15 minutes total)
- Create your wheel and set prizes (5 minutes)
- Customize pass design — logo, colors, info (5 minutes)
- Print QR code and place at restaurant (5 minutes)
Wallet passes are generated automatically when guests win. No separate wallet configuration needed.
Stamp Me — 4 steps (~30 minutes + staff training)
- Create account and configure stamp card
- Set reward thresholds (e.g., 10 stamps = free coffee)
- Enable Apple/Google Wallet integration
- Train staff on scanning stamps
Square Loyalty — 2 steps (~10 minutes if already on Square)
- Enable Loyalty in Square Dashboard
- Set point rules and rewards
Only works within Square ecosystem. No wallet passes.
Como Sense — 5+ steps (1-4 weeks)
- Sales call and contract negotiation
- POS integration setup (technical)
- Menu and reward configuration
- Staff training across locations
- Pilot period and adjustments
Enterprise-grade. Worth it for 10+ locations.
PassKit — 4 steps (~1 hour, more with custom API work)
- Create account and configure pass template
- Set up distribution method (URL, QR, API)
- Configure push notification triggers
- Integrate with your existing systems (API)
Developer-focused.
Loopy Loyalty — 3 steps (~20 minutes)
- Design your pass (drag-and-drop editor)
- Set up distribution link or QR code
- Configure push messages
Simple pass creation tool. No loyalty logic, no gamification, no email capture.
When wallet passes aren’t the right choice
Wallet passes work well for most restaurants, but they’re not always the best fit. Honest assessment:
- You need deep POS integration. If your loyalty program needs to read line-item purchase data, apply rewards automatically at checkout, or sync with inventory — wallet passes alone won’t do this. You need a POS-integrated system like Como Sense or Square Loyalty. Wallet passes are a display and notification layer, not a transaction layer.
- Your guests are mostly 65+. Wallet adoption skews younger. Among 18-44 year olds, 78% have used a wallet pass. Among 65+, it drops to 31%. If your core audience is older, physical loyalty cards or SMS-based programs may get higher participation rates.
- You already have a working app with high retention. If you’re a large chain with an app that already has 50,000+ active users and 40%+ monthly retention, adding wallet passes may fragment the experience. For single-location and small multi-location restaurants, wallet passes are almost always better than an app. For chains with established apps, they’re a complement, not a replacement.
- You need complex tier-based programs. Bronze, Silver, Gold, Platinum tiers with different earn rates, exclusive events, and personalized offers. Wallet passes can display a tier label, but the complex logic behind tier management needs a backend system. Platforms like Como handle this natively. Simpler tools like SpiniX and Loopy Loyalty focus on single-tier reward mechanics.
Wallet integration for restaurants: FAQ
Do guests need to download an app for wallet passes?
No. Apple Wallet is pre-installed on every iPhone. Google Wallet comes pre-installed on most Android devices. The guest taps “Add to Wallet” and the pass saves in under a second. No App Store, no account creation, no storage used.
Can I send unlimited push notifications through wallet passes?
Not exactly. Wallet notifications trigger on pass updates (content changes), time events (relevant dates), and location events (entering a geofence). You can’t blast arbitrary messages like SMS. This is by design — it prevents spam and keeps notification quality high, which is why visibility rates are near 100%.
What happens if a guest doesn’t add the pass?
They still receive the reward via email. The wallet pass is an additional touchpoint, not the only one. Email-only guests show ~21% return rates. Email plus wallet pass guests show ~31% return rates. The wallet amplifies, but email works on its own.
How much does wallet integration cost?
Standalone: building custom passes requires an Apple Developer account ($99/year) plus development time ($5,000-20,000). Through a platform: $15-50/month depending on the tool. Some platforms (like SpiniX) include wallet passes in the base subscription with no per-pass fees.
Is wallet-based loyalty GDPR compliant?
Yes. The guest actively chooses to add the pass. They can remove it at any time. No personal data is stored in the pass itself — it contains a reference ID linked to your server. Location notifications require the guest to enable Location Services, which is their choice.
Which wallet has better reach globally?
It depends on your market. Apple Wallet dominates in the US (~55%), UK (~55%), and Australia (~53%). Google Wallet leads in Southeast Asia (~72%), India (~85%), and most of Latin America (~70%). In Europe, it’s roughly split. A platform that supports both covers 99%+ of smartphone users.