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
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 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.
I am currently developing a marketplace type of website. When it comes to handling payments, I would like to be able to charge customers on behalf of sellers.
Which payment gateway API should I use (if this is even possible)? I am using React and Node.
For reference, what I was looking for was something like Stripe Connect. According to their website: "Marketplaces and platforms use Stripe Connect to accept money and pay out to third parties. Connect provides a complete set of building blocks to support virtually any business model, including on-demand businesses, e‑commerce, crowdfunding, and travel and events."
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.
I'm building an application for a new small business. They run events at race tracks, and the application is a registration system for said events. As a small business the owner doesn't want to worry about handling people's credit card info. They are just starting up and we are building from the ground up. So we are looking at using third party services like Google Wallet and PayPal.
So looking at the documentation, we have the Instant Buy API. Seeing as we aren't planning on taking direct credit card payments, it seems like a pain to setup payment processing through another service to use the Instant Buy. But we aren't selling a "Digital Good", as far as I can tell (I haven't seen a documented definition for this), so does that mean we can't use the API for Digital Goods? I haven't found any documentation that lays this out as a policy. It seems like it would be a lot simpler to implement, even with the cut Google takes.
There is a page at the google wallet documentation site called Which API Should I Use?, the first item there is:
The quick answer: it depends on your goals, your platform and what
kind of goods or services you're selling. The Instant Buy APIs are for
selling physical goods, while digital goods sellers should use the
Google Wallet for Digital Goods API for web apps or Google Play In-app
Billing for Android for native Android apps. To engage your customers
with offers and loyalty programs, use the Wallet Objects API.
Now, the Instant Buy APIs are for those business that have an existing payment gateway setup, but need to offer Google Wallet as a payment option.
In your situation, as you don't have a payment processor setup:
To sell physical goods on web apps and mobile apps that run on
browsers, use Instant Buy for web. You'll keep your existing payment
processor and optimize your payment flow with Google Wallet, just like
with Android. You can use Instant Buy for web to sell digital goods,
but if you lack a payment processor or resources to maintain and
develop a PCI-compliant online store, you should use the Google Wallet
for Digital Goods API.