📣 Upgrade your integration to continue accepting Braintree payments #993
Comments
|
We're getting the same message |
|
Hi @BunnyBuddy thanks for using the Braintree SDK for Android. Can you elaborate on the message you're receiving? |
We got this message, now it may be just a precautionary alert or something but we're using, Now I want to know if I just update the drop in version to 6.16 ? would it break anything (is there any major change in the code) or is it just a simple version update. |
|
@stechiu - Just to make sure, this does not affect the .Net SDK, correct? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Upgrade your integration to continue accepting Braintree payments
Braintree updated the root SSL certificate provider for api.braintreegateway.com (sandbox and prod) on April 12, 2024. The SSL certificates for current Android SDK v4 is set to expire by June 31, 2025.
If you do not update your SDK to the latest version with the updated certificates by June 31, 2025, 100% of your impacted traffic (client via the Android or iOS SDK, server via the server SDKs, server via self-pinning) will fail.
To reduce the impact, your developer will need to update your SDK to version 4.45.0. For details on how to include the SDK, see our setup guide found here.
What other SDKs will be impacted?
The following SDKs need to be updated to the latest version by June 31, 2025. Check the minimum server versions in the Braintree doc.
When do I need to make this change?
By June 31, 2025.
Is there any flexibility in the deadline?
No. Please work with your TAM to ensure you will meet the deadline in time.
What if I’m using a lower version?
Android SDK
iOS SDK
This change is being updated only in version 4.45.0. Any lower versions must migrate to this version by June 31, 2025 to avoid impact of traffic to Braintree SDKs.
What changes does my developer need to make to my integration?
Your developers needs to update the SDK (client and server) to the latest version to eliminate customer service disruptions and for good security practice.
Braintree's official recommendation is that Merchants use official SDKs, not modified ones. We cannot support modified SDKs. Reference our docs for our official SDK - https://developer.paypal.com/braintree/docs/
It is suggested to make this update as soon as possible to reduce any impacts to the customer experience.
I've updated my SDK but I'm still getting emails to update
Braintree regularly pulls the latest list of impacted Merchants who need to update their SDK version before sending each email. If you have communicated with your TAM that you will updated but have not, then you will continue to receive email reminders until you have completed the update.
What happens if I don’t update or miss the deadline?
If you are still processing on a legacy SDK when our SSL Root Certificate update goes live, your API calls will no longer be able to reach Braintree's servers. Your customers will start to see errors when trying to complete checkout and their app logs will show SSL-related errors.
As a result, the specific error message you encounter won't be from Braintree, but rather from the language or framework you are using. The error message will likely be unique to that language or framework, but you can expect it to mention SSL – something along the lines of an invalid certificate, a refused connection, a failed handshake, etc. If you begin to encounter an error along those lines, double check that your integration has been updated to at least the minimum version, and then feel free to reach back out to us for further support.
What region is impacted by this change?
All (global)
The text was updated successfully, but these errors were encountered: