"They had a Silent Post failure as recent as 2/16/2021:
2021/02/16 03:19:27:423 UTC SilentPost for merchant 2262678 failed.
WinHttp ErrorCode: 12002
HTTP StatusCode:
URL: https://www.bamacarry.us/?s2member_pro_authnet_notify=1
I have been going through hoops with Authorize.net, and they just keep throwing the issue back on s2Member.
Using pro forms, we are capturing customers info, and it is charging their credit card, however all variables in the response are showing as NULL. Therefore the customer receives an error in s2member but their card was still charged, so then they submit again several times because they keep receiving an error, therefore charging their card multiple times.
Authorize.net is stating it’s the silent post url that is not responding or timing out on our end, however our timeouts are set to over 3 minutes.
Is there a way to test the silent post url at our website?
This issue happened once before and “fixed” itself, it just started working randomly again. But again has now started doing this randomly with no changes to our system, except for updating s2member.
If I go back to the date that the transaction referenced in their troubleshooting template, I also find Silent Post timeouts:
2021/02/02 06:42:59:996 SilentPost for merchant 2262678 failed.
WinHttp ErrorCode: 12002
HTTP StatusCode:
URL: https://www.bamacarry.us/?s2member_pro_authnet_notify=1
2021/02/01 19:28:45:449 SilentPost for merchant 2262678 failed.
WinHttp ErrorCode: 12002
HTTP StatusCode:
URL: https://www.bamacarry.us/?s2member_pro_authnet_notify=1
2021/02/01 19:24:32:214 SilentPost for merchant 2262678 failed.
WinHttp ErrorCode: 12030
HTTP StatusCode:
URL: https://www.bamacarry.us/?s2member_pro_authnet_notify=1
If we compare the UTC time of the errors that occurred on 2/1/2021 to the transaction timestamps for these declines:
Transaction ID Submitted Timestamp Silent Post Timeout Timestamp
62829943210 01-Feb-2021 22:42:38 PST 2021/02/02 06:42:59:996
62828792248 01-Feb-2021 11:28:24 PST 2021/02/01 19:28:45:449
62828779540 01-Feb-2021 11:24:10 PST 2021/02/01 19:24:32:214
This error specifically indicates that our attempt to connect to this URL timed out, and was unable to successfully connect to this endpoint."
Our techs are also puzzled as to why you’re using a Silent Post URL. You’re submitting these requests via our legacy AIM API, which is a direct POST to our endpoint with a connection that stays open until it times out, which is what you’re reporting, and it specifically is timing out because you’re using a Silent Post URL.
Our techs suggest that, if you’re wanting to ensure this does not occur, you should remove the Silent Post URL as it is intended to be used with the legacy Server Integration Method only. Webhooks would be more appropriate as a backup transaction notification method, if that’s what you’re trying to do with the Silent Post URL.
