Why people leave WalletPasses
- Ads sit on top of the pass list. The free version puts banner ads on the screen where your boarding pass lives, which is jarring at a check-in counter.
- The premium unlock is needed for the basics. Multiple pass groups, automatic sync, and barcode brightness boosts are paywalled in a way that surprises new users.
- Update cadence is slow. Issuer integrations and Wear OS support lag behind Pass2U and Stocard, and bug reports can sit open for months.
- No native loyalty-card scanning. WalletPasses imports .pkpass files but cannot turn a physical plastic card into a digital one, which is the headline feature on most newer wallets.
- Cloud backup is limited. Google Drive backup exists, but cross-device sync is not as smooth as on Stocard or Google Wallet.
If those frictions push you to compare, here are 7 WalletPasses alternatives worth installing.
Which app should you choose?
-
Pass2U Wallet if you want the closest like-for-like swap with active updates. Same .pkpass import flow, fewer ads, and a real card-scanning feature.
-
Wallet (Wallet Union) if you want a clean .pkpass viewer that does one job. Lightweight and import-focused.
-
Stocard if most of what you carry are loyalty and store cards. Best card scanning, large issuer database.
-
Catima if you want open-source and no tracking. Loyalty cards plus passes, no accounts, all local.
-
Google Wallet if you already use it for tap-to-pay and want passes in the same place. Tightest integration with Android.
-
Samsung Wallet if you have a Samsung phone and want notifications on the lock screen. Strong on Samsung, useless elsewhere.
-
PassWallet if you specifically need NFC pass support. Older but still maintained for HID and NFC use cases.
Stay on WalletPasses if you have years of .pkpass files already organised inside it and the premium unlock pays for itself. Migration of dozens of passes is the only real reason to stick.
Comparison table
| App | Best for | .pkpass import | Card scanning | Cloud backup | Rating |
|---|---|---|---|---|---|
| Pass2U Wallet | FR24-style swap | Yes | Yes | Pass2U cloud | 4.6 |
| Wallet (Wallet Union) | Minimal .pkpass viewer | Yes | No | Google Drive | 4.3 |
| Stocard | Loyalty cards | Partial | Yes, strongest | Stocard cloud | 4.6 |
| Catima | Open-source | Limited | Yes | Manual export | 4.8 |
| Google Wallet | Built-in Android | Yes | Yes | Google account | 4.4 |
| Samsung Wallet | Samsung-only | Yes | Yes | Samsung account | 4.4 |
| PassWallet | NFC and HID | Yes | No | Local | 4.2 |
1. Pass2U Wallet, the closest like-for-like swap
Pass2U Wallet is the alternative most WalletPasses users land on first because the .pkpass import flow is identical and the free tier is far less ad-heavy. The tap targets are bigger, the barcode brightness boost is automatic, and the in-app card scanner reads physical loyalty cards and turns them into digital passes without a paywall.
WalletPasses vs Pass2U Wallet is mostly a question of which one keeps shipping. Pass2U has had monthly updates for years, while WalletPasses goes quiet for long stretches. The card-scanning feature is the one WalletPasses still misses.
Advantages:
- Reads .pkpass files exactly like WalletPasses
- Scans physical loyalty cards into digital ones
- Auto-brightness boost when a pass is open
- Wear OS support and lock-screen widgets
Disadvantages:
- Free tier limits the number of custom passes
- Some pass templates need a small one-off purchase
- Account is required for cloud sync
Pricing: Free with limits. Premium unlock removes limits and adds cloud sync.
Bottom line: Pick Pass2U if you want the WalletPasses experience without the maintenance gap. Skip if you only ever store a handful of passes and never need card scanning.
2. Wallet by Wallet Union, a minimal .pkpass viewer
Wallet is the lightest of the .pkpass viewers and is genuinely free. It imports passes from email, files, and QR codes, groups them by issuer, and gets out of the way. There is no loyalty-card scanner and no tap-to-pay, which is exactly the point.
WalletPasses vs Wallet: the two apps target the same niche, and the comparison is mostly about which one feels less neglected. Wallet has been updated more steadily in the last year and treats the free tier with less friction.
Advantages:
- Free, no premium unlock required for the basics
- Clean grouping by pass type and issuer
- Drag-and-drop reordering of the card stack
- Google Drive backup and restore
Disadvantages:
- No card scanning, .pkpass only
- Fewer pass-template options than Pass2U
- Notifications can lag the issuing app
Pricing: Free.
Bottom line: Pick Wallet if you only need a .pkpass viewer and nothing more. Skip if you want to scan plastic loyalty cards or sync across devices.
3. Stocard, when most of what you carry is loyalty cards
Stocard built the loyalty-card use case before Apple Wallet existed and still leads on the breadth of issuer support. The scanner recognises hundreds of European, North American, and Asian retailer cards by barcode, and the app pre-fills the issuer name and logo so the stack stays tidy.
WalletPasses vs Stocard is a category swap. WalletPasses is built around .pkpass imports. Stocard is built around scanning the plastic card in your hand, which is the more common need for most non-traveller users.
Advantages:
- Strongest loyalty-card scanner in the category
- Hundreds of pre-recognised retailers
- Cloud sync across phone, tablet, and Wear OS
- Lock-screen widget for the current store
Disadvantages:
- .pkpass import is limited, not a full replacement
- Owned by Klarna, now bundles payment promotions
- The Plus tier is needed to hide partner offers
Pricing: Free with promotional offers in the feed. Plus removes offers for a yearly fee.
Bottom line: Pick Stocard if your wallet is mostly loyalty cards. Skip if it is mostly boarding passes and event tickets.
4. Catima, open-source and private
Catima is the open-source loyalty-card and pass manager that respects privacy by default. No account, no analytics, no ads, no cloud. Cards live on the device and you back them up by hand or with the export-to-archive feature. Several thousand issuers are pre-recognised by the scanner.
WalletPasses vs Catima: WalletPasses pulls in .pkpass files served by airlines and event platforms; Catima focuses on cards you scan yourself. Catima readers tend to leave WalletPasses precisely because they no longer want a third-party account in the middle.
Advantages:
- Fully open-source under the GPL
- No account, no telemetry, no ads
- Strong barcode scanner with issuer recognition
- Multiple card groups and colour tags
Disadvantages:
- .pkpass support is limited compared with Pass2U or WalletPasses
- No automatic cloud sync, only manual export
- UI is utilitarian, not flashy
Pricing: Free, open-source.
Bottom line: Pick Catima if you want loyalty-card storage with no account and no surveillance. Skip if cloud sync across devices is a must-have.
5. Google Wallet, the built-in choice
Google Wallet started as a payment app and now also stores boarding passes, event tickets, transit cards, and any .pkpass file an issuer chooses to ship. For users already paying with their phone, keeping non-payment passes in the same app removes one icon from the home screen.
WalletPasses vs Google Wallet: Google Wallet wins on integration with tap-to-pay and Google Maps timing, WalletPasses wins on the breadth of .pkpass templates and the freedom to design custom passes.
Advantages:
- Native to Android, no extra account
- Boarding-pass timing prompts in Google Maps and Assistant
- Adds passes from email and Gmail automatically
- Secure enclave protects payment cards
Disadvantages:
- Custom or self-generated .pkpass files do not always import
- Locked to a Google account
- Some pass types are only supported in specific markets
Pricing: Free.
Bottom line: Pick Google Wallet if you tap your phone to pay and want passes alongside cards. Skip if you store mostly self-generated or third-party-issued .pkpass files.
6. Samsung Wallet, only worth it on Samsung
Samsung Wallet is the Samsung-only counterpart to Google Wallet and the only option here that runs on Knox-protected hardware. It handles boarding passes, transit cards, ID, and tap-to-pay with deep One UI integration. The lock-screen pass shortcuts are genuinely better than anyone else’s.
WalletPasses vs Samsung Wallet is also a category swap. WalletPasses is hardware-agnostic; Samsung Wallet only matters if you carry a Galaxy.
Advantages:
- Lock-screen and Edge-panel pass shortcuts
- Samsung Knox secure enclave
- One UI integration with the calendar and Bixby
- Boarding-pass-on-watch via Galaxy Watch
Disadvantages:
- Samsung phones only
- No third-party-template support beyond .pkpass
- Some regions get a reduced feature set
Pricing: Free.
Bottom line: Pick Samsung Wallet if you own a Samsung phone and use the lock screen actively. Skip on any other hardware.
7. PassWallet, the NFC and HID specialist
PassWallet is the older Passbook clone that still has the strongest NFC and HID support of the set. If your office door, gym, or hotel uses an NFC pass distributed as .pkpass, PassWallet is the safest choice to make the tap actually work.
WalletPasses vs PassWallet: PassWallet trades a polished UI for hardware coverage. The look is dated, but it handles edge cases like Wear OS passes and HID lanyard tags that newer apps quietly stopped supporting.
Advantages:
- Strong NFC, HID, and barcode support
- Reads .pkpass from email, files, and URLs
- Lock-screen and notification controls per pass
- One-off upgrade rather than a subscription
Disadvantages:
- Dated UI compared with Pass2U
- Slower updates and fewer template options
- Cloud backup is rudimentary
Pricing: Free with limits, one-time upgrade unlocks the full feature set.
Bottom line: Pick PassWallet if you actually tap your phone at an NFC reader using a .pkpass. Skip if you only need a viewer.
How to choose
If you are leaving WalletPasses because the free tier feels nagging, Pass2U Wallet is the clean swap. Same workflow, more features unlocked, active development.
If you mostly store loyalty cards rather than boarding passes, switch to Stocard or Catima. Stocard wins on scanner accuracy and cloud sync, Catima wins on privacy and the open-source guarantee.
If you already use Google Wallet for tap-to-pay, just enable pass import there and uninstall WalletPasses. The cross-app friction was the whole reason to use a separate wallet.
Stay on WalletPasses if you have a large library of custom-designed passes that depend on specific .pkpass features it supports. Migrating dozens of passes by hand is the kind of work that is not worth doing without a clear reason.
Frequently asked questions
Is Pass2U better than WalletPasses? Pass2U Wallet ships updates more often, has fewer ads in the free tier, and scans physical loyalty cards. For most readers it is the closer-to-current version of what WalletPasses set out to be.
Can I import my passes from WalletPasses to another wallet? Yes. .pkpass files are an open format. Export them from WalletPasses, then open them in Pass2U, Wallet, or PassWallet. Loyalty cards scanned inside WalletPasses do not transfer automatically and have to be re-scanned in the new app.
Is there a free open-source alternative to WalletPasses? Catima is the open-source choice. It is GPL-licensed, stores everything locally by default, and does not require an account.
Does Google Wallet replace WalletPasses on Android? For boarding passes and tickets issued by major airlines and event platforms, yes. For self-generated or third-party-template passes, sometimes not, and WalletPasses or Pass2U is still the safer choice.
Which alternative has the best Wear OS support? Pass2U Wallet and Stocard both have mature Wear OS apps that show the current pass on the wrist with the barcode boosted for scanning.
