---
title: "Apple Wallet vs Google Wallet: a capability comparison"
url: https://getstell.com/platform/wallets
description: "How Apple Wallet and Google Wallet compare on push, real-time updates, NFC identification and location surfacing, and how Stell hides the differences."
---

# Apple Wallet vs Google Wallet: a capability comparison

# Wallets

Apple Wallet vs Google Wallet: a capability comparison How Apple Wallet and Google Wallet compare on push, real-time updates, NFC identification and location surfacing, and how Stell hides the differences. /platform/wallets POST /v1/passes Identical body. One enum value says which wallet, and the add link comes back with the pass PATCH /v1/passes/{id} Identical. Lands on the installed pass, no re-save DELETE /v1/passes/{id} Same events, same payloads, wallet type included Passes are issued for the wallet they will live in, so a customer who wants theirs on both an iPhone and an Android phone holds one of each. Worth designing your member record around from day one, even if you launch on a single wallet. Delivery timing is the platforms', not ours Pass generation is ours and happens in milliseconds. How fast an update then surfaces on the phone belongs to Apple's push infrastructure and Google's device sync: Apple is typically seconds, Google commonly longer, and neither publishes a guarantee. Rendering differs, deliberately Each wallet has its own layout rules, field limits and artwork specs. Templates account for both, so a pass looks native on the platform it lands on rather than identical on neither. / /platform /platform/wallets / /platform One pass. Every wallet. platform:wallets Feature comparison What each wallet supports. Every capability below ships through the same Stell API call. The notes show how each wallet delivers it, differences you never have to code around. Supported Supported with limits, noted in the cell Not offered by the wallet One integration Adding the second wallet is not a second project. The differences in the table above are real, and none of them reach your code. It is not two integrations behind a shared wrapper: the same endpoints serve all platforms, and the only thing that changes between them is which wallet you name when the pass is created. What does differ, stated plainly. See the endpoints in the docs · Bring your own issuer account A pass belongs to one wallet Apple Wallet and Google Wallet deliver the same promise with different machinery: push, updates, NFC and location work differently under the hood. Stell abstracts those differences, so you build against one API and every customer gets the full experience. Book a demo Read the docs See it live One API call, both wallets. Bring your loyalty program or ticket flow. In thirty minutes we'll show the same pass landing in Apple Wallet and Google Wallet, updating in real time.