There is one I believe, but I don't recommend using it. Google Checkout requires that you be able to complete a transaction without creating an account on the 3rd party site. Until aMember has a means by which to deal with this, sites will continue to get removed from the checkout program by Google for violation of the terms.
How does it "know" How would google checkout know that the transaction has created an account on the 3rd party site? My question: what makes for a 3rd party site? is it amember itself? or is the google checkout process so restrictive that, for example, I could not have my script generate an XML request to whomever i want?
Where in the Google Checkout policies does it say that you cannot require your customer to create an account?
https://checkout.google.com/seller/policies.html That being said, they have just recently made an addendum that may circumvent that rule:
I am also been contacted by Google Checkout Team that they inactivate my Checkout Badge because I am collecting user info. In the Google Checkout API new-order-notification, it can pass the user shipping info. Has any one have a solution to deal with this or have a suggestion how we can parse this notification message and create member in aMember? Thanks in advance.
Alex, How can we get the user info such as name, address, order items from the Google Checkout new-order-notification API and insert to aMember? Please advise.
Latest version of plugin (beta) allows this scenario. An account/subscription can be created after direct purchase in Google Checkout.