Showing results for 
Search instead for 
Did you mean: 

Your script timed out while we were trying to post transaction result to it.


I am in way over my head and need some help. I know enough html code to create my own website ( and incorporate for credit card transactions. To my surprise a test transaction actually worked but produced an error message as follows:

Authorize.Net Merchant,

Your script timed out while we were trying to post transaction to it.
   Transaction ID: 2976728987
Transaction Result: This transaction has been approved.

The following message was displayed to the customer:

------------------------------An error occurred while trying to report
this transaction to the merchant. An e-mail has been sent to the merchant
informing them of the error. The following is the result of the attempt to
charge your credit card.

This transaction has been approved.


After speaking to they sent me the following explanation:

Response Reason Code: 52
Response Reason Text: The transaction was authorized, but the client could not be notified; the transaction will not be settled.
Integration Team Suggestions: When Authorize.Net is responding back to a script on your server, our system waits up to 10 seconds for a response. If we do not get a response in 10 seconds, our server will time out and display an error page. The first thing that you will need to look for is the order that your script executes. It is very important that something is printed to the screen before any other process is started. If your script prints to the screen first, we will recognize that you are receiving the information. The most effective method would be to PRINT the headers, and a line of text such as "Processing, please wait."

To resolve this issue:

Check that your script permissions are correct and that it can accept an HTTPS POST.
Check that the script is not completing other functions before writing to the screen, such as writing to a database or sending emails.
Please check to see if there are different processes that are used in your script for approvals, declines, or errors. Check each process to be sure that they will write to the screen before any other functions.
Check if your script is using redirects immediately upon receipt of the response from our servers. Redirects are discouraged because they can potentially interfere with the process.
On occasion, timeouts will occur that are outside of the control of your script or our servers. Typical reasons for these timeouts include Internet traffic, your server is overloaded or malfunctioning, or Internet routing issues. Depending upon your server location and what route is used to send data, it is possible that you may occasionally receive the message you are seeing.

Thank you for contacting our Authorize.Net Customer Support.  The Authorize.Net Knowledge Base, located at, is available 24x7 to provide you with comprehensive answers to virtually any customer support question, as well as useful links to video demos, help files and more. The video tutorials can be found at If you need help, we strongly recommend starting with these resources.

I am not competent to implement the fix for this problem and need some guidance on finding someone who can help.




about the URL. Read the red text.


Relay Response Basics

Relay Response is a feature available to merchants using Server Integration Method (SIM) or Simple Checkout. It instructs the payment gateway to return transaction results to the merchant using an HTML form POST to a specified URL on the merchant's Web server. A script or program at the URL can be used to create a custom receipt page using the transaction information. The custom receipt page is then relayed back to the customer's browser. Relay Response does not redirect the end user back to the merchant’s server, but relays the page content to the end user instead of displaying the Authorize.Net default receipt page.


session is gone because it render on If you need to pass something pass it as a merchant defined fields.

We had problem with the "Your script timed out while we were trying to post transaction results to it." error.  All the time was suggesting that the problem was in the network, that we should check with our web hosting provider. All suggestions by were incorrect.

The solution was: had proper SSLCipherSuite (cipher in proper order) and SSLHonorCipherOrder ON.

After we investigated tens of failed and non-failed transactions and looked at tcpdump data for traffic to, it was clear that every time there was "Your script timed out while we were trying to post transaction results to it." the SSL handshake was not finished. The difference was always "Pubkey Length".

Simply, prefer ECDHE + AESGCM cipher. The is a good start.