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.

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://www.osCommerce.com/community/contributions,904

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 can be set up on the Look & Feel setting page of the 2CO Classic Sellers Area (V2). You will find this link under the Helpful Links section of your account homepage. This URL can also be setup on the new VA sellers area Site Management page.

The URL below must be in both the Pending* and Approved URL boxes. 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.

]]>