Migrating to StoreKit 2: what is deprecated and what replaces it
Short answer: Apple’s documentation now marks the original API for In-App Purchase as deprecated; SKPaymentQueue, SKProductsRequest and SKReceiptRefreshRequest are deprecated from iOS 18 and macOS 15, and App Store receipts and the verifyReceipt endpoint are deprecated too. The replacement is StoreKit 2, available from iOS 15, with JWS-signed transactions. The new iOS 27 subscription Bundles and Suites also require StoreKit 2.
What replaces what
Replacements as named on Apple’s deprecated symbol pages and in the App Store Receipts documentation, read 30 September 2026.
| Original API | Status | StoreKit 2 and server replacement |
|---|---|---|
| SKProductsRequest | Deprecated iOS 18, macOS 15 | Product.products(for:) |
| SKPaymentQueue | Deprecated iOS 18, macOS 15 | product.purchase() and Transaction.updates |
| SKReceiptRefreshRequest | Deprecated iOS 18, macOS 15 | Transaction.all and AppTransaction.shared |
| App Store receipt | Deprecated | JWS-signed Transaction and AppTransaction |
| verifyReceipt endpoint | Deprecated | App Store Server API |
| Server Notifications V1 | Deprecated | App Store Server Notifications V2 |
Why migrate now
Beyond the deprecations, some features exist only in StoreKit 2: the ready-made StoreKit views for building a store, the refund request sheet, subscription renewal status and auto-renew preference, offer eligibility, controlling billing issue messages, and the manage subscriptions sheet. The new iOS 27 subscription options depend on it too: subscription Bundles and Suites require StoreKit 2, and subscriptions created before September 14, 2026 in apps without StoreKit 2 start opted out of multiseat purchases. See Bundles, Suites and multiseat.
When you still need the original API
StoreKit 2 needs iOS 15, iPadOS 15, macOS 12, tvOS 15, watchOS 8 or visionOS 1. Apple says to keep the original API for app versions whose minimum is iOS 14, macOS 11 or earlier. Both APIs can run in the same app on iOS 15 and later, and purchases made through either are visible to both, so you can migrate one flow at a time. Apple lists a few features that may still need the original API, such as promoted In-App Purchases in apps running iOS 11 through 16.3.
Migrating step by step
1. Products. Replace
SKProductsRequest with Product.products(for:). 2. Purchases. Call purchase() on the product and handle the result, instead of adding a payment to the queue. 3. Updates. Start a listener on Transaction.updates at launch to catch renewals, purchases made elsewhere and approvals of pending ones, and call finish() once you deliver. 4. Entitlements. Use Transaction.currentEntitlements instead of parsing the receipt. 5. Server. Stop calling verifyReceipt; verify JWS transactions and query the App Store Server API, and move notifications to App Store Server Notifications V2.Test before you ship
Use a StoreKit configuration file in Xcode for local testing and the sandbox environment for end-to-end tests with your server. Check the paths that break most often in a migration: restoring purchases on a new device, a renewal arriving while the app is closed, an interrupted or pending purchase, and a refund. New products still go through review, see how to submit an In-App Purchase for review.
Where Censuus fits
A working store lets you earn; being found brings the buyers. Censuus ranks apps by the visits they draw, and adding your app is free on the List my app form. Placement comes from traffic and sponsorship: apps climb on the visits they draw, and a sponsor can pay to rise higher.
Frequently asked questions
Is StoreKit 1 deprecated?
Yes. Apple’s documentation marks the original API for In-App Purchase as deprecated, with SKPaymentQueue and SKProductsRequest deprecated from iOS 18 and macOS 15. Apple has not published a removal date.
What replaces verifyReceipt?
The App Store Server API for server-side checks, and JWS-signed transactions you can verify yourself. Apple marks receipts and the verifyReceipt endpoint as deprecated.
What is the minimum iOS version for StoreKit 2?
iOS 15, iPadOS 15, macOS 12, tvOS 15, watchOS 8 and visionOS 1.
Can I use StoreKit 1 and StoreKit 2 in the same app?
Yes, on iOS 15 and later. Purchases made with either API are available to both, so you can migrate gradually.
Do the new iOS 27 subscription features need StoreKit 2?
Yes. Apple requires StoreKit 2 for subscription Bundles and Suites, and subscriptions created before September 14, 2026 in apps without StoreKit 2 start opted out of multiseat purchases.
Guides for app developers
- How to market an app: a stage-by-stage plan
- Submit your app for free
- How to get your app to show up in Google search
- How to get your app recommended by AI assistants
- Free app promotion sites, checked for dofollow
- App store optimization checklist: what Apple and Google actually say
- App launch checklist: iOS and Android, step by step
- How to find beta testers for your app
- How to get more app reviews without breaking the store rules
- How to get your app featured on the App Store and Google Play
- App Store and Google Play screenshot sizes: what you must upload
- How to promote an app on Google Play with Play Console’s own tools
- How to promote an iOS app with App Store Connect’s own tools
- App Store keywords: how to fill the 100-character field
- How to market a fitness app: what Apple and Google let you claim
- How to market a kids app: the store rules that shape it
- How to market a finance app: the store rules to know first
- How to market a dating app: the store rules that shape it
- How to market a subscription app: what the stores require of your offer
- How to market a mobile game: the store rules that shape it
- Apple Ads MCP: connect an AI assistant to your campaigns
- How to promote an app on TikTok with creators
- How to promote an app on YouTube with creators
- How to market a VPN app: the store rules to know first
- How to market an AI app: the store rules that shape it
- How to market an education app: schools, parents and learners
- How to localize your App Store and Google Play listing
- Android vitals and Google Play visibility: the thresholds that hide apps
- App Store and Google Play age ratings: what drives them
- App Store privacy labels and Google Play Data safety: what to declare
- Common App Store rejection reasons and how to avoid them
- How to get the first users for your app
- App preview video specs: App Store sizes, length and rules, and the Google Play video
- App Store custom product pages, and the Google Play version
- App icon size for the App Store and Google Play
- App Store phased release and Google Play staged rollouts
- App Store subtitle and promotional text: limits and how to use them
- Google Play feature graphic: size, placement and rules
- TestFlight public link: set it up, limit it, and fix it when it does not work
- App Store promo codes and offer codes: how they work and their limits
- App Store A/B testing: product page optimization and Google Play experiments
- App Store in-app events: limits, badges and media sizes
- App Store Connect analytics: what each metric means
- Google Play store listing reports: clicks, CTR and the 2026 changes
- Google Play target API level requirements for 2026
- Android developer verification: what changed on September 30, 2026
- App Store and Google Play fees in 2026
- Google Play’s 12 testers for 14 days rule, explained
- How to transfer an app to another developer account
- How to remove an app from the App Store and Google Play
- The app account deletion requirement on the App Store and Google Play
- Google Play 16 KB page size requirement: dates, checks and fixes
- Declared Age Range and Play Age Signals: age assurance APIs for app developers
- Xcode 26 and the iOS 26 SDK requirement for App Store Connect
- The iOS privacy manifest: what to declare and how
- Accessibility Nutrition Labels: what to declare on your App Store page
- Google Play’s photo and video permissions policy, explained
- Google Play Billing Library version requirement: what you need to ship now
- App Tracking Transparency: when to ask and how
- App Store Connect API key: create it, store it, use it
- How to submit an In-App Purchase for review
- The Play Integrity API: what it checks and how to use it
- How long app review takes on the App Store and Google Play
- Google Play policy updates in 2026, with the deadlines
- Rosetta 2 end of support: what Mac developers need to do
- Monthly subscriptions with a 12-month commitment on the App Store
- Subscription Bundles, Suites and multiseat purchases on the App Store
- Sign in with Apple private relay email and the new private.icloud.com domain
- App Store Server Notifications V2: switching from V1 and handling every event
- App Store creative assets: headers and search result visuals in iOS 27
- On-Demand Resources is deprecated: moving to Background Assets
- Time Allowances in iOS 27: how your app gets its category
- Android Contact Picker and the new READ_CONTACTS rules
- The Android 17 location button and Google Play’s precise location rules
- Phone verification without READ_CALL_LOG: what replaces call-based checks
- Apple’s EU business terms from October 1, 2026
- Android 17 app memory limits: detect, test and stay under them
- The Android 17 local network permission
- Android 17 background audio hardening
- Cleartext HTTP and certificate transparency on Android 17
- Android 17: lock-free MessageQueue and static final fields
- Android 17 ignores orientation lock and resizability on large screens
- Android 17 behavior changes: a checklist for target SDK 37
- Preparing your app for iPhone Duo
- Google Play subscription grace period and account hold
- Getting your Android app ready for Googlebook
- The Android 17 Handoff API
- ADB Wi-Fi 2.0 wireless debugging
- Android AppFunctions: your app as on-device tools for AI agents
- Android Live Updates: how to qualify for a promoted notification
- App Store Connect webhooks
- Apple Foundation Models: on-device vs Private Cloud Compute
- Using Claude, Codex and other agents in Android Studio
- Gemini Nano for Android developers
- Firebase AI Logic: the App Check deadline and Gemini 2.5 shutdowns
- Swift 6.4: what’s new for app developers
- The Swift SDK for Android
- Publishing your game on Android Auto and Android Automotive OS
- Liquid Glass in a Compose Multiplatform app
- Expo SDK 58: when it ships and what changes
- Device Hub in Xcode 27
- Using the Xcode MCP server with Claude Code, Codex and other agents
- Xcode 27: release, requirements and point releases
- Gemma 4 and Android skills in Android Studio
- The UIScene life cycle is required in iOS 27
- Migrating to Android Gradle plugin 9
- Navigation 3 for Jetpack Compose
- Kotlin 2.4, 2.4.20 and the road to 2.5
- Upgrading your app build to Gradle 9
- The latest Compose BOM and Compose 1.12
- Compose Multiplatform 1.12 and the Hot Reload MCP server
- Opting out of Liquid Glass with UIDesignRequiresCompatibility
- Flutter 3.47 and the latest stable version
- React Native 0.87 and the latest version
- Android Studio Quail 4 and what comes next
- CocoaPods goes read-only: what changes and when
- Fixing YouTube Error 153 in embedded players
- Fixing “APNS token has not been set yet” in Firebase Messaging
- Older iOS Simulator runtimes and Rosetta destinations in Xcode
- Fixing the fmt consteval error in React Native on Xcode 26.4
Put your app in the ranking
Censuus ranks apps by the visits they draw and by sponsorship, no bots. Listing is free; sponsorship raises placement.