We’ll start with some of the more common processing errors:

• “100 Approved” – This error is specific to customers who purchase with an Amex card. It means the order has been declined and they need to contact the issuing bank.
• “238 Invalid Currency” – Most commonly received when the customer uses an AmEx or a prepaid card to purchase something in a currency that is not native to that card.
• “401 Voice” – The issuing bank wants to speak with the card holder to confirm the order.
• “402 Default Call” – This error is specific to customers who are using an Amex card. It means that they have entered the wrong CVV. The customer should be entering the four digits on the front of the card in the lower left corner, not the three digits on the back.
• “530 Do not honor” – There is something is wrong with the information the customer entered. The customer may need to contact their bank to resolve this issue.
• “606 Invalid Tran Type” – This error usually means one of two things, first the customer is attempting to make a purchase with an AmEx card in a currency other than US Dollars. Second the customer is attempting to make a purchase with a prepaid credit card that we cannot accept.

If there are other errors you would like to see us discuss or you know of any helpful resources (websites, books, etc.), please share them in the comments below.

Related Articles:

• Why do I get parameter error when adding a multiple buy button on the same page?
• Why am I getting a Parameter Error, even though all parameters are setup correctly?
• Receiving parameter error message from HTML code on web page, what could cause this?
• Why am I getting “The sale has been rejected” even when passing demo=Y ?
• Error Message: No shipping available to your country!
• Why do I get an HTTP Error 403 (Forbidden) on Passback?
• Why do I get an HTTP Error 404 (File Not Found) on Passback?
• Why do I get an HTTP Error 405 on Passback?
• Why do I get an HTTP Error 500 (Internal Server Error) on Passback?

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 our shipping method tutorial 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

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.

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:

1. Login to your account.
2. Under the ‘Helpful Links’ section, click on ‘Settings’ near the ‘Look and
   Feel’ section.
3. Check the URL that is currently entered there and correct any mistakes that
   it may contain.
4. Click ‘Save Changes’.

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:

1. Open your web browser.
2. Type in the full URL to your script or return page (including the http://www. part) and press enter.
3. 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 ‘forbidden’ or ‘error 403′ then the information above pertains to your situation.

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.