Rejection by "3.1.1 Business: Payments - In-App Purchase"

Hi,


We develop a web ERP system focused on apparel companies. This system manages finances, sales, billing, production, stocks, taxes, etc. We have on our site a place with "plans and prices", and a link to hire. This link sends an e-mail to our sales team, who will contact the prospect. This link does not open a new account directly.


We've developed an app called "App do Representante" that is used by sales representatives of our customers. Through the app, sales representatives place "offline" orders, and then sync to the cloud, directly inside of our client's ERP system. And to use the app these sales representatives need a login, password, and "connection string." This "connection string" is the "customer nickname", which will be resolved on our cloud server, and then will connect directly to our client's system server to synchronize. The representative does not have the autonomy to create his own login. Logins are created by the sales managers of our customers. We've already had this app running on Android for over a year now.


We were continually rejected by reviewer because of "3. 1.1 Business: Payments - In-App Purchase". The reviewer informs us that we need to integrate with IAP.


We don't know how to proceed, beacuse we do not sell anything inside the app. We do not charge for the application, it's free for use. And we will have other apps that will also integrate the ERP web system, and will work in the same way, requiring a pre-registered user and password, as they will be used by third-party companies that provide services to our customers.


Please, someone who has gone through something like this could share your experience, and how did you solve it?


Thank you very much.

Replies

>This system manages finances, sales, billing, production, stocks, taxes, etc.


Can you explain what the app does that is unique to it?


> The reviewer informs us...


Can we see the rejection(s), and the text of any appeals, thanks.