Our application used Pay TM for payment transaction, when student purchase digital e-course.
So currently our app new version upload on google play console. At that time google play console team reject our application. And display below errors.
=> Your app uses a non-Google Play’s billing system to accept payment for access to in-app features or services, including any app functionality, digital content or goods (collectively “in-app purchases”).
Ref: Google Payment Guidelines
Courses unfortunately comes under digital content according to web hence as shown in this article
Google has announced that all the apps that sell digital content through the Play Store will have to use Google Play's billing system and Google will charge a fixed percentage fee for every purchase made on that app. On September 18, Google blocked the Paytm app on Play Store for violating its policy on sports betting activities.
Related
The current flow of in-app billing is that the Google Play App processes and conveys all billing details between the Android app and the Google Play server, so they never communicate directly.
Why is this restriction in place? Why can't the app directly communicate with the APIs exposed in the Google Play server, like to get details regarding the cause of the restriction. Can we ask the user to Sign in with Google account on the app and make the in-app billing call to server?
Can I implement Pay Tm app integration for payment gateway in my android app to provide pro version of an application instead of google payment option? or which is best option other than google play ?
Here's the link to the payment guidelines for monetization on Google Play...
Developers offering products within a game downloaded on Google Play or providing access to game content must use Google Play In-app Billing as the method of payment.
Developers offering products within another category of app downloaded on Google Play must use Google Play In-app Billing as the method of payment, except for the following cases:
Payment is solely for physical products
Payment is for digital content that may be consumed outside of the app itself (e.g. songs that can be played on other music players).
So, for any app on the Play store, Google in-app billing is used for content consumed within the app, such as unlocking the pro version of the app. For physical goods or digital goods consumed outside the app, other third party payment services are permitted.
We are going to build a mobile app for iOS and Android (might build a web app later) where users can upload videos and their friends and followers can watch them. The videos can be either free or also be tagged with a price. If I tag a video with $1 when uploading it, my friends and followers will have to first pay $1 to watch and after paying that $1 they can watch it any time after that.
My client wants to use Authorize.net to do the payments. In iOS there are restrictions like we must use IAP for such feature. Similarly is there any restrictions on Android as well, that we must use Google In-app Billing or is it OK to use Authorize.net to do the payments?
Taken from this page:
Payments
Apps that employ in-store or in-app purchases must comply with the
following guidelines:
In-store purchases: Developers charging for apps and downloads from
Google Play must use Google Play’s payment system. In-app purchases:
Developers offering products within a game downloaded on Google Play or providing access to game content must use Google Play In-app
Billing as the method of payment.
Developers offering products within another category of app downloaded on Google Play must use Google Play In-app Billing as the
method of payment, except for the following cases:
Payment is solely for physical products
Payment is for digital content that may be consumed outside of the app itself (e.g. songs that can be played on other music players).
In-app virtual currencies must only be used within the app where they were first purchased.
Developers must not mislead users about the apps they are selling nor about any in-app services, goods, content, or functionality
offered for purchase. If your product description on Google Play
refers to in-app features that may require a specific or additional
charge, your description must clearly notify users that payment is
required to access those features.
So I guess the answer is no, you have to use Google Play in-app billing if you want to publish the app in the play store. But the policy states that digital content under some circumstances is excluded, I guess this applies to videos as well, although I'm not to sure about it. Depends on whether the videos can be played outside of the app (at least so it seems).
Is it possible to build an Android app subscription system without link to Google Play in app billing? If using Google Play in app billing, Google Play will charge 30% of the transaction fee. If it is possible to implement the app subscription without link to Google Play,anyone has good tutorial for that? Thanks!
Yes, you could use, for example, the paypal api, but you wont be able to publish it to the play store.
Developers charging for apps and downloads from Google Play must do so by using Google Play's payment system. In-app purchases: Developers offering virtual goods or currencies within a game downloaded from Google Play must use Google Play's in-app billing service as the method of payment. Developers offering additional content, services or functionality within another category of app downloaded from Google Play must use Google Play's in-app billing service as the method of payment, except: where payment is primarily for physical goods or services (e.g., buying movie tickets, or buying a publication where the price also includes a hard copy subscription); or where payment is for digital content or goods that may be consumed outside of the app itself (e.g., buying songs that can be played on other music players).
Source: Are there alternatives to using Google's in-app-billing , as a way to avoid publishing private info?
Wondering whats the difference between Google Wallet Billing APIs and Google Play in-app billing. Whats the advantage of using GooglePlay in-app purchase billing service over Google Wallet billing APIs? I see Wallet APIs also supports Android, then whats the point in using Goole Play IAP app? I'm at a point to implement a cross-platform solution for digital goods purchase in app. My question is what Wallet APIs don't offer over Google Play IAP service?
There are several Google Wallet APIs and they have different applicability. The following may help you.
Google Play In-App-Billing - Used for any digital goods purchase from native Android Apps. http://developer.android.com/google/play/billing/index.html
Google Wallet Digital Goods API - Used for any digital goods purchase from Web Apps. https://developers.google.com/commerce/wallet/digital/
Google Wallet Instant Buy API for Web - Used for physical or digital goods purchase from Web Apps - but you need to have your own payment processing. Google gives you a proxy card to charge.
https://developers.google.com/commerce/wallet/instant-buy/web/tutorial
Google Wallet Instant Buy API for Android - Used only for physical goods or services purchase from native Android apps - you need to have your own payment processing. Google gives you a proxy card to charge.
https://developers.google.com/commerce/wallet/instant-buy/android/tutorial
For 3 and 4 you need to fill out an interest form to get access.
http://getinstantbuy.withgoogle.com/
Hope this helps.
One important difference comes in the form of handling refunds.
Google wallet can be used to fund refunds, but may not handle requests for refunds. Whereas in app billing would forward you a request for refund.
I can see that being an issue when dealing with large volumes of purchases.
Source -http://developer.android.com/google/play/billing/billing_admin.html