How to avoid IAP requirements in companion app to a SaaS website?
I am working on a SaaS website and mobile app. The initial plan was to have account registration only on the website, but after dealing with Apple's review team far too many times on "login only" apps, I want to allow registration in my app.
Normally, this would not be an issue; we would just set up IAP and be done with it, but this app is technically not for us. The main purpose of this app is to bring money in for schools. We do take a cut, but we do not charge an onboarding fee or a license fee for schools to create accounts. The only way the school or we make money is through user sign-ups.
Schools will be able to set their own prices for user subscriptions, which means if we were to offer IAP, we would have to manually update them, and we could potentially have hundreds of subscriptions, and it would be too annoying and frustrating to deal with, so we want to keep the subscription going through Stripe only. We also do not want to deal with Apple/Google Fees, which will take a big bite out of schools' and our income.
What exactly are the rules and ways to correctly handle this?
Currently, the app will be US-only, and 99% of the app requires a subscription.
My plan was to allow users to register in the app, and once they log in, they can see the app's main idea (see example offerings in the app), but they cannot actually redeem or do anything in the app without an active subscription. And add a section that says something like, "To access the rest of the app, finish registration on the website," or something similar.
On the user's profile, we also plan to show their current subscription and a "Manage Account" button that will direct them to the website so they can activate the subscription there. But I do not know whether that is allowed.
Has anyone else built a companion app like this and knows how to handle it?