Hi-
We are getting an error message during several of our transaction. The message says the script timed out while it was trying to post transaction results to it. This is what Auth.net recommends:
Thank you for contacting Authorize.Net!
This transaction resulted in a general error called an error 52.
This error is explained below.
When Authorize.Net is responding back to a script on your server our
system waits 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. In
this case the customer will see the transaction results on an error
page that Authorize.net generates.
If this happens we will either send an e-mail to you indicating:
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 a result of the attempt to charge your
credit card.
or
The transaction will be declined within your Merchant Interface. The
transaction detail will display (Unable to send notification to
Customer). If the customer closes the browser window before we
receive
data from your script to print to the screen we will change the
transaction response reason code to 52.
To prevent these errors 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 have received the transaction results.
To resolve this issue:
- Before doing anything else start writing to your receipt page. For
example: print your page headers and the first part of the page
body.
- 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 receipt of the
response from our servers. Redirects strongly 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 are
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 timeouts.
So, how and where, please?!
Thanks!
