wcw
11-22-07, 01:37 AM
I just got an email from Google and one of the things that caught my eye was, "- 4b: Relaxed policy such that 1:1 Google Checkout button
placement is highly recommended for a consistent user experience,
but not required." The email was entitled "Updates to the Google Checkout Terms of Service and Program Policies".
Does this mean that we can finally put the Google checkout button on the osel screen so that the customer's real data (address) is passed to Google initially instead of the store address which messes up many shipping modules?
If yes, how would we do that? Can the current Google module handle being launched from the osel screen or any page after the customer data is captured in Merchant?
placement is highly recommended for a consistent user experience,
but not required." The email was entitled "Updates to the Google Checkout Terms of Service and Program Policies".
Does this mean that we can finally put the Google checkout button on the osel screen so that the customer's real data (address) is passed to Google initially instead of the store address which messes up many shipping modules?
If yes, how would we do that? Can the current Google module handle being launched from the osel screen or any page after the customer data is captured in Merchant?