You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all, I am self-hosting Invoice Ninja's v4 with PHP 7.2 on digital ocean and got the email from Braintree re updating the SSL certificates before June 30th 2025. Because of Invoice Ninja v4's docker image limitations I can't upgrade to PHP 7.4 (let alone 8.3) but I did download the new SSL certificates from this link and installed them manually: https://github.com/braintree/braintree_php/blob/master/lib/ssl/api_braintreegateway_com.ca.crt
My question is: Does this mean that I am ready for the June 30th deadline and could continue to process payments after June 30th?
Many thanks ahead!
The text was updated successfully, but these errors were encountered:
Thank you for posting this. I have similar issues with the application not supporting the required level of PHP to meet the minimum requirements for the new API. If this really addresses the hard cutoff, that would be very helpful.
Thank you for posting this. I have similar issues with the application not supporting the required level of PHP to meet the minimum requirements for the new API. If this really addresses the hard cutoff, that would be very helpful.
I hope someone from Braintree would comment here to confirm
Hi all, I am self-hosting Invoice Ninja's v4 with PHP 7.2 on digital ocean and got the email from Braintree re updating the SSL certificates before June 30th 2025. Because of Invoice Ninja v4's docker image limitations I can't upgrade to PHP 7.4 (let alone 8.3) but I did download the new SSL certificates from this link and installed them manually:
https://github.com/braintree/braintree_php/blob/master/lib/ssl/api_braintreegateway_com.ca.crt
My question is: Does this mean that I am ready for the June 30th deadline and could continue to process payments after June 30th?
Many thanks ahead!
The text was updated successfully, but these errors were encountered: