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>";

?>

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 set up is correct:

1. Create a new text file using a text editor such as Windows Notepad.
2. Paste the following code into this new file:
   <form method=”POST” action=”[full URL to Your Script Here]“>
   <input type=”hidden” name=”test” value=”1″>
   <input type=”submit” value=”Test Script”> </form>
3. Replace “[full URL to Your Script Here]” with the URL of the script you are attempting to pass back to. Remember that this should be the full URL of your script, including the http:// portion.
4. Save the file as an HTML file, such as “test.html” or “test.htm” to your desktop and close your text editor.
5. Open the file in your web browser and click the “Test Script” button that is displayed.
6. 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 servers configuration. If you see something about “method not allowed” or “error 405″ then the information above pertains to your situation.

Specifying an approved URL at the account level will direct all customers to the same URL after a successful checkout. An approved URL can also be set at the product level by providing an approved URL when creating the product, or by clicking the blue Edit icon under the Actions column for the product on the Products page in your account. Product level approved URLs override the account level approved URL and can direct the customer to a specific location for that product, such as a download page. If multiple products are ordered the customer is provided with multiple approved URLs allowing them to access each product in the sale.

You may also choose to pass the approved URL on the fly by using the x_receipt_link_url parameter. This parameter will override both product and account level approved URLs. The value passed must match the domain registered to the account.

If you are returning the customer to a script on your end it is important to note that parameter information will typically be returned by POST. Parameters however will be returned by GET if either the Header Redirect method is selected or the Plug-and-Play parameter set is used and multiple products are purchased at the same time. Thus if you are using a product level approved URL your return script should be able to handle both methods without breaking. Please Note: You must also have a script set up as the return URL if you wish to receive the pass back information. If you would like this information returned to you, make sure that your return URL ends in the extension of a script. If your return URL ends in any of the following extensions, then pass back will NOT occur, but the customer will still be returned there : .htm, .html, .com, .zip, .pdf, .rar, .doc

Finally, you will determine the method in which your customer is returned to the approved URL. 2Checkout.com provides three methods. You may send the customer to our order processed page which will display a Click here to finalize your order button to redirect the customer, you may bypass the order processed page using a header redirect or you can immediately display your approved URL to the customer while they remain on our server. Your return method can be selected on the Site Management page.

With the Return Method set to Given links back to my website, the customer will be taken to our Order Processed page after completing a successful purchase. This page will feature a Click Here to Finalize Your Order button. When clicked the customer and collected sale parameters will be directed to the provided approved URL.

With the Return Method set to Direct Return, sale parameters will be posted automatically to the approved URL while fetched by our server and displayed to the customer. When using this Direct Return function the URL will be masked to the customer, appearing to still be on the 2Checkout.com domain. This method can be used with redirects as long as each page outputs content more than 255 characters to the browser. If Direct Return encounters a page that redirects without outputting content the process will fail and the customer will be sent to our standard Order Processed page. This occurs usually with a header redirect, specifically content less then 255 characters. This is a common issue as many developers will set their approved URL to a script that processes the return sales parameters then silently forwards the customer to another page. This is usually a thank you or download page for intangible products. The best solution is to handle all post-order processing on the page set as your approved URL, including the thank you message. If no redirects are used, meaning the URL is masked by our servers, then relative links will not point to the correct location. This can be corrected with the use of absolute paths on the approved URL page or by simply using a base tag in the head of the document to provide a reference for the relative paths.

With the Return Method set to Header Redirect the customer will be immediately returned to your approved URL. Using this method, the sale parameters will be returned along with the customer using the GET method.

If you have problems with the return process you’re welcome to contact us at techsupport@2co.com to assist with troubleshooting the issue. Please Note: If you do not specify an approved URL at the account level, product level, or with the x_receipt_link_url parameter the customer will remain on the 2Checkout Order Processed page upon completion of the order.

There is a module that has been developed for osCommerce that is needed to work with 2Checkout. This module is absolutely necessary to be compliant with our system. You may find this module at the following URL:

http://addons.oscommerce.com/info/5343

It is a common problem to have the sales work in the 2CO account but not the osCommerce cart after a sale. This is because there has to be a return URL set up in your account to tell the 2CO system were to send the sale information after it is placed. osCommerce needs this information to correctly process and finish the sale on your end. This URL should be entered under the approved URL field on the Site Management page in the sellers area. If you installed OSC to a directory other than the default directory, you will need to use that directory structure here. Be sure to replace “www.your-domain.com” with your actual domain name.

http://www.your-domain.com/catalog/pm2checkout_process.php

* The Pending URL field is no longer used and may be left blank as 2Checkout no longer accepts e-checks as a payment method.