Has someone seen the following...
Since recently all payment authorizations to https://secure.authorize.net/gateway/transact.dll have started to fail.
I'm trying find what the cause might be and found that the response has code 200 but that the body of the response contains html with a very generic error message saying only
> Error
> This page can't be displayed. Contact support for additional information.
> The incident ID is: N/A.
Anyone seen this or know what the cause might be?
10-22-2018 01:32 PM
Hi @santegoeds,
Can you please point to secure2.authorize.net instead of secure.authorize.net endpoint .
Secure.authorize.net was replaced with secure2.authorize.net as communicated in the below similar post.
HTH, Thanks
12-05-2018 04:33 AM
I am pointing to secure2 and am experiencing the same issue. Authorize support has no other info and suggested I come here.
In troubleshooting, I am logging both
serialize(curl_getinfo($curl))
and
$response
When I test with my personal account, everything works as expected and we have had multiple orders (100s) process correctly, but this one particular customer's
$response
is always the same:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"><html xmlns="http://www.w3.org/1999/xhtml"><head><META HTTP-EQUIV="CONTENT-TYPE" CONTENT="TEXT/HTML; CHARSET=utf-8"/><title>Error</title></head><body><H2>Error</H2><table summary="Error" border="0" bgcolor="#FEEE7A" cellpadding="0" cellspacing="0" width="400"><tr><td><table summary="Error" border="0" cellpadding="3" cellspacing="1"><tr valign="top" bgcolor="#FBFFDF" align="left"><td><STRONG>Error</STRONG></td></tr><tr valign="top" bgcolor="#FFFFFF"><td>This page can't be displayed. Contact support for additional information.<br/>The incident ID is: N/A.</td></tr></table></td></tr></table></body></html>
I don't have any way to explain to this customer what's going on even though I've narrowed down to his account, but I am not seeing enogh error info to move on.
Thanks!
02-05-2019 10:57 AM
It turns out that the account had a secondary address field with a `%` in it...
Soon as that was removed, it went through ok.
02-05-2019 12:51 PM
$url:="https://apitest.authorize.net/xml/v1/request.api"
I using the above url to the api to get the token for hosting a page.. But some times I get the above error. Any help. Is the above url has been changed? Intresting thing is that if I try the same after few minutes it worked..
10-12-2020 02:41 AM
The server MUST send a final response after the request has been completed.Unlike the 204 status code, a 200 response should include a response body. The information returned with the response is dependent on the method used in the request,Errors can be like malformed request syntax, invalid request message.
10-13-2020 10:54 PM - edited 10-13-2020 10:55 PM