Hi,
This question is for those developers who have their app as both an iOS and web app and the question is about handling scenarios where an existing web user is modifying his/her subscription through the iOS app.
Here's the scenario:
The user originally signed up through the web app. He then wants to add additional subscription licenses through the iOS app.
We process subscription payments through Stripe so when the user originally signed up for his subscription, we created and processed his subscription payment through Stripe.
Now, he logs into the iOS app and adds two more subscription licenses.
From a user experience stand-point, it would make sense to process this change through Stripe so that the user doesn't end up with two separate items in his credit card statement. And even the charges in his statement may appear differently and may be hard for him to identify them. In this scenario, our concern is unintentionally violating our agreement with Apple because it looks as if we're trying to avoid paying Apple its commissions.
What's the proper way to handle this scenario?
The opposite scenario is also interesting where the original subscription is done through the iOS app and we handle the payment through Apple and then the user adds more licenses to his subscription through the web app. Again from a user experience stand point, we'd have to stick with Apple to handle additional fees.
I just want to understand the proper way to handle these scenarios so that we don't end up creating issues with Apple.
Thanks,
Sam
This question is for those developers who have their app as both an iOS and web app and the question is about handling scenarios where an existing web user is modifying his/her subscription through the iOS app.
Here's the scenario:
The user originally signed up through the web app. He then wants to add additional subscription licenses through the iOS app.
We process subscription payments through Stripe so when the user originally signed up for his subscription, we created and processed his subscription payment through Stripe.
Now, he logs into the iOS app and adds two more subscription licenses.
From a user experience stand-point, it would make sense to process this change through Stripe so that the user doesn't end up with two separate items in his credit card statement. And even the charges in his statement may appear differently and may be hard for him to identify them. In this scenario, our concern is unintentionally violating our agreement with Apple because it looks as if we're trying to avoid paying Apple its commissions.
What's the proper way to handle this scenario?
The opposite scenario is also interesting where the original subscription is done through the iOS app and we handle the payment through Apple and then the user adds more licenses to his subscription through the web app. Again from a user experience stand point, we'd have to stick with Apple to handle additional fees.
I just want to understand the proper way to handle these scenarios so that we don't end up creating issues with Apple.
Thanks,
Sam