Error 52: Unable to send notification to Customer

[libobasay]

i getting this error from authorized.net

 

Response Reason Text: The transaction was authorized, but the client could not be notified; the transaction will not be settled.

 

When Authorize.Net is responding to a script on your server, our system waits 10 seconds for the script to acknowledge it received our response. If we do not get that acknowledgement in 10 seconds, the response's connection will time out, and an error page would be displayed. This error may also occur if the customer submits a transaction and then closes the web page before we have acknowledged the acceptance of the transaction response.

 

If this error occurs, the customer will most likely come across the following error message:

 

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

 

It is important to note that the transaction will be marked as a General Error within your Merchant Interface. The transaction detail will display the Transaction Status, "General Error (Unable to send notification to Customer)".

 

Resolving this Error:

 

• Before doing anything else, have your script start writing to your receipt page. For example: Print your page headers and the first part of the page body. If your script prints to the screen first we will recognize that you and your customer have received the transaction results.

 

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

 

• Verify that your script is not using redirects upon receiving the response from our servers. Redirects are strongly 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 are poor Internet connectivity, overloaded or malfunctioning Internet routing issues. Depending upon your server location and what route is used to send data, it is possible that you may occasionally receive timeouts.

[forza.stiinta]

Hello!

 

I am getting this error too, but I am not very "advanced", I cannot figure out a precise solution for this. Could you please exaplin exactly how to do this?

 

After the processing is done on authorize.net, on what page is the user taken? (what php page on my site is being called?)

[lindsayanng]

I am just guessing here, but to answer the question "which page are you supposed to be directed to after your payment is processed" it SHOULD be checkout_success.php and checkou_process.php would be right before that