How To Accept ONLY Google Checkout

[geoman64]

It took me forever to get this script set up exactly the way I wanted it - but, I finally did it.

If you have a Zen Cart store, and you want to accept only Google Checkout, (like me), all you have to do is this very simple "cheat":

In your shopping_cart.php file, modify the dimensions for the script's "built-in" checkout button (your_template/buttons/english/button_checkout.gif) to: 1px x 1px. I'm sure that it's also possible to simply make the dimensions 0px x 0px, I just haven't done it yet. To see how this worked in my store, you can see it here:

http://url7.org

Now - when a customer is ready to checkout - all they will see is the Google Checkout button. This is with Level 1 GC integration - but it works perfectly. Everything that is added to the cart will appear on Google's secure Checkout page with the total already there, (so this also eliminates the need for an SSL certificate on your end); and, since the Google Checkout button is the only button your customer will see when they are ready to checkout, there is no confusion, missed orders, or non-paid "completed" checkouts... as I'm sure there is sometimes confusion on the customer's part with the "two-button" checkout setup, (where you have the built-in checkout button, then the "-or-", and the Google Checkout button below that). I was almost at the point where I was simply going to send a payment request to every individual customer who "completed" a checkout without using the GC button (anyone who has tried to use only Google Checkout Level 1 with Zen Cart knows that a customer can actually "complete" an order without actually paying)... but now, that won't be necessary, because they can't "complete" an order without using the GC button itself.

(NOTE: I will be adding the "Powered By Zen Cart" link back to my store site before I begin the tedious work of promoting the store; probably a button or banner, instead of only the small text link. This is an excellent script that deserves a link on every site that uses it).

A word of advice: if you ever get frustrated trying to get this script to work for you.... KEEP TRYING ANYWAY. Dig down into the code... find where the things are that you want to change, one at a time... and most of all, keep a backup of everything as you work so you don't end up with a horrible looking mess. You CAN make Zen Cart work for you, as long as you don't give up.

Good luck to everyone who is working with this fantastic script. It will do pretty much whatever you want: but - if you want anything beyond the default "classic" look, you'll have to put some time and effort into it.

Besides posting this simple work-around, I also want to thank the Zen Cart community personally for the outstanding work and effort that has gone into this script. My wife and I have a son with brain cancer, (glioblastoma multiforme, you can visit our son's page at: http://www.caringbridge.org/visit/ryanotto ), and my successful installation and setup of this script will allow us to stay at home with him during this very difficult time. If someone can explain to me how I can add custom text and links into one of the sideboxes, I need to add text explaining that 10% of all this store's profits will go to the Pediatric Cancer Research Foundation, and also a button-link to http://www.pcrf-kids.com/ in case visitors want to make direct donations to PCRF, or simply find out more about pediatric cancer research.

Again, a sincere Thank You to the entire Zen Cart Community.

[birdoasis]

Now hold on a minuet. I might be wrong but I want to point out somethings that may be wrong in your post. Only because if I'm right, people could be GC banned for following your instructions.

First, You're telling people that they don't need an SSL, when Google won't authorize you without one, as I understand it.

Second, as I understand it, the google checkout button has to be where it is as per their Terms of use.

Now I'm sure there's a third in there somewhere, but I'm being called out to dig a hole or something.

JP

[birdoasis]

Don't get me wrong, if you're right, Fantastic, I'll implement the changes as well, but I just want to sit on the fence of caution here.

JP

[geoman64]

I'm fairly sure that since no financial information will be entered anywhere on the site with this work-around - only on Google's secure servers - (this is only Level 1 integration: not Level 2, which requires a responsehandler, SSL, etc.)

Also, I'll go back and re-read Google's T&C, but I don't see what the problem would be with only offering their payment processor. In fact, I believe there there are actually some "perks" offered by GC for using only their payment option.

If there are any issues with this - believe me, I'm the first person who would like to know about them.

I believe, and I'm kinda "paraphrasing" here, but - the way I understand it, Google's requirement means that their Checkout button must be at least as prominent as it would be the "default" way...

[geoman64]

If anyone has a better understanding than myself and John as to the meaning of GC's T&C concerning the placement of the checkout button, please post it here. I certainly don't want to be banned from GC, and I don't want to cause anyone else to be, either.

But, I personally believe we'll find out that GC has no problem with this tweak, since it will make their button even more prominent than it would be otherwise.

[birdoasis]

I wish we could get rid of the button that shows up before the checkout page, however it turns out that it is against Google's Policies.



3. Google Checkout Branding and Acceptance Logo Guidelines

a. Use standard Google Checkout acceptance logos only
If you're a Google Checkout merchant in good standing, you may display the Google-hosted Checkout acceptance logo on your website. This logo informs prospective buyers that you accept Google Checkout. You may not alter the size, shape, color, or any other aspect of the acceptance logos provided by Google. Any use of the Google Checkout product name, logo, buttons, or associated imagery not explicitly authorized in this section is strictly prohibited.

b. Do not position or present Google Checkout as a form of payment equivalent to Visa, MasterCard, etc.
Google Checkout aggregates existing payment types to allow buyers and merchants to transact. Google Checkout is not a form of payment that replaces or is equivalent to existing payment types and must not be presented as such. Buyers using the ecommerce provider's standard checkout flow should not, therefore, encounter a payment field dropdown with Google Checkout listed alongside payment types like Visa, MasterCard, American Express, etc. Instead, the buyer should have the option of selecting Google Checkout as a distinct checkout flow as required in 4b.

4. Google Checkout buttons and Buy Now buttons

a. Use standard Google Checkout buttons only
You may only use Google-hosted button images for Google Checkout buttons and Buy Now buttons. You may not alter the size, shape, color, or any other aspect of these images.
b. Ensure 1:1 and adjacent button placement
You must place a Google Checkout or Buy Now button immediately beside, above, or below every existing checkout button or link on your website. (Because users tend to read horizontally, we recommend placing the Google Checkout or Buy Now button beside your existing buttons and links.)

You must separate the Google Checkout flow from your existing checkout process. If buyers initiate your existing checkout process, they must not see a Google Checkout or Buy Now button.

If you're using Buy Now buttons, you must display a Buy Now button in a visible and appropriate location for each item you'd like to sell using Google Checkout.
c. Place Google Checkout buttons before your login pages
Buyers should only have to provide their login, purchasing, and other information once. If you require users to register or sign in to your site, you must ensure Google Checkout and Buy Now buttons are available before the login process so buyers are able to check out with Google Checkout without having to log in. (You may still track visits and personalize pages using cookies.)
d. Direct buyers quickly to Google
If you're using Google Checkout buttons, you must ensure that buyers who click the Google Checkout button on your site see the Google Checkout confirmation page within one second, and without seeing any intermediate pages. This will help you avoid shopping cart abandonment. We recommend you consider pre-computing shopping carts, leveraging server to server posting, and other tips in our Developer's Guide.
e. Do not disable the browser's 'Back' button
Buyers who click their browser's 'Back' button should be brought from the Google confirmation page directly back to your site without seeing any intermediate pages. (Learn about server–to-server posting and other best practices in our Developer's Guide.)
f. Identify unsupported purchases
If you're using Google Checkout buttons, you must display the Google-hosted 'not available' button for orders not adhering to our content policies. (Learn more: Google Checkout content policies | Button options)
g. Google Checkout must be available as a checkout option at least 95% of the time
Google Checkout may be unsupported no more than 5% of the time, in which case you are required to display the 'not available' button as described in 4f. At least 95% of the time, Google Checkout must be offered as a checkout option, with the standard Google Checkout button prominently displayed.
h. Direct your 'checkout' links and buttons to the checkout process
Buttons or links containing the word 'checkout' should initiate a checkout process, not a 'view cart' page. The latter may confuse buyers and disrupt the purchase flow.
i. Additional button messaging
Including additional text around the Google Checkout button can help make it clear to buyers that they can check out using either Google Checkout or your existing checkout process. We recommend placing the text “ – Or use – “ between the Google Checkout button and your existing checkout button.

Referance:
http://code.google.com/apis/checkout/terms.html

[birdoasis]

I would like to apologize. I certainly didn't intend to accuse of you causing others to get banned or anything of the sort. I should have worded my postings better.

Before I posted I was out fencing in the heat, so I was a crabby ole poster when I sat down in front of my computer.

So please excuse my abruptness.

I've posted the terms of service above. Please keep us updated if GC takes offense.

JP

[geoman64]

Wow. I never saw that. I appreciate you posting it really, because I will most definitely now change my checkout process back to the "default" way.

No offense taken here, I'm crabby most of the time these days :)

[birdoasis]

Well then you can come help me fence in the heat! ha

[geoman64]

Whoa, now... I already know about that fencing business. I'm an Alabama boy, (so I've done too much of it already) lol