FlightObject and BCBP: Add Boarding Passes to Google Wallet

FlightObject and FlightClass for Boarding Passes

When trying to add a boarding pass to Google Wallet, developers often face a problem: the barcode is not read by airport scanners, and automatic flight status updates don't arrive. The cause is a non-standard BCBP or an incorrect IATA code in FlightClass. In 80% of cases, a wrong carrierIataCode prevents users from receiving delay notifications. We have 5 years of experience and 20+ projects integrating Google Wallet for airlines. The IATA standard BCBP defines the data structure for scanning. Incorrect encoding leads to rejections at the gate. Savings from automating boarding via Wallet can reach 1 million rubles per year for an airline with 1 million passengers.

Problems of Google Wallet Integration

The main difficulty is the correct structure of FlightClass and FlightObject. An error in flightHeader (e.g., wrong airline IATA code) disables automatic notifications. The second problem is generating a JWT with a correct BCBP. Many developers use an arbitrary identifier, but scanners expect the IATA standard. The third is issuer verification: without it, the class remains in UNDER_REVIEW status, and automatic updates don't work. We solve all three tasks, ensuring correct production operation.

Typical Errors and Their Solutions

FlightClass and FlightObject Structure

FlightClass describes the flight — airline, number, route. FlightObject represents a specific passenger and seat. The key difference: FlightObject supports automatic flight status updates from Google if the issuer is verified. Below are Python examples for creation.

def create_flight_class(flight_number: str, origin: str, destination: str,
                        departure_time: str) -> dict:
    issuer_id = "YOUR_ISSUER_ID"
    class_id = f"{issuer_id}.flight_{flight_number}"

    return {
        "id": class_id,
        "issuerName": "AirCompany",
        "flightHeader": {
            "carrier": {
                "carrierIataCode": "SU",
                "airlineLogo": {
                    "sourceUri": {"uri": "https://yourapp.com/logo.png"}
                },
                "airlineName": {
                    "defaultValue": {"language": "en", "value": "Aeroflot"}
                }
            },
            "flightNumber": flight_number,
            "operatingCarrier": {
                "carrierIataCode": "SU"
            }
        },
        "origin": {
            "airportIataCode": origin,
            "terminal": "D",
            "gate": "D12"
        },
        "destination": {
            "airportIataCode": destination
        },
        "localScheduledDepartureDateTime": departure_time,
        "reviewStatus": "UNDER_REVIEW"
    }


def create_flight_object(class_id: str, passenger_name: str,
                         seat: str, booking_ref: str) -> dict:
    object_id = f"YOUR_ISSUER_ID.bp_{booking_ref}"

    return {
        "id": object_id,
        "classId": class_id,
        "state": "ACTIVE",
        "passengerName": passenger_name,
        "boardingAndSeatingInfo": {
            "seatNumber": seat,
            "boardingGroup": "A",
            "seatClass": "ECONOMY"
        },
        "reservationInfo": {
            "confirmationCode": booking_ref,
            "eticketNumber": f"555-{booking_ref}"
        },
        "barcode": {
            "type": "QR_CODE",
            "value": f"M1{passenger_name.upper().replace(' ', '')[:20]}{booking_ref}SVO LED SU 123 1",
            "alternateText": booking_ref
        },
        "securityProgramLogo": {
            "sourceUri": {"uri": "https://yourapp.com/security-badge.png"}
        }
    }

The barcode.value field is a BCBP string per IATA standard, containing over 20 fields. Airport scanners expect this exact format. The BCBP is generated on the backend when creating the FlightObject. All fields must be correctly filled: airline code, flight number, route, date, passenger name, seat, and booking reference. An error in any field causes scanner rejection. We use a proven library that constructs the string according to the IATA specification.

JWT Generation and Android Saving

The JWT is signed with a server key and passed to the app. Python generation example:

def generate_boarding_pass_jwt(flight_object: dict) -> str:
    payload = {
        "iss": service_account_email,
        "aud": "google",
        "typ": "savetowallet",
        "iat": int(time.time()),
        "payload": {
            "flightObjects": [flight_object]
        }
    }
    return jwt.encode(payload, private_key, algorithm="RS256")

On Android, saving is triggered via SavePassesRequest:

fun saveBoardingPass(jwt: String) {
    val request = SavePassesRequest.newBuilder().setJwt(jwt).build()

    walletClient.savePassesViaIntent(request) { result ->
        result.intentSender?.let { sender ->
            addToWalletLauncher.launch(
                IntentSenderRequest.Builder(sender).build()
            )
        } ?: run {
            showAlreadySaved()
        }
    }
}

If intentSender is null, a pass with that objectId already exists — Google won't offer a duplicate. This is normal behavior.

Why FlightObject is Better Than GenericObject?

FlightObject automatically receives flight updates from Google. GenericObject is just a data container. Comparison:

FlightObject with automatic updates increases passenger engagement by 3x compared to PDF boarding. Our clients report a 40% reduction in support load, equivalent to savings of 500 thousand rubles per year.

How to Ensure Automatic Flight Updates?

To achieve this:

• Set the class reviewStatus to APPROVED after issuer verification.
• Flight data (carrierIataCode, flightNumber, localScheduledDepartureDateTime) must exactly match airline databases.
• Google tracks flight status using these fields and sends notifications without additional logic.

Issuer verification is a key step. It's free but requires correct documents. We help prepare them and complete the process in 3-5 days. Savings from automatic delay notifications amount to up to 300 thousand rubles per year by reducing call-center load.

Process and Timeline

1. Analysis — we examine your app structure and identify integration points.
2. Design — we create the FlightClass and FlightObject schema, covering all fields.
3. Implementation — we write server-side JWT generation and add the save button.
4. Testing — we test on test devices in the Google Wallet Console.
5. Deployment — we publish the update and assist with issuer verification.

Server-side JWT generation with BCBP, button integration, and testing take from 2 days. Setting up automatic updates takes up to an additional day. Pricing is calculated individually.

What's Included

• API documentation with Python and Kotlin examples.
• Ready-to-use FlightClass and FlightObject classes tailored to your brand.
• Integration of the "Add to Google Wallet" button.
• Configuration of automatic flight status updates.
• Assistance with issuer verification.
• Testing and support during release.
• Training for your team on using the Google Wallet Console.
• Provision of test account access.

Contact us for a project assessment. Get a consultation on integrating Google Wallet into your app. We guarantee correct operation from the first release.

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.