2Checkout.com » approved url

Why Are the Images/Links on my Approved URL Broken?

knowledgebase — Fri, 04 May 2007 14:34:57 +0000

When the Return Method is set to “Direct Return”, your Approved URL page will be fetched and displayed to the customer while they remain on 2Checkout’s server. Because of this, images and links that use relative paths will not resolve correctly, resulting in broken images and incorrect link destinations.

To fix this, you will need to specify a base URI for your Approved URL. This can be accomplished by inserting the following line between the tag of your page:

The URL specified after ‘href=’ should be changed to your Approved URL.

Can I specify the return URL ‘on the fly’?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

Yes, this is possible. You may pass in a parameter called x_receipt_link_url to control where the customer is returned to on a per-sale basis. Keep in mind that this parameter will over-ride the approved URLs set in your account. Using this method, you could create a special button or link that would return the customer to a different page on your site than is set up on the Site Management page. This is useful for ‘promotional’ type sites as you can avoid having to make any configuration changes to your actual account.

If you are using buttons on your site to sell your goods through 2Checkout, you would add a single line to the button such as this:

This must go between the opening and closing form tag that you see when you view your existing code.

If you are using links to sell your goods through 2Checkout, then you would add this parameter to your links to specify the approved URL, such as this:

&x_receipt_link_url=http://www.your-site.com/return.php

Notice that in both of the above examples, the FULL path is used for the value of this.

Important Note: For security reasons, the domain on your account and the domain that hosts the pass back page must match exactly for this to work correctly. For example, if you have http://www.your-site.com specified on your account, you could pass back to http://www.your-site.com/pages/pass.php but not to http://www.your-other-site.com/pages/pass.php.

Why do I get an HTTP Error 404 (File Not Found) on Passback?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

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 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 correct this issue, follow these steps:

Login to your account.
Click on the Account tab and then select the Site Management sub-category.
Check the URL that is currently entered under the Approved URL field and make sure that it is correct.
Click Save Changes.

Can I have more than one passback URL?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

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.

Having multiple return URLs can conflict with the return features that we have available. The “Direct Return” and “Header Redirect” 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.

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.

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

Related Articles

How Does The Return Process Work?

Parameter Sets

How Does The Return Process Work?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

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 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.

Where do I input the URL of the script on my site I want you to pass back to?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

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 ‘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

I changed the Return URL on the Site Management Page, but after the purchase the buyer still returns to the old link?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

Although the Approved URL was changed on the Site Management page there may still be an approved URL set at the product level, or you may be passing in a different approved URL using the x_receipt_link_url.To ensure customers are redirected to the Approved URL listed on the Site Management page you will need to be certain that their isn’t a product level Approved URL and that you aren’t passing in a return URL with the x_receipt_link_url parameter.

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

x_receipt_link_url

Product Level Approved URL

Site Management tab

The x_receipt_link_url will take precedence over all other return URLs, and the URL listed on the Site Management tab will be used by default if the other two are absent.

Why when you click the confirmation button, instead of redirecting to the return URL, it redirects to a different page than I set up in the Return page?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

Please make sure that the return link you set up for each product you added to our database either has NO return URL, or that it has the URL you want the buyer to be passed back to assigned to it. If the one with the product is different, then it will override the one you set up in the Return page.

If all customers will be redirected to the same URL, you may want to only provide the URL in the Site Management page rather than at the product level.

Why are my buyers being returned to the wrong URL?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

Please Check where you add/edit products in the Admin to see if you set up a return URL that is different than where you want the buyer to be sent to. That return will override the return URLs you set up in the Return page.

How does a direct return work?

knowledgebase — Sat, 30 Dec 2006 07:00:00 +0000

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’s server. The spider prints to the screen whatever the seller’s server returns for the buyer to see.