Push Notifications Reference

Daniel Baudino

Updated March 02, 2026

TL;DR: How to send notifications to wallet pass holders.
  • Apple: Requires pass update + APNs + web service
  • Google: Direct API call, no pass update required
  • Apple: ~20 notifications/day limit (unofficial)
  • Google: 3 notifications/day limit (enforced)
  • Keep notifications time-sensitive and under 140 characters

Overview

This reference covers push notifications for Apple Wallet and Google Wallet passes. The platforms use fundamentally different architectures — Apple requires a cooperative web service, while Google provides a direct API.

Quick Reference

SpecApple WalletGoogle Wallet
Notification triggerPass must be updatedMessage API (no update required)
Daily limit~20 per pass3 per pass
Requires web serviceYesNo
Requires APNsYesNo
Silent updatesYes (no changeMessage)Yes (TEXT type)
Marketing allowedNoLimited
Character limit~140 (60-80 on Watch)~140

Apple Wallet

How It Works

Apple Wallet notifications require a 4-step cooperative process:

  1. Device registers with your server (stores push token)
  2. Pass content changes on your server
  3. Your server sends push notification via APNs
  4. Device fetches updated pass from your web service

You cannot send arbitrary notifications. Notifications are tied to actual pass updates.

BehaviorResult
changeMessage includedUser sees notification
changeMessage omittedSilent background update
Multiple fields with changeMessageSummarized as "Pass was changed"

Notifications are for time-sensitive information that requires immediate attention.

Limits and Restrictions

RestrictionDetails
Daily limit~20 notifications per pass (not officially documented)
TestingPhysical device only (Simulator does not register)
EnvironmentProduction APNs only
Authentication tokenNever change after pass creation

Google Wallet

How It Works

Google Wallet notifications use the AddMessage API:

  1. Call AddMessage API with TEXTANDNOTIFY
  2. Google sends push notification
  3. User taps notification → opens pass
  4. Message displayed on back of pass

No web service required. No pass update required. Direct API call.

Message Types

TypeBehavior
TEXT_AND_NOTIFYSends push notification + adds message
TEXTAdds message silently (no notification)

API Endpoint

POST https://walletobjects.googleapis.com/walletobjects/v1/{resourceType}/{resourceId}/addMessage

Resource types: - loyaltyObject - eventTicketObject - offerObject - giftCardObject - genericObject

FieldRequiredDescription
headerYesNotification title
bodyYesNotification body
idYesUnique message identifier
messageTypeYesTEXT_AND_NOTIFY or TEXT

Notification Limits

LimitValue
Notifications per 24 hours3 per pass
Exceeding limitQuotaExceededException
ThrottlingGoogle may throttle if spam detected

Expiry Notifications

Google can automatically send notifications before pass expiration:

Notification TypeTiming
expiryNotification2 days before expiration
upcomingNotification1 day before pass becomes valid

Platform Comparison

Architecture

AspectApple WalletGoogle Wallet
InfrastructureYour server + APNsGoogle API only
ComplexityHigh (web service required)Low (API call)
Pass update requiredYesNo
Real-time controlYes (your server)Limited (API quota)

Notification Triggers

TriggerApple WalletGoogle Wallet
Field value changeYes (with changeMessage)No (use AddMessage)
Arbitrary messageNoYes (within limits)
Expiration reminderManualAutomatic (optional)
Location-basedVia relevantTextVia locations

Best Practices

PracticeAppleGoogle
Max daily notifications~3 recommended3 enforced
Character length<140 chars<140 chars
Time-sensitive onlyRequiredRecommended
Marketing messagesNot allowedLimited

Common Mistakes

  1. Sending empty push without pass change (Apple) — Device will fetch pass but find no changes

  2. Exceeding Google's 3/day limit — Results in QuotaExceededException

  3. Using sandbox APNs (Apple) — Wallet notifications only work in production

  4. Forgetting changeMessage (Apple) — Update happens silently, user sees nothing

  5. Sending identical messages (Google) — May be flagged as spam

  6. Including marketing in Apple notifications — Violates guidelines

  7. Not monitoring APNs feedback (Apple) — Invalid tokens accumulate

  8. Long notification text — Truncated on lock screen and Apple Watch

Sources

Was this article helpful?
Yes No

More articles in Pass Alerts

Time Based Surfacing Reference

This reference covers time-based pass surfacing for Apple Wallet and Google Wallet. When the rele...

Location And Geofencing Reference

This reference covers location-based pass surfacing for Apple Wallet and Google Wallet. When user...