![]() ![]() ![]() I just tried it again using "curl_setopt($curl, CURLOPT_SSLVERSION, 6) " It failed. Why would it work for UPSXML, but not stripe? Note that in UPSXML I also had to specifyīut this statement doesn't exist in stripe.php. Trying that statement in stripe.php however, did not work. I referenced "curl_setopt($curl, CURLOPT_SSLVERSION, 6) " in my original post that created this thread. I'm sorry, but the very reason I mentioned the UPSXML is because adding the curl statement you suggest worked for the UPSXML issue. I had this with a customer this week (trying to get paypal going on TLS1.2). If this doesn't do it, then the most likely explanation is that your server apparently supports TLS1.2 but it's not been done properly and the right ciphers aren't available. Add among them somewhere:Ĭurl_setopt($curl, CURLOPT_SSLVERSION, 6) To do this find the function sendTransactionToGateway which sets a lot of curl options before the call. As well as that there are curl calls made by the module so you can try forcing them to TLSv1.2 It uses javascript but that's all pulled from the Stripe site so it's out of your control and probably ok. If your server is rated OK then it may be that it is not set to use TLSv1.2 by default and it must be specified.įrom a quick scan of the stripe module there are a couple of ways it communicates. If there's a more complex api then it may need changes to the calls on some servers to specify that it's done over TLS1.2.įirst step is to check your server by putting it into If the integration is a form-based one where the customer is transferred over to make payment separately then it may be that all that is necessary is for your Security Certificate and platform to be up to scratch. It's typically an issue that must be resolved by making sure your hosting environment is up to the right standards, and only occasionally needs application changes. It is common for payment processors to have already updated their test environments to accept only TLS1.2 connections - it is definitely true of Paypal and Sagepay but I don't know about Stripe. The topic of TLS version availability is common across all payment methods as the PCI compliance date looms in June. It looks like your UPS issue was support for a particular XML version and I don't see what that has to do with TLS version (although there may be some coincidental correlation with particular platform versions). ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |