Hi,
I'm not a programmer/developer but it doesn't look too difficult to do (within the developer's environment) and I expect the existing Actinic scripts for Paypal/HSBC etc don't need to be modified too much. (Can't be more than 1-2 days work can it?)
The 50 or so "voters" here have paid Actinic probably somewhere between £20,000 to £40,000 for their software, so surely 1-2 days work is not asking too much, is it?
See:-
http://code.google.com/apis/checkout...per/index.html
Regards
Nick
PS Although it would be a pain, I have recently had some quotes to move to another ecommerce platform.
The main implementation explanation is here:-
Add a Google Checkout button to the checkout pages on your online store. The button needs to be embedded in a form in the HTML for your pages. The button should appear next to your existing checkout buttons. Note: You may add more than one Google Checkout button to your page.
Modify the code for your online store so that the form containing the Google Checkout button also submits information about your customer's order.
Your code needs to create an XML document containing information about the items in your customer's shopping cart. The XML will also contain information about the shipping options that the customer can select and the taxes that should be added to the order. Your code will need to encrypt the XML document and embed the encrypted value in the form that contains the Google Checkout button.
The Checkout API section provides instructions for creating the shopping cart XML. In addition, the Processing an Order section explains how to encrypt your XML document and include it in the form on your checkout page.
In your development environment, your form needs to submit orders to the following URL. You must replace the text [[Merchant-ID]] with the Merchant ID from your Sandbox account.
<form method="POST"
action="https://sandbox.google.com/checkout/cws/v2/Merchant/[[Merchant-ID]]/checkout">
Note: Your production merchant account will have a different Merchant ID and Merchant Key than your Sandbox merchant account. Your code should use the values from the Sandbox account when communicating with the Google Checkout Sandbox service. Similarly, your code should use the values from your production merchant account when communicating with the Google Checkout production service.
Your production system will submit orders to the following URL. You must replace the text [[Merchant-ID]] with the Merchant ID from your production account.
<form method="POST"
action="https://checkout.google.com/cws/v2/Merchant/[[Merchant-ID]]/checkout">
This step is optional. Set up a web service to perform custom calculations for tax, shipping, coupons and gift certificates after the customer has reviewed the order in Google Checkout. The Merchant Calculations API section provides detailed information about custom calculations.
This step is optional. Create a web service that receives and processes new order notifications from Google Checkout. The Notification API and Order Processing API sections thoroughly explain the ways that you can integrate your internal order processing systems with Google Checkout.
After you have thoroughly tested your Google Checkout implementation with the Sandbox service, release your code to your production system to begin accepting orders through Google Checkout. Please remember that you will need to use a different Merchant ID and Merchant Key in your production environment than you use in your test environment. Your Google Checkout buttons will also have different URLs in your test and production environments. You will receive an error if you try to process orders using the wrong Merchant ID or Merchant Key.
Google Checkout Buttons
I'm not a programmer/developer but it doesn't look too difficult to do (within the developer's environment) and I expect the existing Actinic scripts for Paypal/HSBC etc don't need to be modified too much. (Can't be more than 1-2 days work can it?)
The 50 or so "voters" here have paid Actinic probably somewhere between £20,000 to £40,000 for their software, so surely 1-2 days work is not asking too much, is it?
See:-
http://code.google.com/apis/checkout...per/index.html
Regards
Nick
PS Although it would be a pain, I have recently had some quotes to move to another ecommerce platform.
The main implementation explanation is here:-
Add a Google Checkout button to the checkout pages on your online store. The button needs to be embedded in a form in the HTML for your pages. The button should appear next to your existing checkout buttons. Note: You may add more than one Google Checkout button to your page.
Modify the code for your online store so that the form containing the Google Checkout button also submits information about your customer's order.
Your code needs to create an XML document containing information about the items in your customer's shopping cart. The XML will also contain information about the shipping options that the customer can select and the taxes that should be added to the order. Your code will need to encrypt the XML document and embed the encrypted value in the form that contains the Google Checkout button.
The Checkout API section provides instructions for creating the shopping cart XML. In addition, the Processing an Order section explains how to encrypt your XML document and include it in the form on your checkout page.
In your development environment, your form needs to submit orders to the following URL. You must replace the text [[Merchant-ID]] with the Merchant ID from your Sandbox account.
<form method="POST"
action="https://sandbox.google.com/checkout/cws/v2/Merchant/[[Merchant-ID]]/checkout">
Note: Your production merchant account will have a different Merchant ID and Merchant Key than your Sandbox merchant account. Your code should use the values from the Sandbox account when communicating with the Google Checkout Sandbox service. Similarly, your code should use the values from your production merchant account when communicating with the Google Checkout production service.
Your production system will submit orders to the following URL. You must replace the text [[Merchant-ID]] with the Merchant ID from your production account.
<form method="POST"
action="https://checkout.google.com/cws/v2/Merchant/[[Merchant-ID]]/checkout">
This step is optional. Set up a web service to perform custom calculations for tax, shipping, coupons and gift certificates after the customer has reviewed the order in Google Checkout. The Merchant Calculations API section provides detailed information about custom calculations.
This step is optional. Create a web service that receives and processes new order notifications from Google Checkout. The Notification API and Order Processing API sections thoroughly explain the ways that you can integrate your internal order processing systems with Google Checkout.
After you have thoroughly tested your Google Checkout implementation with the Sandbox service, release your code to your production system to begin accepting orders through Google Checkout. Please remember that you will need to use a different Merchant ID and Merchant Key in your production environment than you use in your test environment. Your Google Checkout buttons will also have different URLs in your test and production environments. You will receive an error if you try to process orders using the wrong Merchant ID or Merchant Key.
Google Checkout Buttons
Comment