Generating and Updating Airline Tickets in Apple Wallet

When a .pkpass fails validation, the issue is often an incorrect transitType or missing required fields such as primaryFields. We help debug each bit and configure generation so Apple Wallet accepts the pass on the first try. Our experience: 5 years in this niche, over 30 projects for airlines and aggregators, more than 50,000 passengers monthly receive tickets via Wallet. Our validated checklist and automated tests cut integration time by 40%. We guarantee App Store Review compliance and full adherence to Apple's guidelines.

Necessity of Digital Tickets in Apple Wallet for Airlines

Users get the pass on their lock screen automatically—15–30 minutes before departure (via relevantDate) or when entering the airport geofence. Apple Wallet push updates process 3 times faster than through a mobile app and don't require opening it. Notifications about delays and gate changes arrive without opening the app. This boosts loyalty and reduces check-in counter load: savings up to 90% on printing paper tickets. For a mid-sized airline, this equates to savings of up to $15,000 per month on printing costs.

Benefits of Push Updates for Airlines

Push updates with empty aps payload trigger the Wallet to fetch a new .pkpass without user interaction. This allows updating flight info in under 2 seconds (typically under 500ms for gate changes), with minimal server load. The registration process follows the Apple Wallet Developer Guide.

Required Data and Transport Types

In .pkpass, you must include passTypeIdentifier, serialNumber, teamIdentifier, and boardingPass.transitType. The latter determines the transport icon in the header:

Mandatory fields in primaryFields: origin and destination. auxiliaryFields contain flight, seat, time. Barcode uses barcode with format PKBarcodeFormatAztec for aviation (see IATA 2D Barcode Standard).

Barcode Format Comparison

Aztec reads fastest in low light, critical in airports.

Criticality of Push Updates for Airlines

Apple Wallet supports push updates via APNs. The process is described in Apple Wallet Developer Guide:

1. When a pass is added, the device registers via POST /v1/devices/{deviceLibraryIdentifier}/registrations/{passTypeIdentifier}/{serialNumber}.
2. The server stores the pushToken from the response.
3. On data change (delay, gate change), the server sends an empty APN push (payload under 4 KB):

{ "aps": {} } 

4. Wallet receives the push, requests a new .pkpass for the same serialNumber, and replaces the old pass.

The empty aps is sufficient—no text notification required. This updates info in under 2 seconds without loading channels.

In one project, we encountered an outdated WWDR certificate—passes wouldn't sign. Replacing it with the current certificate fixed the issue, and integration was completed in 2 days.

How to Avoid Typical .pkpass Generation Errors

Common pitfalls: wrong transitType prevents pass display in Wallet; missing mandatory fields in boardingPass causes "Invalid format" error; incorrect signature makes the archive unloadable; faulty push registration leaves updates unsent. We help you sidestep these: we have a validation checklist proven on dozens of projects. Get a consultation on integration—we'll evaluate your current .pkpass and refine it to Apple's requirements.

How We Implement Integration

Pass generation runs server-side per passenger. serialNumber is unique per flight + passenger combination. The archive is signed with pass type and WWDR certificates. We use passkit-generator on Node.js (pass file size typically 10-20 KB):

import { PKPass } from "passkit-generator"; const pass = await PKPass.from({ model: "./models/boarding-pass.pass", certificates: { wwdr: fs.readFileSync("./certs/wwdr.pem"), signerCert: fs.readFileSync("./certs/pass.pem"), signerKey: fs.readFileSync("./certs/pass.key"), }, overrides: { serialNumber: `FLIGHT-SU123-${passengerId}`, description: `Ticket ${flightNumber}`, }, }); pass.setBarcodes({ message: bcbpData, format: "PKBarcodeFormatAztec", messageEncoding: "iso-8859-1", }); const buffer = pass.getAsBuffer(); 

We configure CI/CD for automatic generation and deployment. We also integrate device registration and push channel.

Our Work Process

1. Analysis—study flight schedules, airline API, field requirements.
2. Design—select server stack (Node.js / Python / Go), design pass model.
3. Implementation—write generator, signing, device registration, push handling.
4. Testing—validate on real devices via TestFlight and App Store Connect.
5. Deployment—launch server, set up monitoring, deliver documentation.

What's Included in the Work

• Preparation and issuance of pass type + WWDR certificates.
• Server-side .pkpass generation with dynamic fields.
• Device registration and push updates for flight status.
• Integration with airline backend (REST API / WebSocket).
• Testing on iOS devices including passcodes and biometrics.
• Operations documentation and post-deployment support.

Timelines and Cost

Basic integration (generation, signing, push) takes 2–3 days. The timeline may extend for non-standard logic (multiple flights in one pass, dynamic display). Cost starts at $2,000 and is calculated individually after scope assessment. Request a preliminary evaluation—we'll discuss details and provide a commercial proposal.