Below is a sample PHP script that will catch all Post and Get parameters upon return and print the names of the parameters with their value back to the screen. This may help you develop your return process. Please note that we do not support third party scripts, so we also can not troubleshoot the script itself. It is being provided for your convenience only. We can help you if you are having problems receiving any passback parameters though.

Additionally, you can make use of our developers.2Checkout area to test out your own return script with sample return data. This can assist you when building your 2Checkout return script.

<?php //display all post and get parameters

	echo "<h1>Get Parameter/s:</h1>";
	echo "<pre>";
	if($_GET)
		print_r($_GET);
	else
		echo "There are no get parameters.";
	echo "</pre>";
	echo "<hr/>";
	echo "<h1>Post Parameter/s:</h1>";
	echo "<pre>";
	if($_POST)
		print_r($_POST);
	else
		echo "There are no post parameters.";
	echo "</pre>";

?>

Creating Product Options

To create or edit the product options themselves, go to your products list. On your products list page, you will see an ‘Edit Product Options’ link. Clicking it will link you to the ‘edit product options’ page.

Once you find your way to the ‘edit product options’ page, you will see a list of all your product options. This list contains data fields and existing option names, option values, and any surcharges associated with them. It also has the ability for deleting options. To create new product options, fill in the set of data fields near the top of the page. Choose a name for the new option, as well as any values and surcharges.

• Option Name: The name of the option you create. Once you create it, it will appear in your product options list as a link.
• Option Values: These are the values assigned to the option name you create. They are the actual choices offered for the given option. For instance, if you have ‘Size’ as an option, the values might be ‘Small’, ‘Medium’, and ‘Large’.
• Value Surcharge: This is the additional cost you may charge customers to choose a certain option. Surcharges may be specified in whole numbers (5) or as decimals to two places (5.00, 4.99, etc.). You do not have to add surcharges.

For example, you own a clothing business and sell a variety of apparel. The clothing you sell is not made with just one type of material. All the apparel you sell is made with one of three choices: cotton, wool, or silk. You want your customers to be able to choose what material they want their clothes to be fashioned from. You will create a product option to do this. As the option name, you choose ‘Material’ and enter it into the correct field. As for option values, you would set three: cotton, wool, and silk. You decide to add a surcharge for wool and silk, as the base price advertised on your site is for cotton, and we know that wool and silk are more expensive. So, in the corresponding surcharge fields, you enter the appropriate amounts. For cotton, you would enter 0.00 to specify no surcharge. You decide to charge an extra $10.00 for wool. Enter 10.00 to do so. As for silk, well that is expensive, so you decide to charge an additional $25.00 for that. 25.00 should be entered to accomplish this. When you are finished, click on ‘Save Changes’ to save your options. This will effectively add an option called ‘Material’ to your product options list.

The example used here is precisely that, and the values and surcharges displayed are totally arbitrary. The actual number and types of options and values are unlimited. If, instead of material, you want to offer different sizes or colors, so be it. This system allows you to create
product options as unique as you want, and as you see fit.

Editing Existing Product Options

To edit existing product options, click on the name of the one you wish to edit. It will appear in your list as a link. It will lead you to a page with another set of data fields and delete options. Most of the fields will have previously saved data, but two will be empty. To edit an existing value, simply click in the correct field and change it to what you want. To change the name of the option, click that field and enter what you want. To delete a value, check the box next to the relative values. To add a new set of values, enter the suitable option value and surcharge. When you are totally finished adding, editing, or deleting, click on the ‘Save Changes’ button.

Removing Product Options

To delete a product option on the ‘edit product option’ page, check the delete option box next to the corresponding product option. Check any and all options you wish to delete. To finalize your actions, click ‘Save Changes’.

If you created your products using the Product Upload method, you may create product options for them, as well. You must create your product options for each product using the explanation above in this section. Product options are NOT created in the CVS Template.

Associating Product Options With Your Products

To associate or dissociate product options, you must do this from the ‘edit product’ page. This page is found by going to your products list and clicking on an ‘Edit’ link. The ‘Edit’ link you click should be that of whichever product you want to add options to. At the bottom of the ‘edit product’ page, you will see a list of all available options you created. This list appears in the form of a table, with labeled headings. There are four headings:

1. ‘Available’: The options associated (available) with the particular product you are editing will have a check in the box under the ‘Available’ heading. If the box is not checked, that set of options is not available for (associated with) that product. Warning Product Option Association To associate or dissociate a set of options, simply check or uncheck the corresponding
box, as needed.
2. ‘Option’: This denotes the name of the product option.
3. ‘Values’: This displays the values for each option.
4. ‘Surcharge’: This displays the extra charges you may charge to customers for choosing a given product option.

When finished, click the ‘Save Changes’ button at the bottom of the page. This will save your changes.

If you are going to use a picture of a credit card or a credit card company logo on your web site, it must be clearly and immediately adjacent to the phrase “2Checkout.com is an authorized retailer for (your business name.)” Per Credit Card Association Rules, unless your company has a direct business relationship with the credit card company and is authorized to display the credit card or the logo, the image must be removed from your web site.

Credit card association rules state that only a merchant account holder may display credit card logos on their websites. 2CO does not provide you with a merchant account. You can continue to display these logos, as long as immediately above, beside, or below the logos, there is a clear statement that 2CO is your authorized retailer.

Alternatively, you can display the logos shown here. Right click on the image of your choice below and choose “Save Picture as…” to save as a file on your computer.

Please also see 2CO Certified for “2CO Certified Seller” buttons.

An HTTP 403 Forbidden error indicates that due the set up of your script and/or server, the viewer does not have permission to view this page. For the pass back to function, 2CO must be able to access the script and post the variables to it.

HTTP errors are not generated specifically by 2Checkout. They are a part of the HTTP protocol and are common amongst all web servers. It is therefore beyond the realm of 2Checkouts support to provide you with specific instructions for making these changes as every server is set up differently and 2CO does not provide server administration services as part of our support plan.

To test and see if your file is working correctly:

1. Open your web browser.
2. Type in the full URL to your script or return page (including the http://www. part) and press enter.
3. If you receive the message again, the problem is in your script and/or on your server. Note that the exact wording of the error message may vary slightly depending on your browser and your server. But if you see something about ‘forbidden’ or ‘error 403′ then the information above pertains to your situation.

An HTTP Error 500 (Internal Server Error) indicates that there is a problem inside of your script or the servers configuration. This error is most likely caused by a typo in the code or an invalid or illegal use of a function within the script. For the pass back to function correctly, then your script must be correctly set up.

HTTP errors are not generated specifically by 2Checkout. They are a part of the HTTP protocol and are common amongst all web servers. It is therefore beyond the realm of 2Checkout’s support to provide you with specific instructions for making these changes as every server is set up differently and 2CO does not provide server administration services as part of our support plan.

For assistance with debugging your scripts, we suggest that you contact your server’s administrator, webmaster, or hosting provider’s technical support staff. Due to the nature of this particular error, you may also be able to receive assistance from other suppliers of ours. The 500 error message is often due to a coding error in the script, so some of our other suppliers in our tech support forum may be able to help you find the mistake.

We have observed that this error is experienced in certain web browsers more than in others, in particular within Internet Explorer. If your return page or script does not output at least 530 characters, this can potentially cause a MIME header error. Mozilla based browsers such as Firefox seem to be able to handle these pages and will display either the real error or the small output when Internet Explorer has problems. Since this issue is an issue with the browser software itself, there is little 2Checkout can do to control this. If you are receiving this error, please try to increase the output that your return page generates to more than 530 characters or try a different web browser to see if you observe different results. Note that this is not a solution for all HTTP 500 error messages, but it is meant to be a useful step in debugging your script and has been reported as a successful step by some of our other suppliers.