What is StoreKit 2?

With StoreKit 2 you fetch products with Product, buy with purchase, and listen for changes with Transaction.updates. You iterate Transaction.currentEntitlements to learn what a customer may use. StoreKit verifies each signed value and hands it back as verified or unverified, and you can also verify the JWS string yourself on a server. Start the transaction listener when the app launches, because purchases can finish outside the app, for example an offer code or a win-back offer redeemed in the App Store.

Apple's store views, such as the subscription store view from iOS 17, can draw a complete paywall in a few lines. You can also test without App Store Connect, because a StoreKit configuration file in Xcode lets you configure products locally, offline, in the simulator or on a device. Apple's server side pairs with it: App Store Server Notifications V2 and the App Store Server API return the same signed format.

RevenueDot works with the RevenueCat SDKs, which post StoreKit 2 signed transactions to POST /v1/receipts. RevenueDot verifies the signature against Apple's root certificate, and with the In-App Purchase key it reads the full history. StoreKit 1 receipts need the key. Without it RevenueDot answers 500 with code 7234, so the SDK keeps the purchase and retries once you add the key.

Sources: Apple: Apple In-App Purchase (StoreKit) · Apple: VerificationResult · Apple: Product · Apple: Testing at all stages of development with Xcode and the sandbox