Dear Apple Support Team, Hello! I am currently developing the in-app subscription functionality using Apple IAP API and have encountered a serious technical issue while processing subscription data. I would like to report this issue to you. Issue Description: When calling the subscription API endpoint, the same OriginalTransactionId returns inconsistent results. Specifically, a particular transaction ID (let's call it TransactionId_A) should belong to the subscription order with OriginalTransactionId_A, but it is currently incorrectly associated with OriginalTransactionId_B. This issue severely affects our ability to accurately manage and process subscription data. Here are the relevant log details for your reference: API Endpoint Requested: https://api.storekit.itunes.apple.com/inApps/v1/subscriptions/{TransactionId_A} (Note: The link is a placeholder for the actual API endpoint.) Log Information on February 21, 2025, at 09:40:09: { "AppAccountToken": "{AppAccountToken}", "BundleId": "{BundleId}", "Currency": "CNY", "Environment": "Production", "ExpiresDate": {ExpiresDate}, "InAppOwnershipType": "PURCHASED", "IsUpgraded": false, "OfferDiscountType": "", "OfferIdentifier": "", "OfferType": 0, "OriginalPurchaseDate": {OriginalPurchaseDate}, "OriginalTransactionId": "{OriginalTransactionId_A}", "Price": {Price}, "ProductId": "{ProductId}", "PurchaseDate": {PurchaseDate}, "Quantity": 1, "RevocationDate": 0, "RevocationReason": 0, "SignedDate": {SignedDate}, "Storefront": "CHN", "StorefrontId": {StorefrontId}, "SubscriptionGroupIdentifier": "{SubscriptionGroupIdentifier}", "TransactionId": "{TransactionId_A}", "TransactionReason": "PURCHASE", "Type": "Auto-Renewable Subscription", "WebOrderLineItemId": "{WebOrderLineItemId}" } Log Information on March 21, 2025, at 09:38:49: { "AppAccountToken": "{AppAccountToken}", "BundleId": "{BundleId}", "Currency": "CNY", "Environment": "Production", "ExpiresDate": {ExpiresDate}, "InAppOwnershipType": "PURCHASED", "IsUpgraded": false, "OfferDiscountType": "", "OfferIdentifier": "", "OfferType": 0, "OriginalPurchaseDate": {OriginalPurchaseDate}, "OriginalTransactionId": "{OriginalTransactionId_B}", "Price": {Price}, "ProductId": "{ProductId}", "PurchaseDate": {PurchaseDate}, "Quantity": 1, "RevocationDate": 0, "RevocationReason": 0, "SignedDate": {SignedDate}, "Storefront": "CHN", "StorefrontId": {StorefrontId}, "SubscriptionGroupIdentifier": "{SubscriptionGroupIdentifier}", "TransactionId": "{TransactionId_A}", "TransactionReason": "PURCHASE", "Type": "Auto-Renewable Subscription", "WebOrderLineItemId": "{WebOrderLineItemId}" } From the above logs, it is evident that the same transaction (TransactionId_A) returns different OriginalTransactionId values at different times, which is clearly not expected and severely impacts our ability to correctly process and manage subscription data. I hope you can address and investigate this issue as soon as possible. If you need any further information or assistance, please feel free to contact me. Thank you for your support! Best regards!

For Apple subscription payments, my server does not receive notifications for production environment payments, but it can receive notifications for sandbox payments at the same notification address.

Hello Apple Developers, I’m reaching out to the community with a concept that I truly believe could be a natural fit for the Apple ecosystem: A privacy-focused, iOS-exclusive dating app designed to enhance connections between Apple users while staying true to Apple’s commitment to security and user privacy. The idea is to create an iOS-only dating platform that fosters relationships between users who are part of the Apple ecosystem. The app would integrate seamlessly with Apple’s services (iMessage, FaceTime, Siri, etc.) and provide a premium user experience, where privacy is a priority. Apple users already prefer to communicate using Apple services (iMessage, FaceTime). A dating app designed specifically for iOS users would deepen this ecosystem lock-in, making it easier for Apple customers to connect within a trusted space. Apple is already known for its privacy focus, and an iOS-exclusive dating app would build upon that reputation. It would ensure secure, private interactions, minimizing the risks associated with data sharing in most dating apps today. The app could integrate directly with features like iCloud, Apple Pay (for date-night bookings), and Siri (for matchmaking suggestions), offering users a truly native iOS experience. While the app would remain free to use, here are a few potential monetization methods: Bundling with Apple One/iCloud+ for premium matchmaking features. Apple Pay-based date-night deals with local partners. I’d love to hear your thoughts on whether Apple might be open to this idea. Would there be any challenges from a technical or business perspective in creating a dating app exclusively for iOS users? I’m looking forward to hearing from you all, and thank you for your time and insights. Yours Truly, CapNKirk P.S. This is an idea. But I do not care who uses, implements, or executes this idea. I just want to see Apple take advantage of it.

We set up monthly subscription with a 1-month free trial. We tested it with Sandbox and TestFlight, and the subscription worked as expected. The app is now available on Apple Store, but the monthly subscription is changed to One-Time Charge on Apple Store. When we try to download our app, it asks One-Time Charge with the cost of the subscription fee before downloading the app. However, in our testing, the app was able to be installed without this One-Time Charge, and both free trial and subscription worked well. Does anyone have had the similar issue before? How would you suggest the fixing? Thanks in advance!

Sorry but I'm not good at English. Is the originalTransactionId received for the same subscription by the same user the same in Store Kit v1 and Store Kit 2? Also, will the originalTransactionId be the same even if the subscription price is changed?

Hi, I am experiencing an issue with in-app subscriptions in my React Native application known-singles, using the react-native-iap library. When a user subscribes to a plan, the transaction executes successfully, and a receipt is returned. However, the transaction remains in a pending state indefinitely and does not update. Additionally, the transaction amount is not deposited into my bank account, even though all banking details are correctly set up in App Store Connect. We have thoroughly debugged the issue on our end but could not identify the cause. TestFlight transactions complete successfully, but real purchases remain stuck in pending status. Here are the relevant details of our implementation: React Native version: 0.60.4 react-native-iap version: 4.2.2 Could you please assist in resolving this issue? Any guidance on why transactions are not being completed and why payouts are not being processed would be greatly appreciated. Looking forward to your support.

I think it can be dismissed with dismiss() onInAppPurchaseCompletion action handler but I have no reason to handle it, and if it's not handled it will show error alerts for you (see documentation). How can I dismiss it and still benefit from default onInAppPurchaseCompletion action? Thanks,

Mid January our active subscriptions of our app went to 0 from one day to the other. We have both yearly and monthly subscriptions and hence it should not be 0. we can also see active subscriptions in our user database. anyone else facing this issue? There was another thread from august 2023 that had the same issue but no solution has been posted.

Hi, I have an app where user can select an amount within range 20$ - 2500$ and purchase tokens worth that amount, so if he pays 520$ he gets 520 tokens. They can then use these tokens to unlock content within the app. As far as I've seen, in-app purchase doesn't allow custom price set by user. So does this mean we can use third-party payment services? If no, how can we achieve this using in-app purchase. Thank you.

I am using the standard SwiftUI component for subscription management, and on one device it is showing the user as unsubscribed when their sub is still in service. The subscribe button is active but inert, doesn't do anything. Ideas?

I have auto-renewable subscriptions, and in Xcode everything works fine. It shows a list of subscriptions where I can make a test purchase. But when I send it for review, the review team, as well as TestFlight, simply do not have subscriptions. If the problem was in the code, it would not work in the sandbox as I think. But I think that I configured everything correctly in the subscription settings. The only thing: it shows there for the subscription in appstoreconnect that it is preparing for review, but nothing can be done about it, because it will be solved with the first release of the application. But I do not know where else to look and what to do. The problem is probably not in the code, but I also redirected the subscription config in appstoreconnect a bunch of times. I asked help on review team, no way. Tried to google and chat GPT, no ideas where to find a solution.

Hi, I have a problem with StoreKit regarding in-app subscription purchases. When I upload the app to TestFlight and during the review process, it doesn’t work on a real device. However, it works fine on the simulator. I get the error: "Subscription unavailable" (see image). Does anyone know what might be causing this and how to fix it? Please help!

Hi, I launched and released my app in the App Store after first App build is approved. But its subscriptions are still in the status of Pending Binary Approval. So currently in my App subscription is empty. Is this normal to wail a bit? or should i do something asap. It's very strange for users to see no subscription options in a launched App I think.

We are distributing an application using in-app-purchase with subscription. In order to expand customer support and more optimally timed marketing activities, We want to retrieve the billing status and number of billing users managed on the Apple side and regularly verify that the data we are aware of on the server side is up-to-date. Currently, the App Store Server API provides a way to retrieve status using individual original_transaction_id, but there seems to be no official way to retrieve original_transaction_id for a specific period at once. The same was also true for App Store Server Notifications. Is there a way to specify a period of time, the Apple ID of an app, etc., and obtain the original_transaction_id or transaction_id for a specific period of time?

Hi, I want to offer an auto-renewable subscription (e.g., $1/month) that grants users (10 document analyses per month), with the count resetting at the start of each billing cycle. -Unused analyses will not roll over to the next month- Additionally, any analyses generated while the subscription is active will remain accessible to the user permanently, even if they cancel the subscription. The paywall, app description, and metadata will clearly state that the subscription grants (10 document analyses per month with no rollover) We want this to be implemented as an auto-renewable subscription model, not as a consumable service or a token/credit system (which we want to avoid). Is this model acceptable under Apple’s guidelines, or would it be considered a token/credit system? Any insights or alternative suggestions would be appreciated.. Thanks

Apple rejected in-app purchases & subscriptions due to App Store Localization being rejected. But they didn't provide any reason why they rejected localization. The product status is Developer Action Needed & under details, App Store Localization is rejected. I already tried to edit the description and submit it again, but I am getting the same rejection. The product name & display name are also the same. If anyone knows the reason or resolution to fix this localization issue, then let me know.

Hello everyone, I’m having trouble with our app’s subscription setup during App Store review, and I’m hoping to get some guidance. Our app, offers an auto‑renewable subscription. In App Store Connect, we created the subscription as an “Auto‑Renewable Subscription” with a product identifier. We do not offer consumable or non‑consumable in‑app purchases—only this subscription. However, Apple recently rejected our submission with the following message: “We have started the review of your app, but we are not able to continue because we cannot locate the in‑app purchases within your app at this time. Next Steps To help us proceed with the review of your app, please reply to this message providing the steps for locating the in‑app purchases in your app. Note that in‑app purchases are reviewed in an Apple‑provided sandbox environment. Make sure they have been appropriately configured for review in the Apple‑provided sandbox environment. If you are restricting access to in‑app purchases based on factors such as storefront or device configurations, please include this information in your reply along with steps to enable the in‑app purchases for our review.” I’m confused for a couple of reasons: 1. We only offer subscriptions—there are no consumable or non‑consumable products. Yet, Apple’s message refers to “in‑app purchases.” 2. It seems our subscription product is not being found in the sandbox environment. Our subscription is currently in “Waiting for Review” status in App Store Connect, so when using StoreKit 2 (via Product.products([…])) the array returns empty. 3. I’m not sure if we need to enable something else in App Store Connect for subscriptions to be testable in the sandbox, or if our configuration is insufficient for review. Has anyone encountered a similar situation? What are the steps you took to ensure your auto‑renewable subscription were testable for App Store review? Any tips on dealing with this loop—where the subscription must be approved for reviewers to find it, yet Apple won’t approve the app until they can test it? Thanks in advance for any insights or suggestions!

I am experiencing difficulties including subscriptions for the first time in a new binary version. The subscriptions are currently in “Developer Action Needed” status, and I am unable to reset them to “Ready to Submit”. I assume this is why the “Select In-App Purchases and Subscriptions” option is missing from the binary version page. Since subscriptions are a vital part of the app, their absence has led to the app being rejected in the review process. Any advice on how to proceed?

We had a work card attached to our developer's account. team ID 924RUYJZ34 dev ID 8771bf7b-31a9-4602-baae-02580fe5b6c4 Funds are debited from this card in other services, there are no problems with it, the amount in the account is sufficient. Our membership subscription did not renew automatically. The applications are blocked. We can't renew our subscription, there's no Renew button anywhere. There is no way to extend it on any device, web version, or anywhere else. We can't even cancel and re-arrange it, all the functions don't work. Please help us, how can we renew our subscription?!

Hello is there a way to only allow credit card that is from a certain country to access in-app subscription in my app? Lets say I will only allow credit card from Singapore. I don't think its possible with In-App purchase but my colleague wanted to know and I just wanted to double check here.