Offer codes for in-app purchases replaced Apple's promo codes, and every paid redemption can still come back as a refund
Apple's offer codes now cover consumables, non-consumables and non-renewing subscriptions, with free or discounted pricing. Here's how a refunded offer code purchase reaches your server, what it costs you in compute and payouts, and which settings keep a code campaign from turning into a refund leak.

Key takeaways
- Since March 26, 2026, developers can no longer create promo codes for In-App Purchases in App Store Connect. Apple's offer codes replace them, and they support consumables, non-consumables, non-renewing subscriptions and auto-renewable subscriptions.
- An Apple offer code can be a Free Offer or a Paid Offer at a discounted price. A paid redemption is a real purchase, so the customer can ask Apple to refund it like any other transaction.
- When a customer redeems an offer code for a consumable, non-consumable or non-renewing subscription, App Store Server Notifications V2 sends ONE_TIME_CHARGE. The signed transaction carries offerType 3 and offerDiscountType ONE_TIME.
- Apple sends a CONSUMPTION_REQUEST when a customer requests a refund on any product type, including offer code purchases. The developer has 12 hours to reply through Send Consumption Information, and only with the customer's consent.
- App Store Connect allows up to 10 active offer code offers per app and up to 1 million one-time use codes plus 1 million custom codes per app, per quarter, shared across all In-App Purchases.
- An offer code's eligibility and price can't be edited after the offer is created. Each customer can redeem one code per offer, and deactivating an offer expires its codes immediately without touching past redemptions.
- Google Play promo codes give one-time products away free, so they create no charge to refund. Google allows up to 500 non-subscription promo codes per app, per quarter.
Promo codes for In-App Purchases stopped being something you can create in App Store Connect on March 26, 2026. Apple's offer codes for in-app purchases took their place, and they do one thing the old codes didn't: they can charge money. A Paid Offer sells a consumable, a non-consumable or a non-renewing subscription at a discount. That makes every paid redemption a purchase the customer can ask Apple to refund, after your servers, model calls and payouts have already run at full cost.
How offer codes for in-app purchases work now
Apple announced the change on October 29, 2025. Offer codes used to be a subscription tool. They now cover consumables, non-consumables and non-renewing subscriptions too, in addition to auto-renewable subscriptions. Apple's StoreKit documentation describes them as alphanumeric codes that provide In-App Purchases at a discount or for free, for a specific duration. Existing IAP promo codes still redeem until they expire, and promo codes for free app downloads still exist.
When you create an offer, you choose a Free Offer or a Paid Offer. For a paid one, you set a discounted price for a base country or region and App Store Connect fills in comparable prices for all 175 storefronts. You also pick who qualifies, from three options: never purchased within your app, purchased within your app in the last 30 days, or purchased more than 30 days ago. Selecting all three opens the offer to everyone.
The three kinds of codes
| Code type | Volume | Expiration | Where customers redeem |
|---|---|---|---|
| One-time use codes | 500 to 25,000 per batch, up to 1 million per app per quarter | Required, up to 6 months | Redemption URL, App Store, or in your app |
| Custom codes (your own word, like SUMMER25) | Up to 25,000 redemptions at a time, up to 1 million per app per quarter | Optional, up to 6 months, or no end date | Redemption URL or in your app |
| Sandbox codes | 10 to 10,000 per batch | Optional, up to 6 months | Sandbox account settings on a device |
Each app can run up to 10 active offers at a time, and each customer can redeem one code per offer. In-app redemption needs iOS 16.3, macOS 15.0 or visionOS 1.0 or later for one-time products.
What a refunded offer code purchase looks like on your server
A redemption often happens outside your app. Customers can type a one-time code into the App Store or open a redemption URL, and Apple prompts them to download your app if they don't have it. Your server hears about it before your app does.
For a consumable, non-consumable or non-renewing subscription, App Store Server Notifications V2 sends ONE_TIME_CHARGE. For an auto-renewable subscription, it sends SUBSCRIBED for a new purchase or resubscribe, and OFFER_REDEEMED for an active subscriber. The signed transaction tells you it came from a code.
| Transaction field | Value on an offer code purchase | Why it matters for refunds |
|---|---|---|
| offerType | 3 | Marks the purchase as an offer code redemption |
| offerIdentifier | The identifier of the offer in App Store Connect | Tells you which campaign the refund belongs to |
| offerDiscountType | ONE_TIME for consumables, non-consumables and non-renewing subscriptions | Separates one-time product codes from subscription offers |
| price | The discounted price, in milliunits | Shows what the customer actually paid, and so what a refund returns |
If you still read the old app receipt, note that Apple's legacy offer_code_ref_name field isn't populated for consumables, non-consumables and non-renewing subscriptions. The signed transaction is where these redemptions are visible.
The refund request itself
Nothing about the refund path changes because a code was involved. Apple's Send Consumption Information documentation says the App Store sends a CONSUMPTION_REQUEST when a customer requests a refund on any product type. If the customer consented, you have 12 hours to reply with customerConsented, deliveryStatus, consumptionPercentage, refundPreference and sampleContentProvided. If they didn't consent, Apple says not to respond. A REFUND notification follows if Apple grants it.
What an offer code refund costs you in money
The refund side is small, because the customer paid a discounted price. Your delivery costs don't shrink with the price. A code that sells 1,000 AI credits at a steep discount still triggers 1,000 credits' worth of model calls, billed at your provider's normal rate. A non-consumable unlocked by a code still pulls the same storage and bandwidth as one bought at list price.
| Cost driver | Scaled to the discounted price? | Recovered after a refund? |
|---|---|---|
| Model and API calls behind consumed credits | No | No |
| Compute and bandwidth to deliver the content | No | No |
| Storage for files the customer created or downloaded | No | No |
| Payouts to creators, affiliates or partners | Depends on your terms | Only if your terms allow a clawback |
| The discounted payment | Yes | Returned to the customer |
Here's a hypothetical to make the gap concrete. Say a credit pack lists at $9.99 and your code sells it for $1.99. A customer who redeems, spends every credit and gets refunded takes back $1.99. Your model provider still invoices the full usage. Run that across a code posted on a deal forum and the campaign's real cost is your usage bill, not the discount you planned.

How to keep a code campaign from becoming a refund leak
Every control below acts before money moves, which makes them cheaper than any dispute after the fact.
Choose eligibility on purpose
Ticking all three eligibility boxes is the default temptation. For a paid code on an expensive consumable, consider limiting it to people who have purchased before, because you already hold history on them. Apple's docs don't say whether refunded purchases count as purchases for eligibility, so don't treat this as a refund filter on its own.
Prefer one-time use codes for anything costly
A custom code is one word anyone can share, good for up to 25,000 redemptions at a time. One-time use codes are random and work once each. If a leak would hurt, use one-time codes and hand them out individually.
Deactivate leaked codes fast
Deactivating an offer makes its codes expire immediately. Customers who already redeemed keep what they got, and unredeemed codes don't return to your quarterly limit. Watch redemption volume per offerIdentifier so you notice a leak in hours, not at month end.
Tie the redemption to an account
Purchases redeemed in the App Store arrive without an appAccountToken, because your purchase flow never ran. The App Store Server API's Set App Account Token endpoint lets your server attach one afterward. With it, a refund on a code purchase points at a real user you can act on.
Answer the consumption request honestly
If the customer used the credits or content, say so with an accurate deliveryStatus and consumptionPercentage. If they never opened the app after redeeming, a refund costs you little and resisting it costs credibility. Your refundPreference is one input to Apple's decision. It isn't a veto.
Google Play promo codes don't create this problem
Google Play's promo codes work differently. Codes for paid apps and one-time products give the item away free, and subscription codes grant a free trial of 3 to 90 days. A free item carries no charge for a customer to refund. Google caps non-subscription promo codes at 500 per app, per quarter, and unused codes don't carry over.
A discounted Google Play purchase is an ordinary paid order, and it follows the usual rules. Google decides self-service refunds in the first 48 hours without asking you. The one flow that asks you for evidence is the chargeback review through orders.reviewrefund, with a 24-hour window. For orders placed after August 3, 2026, Google shifts the chargeback's purchase price, less Play's service fee, plus the bank's chargeback fees onto the developer.
Frequently asked questions
- Can a customer get a refund on something bought with an Apple offer code?
- Yes, if they paid for it. A Paid Offer redemption is a normal purchase at a discounted price, so the customer can ask Apple for a refund. Apple sends you a CONSUMPTION_REQUEST, you have 12 hours to reply if the customer consented, and a REFUND notification follows if Apple grants it. A Free Offer has no payment to refund.
- Can I still create promo codes for in-app purchases?
- No. Since March 26, 2026, App Store Connect no longer lets you create promo codes for In-App Purchases. Codes created before then can be redeemed until they expire, and promo codes for free app downloads are still available. Offer codes are the replacement.
- How do I tell that a refunded transaction came from an offer code?
- Check offerType in the signed transaction. A value of 3 means the customer redeemed an offer code, and offerIdentifier names the offer. For consumables, non-consumables and non-renewing subscriptions, offerDiscountType is ONE_TIME.
- How many offer codes can I create for in-app purchases?
- Up to 1 million one-time use codes and up to 1 million custom codes per app, per quarter, shared across all In-App Purchases. Each app can have up to 10 active offers at a time, and one-time use codes come in batches of 500 to 25,000.
- What happens if an offer code leaks online?
- Deactivate the offer in App Store Connect. Its codes expire immediately, customers who already redeemed keep what they got, and unredeemed codes don't go back to your quarterly limit. Refund requests on past paid redemptions still arrive as normal CONSUMPTION_REQUEST notifications.
Sources and further reading
- Apple Developer News: Enhancements to help you submit and market your apps and games (October 29, 2025)
- App Store Connect Help: Create offer codes for In-App Purchases
- Apple Developer: Supporting offer codes in your app
- App Store Server API: offerType and offerDiscountType
- App Store Server API: Send Consumption Information
- App Store Server API: Set App Account Token
- Google Play Console Help: Create promo codes
- 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.