Apple Wallet Integration for Event Tickets

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

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.

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.