Google Checkout was an online payment processing service developed by Google to simplify ecommerce transactions. It operated from 2006 to 2013, allowing buyers to store payment credentials in Google accounts for one-click purchasing. Marketers should understand its sunset timeline to manage legacy checkout references, clean up outdated payment integrations, and avoid linking to deprecated URLs that create 404 errors.
What is Google Checkout?
Google Checkout provided a web-based checkout process where buyers stored credit cards and shipping addresses in their Google accounts. Merchants integrated Google-hosted buttons into shopping carts, allowing purchases via username and password rather than re-entering payment details.
The service launched in the United States on June 28, 2006 and in the United Kingdom on April 13, 2007. It merged with the NFC mobile payment app Google Wallet in 2011 before the web checkout component was fully retired on November 20, 2013.
Why Google Checkout matters
- Legacy SEO cleanup: Thousands of archived pages still reference Checkout buttons or policies. Identifying these prevents crawl budget waste on dead payment gateways.
- Historical UX standards: The service established early norms for one-click checkout flows and button placement above the fold that influence current conversion rate optimization.
- Fee benchmarking: Google's pricing model offered a competitive alternative to PayPal, charging 2.0% plus $0.20 per transaction in the US and 1.4% plus £0.20 in the UK before moving to a tiered structure.
- Fraud protection precedent: Checkout assumed fraud liability for qualifying transactions, shifting risk from merchants to the payment processor.
- Platform migration lessons: The 2013 forced migration demonstrates how API sunsets create technical debt requiring full checkout reconfigurations.
How Google Checkout worked
For merchants:
- Integrate buttons: Place Google-hosted Checkout buttons next to existing checkout options on cart pages, ensuring visibility above the fold on 1024x768 screen resolutions.
- Host images: Use only unmodified Google-hosted button images (no resizing, recoloring, or reshaping).
- Enable instant handoff: Configure the button to post carts immediately, sending buyers to Google within one second without intermediate pages.
- Process transactions: Google handled credit card storage, charging, and fraud screening before depositing funds to the merchant.
For buyers:
- Click the Checkout button on a merchant site.
- Sign in to an existing Google account or create one, where payment and shipping information was stored.
- Review the order on a Google-hosted page.
- Complete the purchase using stored credentials.
Types of Google Checkout
| Type | Description | Fee Structure |
|---|---|---|
| Standard Merchant | Full processing for retail businesses | 2.0% + $0.20 (US), 1.4% + £0.20 (UK); free until February 1, 2008 |
| Non-Profit | Fee-free processing for IRS 501(c)3 organizations | No fees until March 31, 2012 |
| AdWords Integrated | Fee waiver for advertising merchants | Free for monthly transactions under 10x AdWords spend (discontinued May 5, 2009) |
Best practices
Place buttons above the fold: Position Checkout buttons in the initial viewport without scrolling to reduce cart abandonment. Merchants using transparent button variants for off-white backgrounds maintained visual consistency with site design.
Preserve back-button functionality: Configure flows so browser back buttons return buyers directly to the merchant site from Google's confirmation page. Avoid opening Google Wallet in new windows or inserting intermediate pages that break the navigation chain.
Speed the redirect: Send buyers to Google within one second of button click. Delays caused by forced site registration or intermediate loading pages increased dropout rates.
Display before login: Show Wallet buttons prior to requiring site registration. This allowed guest checkout via Google credentials without forcing buyers to create merchant-specific accounts first.
Use restriction indicators: Display "Google Wallet not available" buttons for orders violating content policies (weapons, certain digital goods) rather than hiding buttons entirely or processing prohibited transactions.
Common mistakes
Altering button assets: Resizing, recoloring, or modifying official Google-hosted button images violated policies and risked account suspension. Always use the URL generator provided by Google.
Hiding buttons behind logins: Requiring buyers to register on the merchant site before accessing Checkout options created friction and violated placement guidelines. Buyers needed access to buttons before the merchant login process.
Breaking the back button: Opening Google Wallet in new browser windows or inserting redirect pages between the merchant site and confirmation page prevented users from returning to their carts using standard browser navigation.
Processing restricted content: Failing to use "not available" button variants for prohibited items led to account freezes. Merchants selling digital goods behind login pages needed to display acceptance logos before those barriers.
Ignoring mobile variants: Not implementing mobile-specific button formats reduced conversion on smartphone browsers, which required different button sizes and placements than desktop.
Examples
Example scenario: A 2008 electronics retailer placed Checkout buttons adjacent to PayPal options on cart pages. By maintaining button visibility above the fold and avoiding forced registration walls, they captured buyers who abandoned competing sites requiring account creation.
Example scenario: An IRS-certified charity utilized the non-profit program in 2011 to process donations without incurring the standard 2.9% + $0.30 transaction fees, maximizing donation value until the program ended March 31, 2012.
Example scenario: A merchant participating in the Merchant Referral Program earned $25 for each referred business that processed at least 3 unique customer transactions totaling $500 in sales, offsetting initial integration costs.
Google Checkout vs PayPal
| Factor | Google Checkout | PayPal |
|---|---|---|
| Fee structure | Tiered; 2.0% + $0.20 initially | Tiered model |
| eBay compatibility | Banned in 2006; blocked entirely by June 2011 | Native integration (owned by eBay during the ban) |
| Account requirement | Google account | PayPal account |
| Fraud protection | Google-assumed liability | PayPal Seller Protection |
| Current status | Retired 2013; migrated to Google Pay | Active |
| Back button behavior | Required direct return to merchant | Platform dependent |
FAQ
What replaced Google Checkout? Google retired the web checkout service on November 20, 2013, replacing it with Google Wallet. This later evolved into Google Pay (2018) and the current Google Wallet (2022).
Why did eBay ban Google Checkout? eBay added Google Checkout to its banned payment methods list in 2006, forbidding its use for eBay transactions. By June 2011, eBay prohibited all external checkout systems to maintain integration with PayPal, which eBay owned at the time.
What was the Merchant Referral Program? Google offered $25 for every referred merchant that processed at least 3 unique customer transactions totaling $500 in sales through the Checkout platform.
How did fees compare to PayPal? Checkout initially charged 2.0% plus $0.20 per transaction in the US and 1.4% plus £0.20 in the UK, comparable to PayPal's rates at the time. Google subsequently moved to a tiered cost structure identical to PayPal's model.
Should I remove old Google Checkout references from my site? Yes. Remove legacy button code, update payment policy pages, and redirect old Checkout URLs to current Google Pay implementations or alternative processors to avoid 404 errors and user confusion.
What support channels existed for Google Checkout? Google provided support through a Buyer Help Center, Merchant Help Center, Help Forums, and email support, though these resources are no longer active following the 2013 retirement.
