Why Digital Wallet Loyalty Cards Win
A loyalty card that lives in Apple Wallet or Google Wallet is always accessible — no separate app to download, no login to remember. The customer opens their Wallet app (pre-installed on every iPhone and Android device) and their loyalty card with QR is immediately available.
This reduces the "I forgot my loyalty card" problem dramatically, increasing programme participation rates by 20–40% compared to app-only implementations.
Apple Wallet Passes for Loyalty
Apple Wallet supports loyalty passes as the "rewards" pass type. A loyalty pass in Apple Wallet displays:
- Brand logo and colour
- Member name and loyalty tier
- Points or stamp balance (updatable remotely)
- QR or barcode for scanning at till
Adding location-based notifications:
Configure the pass to display a notification when the customer is near your location: "You have 45 loyalty points — you're 5 points from a reward!" This contextual nudge significantly increases visit frequency.
Google Wallet Passes for Loyalty
Google Wallet (formerly Google Pay) supports loyalty cards via the Google Wallet API (previously Google Pay Passes API). Loyalty passes work similarly to Apple Wallet passes — scannable QR, updatable balance.
Implementation:
Both Apple and Google Wallet passes require backend integration with your loyalty platform. Major loyalty platforms (Yotpo, Loopy Loyalty, Swiftly, Stamp Me) offer native wallet pass support.
Setting Up a Wallet Pass
1. Set up your loyalty programme platform
2. Configure the pass design (logo, colours, fields)
3. Generate a pass distribution URL or email flow
4. When customers enrol, they receive an "Add to Apple Wallet / Add to Google Wallet" button
5. One tap adds the pass to their device
Updating Pass Data Remotely
Both Apple and Google Wallet support remote pass updates. When a customer earns points:
- Push a balance update to their pass
- The pass updates in real time on their device
- iOS shows the update as a notification
This real-time feedback is significantly more engaging than a paper or PDF loyalty card with a static balance.
Putting this into practice
Start with the smallest real test you can run. Generate the code, print it at the exact size you plan to use, and scan it with two different phones in the lighting where it will live. Check that the destination page loads quickly on a mobile connection and that the call to action next to the code tells people what they will get. If anything feels slow or unclear, fix it before you print a full batch, because reprints cost more than a short test. Keep a note of the size, material, and placement that worked so the next batch starts from a proven setup.
Common mistakes to avoid
The most common mistakes are easy to avoid once you know them. Long payloads make modules tiny, low contrast makes edges hard to read, and text placed too close to the border eats the quiet zone the scanner needs. Covering a corner finder pattern with a logo or a sticker breaks detection entirely, and a code placed behind glare or on a curved surface fails even when the print is perfect. Review each of these points on a proof copy, and treat any failure as a reason to adjust the design rather than a reason to blame the scanner.
Quick checklist
- Keep the payload as short as practical so modules stay large.
- Keep dark modules on a light background with strong contrast.
- Leave a clear quiet zone on all four sides of the symbol.
- Test the printed code at the real viewing distance and lighting.
- Confirm the destination page loads fast on a phone.
- Recheck the code after any change to the link, design, or placement.
Related tools and guides
- For local payments, the [Pakistan payment QR](/pakistan-payment-qr) page explains the regional flow and what customers see.
- The [regional payment QR](/regional-payment-qr) guide covers payment codes used across different markets.
- The [bulk generator](/bulk-generator) builds many codes from a table when one-off generation would take too long.
- Test every code with the [QR scanner](/qr-scanner) on more than one phone before you publish or print it.
- The [UTM builder](/utm-builder) adds campaign parameters so scans show up separately in your analytics.
- The [blog](/blog) collects more guides on sizing, printing, security, and payments for QR codes.
