Fees for commercial Apps published into Google Apps Marketplace - google-apps-marketplace

while reading through the online documentation I do not understand if:
there are some fees for commercial Apps published into GAM (or CWS) or the one time 5$ would suffice;
it is mandatory to have a Google Wallet account or not.
Thank you.

Before you publish your first item, you must pay a one-time US$5.00 developer registration fee. They charge this fee in order to verify developer accounts and better protect users against fraudulent activity.
The 5$ fee is just to verify the developer account.
Check this page for more details.
I believe all the payments to Google goes through Google wallet only. However, you have to provide your card information in Google wallet while you are paying.
Hope that helps!

Related

My Google adsense account is verified, then also i'll need to verify my ID after buying play console developer account?

I have a Google Adsense account, I'm using it to show ads on my websites, also I'm using Admob to show ads on my applications. Everything is working fine as I have successfully verified my ID and Address with PIN and receiving money. And now I want to publish my applications on Google Play Store so I visited website to buy console account, it's written that google may ask to verify my identity and if failed money won't be refunded. My question is that after buying it, will google ask me to verify my identity with my photograph and government ID ?
They usually do not try to verify you, but usually it happened when you want to get payment for IAP (in app purchases) inside your apps.
Then they will ask for government ID (I recommend using passport), and will ask you to add a bank account to receive your money, it will take couple of days then they will verify you.
Do not worry it is normal process, the nonrefundable part is the 24$ you pay to open Google Play Developer account.
They may ask you to verify your phone number (it depends on your country, this is not done in all countries)

Use Google Wallet in my website for recurring payment, including user-authentication

I have a website that provides a specific SW service.
I would like to allow users to subscribe to this SW service:
Sign-Up: the user provides credit card details, a username and a password.
Sign-In: the user enters username+password in order to get access to my SW service.
The user's credit card should be charged once per month (i.e., recurring payment).
I'm considering Google Wallet for this purpose, but there are a couple of issues that I'm concerned about:
Can I use the Google Wallet API in order to implement sign-up and sign-in, or should I implement user-authentication separately within my server?
Is the Google Wallet API available only for mobile devices? This is implied in both Google Wallet's website and in Wikipedia. My website is primarily intended for use through desktop PCs, and not through smartphones.
Thank you for your help!
For the sign-up / sign-in part, if you want to use Google's OAuth service you can try at the Google+ Sign-In.
For the recurring payment part, the Google Wallet for digital goods API offers a monthly subscription API and a web-based payment flow. If the user does not already have a credit card saved in their Wallet, they will be prompted only once to add a card.

Steps for billing at Marketplace

I am planning to list a Gmail Contextual Gadget on Google Apps Marketplace. More than a year ago I created a vendor profile and a listing (so I am familiar with those steps), but I never made the gadget commercial. Now I'm ready for setting up the gadget for sale but I am wondering about the billing is implemented. As I've read in the Marketplace billing documentation, Google does not provide any solution for this, but recommends that I implement it myself or use a third-party billing product.
So my questions are:
- Which are the basic steps to create a billing solution for your listing?
- Is there any way keep the payment "manual", in that sense that I enable the product for installation manually (with a token etc) for a customer when the payment is received?
- How long time do I have to estimate for this?
Really appreciate an answer!
You need to use the Licensing api
https://developers.google.com/google-apps/marketplace/licensing

Linking merchant account from another location

We are two developers. I am from the Philippines and the other developer from London, UK. We are done with the game and started adding in-app purchase. I just learned that I cannot open a merchant account as Philippines is not included. But my teammate can since he is in UK. Is it legal if he opens up a merchant account from UK and links to my developer account? Can we legally then implement in-app purchase?
You will have to open a bank account in the UK through a legal representative living there.
The registration process is very thorough in asking you to enter bank information details, so Google will reject countries that are not in this list. Sad, but it's the truth no thanks in part due to legal restrictions worldwide.
Your teammate should open his own developer account and use that to open a merchant account.

How can I find the Google account connected to an API key?

This is very embarrassing: a few months ago I registered my a credit card to my Google account to enable Google translate in an application I am developing. Since then, Google has been happily billing my card, but I have never received an email invoice and when I now log in with the account I think I used, I see the Translate API disabled in the API Console and I can't find any billing tab.
I've searched my emails and electronic receipts but can't find any confirmations connecting a particular Google account (I have about 10 for different clients and projects). Is there any way of working back from the key and find the corresponding Google account? Any other suggestions? It's kind of bad form to not sending some email to confirm a credit card charge of ~$100 a month...
I ended up tracking down the account. It was a gmail account and all the receipts had been emailed to that account too obviously.

Resources