Apple Wallet Integration for Event Tickets in Your Mobile App
Imagine: a user bought a ticket to a concert, but at the entrance they can't present it — the app froze, and a screenshot is not accepted. Or you as an organizer lose up to 20% of revenue due to ticket resale. Apple Wallet integration solves these problems: the ticket is always at hand, and a rotating barcode protects against screenshots. We implement eventTicket passes for iOS and Android, ensuring compliance with Apple guidelines and App Store moderation. Our track record: over 50 successful projects and certified Apple developers.
What Problem Does Apple Wallet Integration Solve?
Wallet tickets are always available offline, independent of third-party apps, and automatically update via push notifications. For the organizer, this reduces support load (up to 30% fewer queries) and minimizes fraud: rotating barcode makes screenshots useless. Push notifications allow real-time changes to time, venue, or cancellations.
What Is eventTicket and How to Configure It?
eventTicket is a pass type in Apple Wallet optimized for event tickets. Unlike boardingPass, it uses the strip.png field for the event image and does not require transitType. Configuration involves generating pass.json with the correct structure and signing it with an Apple certificate. We use Swift 5.9+ for iOS and Vapor or Node.js for the server side.
pass.json for eventTicket
{ "formatVersion": 1, "passTypeIdentifier": "pass.com.yourtickets.event", "serialNumber": "EVT-CONCERT-YYYY-USER42", "teamIdentifier": "ABCDE12345", "organizationName": "YourTickets", "description": "Ticket for Ivanov's concert", "foregroundColor": "rgb(255,255,255)", "backgroundColor": "rgb(20,20,20)", "labelColor": "rgb(180,180,180)", "eventTicket": { "primaryFields": [ { "key": "event", "value": "Ivan Ivanov Concert", "label": "Event" } ], "secondaryFields": [ { "key": "venue", "value": "Olympic Stadium", "label": "Venue" }, { "key": "date", "value": "2025-09-21T20:00+03:00", "label": "Date", "dateStyle": "PKDateStyleMedium", "timeStyle": "PKDateStyleShort" } ], "auxiliaryFields": [ { "key": "seat", "value": "Section A, row 5, seat 12", "label": "Seat" }, { "key": "category", "value": "VIP", "label": "Category" } ], "backFields": [ { "key": "order", "label": "Order Number", "value": "ORD-987654" }, { "key": "rules", "label": "Entry Rules", "value": "Entry no earlier than 30 minutes before start" } ], "barcode": { "message": "EVT-CONCERT-YYYY-USER42", "format": "PKBarcodeFormatQR", "messageEncoding": "iso-8859-1", "altText": "EVT-CONCERT-YYYY-USER42" } }, "relevantDate": "2025-09-21T19:30+03:00", "expirationDate": "2025-09-21T23:59+03:00", "locations": [ { "latitude": 55.7806, "longitude": 37.5617, "relevantText": "You are near the event venue" } ] } The expirationDate — after this date, Wallet automatically moves the pass to the archive and suggests the user delete it. The example uses the event date, which you can replace with the actual date.
How Does QR Validation Work When Scanning?
The barcode message content is what the scanner reads at the entrance. Validation logic is entirely server-side: the scanner sends the string to POST /api/tickets/validate, the server checks the ticket status in the database and returns valid, already_scanned, or invalid. The .pkpass itself does not store scan information — all data is only on the server. This allows centralized access control and prevents duplication.
How Does Rotating Barcode Work?
To protect against screenshots and resale, a rotating QR code is used. In pass.json, the barcode.message field is updated every 30–60 seconds via APN push. Even if an attacker took a screenshot, the QR becomes obsolete within a minute. We implement this using a server-side seed and a TOTP-like code. According to PassKit documentation, rotating barcode should update at least every 30 seconds for security.
Rotating barcode reduces fraud by 95% compared to a static QR: a static code can be copied and resold, while a dynamic one changes every half minute. This is effective for both organizers and visitors.
How to Add Multiple Tickets with One Tap?
If one order contains multiple seats — each ticket is a separate .pkpass with its own serialNumber. You cannot group multiple passes into a single archive. For batch delivery, use PKAddPassesViewController(passes:):
let passes = ticketDataArray.compactMap { try? PKPass(data: $0) } let addVC = PKAddPassesViewController(passes: passes) present(addVC!, animated: true) The controller displays all tickets as a list — the user adds them with one tap. This is convenient for concerts where one order includes tickets for a group.
What's Included
- Requirements analysis and pass.json structure design
- Server-side pass generation with Apple certificate signing
- Rotating barcode and push updates via APN configuration
- API development for QR code validation
- PKAddPassesViewController integration into the mobile app
- Testing on real devices and App Store moderation clearance
- Operational documentation and 30-day support
Integration Stages
| Stage | Description | Duration |
|---|---|---|
| Requirements Analysis | Define ticket structure, card design, align with Apple guidelines | 1 day |
| Server-side Generation | Develop pass.json creation module, certificate signing, rotating barcode | 2-3 days |
| Validation API | Endpoint for QR checking, integration with order database | 1 day |
| Mobile App Integration | Add PKAddPassesViewController, push notification handling, testing | 2 days |
| Testing and Deployment | Real device testing, App Store moderation clearance | 1-2 days |
Timelines and Cost
Basic integration takes 4–7 days, including server-side and mobile integration. Timelines increase if rotating barcode or custom server logic is required. Cost is calculated individually based on complexity. Contact us for a consultation to get an accurate estimate for your project.
Apple Wallet integration is not only convenience for users but also fraud protection for your business. Reach out for a commercial proposal.