Architectural Comparison: Apple Wallet vs. Google Wallet
While Passinstance provides a unified template designer and REST API that abstracts platform complexity, Apple Wallet and Google Wallet differ fundamentally in how passes are packaged, styled, updated, and metered at the OS level:
Detailed Technical Comparison Matrix
| Feature / Technical Constraint | Apple Wallet (iOS & watchOS) | Google Wallet (Android) | Samsung Wallet (Partner-Gated) |
|---|---|---|---|
| Delivery Artifact | Signed .pkpass ZIP archive (application/vnd.apple.pkpass) | RS256-signed Save JWT URL (https://pay.google.com/gp/v/save/<jwt>) + Cloud REST Object | Partner-gated card reference (samsungWalletCardId, samsungWalletRefId) |
| Color Serialization | Must be rgb(r, g, b) (hex and alpha channels rejected by iOS) | Hexadecimal #RRGGBB (hexBackgroundColor) | Hexadecimal #RRGGBB |
| Field Layout Zones | 6 discrete zones: header, primary, secondary, auxiliary, back, footer | Vertical sections: cardTitle, subheader, header, textModulesData (rows), linksModuleData | Vendor template slots |
| HTML / Clickable Links | Permitted only in backFields via attributedValue (<a href="..."> tags only) | Rendered via dedicated linksModuleData.uris array (uri, description) | Dedicated link fields |
| Update & Push Protocol | Two-step: APNs HTTP/2 silent push ({} payload, max 4096 bytes) wakes iPhone to pull GET /v1/passes/... | Single-step: Server executes REST PATCH on walletobjects/v1/...; Google Play Services pushes to phone | Provider REST API |
| Lock-Screen Alert Trigger | Field value changes on a field defining changeMessage: "... %@" | notifyPreference: "NOTIFY_ON_UPDATE" or addMessage (TEXT_AND_NOTIFY, max 3 per 24h) | Not enabled as primary push surface |
| Active Pass Metering | Per registered deviceLibraryIdentifier (1 iPhone + 1 paired Apple Watch = 2 registrations) | Deduplicated per unique <issuerId>.<objectId> across all Android devices signed into the same Google Account | Account-scoped where enabled |
| Geofencing & Beacons | Up to 10 GPS coordinates (locations) + up to 10 BLE iBeacons (beacons) per .pkpass | Up to 10 GPS coordinates on Class/Object (locations note: deprecated/restricted by Google in newer Play Services) | Device-dependent |
| Deletion Telemetry | Immediate DELETE /v1/devices/:deviceLibId/registrations/... call when removed from Wallet | Immediate POST /api/v1/wallet/callback with eventType: "del" | Limited telemetry |
| Contactless NFC Protocol | Apple VAS (ISO/IEC 14443 Type A/B, ECDH P-256, requires Apple NFC entitlement) | Google Smart Tap (NFC_SMART_TAP, collectorId, ECDH P-256) | Not supported |
Important: Do not treat Samsung Wallet as globally identical to Apple Wallet and Google Wallet across every region and workspace. While
Passinstance APImaintains schema fields (samsungWalletCardId,samsungWalletRefId) for Samsung integrations, Samsung Wallet requires partner-gated onboarding per region — inspect Samsung Wallet Support Scope for eligibility details.
Platform-Specific Design & Payload Rules
1. Color Conversion & Contrast Enforcement
Apple's PassKit parser rejects .pkpass archives if backgroundColor, foregroundColor, or labelColor contains a #RRGGBB hex string or an rgba() alpha channel. Passinstance stores normalized color models (Color) and automatically serializes rgb(r, g, b) for Apple .pkpass generation while emitting #RRGGBB for Google Wallet classes.
2. HTML Anchor Restrictions in attributedValue
In Apple Wallet, clickable hyperlinks, phone numbers (tel:), and mailto links are supported exclusively on the back of the pass (backFields) using the attributedValue property. Apple strips all HTML tags except <a href="...">...</a>. On Google Wallet, Passinstance maps these links into the structured linksModuleData section at the bottom of the scrolling pass view:
{
"appleBackField": {
"key": "website",
"label": "TERMS & CONDITIONS",
"value": "https://yourbrand.com/terms",
"attributedValue": "<a href=\"https://yourbrand.com/terms\">View Terms & Conditions</a>"
},
"googleLinksModule": {
"uris": [
{
"uri": "https://yourbrand.com/terms",
"description": "View Terms & Conditions",
"id": "link_terms"
}
]
}
}
3. Multi-Device Registration Counts (iPhone + Apple Watch)
When an iPhone owner with a paired Apple Watch installs an Apple Wallet pass, iOS and watchOS each register an independent deviceLibraryIdentifier and APNs pushToken against POST /v1/devices/.../registrations/.... Passinstance tracks both installedDevices (total push endpoints) and uniqueDevices in the Analytics Dashboard so you can distinguish unique passholders from multi-device installations.
Review Apple Wallet, Google Wallet, and Template Design & Configuration for layout best practices.
