/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Apple releases StoreKit 2 alongside iOS 15, letting developers quickly access a user's purchase history, letting users request a refund in-app, and more

Refunds and subscription management  —  As part of this week's launch of iOS 15, iPadOS 15, and watchOS 8, Apple also introduced StoreKit 2 … Source: Apple Developer .

The Verge Ian Carlos Campbell

Context & Ripple Effects

The StoreKit 2 announcement at WWDC promised that subscriptions, refunds, and purchase history would move inside apps rather than behind App Store web flows — today's release alongside iOS 15, iPadOS 15, and watchOS 8 makes that real for every developer on the new SDK.

Refunds have been Apple-managed territory for years: the EU's 14-day no-questions-asked refund policy set the precedent that refund decisions sit with Apple, not the seller. StoreKit 2 extends that logic into the app itself, which is why this matters beyond an API refresh.

First-order effects

  • Developers can now pull a user's full purchase history through a single API call, replacing custom receipt-validation and server-side lookup code many apps had built themselves.
  • Users can request refunds without leaving the app or contacting the developer, shifting first-touch refund handling onto Apple's flow.

Second-order effects

  • Support teams lose their most common ticket category for paid apps — billing disputes and refund requests now route to Apple before a developer ever hears about them, cutting handling cost but also removing the developer's chance to retain a would-be churner with an offer.
  • With subscription status readable in real time inside the app, developers gain the data to build win-back and upgrade prompts of their own — a capability the later Retention Messaging push in the 2026 App Store overhaul shows Apple eventually productizing itself.

Third-order effects

  • If the pattern holds, the App Store keeps absorbing commerce functions developers used to own — payments, receipts, refunds, retention — leaving developers competing on content while Apple owns the transaction layer, and regulators scrutinize exactly that concentration.

The trend: Apple is steadily internalizing app commerce into platform-owned APIs, from EU-mandated refunds to in-app StoreKit 2 flows to its own retention tooling.