Add Cards to Apple Wallet: Business Guide
Everything you need to know about issuing cards to Apple Wallet as a business. PassKit basics, distribution methods, and the fastest path from decision to production.
Adding cards to Apple Wallet requires either Apple's PassKit framework (technical) or a platform like 7Konto (turnkey). This guide covers both approaches so you can make an informed decision. TL;DR: for most businesses, using a platform is 10-100x faster than building from scratch.
What you'll need
- For custom PassKit: Apple Developer account, engineering team, ongoing maintenance capacity
- For platform approach: brand assets, business info, willingness to configure
- Real iPhones for testing (simulators are inadequate)
Step-by-step process
Understand what Apple Wallet is
Apple Wallet is Apple's app for storing digital passes: boarding passes, tickets, loyalty cards, gift cards, membership cards, payment cards, and more.
- Available on every iPhone (pre-installed since iOS 6)
- Users can add passes from emails, websites, apps, QR codes, or NFC taps
- Passes can update in real-time (balance changes, gate assignments, seat updates)
- Passes can send push notifications
- Passes can trigger geographically (appear on lock screen near relevant location)
- Google Wallet is the equivalent on Android — most platforms support both
Choose your approach
Two paths to adding cards to Apple Wallet: build custom with PassKit, or use a platform like 7konto.
- PassKit approach: technical, flexible, requires 4-12 weeks of development, Apple Developer account, ongoing maintenance
- Platform approach (7Konto or similar): configuration-based, faster, requires no code, includes ongoing platform maintenance
- For most businesses, platform approach is significantly faster and lower total cost
Pro tip
Even large enterprises are moving to platforms unless they have very specific customization needs. Time-to-market usually wins.
Set up your Apple Developer account (PassKit approach)
If choosing PassKit approach, you need an Apple Developer account. Platform users skip this — the platform manages Apple credentials for you.
- Sign up at developer.apple.com ($99/year)
- Create a Pass Type ID in your Apple Developer account
- Generate certificates for signing passes
- Set up webhooks for pass updates
- Establish your infrastructure for pass generation
Pro tip
Only relevant if you're building custom. Platforms handle all of this for you.
Design your card
Apple Wallet passes have specific design constraints. Design your card to work within them.
- Apple provides 6 pass types: boardingPass, coupon, eventTicket, generic, storeCard, thirdPartyReceipt
- For gift cards and loyalty: use storeCard type
- For coupons: use coupon type
- For tickets: use eventTicket type
- Include: logo, brand colors, primary and secondary information fields, image, barcode/QR
- Test on actual iPhone — designs render differently in simulator
Pro tip
Less is more. Wallet passes render small on lock screen. Cluttered designs become unreadable.
Choose your distribution method
How will customers get the pass?
- QR code (they scan to add) — most common, works on any camera
- URL link (they tap to add) — good for email/SMS distribution
- Email attachment (.pkpass file) — direct download
- NFC (they tap phone to a physical reader) — for high-volume physical distribution
- App-based (they tap "Add to Apple Wallet" in your app)
Pro tip
QR codes are the universal choice. Print them on receipts, display on POS terminals, embed in emails, put on business cards. Works everywhere.
Set up pass updates (if applicable)
For dynamic passes (balances, tickets, memberships) — configure real-time updates.
- Custom approach: implement APNs (Apple Push Notification Service) integration
- Set up webhook infrastructure to push updates
- Handle authentication tokens and pass update logic
- Platform approach: automatic — you just update the data, platform handles pass updates
Pro tip
Real-time updates are what make Wallet passes powerful. A gift card that always shows current balance is a much better experience than a static QR code.
Test on real devices
Test the complete flow on real iPhones before launching to customers.
- Test adding from QR, URL, and email
- Test on multiple iOS versions (currently supported: iOS 14+)
- Test on iPhone models across recent years
- Test push notifications and pass updates
- Test edge cases: no internet, low battery, older iPhone
Launch and iterate
Go live, measure adoption, iterate on design and flow.
- Track: pass installation rate, active passes, engagement rate
- A/B test different card designs to find what resonates
- Optimize the "moment of add" — how easy is it for a customer to add the card?
- Iterate based on real usage data
Common issues and solutions
Real problems we've seen when businesses go through this process, and how to solve them.
PassKit implementation is taking longer than expected
Common. Custom PassKit takes 4-12 weeks for most teams. If timeline is critical, switch to a platform approach for a 1-2 week deployment.
Passes not updating in Wallet
Apple Push Notifications need proper configuration. Check certificates, webhook signing, and APNs endpoints. Platforms handle this automatically.
Cards look different in simulator vs real device
Always test on real devices. Simulators approximate but don't exactly match. Small differences in rendering, notifications, and behavior are common.
Skip the guide — we'll do it for you
Free 30-day pilot includes complete implementation by our team. You get the outcome without doing the work.