I need to implement a renewable subscriptions in my mobile application, with different plans, duration and prices (like Netflix is doing), that is valid on mobile but also in my desktop app.
I read many threads and I understood that the only way to know if the subscription is correctly renewed is to check it from the mobile app: this is a problem for me because if I bought a subscription in my mobile app and I stop using it, but I'm still using the desktop application, at the end of the subscription I will not know if the subscription was renewed (because the user never opened the mobile app) and so I'll block the user for log-in in the desktop app.
I also read that it's not possibile to use Stripe or Paypal to manage the payment in mobile app, because the store will block the application that is not using a proprietary purchase system to sell not-physical goods or services.
So, the question is: is there a way to make a recurring subscription and know if it's currently active or not and the total payed without open the mobile app? If not, how can I manage a recurring subscription both in mobile and desktop apps? May be I'll need to create an external web page using a webview and then use Stripe or Paypal?
Thanks.
Matteo
Font:
Renewalbe subscription on mobile
Implement Stripe in Xamarin
EDIT
Our purpose is to manage subscriptions on desktop application but give the mobile user the possibility to buy a plan also on mobile.
Is possible to use a web view or default mobile browser to redirect the user to desktop web page and buy from here, without have any problem when publish app on apple and play store.
Related
I have an app with Free, Premium and Gold subscription plan. Based on the plan user can access features like filters, messages, likes.
Now, I'm planning to have an web app only for payments using stripe. So, users will directed to web app to pay payments.
Will apple allow this approach or will they insist to use in-app purchase?
I'm little confused here. Need your suggestion here?
This is a question for Apple Review team, you should reach out to them directly and clarify. Stripe doesn't replace in-app purchases and you need to use Apple's API to perform in-app purchases. See here for details
I plan to use a 3rd party payment gateway for in-app purchases for an app distributed through the Google PlayStore. I'm aware of Google's policies regarding payments for in-app purchases (https://play.google.com/about/monetization-ads/payments/)
My content / service delivery model is as follows:
When a user pays for a plan he gets—
Certain features in the app
Certain features in our web portal, completely outside the app
Our deployment staff going and visiting the user's location and
providing training and setup services.
For some plans, we will be delivering a physical device to user's
locations (a POS machine to accept card payments)
Since my offerings are a combination of physical and digital goods and services provided within and outside the app, it does not clearly fall under the categories Google mentions in the link above.
My question is: Can I use a 3rd party payment gateway to accept payments within the app given my content / service delivery model?
Do I risk being blacklisted? Does Google give a time window to react by sending an email first before pulling apps down.
I know my question is similar to this one: Android In-app purchases and I'd like to get similar opinions on my planned content / service delivery model.
Kindle PlayStore app, distributed via Play Store also seems to be an example of an app using different payment method from Google's billing APIs
For our usecase/situation below; should we be using SuiteSignOn to make an outbound call or an inbound call?
Usecase:
We have a Netsuite webstore (SCA). People login and purchase medical tests from us. After customers have performed their medical test they can view their results in our external web application (PHP Laravel web app). We want to use 1 single sign on for both applications (NS webstore and Results web app). Ie, the user will use their SCA webstore account login details to login to both applications.
We expect customers to go to the Results web app and somehow login using their NetSuite user credentials. I assume NetSuite (SuiteSignOn) can embed a login form in a external web app?
So would the above usecase be considered a SuiteSignOn outbound call or SuiteSignOn inbound call?
Check into Google Auth. That is supposed to be released as soon as all of the 2017.1 upgrades are rolled out. That would allow you to use the same authentication credentials.
I am hosting a hackathon at my company and intending on making use of the Spotify WebAPI. I wanted to know what the preferred way of registering apps (does every attendee need a Spotify account or is there some work I can do ahead of the hackathon to have everything ready), as well as notify Spotify of a period of time they can expect a high volume of requests originating from my company's IP.
My planned approach is to have 1 premium account with multiple apps registered (1 per team). Is there a better way to do this?
We're planning a web service based on recurring monthly payments.
The site would have similar user accounts as Netflix or Spotify. The site would have an account section were the user can manage the billing and other details.
I've looked into different payment gateway provides, but I'm still wondering how to implement the user account as a part of the main site and how to combine that to the billing system.
First some information:
The site would first have just one monthly plan xx$/month
Credit cards need to be accepted
We're based in EU
We don't want to use PayPal
The user account section would contain:
User profile (name, email, etc.)
Website options (features on / off)
Subscription & billing management (edit credit card, current period, cancel, etc)
Questions:
How to combine the basic user accounts on my site with the billing system provider?
What information should I store in my own database?
Should I use a 3rd party user account management software on top of a payment gateway provider?
If so, which one would work similar to Spotify's account management?
How to setup the first sign up flow where user enters CC information?
Thank you for the ideas!
This is relatively easy to do using Laravel (a php framework) and a package called cashier. This package uses a payment service called Stripe which allows you to create recurring payments. There is even a tutorial on how to do it on Laracast.