Handle a subscription price increase wrong and you don't just annoy the customer, you lose the subscription
Raise an auto-renewable subscription price and the customer gets a say. On the App Store, no consent means the plan expires at the old price. On Google Play, an ignored opt-in increase cancels the subscription. Here is how a subscription price increase works on each store, and what it costs.

Key takeaways
- A subscription price increase is the one change a customer can refuse. On the App Store and Google Play, a subscriber who does not agree can end up paying the old price or losing the subscription entirely, depending on how the increase is set.
- Apple raises the price for you when the increase stays within a threshold, but requires each subscriber's consent when the increase is more than 50 percent of the current price and more than about US$5 per period for non-annual plans, or about US$50 per year for annual plans.
- Apple also requires consent for any increase in certain regions, including Germany, Austria, Poland, and South Korea, and for any subscriber who already had a price increase on that subscription within the past 12 months.
- When Apple requires consent and the subscriber does nothing, the subscription does not renew at the higher price. Apple keeps asking about weekly until the plan expires at the end of the current cycle, still at the old price.
- Google Play makes an increase opt-in by default. If the subscriber never accepts, the subscription is automatically canceled and expired on the first renewal the new price would apply to. Opt-out, where silence keeps the subscriber, is available only in some regions and with limits on amount and frequency.
- Existing subscribers are protected by default on both stores. Google places them in a legacy price cohort at their original price until you migrate them, and Apple lets you preserve the current price for anyone who already subscribed.
You can raise the price of a subscription whenever you want. What you cannot do is assume the customer comes along for the ride. A subscription price increase is the rare product change the customer has a formal right to refuse, and both the App Store and Google Play build that refusal right into the billing system. On the App Store, a customer who never responds to the increase is treated as having said no, and the subscription simply ends. Handle the increase without knowing that, and you do not just annoy people, you quietly cancel the very subscribers you were trying to earn more from.
The mechanics are not the same on each store, and the differences decide how much of your base you keep. Apple has a threshold below which it raises the price for you, and above which it must ask each subscriber to consent. Google Play splits every increase into opt-in, where silence cancels the plan, and opt-out, where silence keeps it, and only offers the friendlier option in some places. Here is exactly how a subscription price increase works on each store, when the customer gets a veto, and what the veto costs you when it lands.
Why a subscription price increase is different from any other change
You can change almost anything about your app without asking permission. You can redesign it, drop features, add tiers, and reprice for new customers, and the store just lets you. A subscription price increase for people who are already paying is the exception. Because it changes a recurring charge the customer already agreed to, both stores treat it as a new agreement the customer has to accept, not a change you can impose. That single fact is why a raise can shrink your revenue instead of growing it. The number on the page goes up, but the set of people willing to pay it can go down, and on one store doing nothing counts as walking away.
When the App Store makes you ask for consent
Apple runs every increase through one test: is it small enough to apply on its own, or large enough to need the customer's yes. When you schedule the increase in App Store Connect, you also choose whether existing subscribers are affected at all, or whether you preserve their current price and only charge new customers more.
The three triggers that require consent
Apple requires a subscriber's explicit consent if any one of three things is true. First, the subscriber is in a region that requires consent for every price change, which includes Germany, Austria, Poland, and South Korea among others. Second, the increase is more than 50 percent of the current price and the difference is more than about US$5 per period for a non-annual subscription, or about US$50 per year for an annual one. Both parts of that second test have to be true, so a large percentage on a cheap plan can still stay automatic. Third, the subscriber already went through a price increase on that same subscription within the past 12 months. Stay clear of all three and Apple raises the price for you, with no action needed from the customer.
| Country | Non-annual threshold | Annual threshold |
|---|---|---|
| United States | US$5 | US$50 |
| United Kingdom | GBP 5 | GBP 50 |
| Canada | CA$7 | CA$70 |
| Australia | AU$8 | AU$80 |
| India | INR 500 | INR 5,000 |
| Japan | JPY 800 | JPY 8,000 |
| Brazil | BRL 40 | BRL 400 |
These amounts vary by country, and Apple can adjust them for tax and exchange-rate changes. The percentage part of the test, more than 50 percent, does not change.
What happens when the customer says nothing
This is the part that costs developers money without them noticing. When Apple requires consent, it asks the subscriber to agree through email, a push notification, and in-app messaging on iOS 13.4 or later. If the subscriber agrees, the plan renews at the new price. If the subscriber does nothing, the plan does not renew at the higher price. Apple keeps asking about once a week, and if consent never comes, the subscription expires at the end of the current billing cycle at the old price. So the price you set too high does not earn you more from those subscribers. It earns you nothing from them, because they roll off instead of renewing. Apple starts the clock early: the first email goes out 60 days before renewal for plans of two months or longer, 27 days ahead for monthly plans, and 7 days ahead for weekly ones.
How Google Play splits every increase into opt-in and opt-out
Google Play protects existing subscribers by default. When you change a price, everyone who already subscribed goes into what Google calls a legacy price cohort and keeps paying their original price until you decide to end that cohort and move them to the new price. When you do move them, Google sorts the increase into one of two modes, and the mode decides what silence means.
Opt-in is the default, and silence cancels the plan
An opt-in increase is the default, and it is what you get in most regions or whenever the increase is too large or too frequent to qualify for the gentler treatment. The subscriber has to actively accept the new price. Google gives you a 7-day head start after you trigger the migration, during which it sends no notifications, so you can tell subscribers yourself inside the app. Then, starting 30 days before the first renewal at the new price, Google notifies them by email and push. If the subscriber never accepts and reaches that first renewal, Google automatically cancels and expires the subscription on the renewal date. Ignore an opt-in increase and you are not kept on at the old price the way Apple does it. You are gone.
Opt-out keeps the subscriber, where Google allows it
An opt-out increase is the one that behaves the way most developers expect. The subscriber is charged the new price at the next renewal unless they actively cancel or change plans, so silence keeps them paying. The catch is availability. Opt-out is offered only in certain countries, only within limits on how much and how often you can raise the price, and only to developers in good standing on Google Play. Where it is allowed, you still have to show each affected subscriber a clear in-app notice at least 30 days ahead, naming the subscription, the current and new price, and the date the new price takes effect, and the advance notice runs 30 or 60 days depending on the country. Price decreases, by contrast, are always automatic and need no acceptance.
| If the subscriber does nothing | App Store | Google Play opt-in | Google Play opt-out |
|---|---|---|---|
| Consent needed | Only above the threshold or in consent regions | Always | Never, they must act to leave |
| Silence means | Plan expires at the old price | Plan is canceled and expired | Plan renews at the new price |
| Where it applies | Everywhere, by the threshold test | Default, most regions | Certain regions, with limits |
| Advance notice | 60, 27, or 7 days by plan length | 30 days before first renewal | 30 or 60 days by country |
What a price increase actually costs you
The sticker price of a raise is easy to read. The real cost is the subscribers you lose in exchange for the higher number, and that cost is largest exactly where the customer has to opt in.
The consent lane is where your base leaks
When an increase needs consent, whether that is an over-threshold raise on Apple or an opt-in raise on Google Play, a share of your subscribers will simply never respond. Those subscribers do not stay on at the old price on Google Play, and they do not stay at all on either store once the cycle ends. So the arithmetic is not old price versus new price. It is the new price times the people who consent, against the old price times everyone who was renewing before. Push the increase into the consent lane on a large enough cohort and the version that raised the price can bring in less total revenue than leaving it alone.
The costs that do not come back
A subscriber who rolls off after refusing a price increase takes more with them than one month of revenue. You lose the renewal tail you were already counting on, the lifetime value of an account that was going to keep paying, and any fixed cost you spent acquiring them that had not yet paid back. None of that shows up as a refund or a chargeback. It shows up as a subscriber who was there last month and is not there this month, which is why a price increase that looks successful in the pricing screen can read as a churn spike in the numbers that matter.

How to raise a price without losing the subscriber
You cannot remove the customer's right to refuse, but you can decide how often you put them in a position to use it.
Stay inside the automatic lane when you can
On the App Store, keeping an increase within the threshold, under 50 percent or under the currency amount, means Apple applies it for you and no subscriber has to consent. On Google Play, keeping the increase within the region, amount, and frequency limits is what makes opt-out available, so silence keeps the subscriber instead of canceling them. Several smaller increases that each stay in the automatic lane will usually keep more of your base than one large raise that forces a consent step. Remember Apple's 12-month rule though: a second increase on the same subscription within a year forces consent no matter how small it is.
Grandfather the subscribers you already have
Both stores let you raise the price for new customers while leaving current subscribers untouched. Apple calls it preserving the current price. Google calls it leaving the legacy price cohort in place. This is the safest way to reprice, because it captures more revenue from every new sign-up without giving a single existing subscriber a reason to reconsider. You give up the extra revenue from your current base, but you keep the base, and for most apps the base is worth more than the raise.
The outcome of a price increase arrives on the same App Store Server Notifications and Real-time Developer Notifications that RefundHalt already reads for refunds and chargebacks. A subscriber who refuses a raise and expires, and a cohort migration that cancels the subscribers who never opted in, both land as subscription state changes on those feeds. Reading them next to your refunds means you can see what a price increase actually cost you in lost subscribers, instead of guessing from an aggregate revenue line that hides the churn underneath it.
The short version
A subscription price increase is the one change your existing customers get to refuse, and each store handles the refusal differently. Apple applies an increase automatically when it stays within a threshold, under 50 percent and under about US$5 per period or US$50 per year, but requires consent above that, in certain regions, or for a second raise within 12 months, and a subscriber who does not consent expires at the old price. Google Play makes increases opt-in by default, where silence cancels the plan, and offers opt-out only in some regions, where silence keeps the subscriber. The way to protect your revenue is to stay in the automatic lane where you can, grandfather the subscribers you already have, and watch the churn a raise creates rather than only the new price it sets.
Frequently asked questions
- Can I raise the price of an existing subscription on the App Store and Google Play?
- Yes, on both stores, but existing subscribers are protected by default and you decide whether to include them. Apple lets you preserve the current price for existing subscribers or apply the increase to them. Google Play places existing subscribers in a legacy price cohort at their original price until you choose to migrate them to the new price.
- When does Apple require a subscriber to consent to a price increase?
- Apple requires consent if any of three things is true: the subscriber is in a region that requires consent for every price change, such as Germany, Austria, Poland, or South Korea; the increase is more than 50 percent of the current price and the difference is more than about US$5 per period for non-annual plans or US$50 per year for annual plans; or the subscriber already had a price increase on that subscription within the past 12 months. Otherwise Apple applies the increase automatically.
- What happens on the App Store if a subscriber does not consent to a price increase?
- The subscription does not renew at the higher price. Apple continues to ask for consent about once a week through email, push, and in-app messaging, and if the subscriber never agrees, the subscription expires at the end of the current billing cycle at the old price. You earn nothing more from that subscriber, because they roll off rather than renew at the new price.
- What is the difference between an opt-in and an opt-out price increase on Google Play?
- An opt-in increase requires the subscriber to actively accept the new price, and if they never accept, Google automatically cancels and expires the subscription on the first renewal the new price would apply to. An opt-out increase charges the new price at the next renewal unless the subscriber cancels or changes plans, so silence keeps them. Opt-in is the default; opt-out is available only in certain regions, within limits on amount and frequency, and only to developers in good standing.
- How much advance notice do subscribers get before a price increase?
- On the App Store, the first email goes out 60 days before renewal for plans of two months or longer, 27 days ahead for monthly plans, and 7 days ahead for weekly plans, followed by push and in-app messages. On Google Play, an opt-in increase notifies subscribers starting 30 days before the first renewal at the new price, and an opt-out increase requires 30 or 60 days of advance notice depending on the country, plus an in-app notice at least 30 days ahead.
- How do I raise a subscription price without losing subscribers?
- Keep the increase inside the store's automatic lane. On Apple, stay under the 50 percent and currency thresholds so the increase applies without consent, and avoid a second increase on the same subscription within 12 months. On Google Play, stay within the region, amount, and frequency limits that make opt-out available. Or grandfather your existing subscribers by repricing only for new customers, which captures more revenue without giving current subscribers a reason to cancel.
Sources and further reading
- Apple Developer, App Store Connect Help: Manage pricing for auto-renewable subscriptions (preserve versus apply the price, the three conditions that require consent, the notification timeline, and the subscription expiring at the old price when consent is not given)
- Apple Developer, App Store Connect Help: Auto-renewable subscription price increase thresholds (per-country non-annual and annual thresholds, and the regions that require consent for all price changes)
- Android Developers: Change subscription prices (legacy price cohort, opt-in as the default and the automatic cancellation when it is ignored, opt-out availability and behavior, the 7-day developer window, the 30 and 60 day notice periods, and automatic price decreases)
- Google Play Console Help: Create and manage subscriptions (a price increase becomes opt-in when a cohort does not meet the region, frequency, or amount criteria)
RefundHalt
The refund autopilot for the App Store and Google Play
Keep reading
A pending purchase looks like a sale, but the money hasn't arrived, and granting it early gives the product away
Both the App Store and Google Play have a pending purchase state, an order the store has accepted but not yet charged. Unlock it before the payment clears and every one that falls through is pure cost. Here is how pending purchases work on each store, what a wrongly granted one costs, and how to handle them without leaking.
Renewals fail more often than customers cancel, and that involuntary churn is revenue you can still win back
A declined card, not a tap on cancel, ends a large share of subscriptions, and the store keeps trying to collect for weeks. Here is how the billing grace period, billing retry, and account hold work on the App Store and Google Play, and what involuntary churn really costs you.