Skip to content
AppDues
Log in
Contact salesSign up

StoreKit 2 overview: APIs, server changes and migration choices

StoreKit 2 modernises Apple in-app purchases with a cleaner client API, signed transaction data, more reliable server notifications and new support tools. This guide explains what changed, where the old workflow breaks, and how to decide whether to adopt StoreKit 2 immediately or maintain both StoreKit versions during the transition.

A cleaner client API and no transaction queue

The client API is built around modern Swift concurrency, including async/await. A JSON backing value lets developers reach newer capabilities without waiting for a later operating-system release, and purchases can be validated directly. The older SKPaymentTransactionQueue is replaced by Transaction.listener. Transaction changes are intended to appear in real time across devices, and on a first install the customer's transactions are already loaded, removing the need to restore purchases immediately after installation. Receipt verification can now be handled through StoreKit, although manual validation remains possible with the new receipt format.

Migration decision: iOS 15 and dual implementation

StoreKit 2 requires iOS 15 or later. An app that must also run on iOS 14 therefore needs separate StoreKit 1 and StoreKit 2 implementations, or it can stay on StoreKit 1 until iOS 14 support is dropped. Use this decision checklist: confirm the minimum iOS version your users run; inventory every purchase, restore, receipt-validation and subscription-status path; decide whether dual implementation is worth the maintenance cost; plan server changes for signed transactions and notifications V2; and test refunds, consumption responses, renewal extensions and sandbox notification URLs before release. A common failure distinction is that the refunds API does not grant refunds itself: it lets customers start the refund process, while Apple communicates the decision within 48 hours.

Server API, signed receipts and notifications V2

The new server API replaces /verifyReceipt. Instead of sending a receipt, callers use originalTransactionId, with separate endpoints for the latest transactions and the full paginated history. Receipts use JSON Web Signatures and are divided into Signed Transactions rather than one receipt containing the entire history. App Server Notifications V2 are more reliable and complete, making near-real-time subscription tracking easier, although polling may still be needed if a notification is missed during server downtime. Sandbox testing gains a notification URL, plus controls to clear purchase history, change account region and adjust renewal rates.

Support APIs: refunds, consumption, lookups and extensions

The refunds flow gives customers an in-app way to request a refund and explain the reason. When a refund is requested, the App Store sends a CONSUMPTION_REQUEST notification and the server has 12 hours to respond with context such as whether content was delivered, how long the customer has subscribed and how much has previously been refunded. A Manage Subscriptions API can open the existing subscription-management flow. Invoice Lookup uses the invoice order ID from the customer's email to retrieve a purchase in the new JWS format, while Refunds Lookup returns all refunds a user has requested. The Renewal Extension API can add up to 90 days, twice a year, for cases such as an outage or another customer-impacting problem.

Feature inventory from the FAQs

Additional FAQ-listed capabilities include restoring purchases from receipts, subscriptions for auto-renewing and non-consumable products, App Store account information, Family Sharing, customisable product pages, Apple Pay authorisation, promotion codes, improved server-to-server transaction tracking, download validation and control, broader API access to app content, promotional discounted pricing, and improved App Store messaging, product-page design, security and privacy. Treat this list as a feature inventory, not as a claim that every item is new or unique to StoreKit 2.

Frequently asked questions

What new features have been added to StoreKit with version 2?

StoreKit 2 adds async/await support, a JSON backing value for using features before new OS releases, purchase validation, a Transaction.listener in place of the transaction queue, StoreKit-based receipt verification, a new server API using originalTransactionId instead of sending receipts back and forth, JSON Web Signature receipts split into Signed Transactions, App Server Notifications V2, refund initiation, a Consumption API, Manage Subscriptions, invoice and refund lookup, renewal extensions of up to 90 days twice a year, and sandbox controls for purchase history, account region and renewal rates.

Can I use my existing app analytics tools with StoreKit 2?

Yes. Tools such as Google Analytics for Firebase, Flurry and Mixpanel are described as compatible. Existing analytics and reporting tools can still be used, although implementation code needs updating to use StoreKit 2 capabilities. Apple also provides an API for collecting and analysing StoreKit 2 usage data.

How does payment processing work in StoreKit 2?

A purchase begins when a user taps a buy button for a product. StoreKit sends device and purchase details to the App Store server, Apple verifies the payment information and grants approval, and the app is notified through a callback URL containing payment information and whether the purchase succeeded. The app can then process that information and complete the transaction, and Apple sends an electronic receipt to developer and customer email addresses as proof of payment.