Hi There,
I'm trying to understand the limitations we may have for an app we are developing.
We have a coffee shop app, which would like to offer of a deal - example: a monthly coffee subscription, for $20 you get 10 black coffees for the month which can be redeemed in either our web or mobile apps during the set duration. This is not an in-app purchase, but one that will end up with physical coffee, though it will be received over a period of time.
Do we know if it's okay to use a webview to link to the subscription page for managing their coffee subscription (handled outside of IAP as it is a physical good)? They would add their payment info the same way they already do with other integrations like square or stripe payment forms, and then we link them to the actual payment site. I see some things about not even giving the option to show the link or tell the customers what the link is if they want to investigate the option which would be very difficult for the customer to manage. We want a good experience.
The guideline itself says "you must use purchase methods other than in-app purchase to collect those payments, such as Apple Pay or traditional credit card entry."
Does anyone see an issue with the planned approach? I see the different lawsuits with EPIC and what not and we don't to end up with a rejected app if we can avoid it.