When I change the status of an order to complete, it charges the credit card. I had an SSL certificate that expired. I renewed and installed the new certificate in my server.
Now I'm getting the following error when CS-CART attempts to charge the credit card:
orders Capture failed for order_id='17211': Failed Capture: 05/08/2018 23:17:59: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
I verified the SSL certificate. Also, when I go to admin.php?dispatch=settings_wizard.view in the administration page I click on the button "check SSL" and it returns "ok".
Any clues on what I need to change for cs-cart to accept my certificate?
I'm using the EZ Payment Capture addon to submit payments through authorize.net. The SSL certificate error is when the payment is attempting to be captured. Not sure if the addon or authorize.net that is returning the error.
As responded to in email, Authorize.net has tightened its cyphers used for SSL. You need to ensure that both your server and CURL CA Bundles (Certificate Authority bundles) are up to date. Most likely the CURL CA Bundle is not current.
In your email, you stated you had installed a new SSL certificate and were getting this error:
orders Capture failed for order_id='17211': Failed Capture: 05/08/2018 23:17:59: SSL certificate problem, verify that the CA cert is OK. Details: error:14090086:SSL routines:SSL3_GET_SERVER_CERTIFICATE:certificate verify failed
which is coming from Authorize.net. You should have received the same error when the "Authorize only" is done during the order process. Both the order process and the Payment Capture addon use the core cs-cart routines for POST/GET operations to Anet. Hence, you should not have a situation where one succeeds and one fails other than the order process uses a GET and the capture uses a POST.
If you JUST installed the new SSL certificate, it is possible that the old certificate is cached within your browser. If you clear your browser cache the problem could also go away if the CURL CA bundle is up to date.