[fido]

Things I don't want: 1. Google branding my checkout process 2. Forcing MY users (who already created an account with me) to create a Google Checkout account. 3. Auto checking a "news and special offers" box to send my users email

Also, is there a support phone number anywhere?

[kposehn]

Agreed about the email checkbox - I don't want anyone emailing a user I've spent time and money to get without me getting a cut.

Piggybacking their own bulk email lists on top is a no-no, even if it is part of the Google Checkout option, imho.

[lobo_tuerto]

Would it be ok if you proxied the process for your users?

What if you created the Google Checkout account for them? could you act like a gate keeper for his e-wallet? is that possible/legal?

[lobo_tuerto]

Well, this was an honest question about proxying the creation of the needed accounts automatically from your app. And wanted to know if this was permitted/legal.

You know, taking the credit card data from the user, storing it in your secure app, creating an email address within your app, submiting info provided by your user to Google Checkout and then when a payment needs to be done:

User needs money to pay something you are selling -> Your app then goes onto the Google Checkout account of the customer and tries to get some money for you.

You basically are making your own API on top of the current Google Checkout. Maybe using scraping and stuff (just like how InDinero scrapes and get your bank data).

I'm asking because I cannot verify if this indeed can be done. I cannot create a Google Checkout account since I'm not from the USA.

[abraham]

Then don't use it.