In the world of online payments, you may encounter the occasional error code. Some, like common browser errors and 2CO specific errors have their solutions documented (see below), while others receive little explanation. To help remedy this situation, we’ll be providing information about some of the errors you may receive if you’re a customer making purchases or a supplier testing the transaction process.
We’ll start with some of the more common processing errors:
Continue reading…
Why am I getting this “No shipping available to your country!” error?
No shipping available to your country!
(The vendor may need to define a shipping method.)
This error is generated when the supplier is selling a tangible product and the shipping country entered by the customer does not have a valid shipping method set up in the supplier’s 2Checkout account. If the supplier wishes to ship to that country they will need a shipping method that includes it. Suppliers can follow the instructions listed in Chapter 5 of the Users Guide for assistance creating or editing shipping methods.
If you are an international customer and wish to place an order with a supplier who does not ship to your country, you can use the service provided by Access USA to facilitate shipping to your location.
Click here to learn more about Access USA.
Related Article: Reshipping Packages
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.
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’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.
For assistance with debugging your scripts, we suggest that you contact your server’s administrator, webmaster, or hosting provider’s technical support staff. Due to the nature of this particular error, you may also be able to receive assistance from other suppliers of ours. The 500 error message is often due to a coding error in the script, so some of our other suppliers in our tech support forum may be able to help you find the mistake.
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 suppliers.
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:
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 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 is working correctly:
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.
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:
The likely cause is that a banned credit card is being used for a demo transaction. Demo transactions are still sent through parts of our fraud system, and will therefore get caught with this error. Make sure you are not using all 1’s for the credit card number and also make sure that it does not begin with ‘411′. Using sequential numbers can also cause this error to occur, such as using 123456789. A safe one to use for testing is ‘597910143452349′ or any other random number that fits the above criteria while still consisting of 15 or 16 digits.
Vacation Rental Software
Visualizer Photo FX
