Transaction is failing with authorize error
Permalink Browser Info Environment
When trying to complete a transaction, the submit button disappears, and the following is displayed in the firefox(firebug) error console:
We have tried reissuing the ssl with a stronger encryption (sha2) but that did not change the error.
SSLv3 is confirmed disabled on that server.
Any help would be greatly appreciated.
Thanks!!
{"success":false,"msg":"We're sorry! There was an error processing your card. This is the message we received: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed Please try again, perhaps with a different credit card."}
We have tried reissuing the ssl with a stronger encryption (sha2) but that did not change the error.
SSLv3 is confirmed disabled on that server.
Any help would be greatly appreciated.
Thanks!!
| Type: | Discussion |
|---|---|
| Status: | In Progress |
Hi,
We have discover the issue. Basically CURL was failing. More info here
http://unitstep.net/blog/2009/05/05/using-curl-in-php-to-access-htt...
We were able to add the exception in the curl options, but then actually fixed the issue on our server (which is the better, secure choice).
We have discover the issue. Basically CURL was failing. More info here
http://unitstep.net/blog/2009/05/05/using-curl-in-php-to-access-htt...
We were able to add the exception in the curl options, but then actually fixed the issue on our server (which is the better, secure choice).
Hi,
We have discover the issue. Basically CURL was failing. More info here
http://unitstep.net/blog/2009/05/05/using-curl-in-php-to-access-htt...
We were able to add the exception in the curl options, but then actually fixed the issue on our server (which is the better, secure choice).
We have discover the issue. Basically CURL was failing. More info here
http://unitstep.net/blog/2009/05/05/using-curl-in-php-to-access-htt...
We were able to add the exception in the curl options, but then actually fixed the issue on our server (which is the better, secure choice).
I'm glad you figured it out. The message you were seeing (regarding the SSL) came from Authorize.net, not our add-on. As such, the add-on WAS performing correctly. But Authorize.net didn't like the insecure way you were transmitting the data. Our add-on was simply passing their message back to you.
I'm glad you resolved the issue. Let us know if you need anything else.
I'm glad you resolved the issue. Let us know if you need anything else.
Thanks for replying!
We have discover the issue. Basically CURL was failing. More info here
http://unitstep.net/blog/2009/05/05/using-curl-in-php-to-access-htt...
We were able to add the exception in the curl options, but then actually fixed the issue on our server (which is the better, secure choice).