Skip to main content

Understanding Apple and Google Wallet

The Must-Read Quick Guide to Wallet Pass Limitations & Capabilities

Paul Tomes avatar
Written by Paul Tomes
Updated this week

Introduction

Before creating digital passes with PassKit, it’s essential to understand how Apple Wallet and Google Wallet truly work. These platforms have specific rules and limitations—not imposed by PassKit, but by Apple and Google themselves.


What Digital Passes Excel At

Digital passes are powerful tools for replacing physical cards, tickets, and coupons. With PassKit, you can create:

  • Loyalty & Membership Cards – Track points, rewards, and VIP access

  • Coupons & Offers – Deliver instant, scannable promotions

  • Event Tickets – Enable quick check-ins and real-time updates

  • Boarding Passes – Update flight gates, times, and seating dynamically

  • Digital IDs – Verify identity or grant access

Key Features:

Barcodes, QR codes, and NFC – For easy scanning
Real-time updates – No need for users to download new passes
Wallet integration – Always accessible on users’ devices


What Wallet Passes Don’t Do

These are not PassKit limitations—they are ecosystem rules set by Apple and Google:

Feature

Limitation

Why?

Design Freedom

Must follow Apple/Google templates.

Ensures consistency & security.

Automatic Location Tracking

Just opening a pass doesn’t trigger actions.

Privacy & battery optimization.

Payments

Cannot process transactions (use Apple/Google Pay).

Separate from payment systems.

Push Notifications

Users must have notifications enabled for updates.

User control & anti-spam.

PassKit gives you more flexibility than most alternatives—but these core rules apply to all wallet providers.


How Pass Updates Really Work

Wallet passes are not magic

  • They don’t automatically update just because someone pays with Apple Pay or Google Pay.

  • They don’t detect when a customer walks into your store and completes a transaction.

  • There’s no link between payment cards and passes in the Wallet app.

Passes need to be explicitly told what to update

There are 3 main ways to trigger updates

  1. Manual UpdateYou log into PassKit and edit passes directly.

  2. Scan-Based Update – A staff member scans the pass (e.g., with PassReader).

  3. System Integration – You POS/CRM/Event Softwate sends transaction the updated information to PassKit

No trigger? No update!

Opening or viewing a pass does nothing - this is by design. This is how all wallet systems operate—PassKit simply provides the tools to make it seamless.


Common Misconceptions

Myth:"If a customer opens their pass, I’ll get data"

Fact: You only get data if a pass is issued, installed, updated or deleted.

Myth: "I can design passes however I want"

Fact: Apple & Google enforce templates—PassKit offers the most customization possible.

Myth: "Another wallet provider can bypass these rules"

Fact: These are Apple & Google’s rules—PassKit provides more features than competitors.


Key Considerations Before Getting Started

Ask yourself these critical questions to ensure success:

1. How Will Passes Update?

Choose your update method based on your workflow:

  • Manual Updates (You edit passes directly in PassKit)

  • Staff Scanning Passes (Using PassReader or your own scanning app)

  • Automated Integration (Best for scalability):

    • No-Code Options:

      • PassKit is available on Make.com (formerly Integromat) and Zapier

      • Connect to 5,000+ apps (e.g., Shopify, Mailchimp, Google Sheets) without coding

    • Developer-Led API Integration:

      • Directly connect your POS (Square, Clover, etc.), CRM (Salesforce, HubSpot), or custom systems

2. What Data Needs to Be Dynamic?

Identify which elements must update in real-time:

  • Loyalty points/balances

  • Membership tiers/status

  • Coupon redemption status

  • Event check-ins/access control

  • Expiration dates or limited-time offers

3. Will Users Enable Push Notifications?

  • Pass updates can trigger notifications, but users must opt-in.

  • Design your UX to explain the value (e.g., "Enable notifications for real-time rewards!").

4. Do You Need Developer Help?

  • No-Code: Use Make/Zapier if your tools are supported.

  • Pro Code: For custom systems, a developer will need to use PassKit’s API.

  • Hybrid: Some platforms (like Shopify) offer pre-built integrations + customization.

Pro Tip: Start with no-code automation to test workflows, then scale to API if needed.


Conclusion

Now that you understand how Apple Wallet & Google Wallet truly work—and why PassKit is the most powerful platform within these rules—you’re ready to build amazing digital pass experiences.

🚀 Sign up for PassKit today and start creating!


Did this answer your question?