Jira and their subscription model

I'm trying to understand the guidelines for the approval process of applications with external subscriptions on a B2B model.


I'm researching subscription models and using them inside of an IOS application.


Here is my bussiness case:

I have a Microsoft and a Web Application, and we are looking to extend out clients to an IOS app.

I have a working system in which users can register, buy their subscriptions through our sales representative. and they can register into our applications with a trial license.


All is nice and pretty, but when we started the disscussions about an IOS app, the approval process guidelines came into play.

I'm trully confused to what's allowed and what's not.


Doing a market research I found Jira/Confluence to offer a similar model to what I'm researching. Users/Businesses register on the website and they have an app to support their Cloud functionality.

Is this allowed? If it is, under what guidelines are they operating.

I keep seeing in-app purchase which is really throwing me off. That being said, I'm assuming that in-app purchase require apple to handle the subscriptions and I'm concerned about how to sync those subscriptions to my existing system.


If there anything I'm missing here, please let me know or if there is anything that apple offer to handle cases like this.


Thanks in advance

jira is simply cloud based. Their app hooks into a user's account on the backend. The app is free and all purchases/transacations occur outside the app.


If you want to follow their model, you'll need to create your own backend, sell whatever on your own website, then get an app into the store that ties into those remote services post-purchase.


Apple only insists that your app does not display a buy button that links to a website etc. outside of the app. See the ASRGs 3.1.1 In-App Purchase


References:

Jira and their subscription model
 
 
Q