Apple and Google wallets diverge on passes, access and privacy

Apple Wallet and Google Wallet both store payment cards, tickets, loyalty cards, boarding passes and other digital passes. Apple Pay and Google Pay process the transactions. In practice, the choice is largely determined by the user’s phone ecosystem: Apple Wallet is built for iPhone, while Google Wallet is used on Android.

Engadget said Apple Wallet generally relies on officially supported passes, which can offer features such as live boarding-pass updates and Apple Watch integration. The comparison also notes that iOS 27 allows custom passes, although the scope and availability of that support remain unclear.

Google Wallet has offered more flexibility, including an “Everything Else” option that can digitise photos of unsupported cards such as parking, library or gym cards. Those passes may lack live updates. Google Wallet also provides a web interface, while Apple Wallet does not.

The services differ in how payments are initiated. Apple users can select a card before paying, while Google Wallet generally uses the default card once the phone is unlocked. Both support contactless payments, wearable devices and, where available, transit payments.

Apple’s Express Mode can allow eligible transit cards to work without authentication, including for up to five hours after a supported iPhone’s battery runs out. Google Wallet also supports unauthenticated transit payments, although the phone screen must be on.

Digital-ID support varies by jurisdiction, government, provider and device, and neither wallet pass is universally accepted as a replacement for physical identification. Engadget also characterises Apple as retaining neither transaction history nor true card details on its servers, while Google retains purchase details and real card numbers. Both services are presented as secure, but the comparison gives Apple an edge on privacy.