Apple Wallet vs Google Wallet for Business

By · Published · Last updated · 7 min read

Apple Wallet and Google Wallet both hold your customers' loyalty cards, memberships, coupons, gift cards and tickets, but a business issues and updates passes on each in a different way. Apple Wallet passes are signed files (.pkpass) that you build with a certificate from your Apple Developer account and update through a web service you run. Google Wallet passes are objects created through Google's API, from a class you define, and the customer adds one from a link containing a signed token. Most businesses issue both, because their customers are split between iPhone and Android. Every technical claim below links to Apple's or Google's own developer documentation, read in November 2026. Where a vendor's documentation does not say something, we say so instead of guessing. Disclosure: Shakewell Wallet is our product, and it issues both kinds from one design.

The names: Passbook, Wallet and Google Pay

You will see older names in search results and articles. Apple's developer documentation today is a section called Wallet Passes (Apple: Wallet Passes), and Google's is the Google Wallet API (Google Wallet developer docs). "Passbook" and "Google Pay passes" are older names for the same ideas, and you will still see them in older guides, forum posts and code. For a business, the practical point is that "Apple Passbook vs Google Wallet" is today a comparison of Apple Wallet and Google Wallet, and the old names add nothing you need to learn.

Pass types

Apple's pass format has five styles, each with its own layout: boarding pass, coupon, event ticket, generic and store card (Apple: Pass). A loyalty or stamp card normally uses the store card style, and a membership card often uses store card or generic.

Google lists its pass types by category: retail (loyalty cards, gift cards and offers), tickets for travel and events, access, health, and a generic type for everything else (Google Wallet developer docs). Google has a specific loyalty type, and its objects hold a state and a valid time interval.

One idea, such as a membership card, becomes a different structure on each side. A platform takes one design and produces the right pass for each wallet.

How a pass is issued

Apple. You create a pass type identifier in your Apple Developer account, create a signing certificate for it, and build a signed bundle. You generate a manifest of SHA-1 hashes of each file, sign that manifest with a PKCS #7 detached signature using the certificate's private key, zip the result and give it the .pkpass extension (Apple: Building a pass). Each pass is identified by the pass type identifier and a serial number, and adding a pass with the same pair as one already on the device overwrites it. See certificates explained.

Google. There is no file to sign per customer. You create a pass class, the template shared by passes, and then an object for each customer, which references the class by its identifier. The customer gets an "Add to Google Wallet" link built from a JWT, which is signed with the key of a service account (Google: JWT). Google's documentation shows the class and object being created when the customer saves the pass, so one link can create both. Google's reference adds that a draft class cannot be used to create objects (Google: loyalty class).

Apple WalletGoogle Wallet
What you issueA signed .pkpass fileA class and an object, added by a signed link
What signs itA certificate for your pass type identifierA service account key
Account you needApple Developer accountGoogle Wallet issuer account
Identity of a passPass type identifier plus serial numberObject ID, referencing a class
UpdatingYour web service plus a push to the deviceAn API call that patches the object

How updates and notifications work

Apple. An updatable pass names a web service and carries an authentication token. When a customer installs it, the device registers with your server and gives it a push token. When the pass changes, your server sends a push notification with an empty payload through Apple's push service. The device then asks your server which passes changed and downloads the new one (Apple: Adding a web service to update passes). You can update any information in the pass except the authentication token and the serial number. Apple's documentation also says a push for a pass update works only in the production environment, which affects testing. You run the web service yourself, or you use a platform that does.

To make a change visible, a field can carry a change message, an alert text shown when the field updates. Apple's documentation says you must provide one for the system to show a change notification (Apple: PassFieldContent). Without it, the pass updates quietly.

Google. You update an object with an API call to patch it (Google: patch), and there is no web service of your own to run. You can notify two ways. A message can be added to an object with addMessage (Google: addMessage), and an object holds up to 10 messages, which are displayed in the app (Google: loyalty object). Or a field update can request a notification by setting notifyPreference to NOTIFY. Google says this is attempted only for fields on an allowlist, and that the setting applies to a single request and must be sent each time.

What each shows on the lock screen

Apple documents lock-screen behaviour directly. A pass can list locations, each with text to show on the lock screen when the pass is relevant, and it can list a relevant date or interval, which tells Wallet when to bring the pass forward (Apple: locations, Apple: relevant dates). An update with a change message shows as an alert.

Google's reference says this much: messages are displayed in the app, field-update notifications are optional and limited to an allowlist, and the old locations field on a class no longer triggers geo notifications, with merchantLocations as its replacement (up to 10 per class). Google's reference does not describe how a message looks on an Android lock screen, so test it on a real phone before you promise it to anyone.

Barcodes

Both wallets show a barcode for scanning. Apple lists QR, PDF417, Aztec, Code 128, Code 39, EAN-13, I2of5 and Codabar formats (Apple: barcodes). Google's barcode type list is longer, including QR code, PDF417, Aztec, Code 128, Data Matrix and text only (Google: BarcodeType). QR, PDF417, Aztec and Code 128 are on both lists and are the long-standing Apple formats, so use one of those if you want the same code in each wallet and on older iPhones.

Device reach

Apple Wallet passes are for iPhone users and Google Wallet passes are for Android users, which is why a QR code or link that works for both is the practical way to reach everyone. A customer who opens the install link on an iPhone is offered Apple Wallet, and on Android Google Wallet. Minimum OS versions change, so check Apple's and Google's current requirements before you target a specific device.

Why most businesses issue both

  • Your customers are split. If you issue only one, you turn away the other half at the counter.
  • The work is mostly shared. The design, data and message are the same. Only the signing, hosting and API calls differ.

If you build it yourself, plan for two code paths, one certificate to renew and one service account key to protect. The how-to guide walks through both. With Shakewell Wallet, one card design and one link produce Apple Wallet and Google Wallet passes, and a customer joins from a link or QR code with no app. Plans are flat monthly with no per-pass fees, and there is a free plan for up to 250 customers with a card each month (pricing). See also how wallet pass updates and push notifications work.

Frequently asked questions

Is Apple Passbook the same as Apple Wallet? Passbook is the older name. Apple's current developer documentation calls the section Wallet Passes, and a pass built for Passbook is the same kind of file.

Do I need an Apple Developer account and a Google account to issue passes? If you build passes yourself, yes: an Apple Developer account for the pass type identifier and certificate, and a Google Wallet issuer account with a service account. With a platform that signs for you, you do not.

Which wallet should I support first? Whichever your customers use most, and plan for both.

Can I update a pass after it is issued? Yes on both. Apple updates through a web service and a push, and Google through an API call to the object.

All guides

Guides + product

Ready to ship your first wallet card?

Set up takes minutes. 60-day free trial. No card needed.