12-08-2013 10:37 PM
I have also tried with sample code provided authorize.net for sim but not working for https but working for http.
12-11-2013 01:29 PM
I am experiencing similar results, although I am using DPM. But, its not just me, it seems that this is a extremely common issue with seemingly no help from Authorize.Net.
What we need as developers is a difinitive way to determine if Authorize.NET has some issues with the SSL certificate we are using. The one we are using is from GoDaddy, a large CA.
I have viewed all the troubleshooting pages and I have seen almost every post on here about the issue and all things I should have tried, I probably have. Most of the posts are left with no answers.
Am I suppose to tell my client to keep buying SSL certificates until we find one that works? Doesn't sound like the right solution.
At this point, I am rather frustrated.