What is the difference between Google Pay Api and Android Pay Api. What I know is using Android Pay Api we use do both payment and adding loyalty cards. Now google has introduced Google Pay Api. Is it replacement for Android Pay Api?
Google just announced that it’s combining all of its different payment services, including Android Pay and Google Wallet, into one unified service, simply called Google Pay.
With the new system, payment information saved in your Google account will be available everywhere you use Google products: in Chrome for web purchases, in YouTube for renewing your subscriptions, in apps on Android for in-app purchases, and at retail outlets with NFC payments.
Reference link -- Google Pay
Related
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.
I want to set up my Android app to accept money from users Google Pay accounts and disperse money to Google Pay accounts all from the app. I have seen people mention that Google Pay returns a token, and I need to use a payment processor, however I am not sending the money to their bank accounts. I want the entire transaction to go from their Google Pay account, to my Google Pay account, back to their Google Pay account. Is that possible or does Google Pay simply return an instance of their banking information even when they're using Google Pay as well?
Unfortunately, the Google Pay API does not offer this functionality. It's used by merchants to accept payments from their customers and it thus requires a payment processor.
Google Pay Send is a feature inside of Google Pay which is used for peer-to-peer payments and it doesn't offer an API.
In short, you can't leverage Google Pay for third party money transfers directly - you would need to use a payment processor or gateway to facilitate the transfers.
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
Is the Google Wallet online payment system on Android phones mandatory for e.g. movie, songs or game levels purchases in a similar way the Apple’s In-App-Purchase is on iOS?
According to the information here “Developers offering additional content, goods, or services for an application downloaded from Android Market must offer an authorized Payment Processor as the payment option“.
Our understanding is that if user has installed an application, which plays movies and users pay per single movie view application needs using the Google Wallet otherwise it can be removed from Google Play. Is that correct?
Similar situation is within game if user wants to pay for the additional level. Is that correct?
For subscriptions it is not required to use the Google Wallet (again the similar situation is on the iOS).
STeN
I had an app that had LogiaMobile billing integrated and was rejected from Google Play for that very reason (it was in Sept 2011). The app tried to bill users when they wanted to download videos.
Find a good explanation about the policies in this Techcrunch article
My advice would be to always integrate Google In-App billing (now v3 is far more confortable to work with).
I hope this is what you were asking for :)
'Google Wallet' is a confusing name, because it may refer to different thing. First there is the Google Wallet app that lets you pay with your phone via NFC. You certainly don't need this to buy things from the Play Store and it is supported only in the US, and only on a limited number of devices. Google Wallet also refers to Google's online payment system (aka Google Checkout). You need to register your credit card with that in order to make purchases on Android. It serves as the 'authorized Payment Processor' in most case. Other ones being carrier billing on supported carriers.
I want to use Google Play's in-app billing for one of my applications. But it seems I can't use it.
First problem is that according to supported locations for merchants my country - Turkey - is not in the list.
And as a second problem, my app is listed on some other markets except Google Play. Google Play in-app billing overview section In-app Billing Requirements and Limitations says that In-app billing can be implemented only in applications that you publish through Google Play. Therefore even if Turkey will be in merchant list in the future, I could not use Google Play's in-app billing for other markets. Is that right?
Then I thought using other APIs like ZooZ, Authorize.net (Actually, I did not examine them deeply, but I guess they do what I want)
But this time I read in Android Market Developer Distribution Agreement that All fees received by Developers for Products distributed via the Market must be processed by the Market's Payment Processor. Is that a problem for using such APIs? If so, what should I do for in-app purchase?
If your country is not supported, you can't really use In-App billing for your app. You could look at alternate stores, for example, Amazon app store. they have recently implemented In-App billing.
https://developer.amazon.com/welcome.html
The simple answer for Google Play would be "No" for now, till Google supports Turkey.
Get a bank account in a country that does support merchant accounts.