06-05-2011 01:06 PM
Today, this morning and afternoon, Internet Explorer has apparently been objecting to any content from https://verify.authorize.net and reports, "There is a problem with this website's security certificate. The security certificate presented by this website [https://verify.authorize.net] was not issued by a trusted certificate authority." And, "This certificate cannot be verified up to a trusted certification authority."
Issued to: verify.authorize.net
Issued by: Entrust Certification Authority LC - L1C
Valid from 1/27/2011 to 1/23/2013
However, I am able to access the content from Mozilla browsers without problem.
This is a significant problem for the public in accessing content from https://verify.authorize.net and not an issue of going through someone else's server, and does not appear to have any connection with "adding an EnTrust CA certificate" to any server other than those which belong to Authorize.net. For example, it occurs when customers try to read the SIM security code image or view the image at https://verify.authorize.net/anetseal/images/secure90x72.gif or if someone simply walks up to a computer and enters the URL https://verify.authorize.net
06-06-2011 02:48 PM
Thanks for the heads up. I've sent this on to the right people and they are currently looking into it to see what's going on. I'll respond to this thread once I have more info or once the issue's been resolved.
Developer Community Manager
06-07-2011 11:59 AM
OK, so it looks like the seal issue has been resolved. Please let me know if you continue to see any issues.
Developer Community Manager
02-06-2012 05:35 PM
I'm having a similar but different problem. We run inside a walled garden, with a white list of the domains that users are allowed to access before making a purchase. We use Authorize.Net to perform the purchase, so we have a verify seal on the credit card form page, which is still inside the walled garden.
Verification succeeds if I load the credit card form page from outside the walled garden, but if fails when I am inside the walled garden with the "unable to verify" message (the redirect to error.htm).
So I'm fairly sure that we need to add a domain to the white list to allow the verification to succeed inside the walled garden. My question is, what is that domain? verify.authorize.net is already there, and answers, returning the redirect to error.htm Are there any debug scripts that can help diagose the problem?
02-06-2012 09:47 PM
Well, I just checked, and the only assets on the page are from verify.authorize.net. Given, it's http and not https, at least on my implementation, don't know if that would make a difference?
02-09-2012 02:18 PM
The verify seal works on either http or https depending on the site that you have implemented it on. You may want to make sure that you are allowing connections on both ports 80 and 443.