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.

2Checkout can return the customer to an Approved or Pending URL after a sale. If we can immediately verify the availability of funds, then the customer is sent to the Approved URL. If we are not able to do this, then they will go to the Pending URL. For example, a digital check would always be sent to the Pending URL because we can not immediately verify the availability of funds. A confirmation email is sent out when the check clears, but no pass back ever occurs after the initial sale. Another way of saying this is that if the credit_card_processed parameter is “Y”, then the customer goes to the Approved URL, but if it is “K” then they will go to the Pending URL.

You may also specify the Approved and Pending URL on the product level in the Classic Sellers Area as well as the new Vendors Administration Area. Any URL set here over-rides the main ones set on the Look and Feel settings page.

The terms pass back URL and return URL generally mean the same thing and can be used interchangeably. However, pass back refers to the information or parameters that we send back to your site after a sale. Return refers to the actual process of sending the customer there. Pass back URL and return URL are the same because in this context it simply means “where do you want return/pass back to go to?”

Additionally, the x_receipt_link_url parameter can be used to specify the return URL on the fly. If you take this approach, this parameter will over-ride any URL set on the Look and Feel settings page. You may use this parameter to have a specific button or link use a return URL that is different than the ones set on the Look and Feel page. If you do this, your return script would need to check the value of the credit_card_processed parameter itself to determine what the appropriate course of action should be. Another way of saying this is that, since this parameter only allows you to specify one return URL rather than both the Approved and Pending URLs, whatever script it is returning the customer to will need to check the value of the credit_card_processed parameter to determine whether they should provide the customer with a “Thank You for Ordering! / Here is Your Download!” page, or a “You will receive more information when your payment is approved” screen.

It is also important to note that if x_receipt_link_url is used, then the return page must match the domain on the account. If the URL is saved on the Look and Feel page or the product level, then we can return them anywhere. In short, if the URL is in our database we can return them there. If not, then it must match for security reasons.

2Checkout.com will also POST the information to your return URL in all cases, regardless of whether Direct Return is enabled or disabled. It is important to note that we will not allow a mix of GET and POST in the return process. If you are trying to return the customer to “http://www.yoursite.com/your_script.php?param=value” then we actually return the customer to “http://www.yoursite.com/your_script.php” and the ‘param=value’ will be returned as POST information with the rest of the sales information that we normally pass back.

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

The order of precedence for return from highest to lowest is:

1. x_receipt_link_url
2. Product Level
3. Look and Feel page

The x_receipt_link_url will take precedence over all other return URLs, and the Look and Feel page will be used by default if the other two are absent.

1. Click on the ‘Account’ tab.
2. Click on the ‘Site Management’ sub category.
3. Input the URL into the Approved and Pending URL boxes on this page.
4. Click ‘Save Changes’.

If you our using our free Plug and Play shopping cart, then you may specify an Approved and Pending URL on each product individually. You should see the options for these URLs while creating a product, but to add them to existing products, click Edit next to the product you wish to add them on. Any return URLs set on the product itself will over-ride the ones that you set on the Look and Feel page.

The Approved and Pending URLs may be the same URLs if you wish, but they can also be separate URLs. We will send the customer to the Approved or Pending URL depending on what the value of the credit_card_processed parameter is. It is only either Y or K. We will set the value of this to Y if we can immediately verify the availability of funds after the sale and then send the customer to your return Approved URL. We will set it to K and return them to the Pending URL if we can not immediately verify the availability of funds, such as if the customer paid by digital check. If you put the URL to the same script in both boxes, then the script should check the value of this parameter to determine the needed course of action.

The URL you enter here must have the extension of a script. If a static HTML file is used, such as an .htm or .html file, we will still send the customer back to that page. However, we will not pass back any details of the sale with them unless it is 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