Apple now lets AI apps sell expiring consumables, but expiry won't protect you from refunds
Apple's new entitlement lets generative AI apps sell expiring consumables with a 12-month minimum term. Here's what it allows, what it costs you to run, and how to track credits so your reply holds up when a customer asks Apple for a refund.

Key takeaways
- Apple now lets generative AI apps request an entitlement to sell expiring consumables, credit packs that lapse after a minimum term of 12 months unless local law requires otherwise.
- Apple's App Review Guidelines still say credits bought through in-app purchase may not expire, so the expiring consumables entitlement is the only way an AI credit pack can lapse on the App Store.
- Only credits that unlock generative AI services qualify for expiring consumables, existing in-app purchases can't be converted, and only an Account Holder can request the entitlement.
- Apps with expiring consumables must show the expiry term on the paywall, display the balance, spend the oldest credits first and email customers 30 days and 7 days before credits expire.
- Expiry doesn't change App Store refunds. Apple points expiring consumables to Send Consumption Information, and a developer has 12 hours after a CONSUMPTION_REQUEST to reply.
- Apple's consumptionPercentage describes the share of one transaction the customer consumed, in milliunits, so AI credits that expired unused shouldn't be reported as consumed.
- A refunded AI credit pack returns the customer's money but not the model API calls, compute and storage the developer already paid for to serve it.
Apple will now let generative AI apps sell expiring consumables, credit packs that lapse if they sit unused. The change arrived as a short entry on Apple's App Store developer news page, with no date and no press release, plus a request form for Account Holders. It's a real carve-out. Apple's App Review Guidelines still say credits or in-game currencies bought through in-app purchase may not expire, and this entitlement is the only door around that rule.
Apple is already using the model itself. On November 9, 2026, it started selling $49.99 intelligence usage packs in Logic Pro that roll over month to month and expire 12 months after purchase, 9to5Mac reported. What the entitlement doesn't touch is refunds. Expiry limits how long you owe a customer service. It doesn't stop that customer from asking Apple for their money back after the credits are spent, and your only say in that decision is still a reply to Apple's CONSUMPTION_REQUEST within 12 hours.
What Apple's expiring consumables entitlement allows
Apple drew the boundaries tightly. The entitlement covers credits that buy AI output and nothing else.
Who qualifies
- Your app is on the App Store and sells consumable in-app purchases, such as credits or tokens, that unlock generative AI services.
- The credits pay for AI output: generated images, seconds of AI video, minutes of text to speech, or text reviewed and summarized by AI.
- Only an Account Holder in the Apple Developer Program can request it, through a form in App Store Connect.
- Existing in-app purchases can't be converted. Expiring consumables must be created as new products so App Review can check them.
Mixed catalogs get split. Apple's own example is an app that sells stock photo credits and AI image credits. Only the AI image credits can expire.
What you owe customers in return
| Requirement | What Apple asks for |
|---|---|
| Expiration term | At least 12 months, unless local law requires otherwise |
| Paywall | The term shown next to the price or purchase button, plus which features use the credits |
| Balance | The current balance shown in the app, as credits or a percentage |
| Order of use | Oldest credits first, so the balance expiring soonest goes first |
| Reminders | An email 30 days and 7 days before expiry to anyone with a balance |
| Subscription credits | Not expiring consumables, and used before them |
App Review checks these rules when you submit the new products. Apple also says a subscription can include an allowance, giving the example of up to 500 credits a month, and those included credits must be spent before any expiring pack.
Why expiry doesn't change your refund exposure
A customer can still ask Apple to refund a credit pack. Apple's page on expiring consumables doesn't describe a new refund rule. It points you to the Send Consumption Information endpoint, the same one every other in-app purchase uses.
When a refund request comes in, Apple sends your server a CONSUMPTION_REQUEST notification. If the customer consented to sharing their data, you reply within 12 hours. Apple says it weighs a variety of factors, and the final refund percentage may differ from the figure you send. Apple decides. You supply evidence.
| Field | Required | What to send for an expiring credit pack |
|---|---|---|
| customerConsented | Yes | true, and if the customer didn't consent, don't reply at all |
| deliveryStatus | Yes | Whether the credits arrived and worked |
| consumptionPercentage | No | Share of this transaction's credits spent, in milliunits, where 100000 is 100% |
| refundPreference | No | GRANT_FULL, GRANT_PRORATED or DECLINE |
| sampleContentProvided | Yes | Whether you offered a free sample, a trial or a description of the feature before purchase |
Expired credits weren't consumed
Here's the trap. Apple defines consumptionPercentage as the portion of the product the customer consumed. Credits that lapsed unused weren't consumed by anyone. If a customer spent 120 of 200 credits and the other 80 expired, the honest figure is 60000, not 100000. Apple hasn't published guidance on expired balances, so report what was used and let your terms explain the expiry.
Two more rules apply. If deliveryStatus isn't DELIVERED, consumptionPercentage must be 0, or Apple rejects the reply with an HTTP 400 error. And Apple's own example for a transaction with a quantity of two, where one unit was fully used, is 50000.
Oldest-first decides which purchase was spent
Consumption is reported per transaction, not per account. Say a customer bought a 200-credit pack in March and another in September, then spent 250 credits. Oldest-first means the March pack is empty and the September pack has given up 50 credits. A refund request on the September purchase should report 25000. Not 100000, and not an average across the account. If the customer also had a subscription allowance, those credits went first and count against neither pack.
Keep a ledger per purchase
- Store each pack as its own lot with the transaction ID, purchase date, expiry date, credits granted and credits left.
- Debit any subscription allowance first, then the lot that expires soonest.
- Log every debit with the request it paid for, so you can show the use later.
- Put credits back into the same lot when a generation fails, and record that output as not delivered.
- Mark lapsed credits as expired, never as spent.

What a refunded credit pack costs you in money
Take an illustrative case. A customer pays $9.99 for 200 AI image credits. Each generation calls a model API that bills you per request, and the images sit in storage you pay for every month. The customer spends 150 credits, then asks Apple for a refund.
If Apple grants it, the $9.99 goes back to the customer and your proceeds on that sale reverse. The 150 API calls don't. You paid for them when they ran. The storage keeps billing until you delete the files. If any of those generations triggered a payout to a model partner or a creator, that money is already gone too.
| Cost on the refunded pack | Reversed by the refund |
|---|---|
| Price the customer paid | Yes, returned to the customer |
| Your proceeds on the sale | Yes, taken back |
| Model API calls already made | No |
| GPU or server time already used | No |
| Storage for generated files | No, it runs until you delete them |
| Partner or creator payouts | No |
Expiry helps on exactly one line of that bill. Credits that lapse unused never turn into API calls, so a stale balance stops being something you might have to serve after 12 months. It does nothing for the 150 credits that were spent.
Google Play is taking a different route
Google's answer for AI apps isn't expiry. On September 29, 2026, it announced Usage-Based Billing on the Android Developers Blog: prepaid metered billing where a user's balance tops up automatically when it falls below a set threshold. Google says it is testing and rolling out its new subscription features, many of them through its Early Access Program.
Refunds on Google Play still follow the usual paths. Most are decided by Google without asking you. The one flow that asks for your evidence is the chargeback review. Google sends a pending refund review notification and you have 24 hours to answer through orders.reviewrefund with a refund preference and purchase usage. For orders placed after August 3, 2026, developers cover the purchase price, less Play's service fee, plus the bank's chargeback fees. On a $9.99 credit pack, an unanswered chargeback costs you more than the sale ever paid you, before you count the compute.
| App Store | Google Play | |
|---|---|---|
| Expiring AI credits | Allowed with Apple's entitlement, 12-month minimum | Not part of Google's Usage-Based Billing announcement |
| Where you answer a refund | CONSUMPTION_REQUEST, through Send Consumption Information | Chargeback review, through orders.reviewrefund |
| Response window | 12 hours | 24 hours |
| Who decides | Apple | Google Play, and the bank for chargebacks |
Should you apply for the entitlement
If your credits pay for model calls, it's probably worth it, as long as you price in the obligations. The balance display, the reminder emails and the oldest-first logic are work you'd want anyway, because they're the same records a clean consumption reply needs. Settle one question before you ship. Can your system say, for any single transaction, exactly how much of it was spent and how much expired? If it can, expiry is a tidy upgrade. If it can't, the first refund request will show you.
Frequently asked questions
- Can in-app purchase credits expire on the App Store?
- Only with Apple's expiring consumables entitlement. App Review Guideline 3.1.1 says credits or in-game currencies bought through in-app purchase may not expire, and the entitlement is limited to consumables that unlock generative AI services, with a minimum expiration term of 12 months unless local law requires otherwise.
- Can customers get a refund on expiring AI credits?
- Yes. A customer can ask Apple to refund any in-app purchase, and Apple decides. When they do, Apple sends your server a CONSUMPTION_REQUEST, and you can reply within 12 hours through Send Consumption Information with how much of that purchase was used.
- Should expired credits count as consumed in a consumption reply?
- No, based on Apple's own definition. Apple describes consumptionPercentage as the portion of the product the customer consumed, and credits that lapsed unused weren't consumed. Apple hasn't published guidance specific to expired balances, so report the credits actually spent from that transaction.
- Can I make my existing credit packs expire?
- No. Apple says expiring consumables must be created as new in-app purchases so App Review can confirm they meet the requirements. Existing products can't be converted or repurposed.
- Does Google Play let AI credits expire?
- Google hasn't announced an equivalent of Apple's entitlement. Its September 29, 2026 announcement introduced Usage-Based Billing, a prepaid metered model where the balance tops up automatically, which Google says it is testing and rolling out.
Sources and further reading
- Apple Developer: Providing expiring consumables for generative AI apps
- Apple Developer: App Review Guidelines (3.1.1)
- Apple Developer: Send Consumption Information
- Apple Developer: consumptionPercentage
- 9to5Mac: Apple launches $50 intelligence usage packs for select AI features (November 9, 2026)
- Android Developers Blog: Driving growth on Google Play, the next era of subscriptions (September 29, 2026)
- Android Developers: Provide refund and chargeback suggestions
- 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.