I'm having problems creating an In-App Purchase. It throws the following Error message: "An error has occurred. Try again later." And inspecting it with the browser dev tools reveals this: { "errors" : [ { "id" : "...", "status" : "409", "code" : "ENTITY_ERROR.IAP_CREATION_NOT_ALLOWED", "title" : "You cannot create new in-app purchase.", "source" : { "pointer" : "/data/id" } } ] } There was a pending agreement, and we have accepted it yesterday, but I am still getting the same error.

Hi, Our application offers 3 non-renewing subscriptions. I have integrated the necessary code, and our App Store Account Paid Agreement status is Active. Transactions are successfully completed in the sandbox environment. However, I am facing difficulties with server-side validation. The /verifyReceipt API is deprecated, and I need an alternative method for server-side validation. The Apple documentation is quite confusing, and I couldn't find any articles related to the new approach for server-side validation. I would greatly appreciate it if you could provide a detailed guide on how to perform server-side validation with the new method. Thank you in advance.

I have yearly auto renew subscription. in ASC I generate a promo code. giving user free subscription. At the end of the year are they [A ] renewed automatically for free so promo code continues? [B ] renewed automatically at the actual subscription price [ C] not renewed so effectively get to choose to start a subscription at the current price [D ] none of the above

I'm having problems creating an in-app purchase apple store connect it got error cannot create while my account is in admin role Error message: "An error has occurred. Try again later." Has anyone had the same problem and solution Thank!

{ "errors" : [ { "id" : "9627df33-29f3-4764-9b77-cc6f1fd14129", "status" : "409", "code" : "ENTITY_ERROR.IAP_CREATION_NOT_ALLOWED", "title" : "You cannot create new in-app purchase.", "source" : { "pointer" : "/data/id" } } ] }

We are a small startup and in process of launching our product. For now we have digital services (user can add and see data as they entered only be subscribed), but later we would have value added services - including hardware ( devices e.g. Glucometer). Current payment workflow we have uses Razorpay as payment gateway. We have two options: We can either make a web page for the payments to be collected via Razorpay. this will have less impact on the code and implementation. (like there's for Netflix and Spotify where they redirect to browser for payment than in-app purchase) We can add the apple payment gateway for the payments. Questions: What would be the charges in both the scenarios ? E.g. If we take 100rs payment from patient then how much would go to apple in scenario 1 and 2. Is there any support for small startups where apple provides some discount with respect to the payments collected ?

Hello, I'm using 'App Store Server Notifications V2'. I have a question about 'CONSUMPTION_REQUEST' notification in 'notificationType'. I was wondering if there would be any impact on refunds if I received this notification and didn't respond. (Always refund etc..)

Hi, I am trying to determine if an in-app purchase will be required within the app we are developing. We provide a web platform where the user can sign in and offer/search services correlated to entertainment world (showman, catering, DJ, live food lesson, etc.). The web app has 2 target: consumer users and business user. Consumer users can search services that tay want and chat business users owner of that services. Business users can create their ownpages in order to be visible to the consumer users in the community. Business users can also access too specified premium features for visibility. We are now designing a mobile app with only few features: Register login section Search business pages The users are the same and there is no differences in the mobile features (no hide premium functionalities). For these small features we have to implement the in-app purchase? The idea is to provide initially a small "companion" app to search business pages. Fo the next releases, where we want to provide more features, premium functionalities for business user we will integrate in-app and we already have plans to implement it. Thanks in advance!

Is it possible - in appstore - to create a subscriptions model similar to what microsoft teams and google workspace has for team memberships? We want to have a subscription price per user per month (or year). Administrator should be able to add additional users (and add a subscription for the new users) - It doesn't seem to be possible - only option is to have prefix subscriptions with 5 users, 10user, 15 users etc. (we've also looked into consumables - but the lack the option to be reoccurring payments) Thanks in advance?

I also still getting the same error from sandbox "x": "Invalid response: Client error: GET https://api.storekit-sandbox.itunes.apple.com/inApps/v1/transactions/2000000632845273 resulted in a 401 Unauthorized response", while for production url "x": "Invalid response: Client error: GET https://api.storekit.itunes.apple.com/inApps/v1/transactions/2000000632845273 resulted in a 404 Not Found response:\n{"errorCode":4040010,"errorMessage":"Transaction id not found."}\n",

My app is currently in review (review completed). I'm using the Get Transaction info API with a sandbox purchase transaction ID. "x": "Invalid response: Client error: GET https://api.storekit-sandbox.itunes.apple.com/inApps/v1/transactions/2000000632750685 resulted in a 401 Unauthorized response", However, when using the production url "Invalid response: Client error: GET https://api.storekit.itunes.apple.com/inApps/v1/transactions/2000000632750685 resulted in a 404 Not Found response:\n{"errorCode":4040010,"errorMessage":"Transaction id not found."}\n", Should I generate my JWT differently for sandbox vs production? If not, what else could cause this issue? Is there any missing congigration?

Hello everyone! By the guidelines we have to use IAP because actual service happens in the application itself: it is an app for scheduling actions. The business problem is that IAP does not allow the refund functionality which is important in-app in case the actual scheduled action will not happen. Is there a way to use Stripe still exactly cos we need to implement refunds in the app?

Hello, I am encountering an issue where I receive an App Store Server Notification V2 upon the purchase of a consumable item. I have configured the App Store Server Notification V2 endpoint to handle notifications related to subscription products. However, I did not expect to receive notifications for consumable purchases. The notification includes the following signedPayload decoded into the ResponseBodyV2DecodedPayload object with the following values: notificationUUID: 3cd6410b-0c89-4247-aba5-20710e79895e notificationType: null subtype: null The transaction information decoded from the ResponseBodyV2DecodedPayload object is as follows: transactionId: 2000000633622618 webOrderLineItemId: null productId: heart_2 To debug, I called the Get Notification History API of the App Store Server API, and the mentioned notification for the consumable product purchase is not included in the history. Only notifications related to subscription product purchases are retrieved. According to the notification type documentation, there is no explanation for cases where both notificationType and subtype are null, nor is there any mention of receiving notifications for consumable purchases. Therefore, I am uncertain how to interpret and handle this notification. Could you please provide an explanation or guidance on this issue? Thank you. References: https://developer.apple.com/forums/thread/737592 https://developer.apple.com/documentation/appstoreservernotifications/notificationtype

Hello, I studied this and this documents and I find certain contradiction with this discussion. Could you help me out, please? I set up my subscriptions this way: , where Pro (annual or monthly) offers most of the features and Mobile Pro (annual or montly) least of the features. Do I get it right, that: Upgrading: to annual: What happens here? to monthly: [link] The customer’s prorated payment from lower level subscription is refunded to the original payment method. They’re charged for the higher level subscription, which goes into effect immediately. Downgrading: both annual and monthly: [link] They’re charged for the lower level subscription on their next renewal date. They continue using their current subscription until then. Crossgrading: to annual: What happens here? to monthly: [link] ...the crossgrade goes into effect on the customer’s next renewal date. They continue using their current subscription until then. Thanks.

Hi all, Our app has been rejected several times without any clear explanation of what we need to do. The latest rejection reason is as follows: Guidelines 3.1.1 - In-App Purchase and 3.1.3(c) - Enterprise Services We noticed in our review that your app offers enterprise services that are sold directly to organizations or groups of employees or students. However, these same services are also available to be sold to single users, consumers, or for family use without using in-app purchase. When an organization or group buys access to your app's enterprise services, you don't need to use in-app purchase. But when providing access to an individual user, consumer, or for family use, you should use in-app purchase. To which we responded with: We would also like to clarify our app and business model: 1) Our app is a free app intended for companies, organizations, and business owners. Individual users can sign up for our app, but with some restrictions. We designed it this way so that users can try our app before registering their company or business. 2) In the previous app version, we enabled users to subscribe and unlock more features within our app using our own mechanism. Hence, the review referred to Guidelines 3.1.1. In this version, we have removed the feature so that users cannot purchase any subscriptions. Since users cannot purchase anything from our app, we believe Guidelines 3.1.1 should no longer apply for the app review. But our app is still not approved. Instead, they replied with: We are not able to provide feedback on app concepts or features, but we recommend evaluating your suggestions against the App Review Guidelines, as well as the Apple Developer Program License Agreement, and the Human Interface Guidelines. Can anyone enlighten us why does the reviewer still referring to Guidelines 3.1.1 when there isn't anything that user can purchase from our app? And what do they actually want us to do?

Attempts to purchase an SKProduct or restore all completed transactions via the usual method calls in StoreKit leads to failure in the beta environment with the following error: Error Domain=SKErrorDomain Code=0 "An unknown error occurred" UserInfo={NSLocalizedDescription=An unknown error occurred, NSUnderlyingError=0x300b10210 {Error Domain=ASDErrorDomain Code=500 "(null)" UserInfo={NSUnderlyingError=0x300b10090 {Error Domain=AMSErrorDomain Code=301 "Invalid Status Code" UserInfo={NSLocalizedDescription=Invalid Status Code, AMSURL=https://sandbox.itunes.apple.com/WebObjects/MZBuy.woa/wa/inAppBuy?REDACTED, AMSStatusCode=500, NSLocalizedFailureReason=The response has an invalid status code}}}}} We've tried with existing sandbox user accounts, and created fresh ones which also fail in a similar way. Our beta testers report the same thing. Nothing has changed in our IAP code, and this started happening about 24-48 hours ago. It seems to be a server-side error - please can someone verify on Apple's side?

Before I launched my app, I ran a TestFlight beta program and also included a one time purchase in the TestFlight build to test the functionality. Now that the app is available in the App Store, I had closed the TestFlight program, but am looking to reopen it again to test iOS 18 specific features. The issue is, the beta testers that previously purchased the IAP on TestFlight but didn't actually purchase the IAP on the App Store version would be able to use the paid features of the app for free as long as they have the TestFlight build. Therefore I would like to revoke all the purchases made via the TestFlight build. Is there any way to do that?

Hi, I am new to StoreKit and IAP. I am developing the 1.0 version of my app, and I plan to offer non-consumable items in version 1.0, with plans to offer auto-renewable subscriptions in the future 2.0 version. According to the App Store's review requirements, when I add a new type of item in the app, I need to submit the app version for review as well. What I want to know is, after I add auto-renewable subscription items in App Store Connect for use in version 2.0, will these new items be returned when my 1.0 version queries product information through the StoreKit interface? If they are returned, since version 1.0 does not support auto-renewable subscriptions, do I need to add compatibility code to ignore the unsupported items? Ideally, according to the App Store's requirement to submit a new app version along with the type of products, StoreKit would help filter out product types that are not supported by older app versions, but I wonder if this is the case?

Hi all. Our application uses server-side validation of user subscriptions. After purchasing a subscription, the server keeps track of the subscription renewal statuses. But for the second week already, when requesting information on subscriptions, the server receives 403 Forbidden error. At first we decided that our ip was blocked somewhere and tried to change the ip to a new one. But changing the ip address did not give any results. We keep getting 403 Forbidden error on all requests to check subscriptions from our server. The request goes to the following address /verifyReceipt This method is deprecated and it is necessary to change the method of verification to a new one, but it can't be done quickly. At the moment, there is no information when verifyReceipt will be disabled. And we need to verify subscriptions. Maybe someone has encountered a similar problem? Thanks for the help!

I'm using the App Store Server API's Get Transaction History. If you specify DESCENDING for the sort parameter, receipts will be sorted in chronological order when verified in a sandbox environment, but in a commercial environment they will be in random order. Is there anyone stuck with a similar problem?