Win-back offers bring lapsed subscribers back at a discount, and the eligibility rules decide who can refund it
Apple's win-back offers let you price a returning subscriber's first period at a discount, or free. Here's how a refunded win-back offer reaches your server, what it costs you in compute and payouts, and which App Store Connect eligibility settings keep refund cyclers out.

Key takeaways
- Apple's win-back offers are free or discounted offers for an auto-renewable subscription, shown only to customers whose subscription has expired and has auto-renew turned off.
- A refunded win-back offer purchase reaches the developer's server as an ordinary REFUND notification. The transaction carries offerType 4 and the offerIdentifier the developer chose in App Store Connect.
- Apple sends a CONSUMPTION_REQUEST for refund requests on any product type, including win-back purchases, and the developer has 12 hours to reply through Send Consumption Information, with the customer's consent.
- App Store Connect sets win-back eligibility with three settings: Minimum Paid Duration (1 to 24 months, or 3, 4 or 5 years), Time Since Last Subscribed (1 to 24 months, minimum and maximum both required) and an optional Wait Between Offers of 2 to 24 months.
- Apple allows up to 350 win-back offers per subscription and up to 5 running at once per storefront, per subscription. The price can't be changed after an offer is created.
- With Streamlined Purchasing on, which is the default, a customer can redeem a win-back offer entirely outside the app, so the app receives a finished transaction before anyone has signed in.
- Google Play has no Apple-style win-back eligibility in Play Console. A lapsed-subscriber offer there uses developer-determined eligibility, and the app alone decides who sees it.
Lapsed subscribers are the cheapest customers you'll ever reacquire, and win-back offers are Apple's tool for doing it: a free or discounted first period, shown to people whose subscription ran out. The catch is that a returning subscriber can ask Apple for that money back like any other purchase. A refund on a win-back offer returns a small payment while your servers, model calls and payouts have already run at full cost. Who gets the offer in the first place is your strongest defense, and App Store Connect gives you more control over that than most developers use.
How Apple's win-back offers work
Apple defines a win-back offer as a free or discounted offer for an auto-renewable subscription, for customers whose subscription is churned. Churned has a precise meaning in StoreKit: the subscription's expirationDate is in the past and willAutoRenew is false. Someone in a billing grace period or billing retry state doesn't qualify, because their subscription hasn't lapsed yet.
You configure each offer per subscription product, not per group. Apple lets you create up to 350 win-back offers per subscription and run up to 5 at a time per storefront, per subscription. You pick one of three payment modes: Pay as you go, Pay up front, or Free. Once an offer exists, its price is locked.
Customers find the offers in more places than your paywall. Apple shows them on the Manage Subscriptions page in the customer's Apple account on iOS 14.3, iPadOS 14.3 and macOS 14 or later, and inside your app on a system win-back offer sheet on iOS 18, iPadOS 18 and macOS 15 or later. If you promote the offer, it can also appear on your product page and in App Store recommendations. You also get a direct link in the format https://apps.apple.com/win-back/<offer Apple ID> to send by email.
The three eligibility settings
| Setting | Allowed values | Required | What it does for refund exposure |
|---|---|---|---|
| Minimum Paid Duration | 1 to 24 months, or 3, 4 or 5 years | Yes | Limits offers to people who paid for a meaningful stretch before they left |
| Time Since Last Subscribed | 1 to 24 months, as a min and max range | Yes, both ends | Targets a lapse window, so someone who cancelled last week can't bounce straight back at a discount |
| Wait Between Offers | 2 to 24 months | No | Stops the same customer from redeeming the same offer again right after it ends |
What a refunded win-back purchase looks like on your server
Nothing about the refund is special, and that's the problem if you aren't looking for it. When a customer redeems a win-back offer after their subscription expired, App Store Server Notifications V2 sends SUBSCRIBED with the subtype RESUBSCRIBE. The signed transaction includes offerType with a value of 4, which Apple reserves for win-back offers, plus the offerIdentifier you typed into App Store Connect.
If the customer then asks Apple for a refund, you get the same sequence as any other subscription. Apple sends a CONSUMPTION_REQUEST, which it does for refund requests on any product type. You have 12 hours to call Send Consumption Information, and only if the customer consented to sharing that data. If Apple grants the refund, a REFUND notification follows.
Where the refund reply helps and where it doesn't
The refundPreference field in your reply accepts DECLINE, GRANT_FULL or GRANT_PRORATED. For an auto-renewable subscription, Apple says not to send a consumptionPercentage with GRANT_PRORATED, because the App Store works out the consumption itself. Your preference is one of several factors Apple weighs. It isn't a veto.
- If the customer used the discounted period heavily,
DECLINEorGRANT_PRORATEDwith an honestdeliveryStatusis the accurate answer. - If the customer never opened the app after redeeming, say so. A refund there costs you little, and pushing back on it costs credibility.
- Keep
offerIdentifierin your refund log. It's the only way to tell which of your offers draws refunds.
What a win-back refund costs you in money
The revenue side is small by design. A discounted first period is the lowest price that subscriber will pay you, so the refund itself returns a modest amount. Your costs don't scale down with the price. A returning subscriber often does the expensive things first: re-syncs a library, regenerates content, restores storage you'd moved to a cheaper tier.
| Cost driver | Billed at the discounted price? | Recovered after a refund? |
|---|---|---|
| Model and API calls made during the offer period | No, billed at your provider's full rate | No |
| Compute and bandwidth to restore a returning account | No | No |
| Storage kept warm for the returning subscriber | No | No |
| Payouts to creators or partners for content consumed | Depends on your payout terms | Only if your terms let you claw it back |
| The discounted subscription payment | Yes | Returned to the customer |
A worked example makes the gap concrete. Say your normal monthly price is $9.99 and your win-back offer charges $2.99 for the first month. A subscriber who comes back, runs a month of heavy usage and gets refunded hands back $2.99 of revenue, but your provider invoices for the usage at its normal rate. The cheaper you make the offer, the larger that gap gets.

How to set eligibility so refund cyclers don't qualify
Eligibility is the cheapest control you have, because it acts before any money moves. These settings and checks come straight from Apple's documentation.
Require real paid tenure
Set Minimum Paid Duration high enough that only customers with a real paying history qualify. Apple's docs don't say whether refunded time counts toward that duration, so don't treat it as a refund filter on its own.
Always set Wait Between Offers
Two months is the minimum Apple accepts. For an offer with expensive usage, a longer wait means a customer who refunds can't cycle the same discount every few months.
Check eligibility before you send the direct link
Before emailing a win-back link, call Get All Subscription Statuses. The renewal info includes eligibleWinBackOfferIds, with the best offer first. Apple says to send the link to eligible customers only.
Decide whether redemption should start in your app
Streamlined Purchasing is on by default. With it on, the customer finishes the purchase outside your app and you get a completed transaction later. Turning it off sends a PurchaseIntent to your app instead, so you can ask the customer to sign in before they buy. Apple requires your latest approved binary to use the PurchaseIntent API before you can switch it off. Redemptions from the Manage Subscriptions page always behave as if Streamlined Purchasing is on, so your server still has to handle transactions that arrive before sign-in.
Google Play handles lapsed-subscriber offers differently
Google Play Console has no win-back eligibility settings like Apple's. Google lists win-back offers for lapsed subscribers as an example of developer-determined eligibility, where you solely decide the business logic and determine eligibility in your app. Google doesn't evaluate those rules, and these offers can't be bought outside your app.
That puts the refund-cycling check entirely in your code. Look up the user's refund history before you show the offer. Google's own refund decisions in the first 48 hours don't ask you for evidence. The one Google flow that does is the chargeback review through orders.reviewrefund, which gives you 24 hours. For orders placed after August 3, 2026, Google shares chargeback costs with you: you carry the purchase price, less Play's service fee, plus the bank's chargeback fees.
Frequently asked questions
- Can a customer get a refund on an Apple win-back offer?
- Yes. A win-back offer purchase is an ordinary auto-renewable subscription transaction, so the customer can ask Apple for a refund. Apple sends you a CONSUMPTION_REQUEST, you have 12 hours to reply with consent, and a REFUND notification follows if Apple grants it.
- How do I know a refunded transaction came from a win-back offer?
- Check the offerType field in the signed transaction. A value of 4 means a win-back offer, and offerIdentifier names the specific offer you set up in App Store Connect.
- Can the same customer use a win-back offer more than once?
- It depends on your settings. The optional Wait Between Offers setting makes a customer wait 2 to 24 months after a win-back offer ends before redeeming the same offer again. If you leave it empty, that setting adds no wait.
- Who is eligible for an Apple win-back offer?
- Only customers whose subscription has expired with auto-renew off, and who match the offer's Minimum Paid Duration and Time Since Last Subscribed settings. Subscriptions in a billing grace period or billing retry state aren't eligible.
- Does Google Play have win-back offers?
- Not as a Play Console eligibility setting. Google treats offers for lapsed subscribers as developer-determined eligibility, so your app decides who sees the offer and Google doesn't check those rules.
Sources and further reading
- Apple Developer: Supporting win-back offers in your app
- App Store Connect Help: Set up win-back offers
- App Store Server API: eligibleWinBackOfferIds
- App Store Server Notifications: notificationType
- App Store Server API: Send Consumption Information
- App Store Server API: refundPreference
- Google Play Console Help: Understanding subscriptions (offer eligibility)
- Google Play Console Help: Updates to refund protection and chargeback cost responsibility
RefundHalt
The refund autopilot for the App Store and Google Play
Keep reading
Brazil is now checking which games still sell loot boxes to kids, and loot box refunds are where the bill lands
Brazil's justice ministry asked the data protection authority to monitor six games that sell loot boxes without age checks. Here's what the law requires, what Apple and Google already demand, and how to price and handle loot box refunds when the box is already open.
Accidental in-app purchases are the refunds you can't win, so the fix belongs on your purchase screen
Accidental in-app purchases come back as refunds on both stores, and no usage evidence proves a tap was meant. Here's how Apple and Google label them, what each one costs you in compute and payouts, and the purchase screen design that stops them before the charge exists.