iOS subscription renewal price increases: notifying existing subscribers and staying compliant

When you raise an iOS subscription price, Apple's consent and notification rules determine who stays subscribed and who churns. Here's how active vs passive acceptance works—and how to build your own communication layer on top.

When you raise the price of an iOS auto-renewable subscription, Apple doesn't simply charge existing subscribers the new rate at their next billing date. Depending on the size of the increase, the storefront, and whether you've configured grandfathering, each affected subscriber must either consent to the new price or see their subscription lapse. Understanding this mechanism—and building your own communication layer on top of Apple's—is the difference between a planned, measured price increase and a churn spike you're scrambling to explain.

Active consent vs. passive acceptance: the core distinction

Apple divides the price-increase experience into two consent pathways. Active consent requires the subscriber to open the app and tap "Agree" before their next billing date. If they don't act in time, the subscription lapses at the end of the current paid period. Passive acceptance—introduced progressively from 2022 onward—allows subscribers who do not explicitly reject the change to renew automatically at the new price. In both cases, Apple sends email and push notifications to subscribers, but the downstream renewal behavior differs significantly.

Passive acceptance is not universal. Apple's documentation limits it to specific storefronts and price movement thresholds—broadly, smaller increases on lower-priced subscriptions in markets Apple has deemed eligible. As of early 2026 published documentation, the United States supports passive acceptance, while high-growth markets including Brazil, India, and Turkey required active consent. Verify current eligibility directly in App Store Connect before assuming passive acceptance applies to your global subscriber base.

What happens when you submit a price increase

When you submit a new price through App Store Connect—or via the API, as covered in our price-update workflow guide—the system triggers an automatic sequence for existing subscribers:

• New subscribers see the higher price immediately on the product page and paywall.
• Existing subscribers receive an email and push notification from Apple explaining the upcoming change. This notification is brand-neutral; it comes from Apple, not from your app or company name.
• The in-app StoreKit consent sheet becomes available the next time an affected subscriber opens your app.
• At each subscriber's next billing date, those who consented (actively or passively) renew at the new price. Those who did not consent, lapse.

The consent sheet itself is system UI provided by StoreKit—you don't design it, but you control when you surface it. Presenting it immediately on cold app launch tends to underperform, because the subscriber has no context for why the price is changing. RevenueCat's implementation guidance suggests wrapping the StoreKit prompt in a small amount of contextual UI—a brief banner or bottom sheet explaining the reason for the change—before triggering the system prompt itself. This framing step measurably improves consent rates in implementations where it's been tested.

Building your own communication layer

Apple's system notifications are necessary but rarely sufficient. They're generic, unbranded, and compete with dozens of other App Store communications in a subscriber's inbox. Developers and studios that manage price increases with the least churn consistently layer their own messaging on top of Apple's. A practical sequencing approach:

The re-engagement push in the day 14–25 window is commonly overlooked. Apps with low daily active usage—productivity tools, reference apps, utilities—have a meaningful cohort of subscribers who might not open the app at all during the 30-day consent window. These subscribers are not declining the price increase; they're simply not seeing the prompt. A targeted push to dormant subscribers can recover consent from users who would otherwise lapse from inattention rather than disagreement.

Framing matters as much as timing. Research from Phiture's subscription optimization work suggests that messaging a price increase alongside a concrete value narrative—"We've shipped X, Y, and Z this year"—consistently outperforms announcing the change in isolation. Subscribers who feel the product has delivered value are more likely to consent, even at a higher price point. If your pricing change coincides with a feature launch or a meaningful product milestone, tie the messaging together.

For subscriber email, the content approach that tends to perform best acknowledges the change directly, explains the reason honestly (infrastructure costs, additional features, sustainability), and gives the subscriber a clear next step. Burying the price increase in a paragraph of feature news typically backfires—subscribers notice the charge at billing time and feel misled.

Multi-territory and purchasing-power considerations

If your app is available in multiple App Store storefronts—and most subscription apps with meaningful scale are—a price increase in one territory triggers Apple's notification machinery only for subscribers in that storefront. You may be raising prices across five territories simultaneously, each with different consent eligibility rules, different effective price burdens relative to local incomes, and different subscriber price sensitivity.

Low-PPP markets deserve particular care. RevenueCat's annual subscription benchmark reports and data compiled by Sensor Tower have noted that churn sensitivity to price changes tends to be meaningfully higher in markets where purchasing power parity creates a larger effective price burden. A 20% increase that produces minimal churn in the United States or Germany can produce substantially more in markets like India, Brazil, or Indonesia, where that same price in local purchasing-power terms already represents a premium product. Our post on why churn is higher in low-PPP markets covers the structural reasons in detail.

This asymmetry is one reason per-territory pricing is worth using when raising prices selectively. The App Store Connect API allows you to set different prices by territory, which means raising prices in high-PPP markets while holding or even reducing them in low-PPP markets is a legitimate and increasingly common strategy. For a complementary approach—grandfathering existing subscribers at the old price rather than notifying them—see our guide to Apple's grandfathering rules for subscription price changes, which covers the mechanics and revenue trade-offs.

Monitoring after the notification window closes

The 30-day consent window is the highest-stakes measurement period for any subscription price increase. Set up monitoring before you submit the change—not after the billing cycle runs—so you have a baseline to compare against. Key signals:

• Renewal rate for the affected cohort — App Store Connect Analytics segments renewal by subscription product. A meaningful drop relative to your trailing baseline renewal rate is the clearest signal of consent friction or subscriber disagreement with the new price.
• Refund rate — A spike in refund requests in the days after billing suggests subscribers who were passively accepted weren't expecting the higher charge. Apple processes these refunds, but the volume signals that your pre-billing communication didn't land.
• App Store review sentiment — Price increases sometimes surface in reviews, especially when subscribers feel surprised. AppFollow and Sensor Tower's review analytics tools can flag sentiment shifts before they accumulate into a rating problem. Responding to pricing-related reviews promptly and professionally reduces the long-term rating impact.
• App Store Server Notification events — If you've implemented real-time subscription tracking (covered in our subscription lifecycle guide), the DID_RENEW, EXPIRED, and GRACE_PERIOD_EXPIRED notification types give you event-by-event visibility as the consent window resolves, rather than waiting for Analytics to aggregate.

The cohort analysis is the most actionable output. Segment by territory, by subscription tenure (subscribers of under six months versus over two years behave differently), and by consent type where your tooling supports it. This segmentation usually reveals whether churn is concentrated in a specific market or user segment—and whether a targeted win-back campaign using iOS promotional offers is worth running for subscribers who lapsed but might return at a discount.

Price increases are one of the highest-leverage levers in subscription revenue management, and they're underused by indie developers who worry about subscriber backlash. The evidence from tools like RevenueCat's benchmarks is that well-communicated increases—tied to value and executed with a thoughtful consent flow—produce far less churn than developers typically fear. The risk is not the price increase itself; it's the silent subscriber who opens your app three weeks into the consent window, sees an unexplained system prompt, and dismisses it without understanding what they're agreeing to.

Sources and further reading

• Apple App Store Connect Help — official documentation for managing subscription pricing and notifications
• Apple StoreKit documentation — subscription transaction handling and consent flows
• RevenueCat Blog — annual subscription benchmarks and implementation guides for price changes
• Phiture Mobile Growth Stack — subscription optimization research and pricing strategy
• AppFollow Blog — App Store review analytics and subscriber sentiment tracking
• Sensor Tower Insights — app market data and subscription pricing trend reports