App Store Connect displays the In-App Purchases and Subscriptions section on your app's version page when your app has an In-App Purchase or subscription with a Ready to Submit status. To locate the In-App Purchases and Subscriptions section: In Apps, select the app you want to view. In the sidebar, select the app version. On the version page, scroll down to the In-App Purchases and Subscriptions section. For more information, see Submit an In-App Purchase.

General: Forums topic: StoreKit Forums tag: In-App Purchase App Store Pathway Simple and safe In-App Purchases Auto-renewable subscriptions In-App Purchase documentation Getting started with In-App Purchase using StoreKit views documentation Supporting business model changes by using the app transaction documentation Testing at all stages of development with Xcode and the sandbox documentation App Store Server Notifications documentation App Store Server API documentation Simplifying your implementation by using the App Store Server Library documentation TN3185: Troubleshooting In-App Purchases availability in Xcode technote TN3186: Troubleshooting In-App Purchases availability in the sandbox technote TN3188: Troubleshooting In-App Purchases availability in the App Store technote Understanding StoreKit workflows sample code Implementing a store in your app using the StoreKit API sample code What’s new in StoreKit and In-App Purchase video

Hello, I'm the developer of FOS Social (Apple ID: 6755471015), a creator-membership marketplace currently in TestFlight. I've submitted the Advanced Commerce API access request form twice and have not received any response, confirmation, or status update. My most recent submission has Request ID: UVQ7FUZVV3. Our use case: FOS Social is a social platform where viewers subscribe to individual content creators through independent auto-renewable monthly subscriptions across three tiers ($10 / $17 / $29). A single viewer must be able to hold concurrent active subscriptions to multiple creators at the same tier — for example, subscribed to Creator A at Gold and Creator B at Gold simultaneously. This matches Apple's stated eligibility model for the Advanced Commerce API: "exceptionally large catalogs of subscription content — apps that include frequently added content from multiple creators, where each creator's offering is merchandised as a single auto-renewable subscription." Why standard StoreKit doesn't work for us: We currently reuse one product ID per tier across all creators (e.g. com.fosssocial.creator.gold.monthly). When a viewer already subscribed to one creator at Gold tries to subscribe to a second creator at Gold, StoreKit returns "already subscribed" and treats it as a renewal rather than a new independent subscription. Pre-creating a separate subscription group per creator in App Store Connect is not feasible since our creator base is dynamic and growing. My questions: Is there any way to check the status of an Advanced Commerce API access request, or a typical response timeframe we should expect? Is there anything that commonly causes these requests to go unanswered (e.g. submission not made by the Account Holder, app still in TestFlight, missing information)? Is there a recommended escalation path when the request form has been submitted multiple times with no reply? I've also opened a support case (Case ID: 102934491974) but wanted to ask here as well in case anyone from the community or Apple has guidance. Thank you!

Hi, We received App Review feedback under Guideline 3.1.1 for our in-app purchases, and we’d appreciate guidance on the expected next step. What we submitted; We created and completed metadata for the new consumable IAPs (pricing, availability, review screenshots, localizations). We uploaded and submitted app version 1.8 with a recent binary (build processed/VALID in App Store Connect). We also submitted the consumable IAPs for review. Outcome: App version 1.8 was approved (currently Pending Developer Release). The consumable IAPs were returned with Developer Action Needed. Our confusion We already uploaded/submitted a new binary (1.8) for this release, and the consumable purchase flows are implemented in that binary (Store / offers). The app binary itself was approved, but the consumable IAPs were rejected with a request for another new binary. For a first-time expansion from Non-Consumable-only to Consumables, is a separate / subsequent binary submission always required even if the approved version already contains the purchase UI?

I have a non-consumable in-app purchase that is Approved and visible on my app's public App Store product page, but on-device StoreKit returns no product for its identifier — for 5+ days now. App: Élec NF C 15-100 — Apple ID 6784323130 — bundle com.comptoirstudio.elec Product ID: elec_pro_avie (non-consumable, 9.99 EUR) What is confirmed correct: IAP status: Approved, Cleared for Sale in all territories Paid Applications Agreement: Active; Banking and Tax forms: complete, nothing pending The IAP appears in the "In-App Purchases" section of my live App Store listing The App Store Server API returns the product correctly (verified via RevenueCat) An In-App Purchase Key (.p8) is configured The failure: On-device SKProductsRequest (StoreKit 1) and Product.products(for:) (StoreKit 2) both return an empty product list for elec_pro_avie Reproduced in production (live v1.1.0/1.2.0) and TestFlight/sandbox Reproduced on multiple devices and Apple IDs (FR and US) Product identifier matches exactly; bundle ID matches This looks like a StoreKit product-catalog sync issue on Apple's side: server-side everything resolves, but the device-facing catalog never serves the product. Could an Apple engineer force a re-sync of this product, or advise what else could block on-device delivery? A TSI/ticket (submitted last Friday) has had no response yet. Thank you.

Hello, we are preparing an app that sells digital subscriptions consumed within the app and we fully understand that Guideline 3.1.1 requires such content to be sold through In-App Purchase. Our question concerns one specific case: In-App Purchase does not appear to be available for App Store accounts in the Russia region. For users in that region, what is the compliant way to offer a digital subscription? Would using an approved local third-party payment provider be acceptable when IAP is not available and if so, are there any conditions or entitlements we should be aware of? For all other regions where IAP is available, we plan to use In-App Purchase as required. Thank you! Kind regards

Hello everyone I'm testing promotional offers on for my app. I've setup a product with a promotional offer for it. I've also have our backend developer setup signature generating. However when I tried to purchase the offer from my app, I'm getting the error: `Error Domain=SKErrorDomain Code=0 "An unknown error occurred" UserInfo={NSLocalizedDescription=An unknown error occurred, NSUnderlyingError=0x149a7c330 {Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={NSUnderlyingError=0x149a7cba0 {Error Domain=AMSErrorDomain Code=305 "(null)"}}}} ` Also during the purchase process, I noticed the Xcode console printed out this: <SKPaymentQueue: 0x10d3fc210>: Payment completed with error: Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={client-environment-type=Sandbox, storefront-country-code=VNM, NSUnderlyingError=0x149a7d320 {Error Domain=AMSErrorDomain Code=305 "Purchase Failed Server canceled the purchase" UserInfo={AMSURL=https://sandbox.itunes.apple.com/WebObjects/MZBuy.woa/wa/inAppBuy?guid=00008110-0001549C36BA401E, AMSDescription=Purchase Failed, NSDebugDescription=Purchase Failed Server canceled the purchase, AMSServerCorrelationKey=3Y44VA33BIC5CZCH5I7WLTQ5DA, AMSStatusCode=200, AMSServerPayload={ "cancel-purchase-batch" = 1; customerMessage = "Unable to process your request."; dialog = { defaultButton = ok; explanation = "Please try again later.\n\n[Environment: Sandbox]"; initialCheckboxValue = 1; "m-allowed" = 0; message = "Unable to process your request."; okButtonString = OK; }; failureType = ""; "m-allowed" = 0; metrics = { actionUrl = "sandbox.itunes.apple.com/WebObjects/MZBuy.woa/wa/inAppBuy"; asnState = 0; dialogId = "MZCommerce.SystemError"; eventType = dialog; message = "Unable to process your re"; mtEventTime = "2026-07-15 06:14:16 Etc/GMT"; mtTopic = "xp_ase_payments/appstore_payments_ue"; options = ( OK ); }; pings = ( ); }, AMSFailureReason=Server canceled the purchase}}} Could someone please help me figure out what the problem is? Thanks in advance!.

Hello, I need to set up the Paid Apps agreement in App Store Connect (to offer in-app purchases), but I don't see any button or link to request it. In App Store Connect under Business (Agreements, Tax, and Banking) I only see the Free Apps agreement as Active. There is no "View and Agree to Terms" banner and no option to add or activate the Paid Apps agreement anywhere. What I already checked: I'm signed in as the Account Holder (not Admin or another role). The Apple Developer Program membership is active and paid. I tried both the new "Business" section and the old "Agreements, Tax, and Banking" page — no Paid Apps row, no request button. Tried different browsers and clearing cache, same result. Questions: What conditions must be met for the Paid Apps agreement option to appear for an account? Is there a known delay or eligibility/verification step (e.g., for individual accounts or specific regions) before it shows up? Is contacting Apple Developer Support the only way to resolve this, or is there something I can do myself in the account? Thanks in advance for any pointers.

Hi, I was creating an iOS app for my country Ethiopia that has in app purchase to unlock app features. The apple policy says for such payment, we must use Apple IAP but not external payment methods such as stripe or local. However, in my country, Ethiopia, Apple IAP is not available. My question is can I use local payment methods or guide users on how to pay using available payment methods in the country where Apple IAP is not available? I need to make sure my app is acceptable during review using local payment method just because Apple IAP is not available in my country. Thank you

We're seeing differences in the purchase dialog and overall presentation when testing with Sandbox accounts compared to commercially available apps. Are these UI differences are expected and are simply a characteristic of the Sandbox testing environment, or if there are any configuration requirements that affect the purchase sheet appearance? It would be helpful to know whether developers should expect the production purchase UI to match App Store apps once the app is distributed through TestFlight/App Store, or if there are additional factors involved. Sandbox UI Expected UI

My app Side A (Bundle ID: com.sighta.sidea, Apple ID: 6784347458) was approved and released on June 25, 2026. All 4 In-App Purchases have status "Approved" in App Store Connect, but they are not purchasable in the live app. Symptoms: Product.products(for:) returns an empty array in production (StoreKit 2) Console.app / storekitd logs confirm the request reaches Apple's servers but returns 0 products The App Store product page shows no "In-App Purchases" section "Submit for Review" button for the IAPs is grayed out in App Store Connect IAP Product IDs: com.sighta.sidea.pro (Non-Consumable) com.sighta.sidea.tip.small (Consumable) com.sighta.sidea.tip.medium (Consumable) com.sighta.sidea.tip.large (Consumable) What I've tried: Verified all IAP metadata is complete in App Store Connect Tested on multiple devices (iPhone 16, iPhone 17, iOS 26.5) Deleted and reinstalled the app Added retry logic (3 attempts, 3s delay) — no change Opened a Developer Support ticket 2+ weeks ago, no resolution This is a production bug affecting all users — nobody can purchase Pro or leave a tip. Has anyone seen this resolved? Is there a known backend propagation issue? Open ticket: 102927941095

Hi App Review team, I'm posting here as a last resort after7 weeks with no movement and 4 unanswered support requests. I'm about to lose my launch window next week and I need someone at Apple to look at this. The situation: App: BMH Themes — App ID 6763770421 — Bundle ID com.bringmedinahome.bmhthemes Version 1.0 (Build 24): reviewed and APPROVED, currently "Ready for Distribution". In-app purchases: 904 are APPROVED, but 1,134 have been stuck in "Waiting for Review" for 7 weeks. The 1,134 stuck items are the exact same type as the 904 already approved — so this is clearly not a content issue. None of the 1,134 show any rejection or "Developer Action Needed" message. Nothing is pending on my side. I have submitted 4 support requests over the past weeks. None received a substantive response. Why this is urgent: My company is now legally registered, my VAT number is being issued, my business bank account is active, and my full marketing campaign is finalized for a launch next week. I cannot launch with 1,134 of my products frozen — releasing a half-empty catalog would waste the entire launch. These stuck in-app purchases are the ONLY remaining blocker. My request: Could someone please check whether these 1,134 in-app purchases are correctly queued, confirm whether there is an internal processing issue, and escalate to the App Review / in-app purchase team? The app is already approved — only these items are stuck. Thank you very much for any help.

"关于一次性兑换码我有一些疑问，希望大家能帮我解答，谢谢 我的构建版本目前的状态是【等待开发者发布】，现在的状态是不可以申请一次性兑换码的，需要是可分发状态，我想问一下这个可分发状态是属于那个阶段？ 是我点了发布之后就是可分发吗，可分发是否就是上线了？如果我点定时发布是不是也是进入到可分发阶段？如果我设定预下载是不是就可以申请一次性兑换码了？ 还是说我进行一些其他操作就可以申请正式的一次性兑换码了"

Our sandbox accounts don't work now. We are testing our IAP product now, so we needed our sandbox accounts to be logged in, for purchaise test. Settings -> Developer -> Sandbox Apple Account screen - > log in : Not working Logged out status -> test app -> purchasing IAP product : Not working our 4 members of dev team have same problem now.

My Non-Consumable IAP was rejected with Guideline 3.1.1 and now has status ‘Developer Action Required’. The problem: On the version page in App Store Connect, the ‘In-App Purchases and Subscriptions’ section does not appear at the bottom. I cannot link the IAP to a new version submission. Every time I submit a new binary, Apple approves the app version but rejects the IAP afterward — even though I have no way to attach it to the version in the first place. This seems to be a circular issue: the IAP doesn’t appear on the version page because of its current status, but the only way to fix the status is to submit it with a new version. Has anyone experienced this and found a solution? Any help appreciated!​​​​​​​​​​​​​​​​

Hi everyone, I’m currently stuck with a blocking issue in App Store Connect and would really appreciate any guidance or insight. Issue: My app version (iOS App 1.0) is missing the “In-App Purchases and Subscriptions” section entirely. Because of this, I cannot attach my subscriptions to the version, which is preventing me from submitting the app for review. Additionally, I also do not have the option to create a new version, so I can’t work around the issue by moving to 1.0.1. What happened before this: I uploaded a build (Build 24) Submitted the app for review Then removed the submission After that, the IAP section disappeared completely Since then, I cannot attach subscriptions or create a new version Current state: Subscriptions are created and show “Waiting for Review” New Build is attached to Version 1.0 All metadata and screenshots are complete “In-App Purchases and Subscriptions” section is missing “Add Version” option is not available What I’ve tried: Removing and re-adding the build Waiting for UI refresh/processing Contacting Apple Developer Support (case has been escalated for 6 days with no response) Impact: This is currently blocking my app launch because I would be rejected since the subscriptions are not linked, as I cannot submit my first subscription with the app. Questions: Has anyone experienced a missing IAP section after removing a submission? Is there any way to force reset the app version state from the developer side? Is this a known App Store Connect issue? Any help or suggestions would be greatly appreciated. Thanks in advance.

I have been rejected twice under Guideline 2.1(b) because my In-App Purchase subscriptions are not submitted for review. I cannot figure out how to attach them to my submission. Here is my situation: I have 6 auto-renewable subscriptions fully configured in App Store Connect under "Barrel Pro Subscriptions" — all have screenshots, pricing, descriptions, and review notes My app is iOS only, built with React Native/Expo My current version is 1.1, Build 10 (1.1.0) The problem: The "In-App Purchases and Subscriptions" section does not appear anywhere on my version page. I have scrolled to the very bottom and it is not there. I cannot find any way to attach my subscriptions to my submission before clicking "Submit for Review." The blue info box on the Subscriptions page says: "Your first subscription must be submitted with a new app version. Select it from the app's In-App Purchases and Subscriptions section on the version page." But that section does not exist on my version page. What I have tried: Cancelling the rejected submission and starting fresh Creating a new version (1.1) manually Uploading a new build (Build 10) Checking both "In-App Purchases" and "Subscriptions" sections in the sidebar Has Apple removed this section from the version page? How do I attach my subscriptions to my submission in 2026? Any help is greatly appreciated. Thank you.

I work with bloggers who write reviews about my app. I would like to track sales that originate on specific sites so I can pay them commissions, like an affiliate program. For example, if a person discovers our app by reading a review, I would like to give the blogger a URL to the App Store a UTM code so that I can track if the article generates sales of my app. if there is a 3rd party affiliate program management platform or software to do this, I might be open to using it. i’ve tried searching the web and other developers about this. It should be simple but it’s elusive if it’s out there at all.

I have a macOS app submission that Apple rejected because of the subscription view. The reason given is: One or more auto-renewable subscriptions are marketed in the purchase flow in a way that may mislead or confuse users about the subscription terms or pricing. Specifically: The auto-renewable subscription promotes the free trial, introductory pricing, or introductory period for the subscription more clearly and conspicuously than the billed amount. The rejection pointed to Apple's HIG for In-App Purchases and an the article Auto-renewable subscriptions. The image below shows two exemplars from Apple's HIG and our subscription view (using Apple's SubscriptionStoreView). I am having troubles squaring the reason for our rejection with Apple's own HIG examples. Does anyone know of a difference between our view and Apple's examples that would prompt the rejection? The only thing I can think of is to remove the "Try It Free " by changing the modifier from .subscriptionStoreButtonLabel(.multiline) to .subscriptionStoreButtonLabel(.price) (Meanwhile, Apple's rejection because of the subscription content seems to have broken my ability to sync the StoreKit content in AppStoreConnect with Xcode(?). I am still trying to resolve problem too.)

Hi, I'm trying to hook up some test in app purchases to test purchase code between our app and our app's backend. When I try to load products (requestProductData) with my Sandbox account, my product identifiers come back in the invalid product identifiers member of the response. My product says it's in "waiting for review" status in app store connect, and I'm logged in to the app store with my sandbox account on my device. We just accepted the paid apps agreement as well--is there some propagation time to that? The product ID I'm using (both in app store connect and in-app) is test_durable. Do I need to append the package name to that or something? I've dug through the docs and through the forums here and come up empty. I tried using the Xcode storekit test harness and the issue there is that because that doesn't actually talk to the store apis, I can't use that to test my backend correctly validating/processing the transactions. Thanks!