Skip to main content
iOS and Android Wallets Explained: Digital Wallets, PKPass, Use Cases and Integration

iOS and Android Wallets Explained: Digital Wallets, PKPass, Use Cases and Integration

iOS and Android Wallets Explained: Digital Wallets, PKPass, Use Cases and Integration

Digital wallets on iOS and Android let people store cards, tickets, IDs and other digital credentials directly on their smartphone. They replace physical cards and offer a secure, convenient and deeply integrated way to deliver and use information.

The best-known platforms are Apple Wallet on iOS and Google Wallet on Android. Both are built deep into their operating system and support standardized formats as well as modern security mechanisms.

What Are iOS and Android Wallets?

Wallets are native apps that let users store and use digital content, for example:

  • Tickets (events, concerts, transit)
  • Boarding passes
  • Loyalty and membership cards
  • Vouchers & coupons
  • IDs and access cards
  • Payment cards (optional, depending on the use case)

Wallets tie directly into the device hardware, including:

  • NFC
  • QR code scanning
  • Biometric security (Face ID, Touch ID, fingerprint)
  • Push notifications

Apple Wallet (iOS)

Apple Wallet is the native wallet app on iPhone and Apple Watch. Technically it is built on the PKPass format.

Apple Wallet supports, among other things:

  • Event tickets
  • Boarding passes
  • Store cards / loyalty cards
  • Coupons
  • Transit cards

Wallet content can be added by link, QR code, email or directly from an app.

Google Wallet (Android)

Google Wallet is the Android counterpart to Apple Wallet. It uses its own APIs but follows functionally similar concepts.

Google Wallet supports:

  • Event and transit tickets
  • Loyalty and membership cards
  • Offers & coupons
  • Digital IDs (in selected countries)

Unlike Apple Wallet, Google Wallet does not use PKPass files, but a JSON-based API structure.

What Is PKPass?

PKPass is the file format for Apple Wallet. Technically, a PKPass file is a signed ZIP archive with a fixed structure.

A PKPass file contains, among other things:

  • pass.json – the actual data (title, fields, barcodes)
  • Images (icon, logo, background)
  • manifest.json – hashes of every file
  • Signature – the digital signature from Apple

The signature guarantees that the pass has not been tampered with.

What Can You Do with Wallets?

Digital wallets suit a wide range of use cases:

  • Event tickets with a QR or NFC code
  • Access cards for buildings or events
  • Loyalty cards with a barcode or number
  • Vouchers with an expiration date
  • Status indicators (VIP, active, redeemed, and so on)

Additional capabilities:

  • Automatic display on the lock screen
  • Location-based prompts
  • Push updates when something changes
  • Offline availability

Advantages of Wallet Solutions

  • No app required of the end user
  • High visibility (lock screen, system integration)
  • Usable offline
  • Strong security (signatures, OS sandbox)
  • Easy distribution by link or QR code

Drawbacks and Limitations

  • Different implementations for iOS and Android
  • Apple Wallet requires PKPass signing
  • Limited layout flexibility
  • Not a full replacement for complex apps

How Do You Use Wallets in Your Own Project?

The typical flow looks like this:

  1. Define the use case (ticket, card, voucher)
  2. Settle on a data model
  3. Generate the wallet pass dynamically
  4. Deliver the pass by link or QR code
  5. Optional: updates & push notifications

Technical Requirements

Apple Wallet (PKPass)

  • An Apple Developer account
  • A Pass Type ID
  • An Apple certificate (.p12)
  • A server to sign the PKPass files
  • Delivery over HTTPS

Google Wallet

  • A Google Cloud project
  • Google Wallet API access
  • A service account
  • A JSON-based pass definition

Example: A Simplified PKPass Flow


1. Collect the data (name, ticket ID, barcode)
2. Generate pass.json
3. Add assets (logo, icon)
4. Create manifest.json
5. Sign with the Apple certificate
6. Deliver the .pkpass

The user opens the link and iOS automatically offers to add the pass to Wallet.

Wallets vs. Your Own App

Criterion Wallet Own app
Installation None App store
Offline Yes Partly
Flexibility Limited Very high
Time to market Fast Slower

Typical Areas of Use

  • Event & ticketing systems
  • Community & membership cards
  • Access control
  • Marketing & promotions
  • Check-in & registration systems

Conclusion

iOS and Android wallets offer a powerful way to deliver digital content without building your own app. Formats like PKPass and the Google Wallet APIs let you integrate tickets, cards and vouchers securely, offline-capable and close to the operating system. For many projects, wallets are a lean, maintainable and user-friendly alternative to a classic app.