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 |
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 |
Setup complexity compared
What it takes to go live on each platform
- 1Create your wheel and set prizes (5 minutes)
- 2Customize pass design -- logo, colors, info (5 minutes)
- 3Print QR code and place at restaurant (5 minutes)
Wallet passes are generated automatically when guests win. No separate wallet configuration needed.
- 1Create account and configure stamp card
- 2Set reward thresholds (e.g., 10 stamps = free coffee)
- 3Enable Apple/Google Wallet integration
- 4Train staff on scanning stamps
Stamp-based model. Guests collect stamps per visit or purchase. Wallet pass displays stamp count.
- 1Enable Loyalty in Square Dashboard
- 2Set point rules and rewards
Only works within Square ecosystem. No wallet passes -- loyalty lives in the Square app. Fastest setup if you're already a Square merchant.
- 1Sales call and contract negotiation
- 2POS integration setup (technical)
- 3Menu and reward configuration
- 4Staff training across locations
- 5Pilot period and adjustments
Enterprise-grade. The setup complexity reflects the integration depth -- Como connects directly to your POS, CRM, and menu systems. Worth it for 10+ locations.
- 1Create account and configure pass template
- 2Set up distribution method (URL, QR, API)
- 3Configure push notification triggers
- 4Integrate with your existing systems (API)
Developer-focused. The API is well-documented, but you need someone technical to set it up properly.
- 1Design your pass (drag-and-drop editor)
- 2Set up distribution link or QR code
- 3Configure push messages
Simple pass creation tool. No loyalty logic, no gamification, no email capture. You manage the pass content manually.
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: