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.

Payments in Mobile Apps: In-App Purchase, StoreKit 2, Google Billing, Stripe, RevenueCat

In every monetization project, we balance App Store and Google Play policies, PCI DSS requirements, and purchase verification logic on the backend. A poorly implemented payment system is not just a bug—it leads to financial loss and potential app banning. Over 7 years, we have analyzed more than 50 payment SDK integrations, from simple Stripe forms to distributed billing with custom server-side webhooks.

In-App Purchase: Two Platforms, Two Different APIs

If your app sells digital content or subscriptions, Apple and Google require you to use their payment systems. This is non-negotiable: violating App Store rule 3.1.1 or Google Play Developer Policy results in app removal. Physical goods and offline services are a different story.

StoreKit 2 (iOS 15+)

StoreKit 2 is a complete overhaul of the original StoreKit with async/await API. Product.products(for:), product.purchase(), Transaction.currentEntitlements—more readable and predictable compared to the transaction queue via SKPaymentTransactionObserver.

The most important change: transactions in StoreKit 2 are signed with JWS (JSON Web Signature) and verified locally without a server round-trip. Transaction.verificationResult returns .verified(Transaction) or .unverified(Transaction, VerificationError). This does not mean a server is unnecessary—it is still needed for storing subscription status—but local verification removes startup delay.

StoreKit.AppTransaction verifies the actual app download from the App Store. Required for paid downloads or non-renewing purchases.

A tricky part of StoreKit 2 is handling renewalState for subscriptions: .subscribed, .expired, .inBillingRetryPeriod, .inGracePeriod, .revoked. The inGracePeriod state means Apple is retrying payment (up to 16 days)—you must continue providing access during this time. Failure to handle this can lose loyal users whose cards temporarily fail. Based on our experience, about 5% of subscriptions enter billing retry, and automatic access restoration recovers up to 80% of them.

Google Play Billing Library (v6+)

Google Billing is more complex than StoreKit in terms of scenario handling. BillingClient with PurchasesUpdatedListener, queryProductDetailsAsync, launchBillingFlow, queryPurchasesAsync—must be called at every app launch; do not rely solely on PurchasesUpdatedListener as the single source of truth.

Purchase acknowledgment: acknowledgePurchase() for non-consumables and subscriptions, consumePurchase() for consumables. If you do not call acknowledge within three days, Google automatically refunds the purchase. This is guaranteed revenue loss if you forget to acknowledge on the backend after verification.

ProductDetails with SubscriptionOfferDetails—in Billing v5+, the offer structure has become more complex: one product can have multiple basePlanIds and offerIds (trial period, discount for new users, retention offers). BillingFlowParams.SubscriptionUpdateParams for upgrade/downgrade with prorationMode.

Why Is Server-Side Verification Mandatory?

Never trust only client-side code when unlocking paid content. Client-side verification can be bypassed by modifying the app.

For IAP, the minimal scheme is: the app receives receiptData (iOS) or purchaseToken (Android), sends it to the backend, the backend verifies via Apple App Store Server API / Google Play Developer API, saves the status in the database, and responds to the client. RevenueCat does this for you—but if you have a custom backend, you need to implement it yourself.

Webhooks are more important than they seem. Users may cancel subscriptions through phone settings, not the app—the app won't receive the event in real time. Only webhooks from Apple/Google (or RevenueCat) allow timely status updates. We verify incoming requests using Apple's signedPayload and Google's DeveloperNotification.

How Does RevenueCat Simplify Integration?

Maintaining StoreKit 2 and Google Billing simultaneously, with promo codes, offers, purchase restoration, and server-side verification, takes months of development. RevenueCat handles most of this layer.

RevenueCat is not just a payment SDK. It offers:

• A unified API for iOS and Android (and Stripe for web)
• Server-side verification and subscription status storage
• Webhooks for events (purchase, renewal, cancellation, billing issue)
• Analytics for cohorts, MRR, churn
• A/B testing of offers via Experiments

Purchases.configure(withAPIKey:) at startup, Purchases.shared.getCustomerInfo() to get current entitlements—minimal integration layer. Purchases.shared.purchase(package:) instead of directly calling StoreKit/Billing.

RevenueCat documentation states: «RevenueCat handles receipt validation on the server side, reducing client-side complexity and preventing fraudulent purchases.»

Limitations of RevenueCat: it is paid (free up to $2.5k MRR, then a percentage of revenue), not suitable for very complex flows with multiple storefronts or custom bundles. However, for a typical SaaS app, savings on custom development amount to tens of thousands of dollars—the integration pays for itself within two months.

Stripe in Mobile Apps

Stripe is used for physical goods, services, and B2B payments where IAP is not required by platform policy.

Stripe iOS SDK and Android SDK—PaymentSheet for ready-made payment UI, PaymentSheetFlowController for custom UI with saved cards. Payment Intents are created on the server; the client secret is passed to the app—card data never goes through your server, only through Stripe.

Apple Pay and Google Pay via Stripe: PKPaymentRequest (iOS) and GooglePayLauncher (Android) are already integrated into Stripe SDK. Apple Pay conversion rates are 1.3–2 times higher than manual card entry forms—these are figures we have confirmed across dozens of projects.

Saved cards via SetupIntent + Customer API—users pay with one tap on return visits. Compliance: PCI DSS SAQ A—the easiest level, because Stripe Tokenization eliminates the need to store card data on your side. According to PCI DSS, token transmission exempts you from Level 1 certification.

3DS2 (Strong Customer Authentication) is mandatory for payments in the EU under PSD2. Stripe handles it automatically via PaymentIntent.confirmPayment, but you need to correctly handle the .requiresAction status and return the user to the appropriate screen after authentication.

What Is Included in the Work (Deliverables)

Process and Timeline

We start by clarifying the business model: subscriptions, one-time purchases, consumables, freemium. The architecture depends on this. Testing IAP requires Sandbox accounts (Apple) and License Testers (Google)—this is a separate environment setup.

Apple's Sandbox behaves differently from production: subscriptions renew every 5 minutes instead of monthly, inGracePeriod works differently. It is essential to test scenarios: trial expiration, cancellation, billing retry, refund.

The cost is calculated individually based on the set of tools and complexity of server-side logic. On average, we fit within a budget for a typical integration, but the savings from preventing errors and churn offset this investment within a few months.

Get a consultation for your project—contact us. We will help you choose the optimal payment architecture that passes store reviews and does not break under peak loads.