Google Checkout

Requirements:

Getting Started:

Sign up as a Google Checkout merchant if you have not yet done so.

Please note that you must complete these steps for your production account. You must also complete these steps in your sandbox account if processing test transactions through the Checkout Sandbox. These steps must be followed carefully:

Using Google Analytics:

To use Google Analytics you must use the ga code, not the older urchin code. Follow the instructions below:

1) Open Application.cfm and set attributes.useanalytics = "1".
2) Open ezcart/google_analytics.cfm in an editor and enter your analytics ID in the first line in the analyticsid attribute.
3) Place the following line of code ibefore the closing HEAD tag and before the closing BODY tag. It must be included twice. If you need to change the path or move the file that is fine.

<cfinclude template="ezcart/google_analytics.cfm">

cf_ezcart Features NOT Supported Using Google Checkout:

  1. Deferred payments.
  2. If you charge local taxes, the order will be authorized for the highest tax amount (after adding state tax, county tax and city tax) for the customer's state. Upon order completion, you may recalculate sales tax and capture the transaction for the final amount, or refund the difference (either method is simple through our integration). The final tax amount will be tracked as "State" tax and not broken down by locality.
  3. You may set Google Checkout to calculate real time shipping rates. However at this time only shipping to US addresses is supported. If you ship internationally, you may use one of cf_ezcart's built-in shipping calculation methods below.
    1. Ship based on order total or number of items purchased.
    2. Ship based on your own calculations ($X first pound and $X each additional pound).

Customer Experience:

We allow your customers to check out without logging in at your site when using Google Checkout. This is a requirement of Google. We automatically relate google orders to the correct customer when possible. This is the logic we follow:

  1. First, if the person has logged in at your site, we pass their customer id with the order. If so, we relate the google order to this customer. Otherwise...
  2. Check if the google billing email AND google buyer id both match a customer. If so, we relate the google order to this customer. Otherwise...
  3. Check if the google buyer id matches a customer. If so, we relate the google order to this customer. Otherwise...
  4. Check if the google billing email matches a customer. If so, we relate the google order to this customer. Otherwise...
  5. Add a new customer.

Also, we work with unique customer email addresses and use that for login. One scenario above is that a person may have placed orders at your site as bob@abc.com and bob@someisp.com and have 2 customer accounts. If they logged in at your site as bob@abc.com, and their google email address is bob@someisp.com, when we updated the record at your site, there would then be 2 customers with bob@someisp.com as the email address. We therefore check, and if the email address already exists, we don't update the email address of the active customer.

Become a Google Checkout Merchant