|
Elizabeth
|
July 30, 2017 at 6:48 pm
Authorize.Net Merchant,
Your script timed out while we were trying to post transaction results to it.
Transaction ID: 60611902023
Transaction Result: This transaction has been approved.
The following message was displayed to the customer:
——————————The reporting of this transaction to the Merchant has timed out. 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.
It is advisable for you to contact the merchant to verify that you will receive the product or service.
|
|
Josh
|
July 31, 2017 at 1:55 pm
Hi Dorian,
Here’s what Authnet says about the error, along with some troubleshooting/testing items:
https://support.authorize.net/authkb/index?page=content&id=A663&impressions=false
|
|
Elizabeth
|
July 31, 2017 at 6:07 pm
That really doesnt help because we use what you guys provide. I dont know what to do. Use SIM or AIM?
|
|
Josh
|
July 31, 2017 at 6:27 pm
Hi Dorian,
You’re correct that you use the gateway integration Event Espresso provides, however much of what’s in the guide I linked deals primarily with hosting, and you’re not using hosting that Event Espresso provides. I’ll break out the parts from the guide that applies to hosting and other parts that affect the gateway below:
The Relay URL does not include a non-standard port for HTTP or HTTPS traffic. Authorize.Net uses the default ports 80 (HTTP) and 443 (HTTPS) for Relay Response and all other API services. Ports appear in URLs after the domain name, and have a colon (” : “) before it, e.g. https://secure.authorize.net:443/gateway/transact.dll is on port 443. If no port is specified, this issue does not apply to you.
Your web server is available on the public Internet, and the server has disabled HTTP access control, or has access control configured to always allow connections from Authorize.Net.
Your web server is not using a proxy, or if it is, has been configured to allow Authorize.Net to connect to the server via the proxy.
Your domain’s TLS certificate does not use Server Name Indication (SNI). Authorize.Net is unable to validate SNI certificates at this time.
Your Web server does not block HTTP/HTTPS requests without User-Agent strings. Authorize.Net does not include a User-Agent on Relay Response or Silent Post connections.
The above apply to your web host configuration
|
