Navigation: Modules > Google Checkout > Google Checkout Configuration

Google Checkout Configuration

 Print this Topic    Previous page  Parent page  Next page

 

If you are not familiar with table windows, please read Working with table windows first.

 

The Google Checkout configuration window lets the admin configure settings that affect the Google Checkout module. This window has two columns - Google Checkout Config Name and Google Checkout Config Value. All the cells under Google Checkout Config Name are informational and most of the cells under Google Checkout Config Value are editable. The following is a description of each row:

 

Mode of Operation

Choose if the module should use the Google Checkout Sandbox (Google Checkout test environment) or the live  Google Checkout servers. You can use the test server to check your setup and then move this field to live to start accepting real customer payments. Valid values are Test/Demo for the test server and Live for the live server. The edit mode for this field is a dropdown list.

Google Checkout Merchant ID

The merchant ID associated with your Google Checkout account. You will be able to find this information by signing into your Google Checkout account and clicking  on Settings > Integration. The edit mode for this field is a textbox.

Google Checkout Merchant Key

The merchant key associated with your Google Checkout account. You will be able to find this information by signing into your Google Checkout account and clicking  on Settings > Integration. The edit mode for this field is a textbox.

Google Checkout Payment Type

Choose if the customer is shown only a one-time payment button when he/she chooses to pay or subscription buttons. Valid values are:

 

▪Use subscription payments where possible
▪Always use one-time payments

 

If you choose to always use on-time payments, the customer is presented with one Google Checkout payment button with the total that they have to pay this time. When the next invoice is generated, the customer will have to come back to the user area and go through the same payment process to make another payment.

 

If you choose to use subscription payments where possible, the customer is presented with multiple Google Checkout payment buttons, one for each term (example, a button for monthly payments and another button for yearly payments). The customer has to click on each button and make the Google Checkout subscription payments to complete the entire payment. However, after this, the customer will not need to come back to the client area and make fresh payments every time an invoice is generated.

 

The edit mode for this field is a dropdown list.

API callback URL

The API callback URL is the URL at which Google Checkout notifies your installation of PawBill about new payments and changes in payment state. You will need to copy the URL shown in this field, sign into your Google Checkout account and click on Settings > Integration. Paste the URL into the field named API callback URL.

 

Additionally, you may enable "Require notification acknowledgments to specify the serial number of the notification" under advanced settings to make the notifications more reliable. PawBill always includes the serial number with every notification.

 

This field is not editable