<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>2Checkout.com &#187; passback</title>
	<atom:link href="http://www.2checkout.com/blog/tag/passback/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.2checkout.com</link>
	<description>merchant account / credit card processing alternative</description>
	<lastBuildDate>Mon, 06 Feb 2012 21:37:21 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Why do I get an HTTP Error 500 (Internal Server Error) on Passback?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-500-internal-server-error-on-passback/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-500-internal-server-error-on-passback/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[server]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/why-do-i-get-an-http-error-500-internal-server-error-on-passback/</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>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.</p>
<p>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&#8217;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.</p>
<p>For assistance with debugging your scripts, we suggest that you contact your server&#8217;s administrator, webmaster, or hosting provider&#8217;s technical support staff. </p>
<p>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 users.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-500-internal-server-error-on-passback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why do I get an HTTP Error 404 (File Not Found) on Passback?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-404-file-not-found-on-passback/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-404-file-not-found-on-passback/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[approved url]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[parameters]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return url]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/why-do-i-get-an-http-error-404-file-not-found-on-passback/</guid>
		<description><![CDATA[An HTTP 404 File Not Found error indicates that the URL specified as for your script is incorrect. For the pass back to function, 2CO must be able to locate and access the script and post the variables to it. HTTP errors are not generated specifically by 2Checkout. They are a part of the HTTP [...]]]></description>
			<content:encoded><![CDATA[<p>An HTTP 404 File Not Found error indicates that the URL specified as for your script is incorrect. For the pass back to function, 2CO must be able to locate and access the script and post the variables to it.</p>
<p>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.</p>
<p>To correct this issue, follow these steps:</p>
<ol>
<li>Login to your account.</li>
<li>Click on the <strong>Account</strong> tab and then select the <strong>Site Management</strong> sub-category.</li>
<li>Check the URL that is currently entered under the Approved URL field and make sure that it is correct.</li>
<li>Click <strong>Save Changes</strong>.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-404-file-not-found-on-passback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why do I get an HTTP Error 403 (Forbidden) on Passback?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-403-forbidden-on-passback/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-403-forbidden-on-passback/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/why-do-i-get-an-http-error-403-forbidden-on-passback/</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>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.</p>
<p>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.</p>
<p>To test and see if your file is working correctly:</p>
<ol>
<li>Open your web browser.</li>
<li>Type in the full URL to your script or return page (including the http://www. part) and press enter.</li>
<li>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 &#8216;forbidden&#8217; or &#8216;error 403&#8242; then the information above pertains to your situation.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-403-forbidden-on-passback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Can I have more than one passback URL?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/can-i-have-more-than-one-passback-url/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/can-i-have-more-than-one-passback-url/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[approved url]]></category>
		<category><![CDATA[multiple]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return]]></category>
		<category><![CDATA[url]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/can-i-have-more-than-one-passback-url/</guid>
		<description><![CDATA[It is possible to use multiple pass back URLs, or approved URLs, with our system. If you are using our free Plug and Play shopping cart, then you simply need to add the URLs to the products themselves to achieve this. You may specify the Approved and Pending* URLs on each individual product that you [...]]]></description>
			<content:encoded><![CDATA[<p>It is possible to use multiple pass back URLs, or approved URLs, with our system. If you are using our free Plug and Play shopping cart, then you simply need to add the URLs to the products themselves to achieve this. You may specify the Approved and Pending* URLs on each individual product that you have created in our system. These URLs will over-ride any URL set on the Site Management page. We will then use this URL to return the customer to when it is purchased.</p>
<p>Having multiple return URLs can conflict with the return features that we have available. The &#8220;Direct Return&#8221; and &#8220;Header Redirect&#8221; methods will make the customer skip the Order Processed page and go directly from the Billing Information page of the checkout process to your approved URL. We can only return the customer to one page at a time, so when multiple products are purchased that have different approved URLs, the immediate redirect is disabled for that sale. The customer will then be presented with a list of the products or services they purchased along with their respective return URLs to click on our Order Processed page. More information on the return process and supported parameter sets can be found in the Related Articles at the bottom of the article.</p>
<p>If you are using a third party or customer cart or script, then multiple return URLs may still be used, but the implementation of this would have to be on your end as the product information in the 2CO database is not used. If you are not passing in product_id parameters, then you are not using the Plug and Play cart of ours. To achieve multiple return URLs with a customer cart or third party cart, you may use the x_receipt_link_url parameter to control where the customer is returned to. The value of this parameter MUST match the domain that is listed on your 2Checkout.com account for security reasons. You would then need to design your cart or script to pass this parameter into our system along with the appropriate value for that sale.</p>
<p><strong>*The Pending URL field is no longer used and may be left blank as 2Checkout no longer accepts e-checks as a payment method.</p>
<p><strong>Related Articles</strong></p>
<ul>
<li><a href="http://www.2checkout.com/blog/knowledge-base/suppliers/tech-support/passbacks-and-returns/how-does-the-return-process-work">How Does The Return Process Work?</a></li>
<li><a href="http://www.2checkout.com/blog/category/knowledge-base/suppliers/tech-support/3rd-party-carts/parameter-sets">Parameter Sets</a></li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/can-i-have-more-than-one-passback-url/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>What PHP code can I use to test return parameters?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/what-php-code-can-i-use-to-test-return-parameters/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/what-php-code-can-i-use-to-test-return-parameters/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[parameters]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[php]]></category>
		<category><![CDATA[return]]></category>
		<category><![CDATA[script]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/what-php-code-can-i-use-to-test-return-parameters/</guid>
		<description><![CDATA[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 [...]]]></description>
			<content:encoded><![CDATA[<p>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.</p>
<p>Additionally, you can make use of our <a href="http://developers.2checkout.com/return_script">developers.2Checkout area</a> to test out your own return script with sample return data. This can assist you when building your 2Checkout return script.</p>
<pre>
&lt;?php //display all post and get parameters

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

?&gt;</pre>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/what-php-code-can-i-use-to-test-return-parameters/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why do I get an HTTP Error 405 on Passback?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-405-on-passback/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-405-on-passback/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[error]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return]]></category>
		<category><![CDATA[server]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/why-do-i-get-an-http-error-405-on-passback/</guid>
		<description><![CDATA[This is a problem with your script and/or your web server. The error means that you are attempting to pass back to a file does not have the necessary permissions on the server to receive Post information from another script. If you have administrative or root access to your server, be sure that this file [...]]]></description>
			<content:encoded><![CDATA[<p>This is a problem with your script and/or your web server. The error means that you are attempting to pass back to a file does not have the necessary permissions on the server to receive Post information from another script. If you have administrative or root access to your server, be sure that this file has been set up to be treated as a script and that the appropriate user accounts have read and execute permissions on the script. If you are in a shared hosting situation, please contact your server administrator or the support department for your host.</p>
<p>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.</p>
<p>To test and see if your file set up is correct:</p>
<ol>
<li>Create a new text file using a text editor such as Windows Notepad.</li>
<li> Paste the following code into this new file:<br />
<strong> &lt;form method=&#8221;POST&#8221; action=&#8221;[full URL to Your Script Here]&#8220;&gt;<br />
&lt;input type=&#8221;hidden&#8221; name=&#8221;test&#8221; value=&#8221;1&#8243;&gt;<br />
&lt;input type=&#8221;submit&#8221; value=&#8221;Test Script&#8221;&gt; &lt;/form&gt;</strong></li>
<li> Replace &#8220;[full URL to Your Script Here]&#8221; 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.</li>
<li> Save the file as an HTML file, such as &#8220;test.html&#8221; or &#8220;test.htm&#8221; to your desktop and close your text editor.</li>
<li> Open the file in your web browser and click the &#8220;Test Script&#8221; button that is displayed.</li>
<li> 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 &#8220;method not allowed&#8221; or &#8220;error 405&#8243; then the information above pertains to your situation.</li>
</ol>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-do-i-get-an-http-error-405-on-passback/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How Does The Return Process Work?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/how-does-the-return-process-work/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/how-does-the-return-process-work/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[approved url]]></category>
		<category><![CDATA[direct return]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/how-does-the-return-process-work/</guid>
		<description><![CDATA[After the successful completion of a sale 2Checkout.com can return the customer and sale parameters to a script or page on your site. This URL can be entered on the Site Management page by clicking the Account tab followed by the Site Management sub-category. Specifying an approved URL at the account level will direct all [...]]]></description>
			<content:encoded><![CDATA[<p>After the successful completion of a sale 2Checkout.com can return the customer and sale parameters to a script or page on your site. This URL can be entered on the Site Management page by clicking the <strong>Account</strong> tab followed by the <strong>Site Management</strong> sub-category.</p>
<p>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.</p>
<p>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.</p>
<p>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. <em>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</em></p>
<p>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.</p>
<p>With the Return Method set to <strong>Given links back to my website</strong>, 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.</p>
<p>With the Return Method set to <strong>Direct Return</strong>, 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.</p>
<p>With the Return Method set to <strong>Header Redirect</strong> 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.</p>
<p>If you have problems with the return process you&#8217;re welcome to contact us at techsupport@2co.com to assist with troubleshooting the issue. <em>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.</em></p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/how-does-the-return-process-work/feed/</wfw:commentRss>
		<slash:comments>11</slash:comments>
		</item>
		<item>
		<title>Where do I input the URL of the script on my site I want you to pass back to?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/where-do-i-input-the-url-of-the-script-on-my-site-i-want-you-to-pass-back-to/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/where-do-i-input-the-url-of-the-script-on-my-site-i-want-you-to-pass-back-to/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[approved url]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/where-do-i-input-the-url-of-the-script-on-my-site-i-want-you-to-pass-back-to/</guid>
		<description><![CDATA[To specify a URL for our system to pass back to, please follow these steps: Click on the ‘Account’ tab. Click on the ‘Site Management’ sub category. Input the URL into the Approved and Pending URL boxes on this page. Click &#8216;Save Changes&#8217;. If you our using our free Plug and Play shopping cart, then [...]]]></description>
			<content:encoded><![CDATA[<p>To specify a URL for our system to pass back to, please follow these steps:</p>
<ol>
<li>Click on the ‘Account’ tab.</li>
<li>Click on the ‘Site Management’ sub category.</li>
<li>Input the URL into the Approved and Pending URL boxes on this page.</li>
<li>Click &#8216;Save Changes&#8217;.</li>
</ol>
<p>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.</p>
<p>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.</p>
<p>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</p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/where-do-i-input-the-url-of-the-script-on-my-site-i-want-you-to-pass-back-to/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Why won’t my parameters pass back?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-wont-my-parameters-pass-back/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-wont-my-parameters-pass-back/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[parameters]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/why-wont-my-parameters-pass-back/</guid>
		<description><![CDATA[Parameters are only passed back to a script. This means your Approved URL needs to end in a script extension (cgi, pl, php, asp, jsp, ETC).]]></description>
			<content:encoded><![CDATA[<p>Parameters are only passed back to a script.  This means your Approved URL needs to end in a script extension (cgi, pl, php, asp, jsp, ETC).</p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/why-wont-my-parameters-pass-back/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>How does a direct return work?</title>
		<link>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/how-does-a-direct-return-work/</link>
		<comments>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/how-does-a-direct-return-work/#comments</comments>
		<pubDate>Sat, 30 Dec 2006 07:00:00 +0000</pubDate>
		<dc:creator>knowledgebase</dc:creator>
				<category><![CDATA[Passbacks and Returns]]></category>
		<category><![CDATA[approved url]]></category>
		<category><![CDATA[direct return]]></category>
		<category><![CDATA[passback]]></category>
		<category><![CDATA[return]]></category>

		<guid isPermaLink="false">https://192.168.2.217/fresh/blog/2006/12/30/how-does-a-direct-return-work/</guid>
		<description><![CDATA[The direct return works through a spider on 2Checkout.com that does an HTML GET from our server with all the variables to the seller&#8217;s server. The spider prints to the screen whatever the seller&#8217;s server returns for the buyer to see.]]></description>
			<content:encoded><![CDATA[<p>The direct return works through a spider on 2Checkout.com that does an HTML GET from our server with all the variables to the seller&#8217;s server. The spider prints to the screen whatever the seller&#8217;s server returns for the buyer to see.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.2checkout.com/blog/knowledge-base/merchants/tech-support/passbacks-and-returns/how-does-a-direct-return-work/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

