Free
Testing & side projects
$0 /month
- 1,000 passes/month
- Limited branding
- Signed .pkpass delivery
Flat pricing. No per-pass fees, no per-device fees.
For reference, PassKit charges $1,300/month for the same pass lifecycle features.
30-day Pro trial
Pro
Production apps
$19 /month
- 100,000 passes/month
- Live updates & push notifications
- Lock-screen location triggers
- Logo, thumbnail, strip, icon
- Priority email support
Bring your own cert
Sign with your Apple Developer ID
Custom
- Sign with your Apple certificate
- Managed APNs on dedicated, low-latency workers
- Volume pricing past 100k passes/month
- SLA & dedicated technical support
- Custom contract, DPA & onboarding
Frequently asked questions
What's in the 30-day Pro trial?
Every new account starts on Pro for 30 days: all features, all image slots, lifecycle updates, unlimited passes. After that, keep Pro at $19/month or stay free under 1,000 passes/month. No card up front, no auto-charge.
Does this work with Google Wallet too?
The signed .pkpass file we return opens directly in Google Wallet on Android, so one API call lands a pass in both wallets. Live updates and push notifications are Apple-only. Google Wallet doesn't honor webServiceURL.
Can I update a pass after it's been added to someone's wallet?
Yes. Every pass gets a unique serial, returned in the X-Serial-Number response header and embedded inside the .pkpass file. PUT a new body to /api/pkpass/<serial> and the pass refreshes on every iPhone, iPad, or Apple Watch the customer added it to. Identical bodies don't trigger a push and don't count against your quota.
How do I send the pass to my customers?
The API response is the signed .pkpass binary. Forward it however you already reach your user: email attachment, "Add to Wallet" button on a confirmation page, SMS link, or in-app download. Apple Wallet picks it up automatically when opened on iPhone. Google Wallet does the same on Android.