How to add in-app purchases with StoreKit 2

What in-app purchases do for an iOS app

In-app purchases are how you sell anything digital inside an iOS app: a one-time unlock, consumable credits, or access to content. Apple handles the payment, the buyer's payment method, taxes, and refunds. Your job is to load the products you defined in App Store Connect, run the purchase, and unlock the right thing once it succeeds. For digital goods consumed in the app, Apple requires this path under guideline 3.1.1, so Stripe and other processors are not an option there.

Adding it with AppFlight, and manually

With AppFlight you describe what you sell, for example a one-time Pro unlock, and the AI generates the StoreKit 2 code to load the product, run the purchase, and gate the feature. You still create the product records in App Store Connect yourself, since those live in Apple's system, and AppFlight references them by product ID.

Manually, you add a StoreKit configuration or create the products in App Store Connect, then write code that calls Product.products(for:) with your IDs, calls purchase() on the chosen product, and checks the VerificationResult. There is no client key to manage here. StoreKit talks to Apple directly using the signed-in Apple Account.

A SwiftUI example

Load a product, run the purchase, and verify the transaction:

import StoreKit
import SwiftUI

struct StoreView: View {
    @State private var product: Product?

    var body: some View {
        VStack {
            if let product {
                Button("Unlock Pro for \(product.displayPrice)") {
                    Task { await buy(product) }
                }
            }
        }
        .task {
            product = try? await Product.products(for: ["com.example.pro"]).first
        }
    }

    func buy(_ product: Product) async {
        guard let result = try? await product.purchase() else { return }
        if case .success(.verified(let transaction)) = result {
            // Unlock the feature, then finish the transaction.
            await transaction.finish()
        }
    }
}

Common pitfalls

Forgetting to call transaction.finish() leaves the purchase pending and can cause repeat prompts. Not listening to Transaction.updates means purchases made on another device, or Ask to Buy approvals, never unlock until the next manual load. Testing only in the simulator misses real edge cases, so use a sandbox Apple Account or a StoreKit configuration file. If you want cross-platform entitlements, server validation, and paywall analytics without building them, RevenueCat sits on top of StoreKit and handles that layer.