Braintree set March 30, 2026 as the expiry date for the SSL certificates pinned in older iOS and Android SDK versions. Drop-in, its ready-made checkout UI, is deprecated, becomes unsupported in 2027 and only runs on the older SDK lines. Below: what each date means, how to check what a build ships, and an order of work that keeps checkout running.
Braintree changed the root certificate provider for api.braintreegateway.com on April 12, 2024 and shipped SDK releases with updated pinned certificates. On April 22, 2025 it moved the deadline to March 30, 2026. Its docs say that unless you retire app versions with the older SDKs or force an upgrade, "100% of your customer traffic will fail."
Braintree's GitHub announcements say API calls from those builds no longer reach its servers, and the SSL errors come from your language or framework, not from Braintree: an invalid certificate, a refused connection or a failed handshake. Server SDKs and self-pinning servers were covered too. Both were closed on May 13, 2026, as the date had passed and the migration was complete.
| SDK in the build | Versions with the new certificates |
|---|---|
| iOS SDK v6 | 6.17.0 or later |
| iOS SDK v5 | 5.26.0 or later |
| iOS Drop-in 9.x | 9.13.0 or later, on iOS SDK 5.26.0 or later (the announcements say Drop-in 9.12.2 or later) |
| Android SDK v5 | 5.0.0 or later |
| Android SDK v4 | 4.45.0 or later |
| Android Drop-in 6.x | 6.16.0 or later (no Drop-in 5.x release has the new certificates) |
| Android SDK v3 | 3.22.0 or later, per the Android announcement; the 3.22.0 release (March 2026) updated the pinned certificates. The iOS repository's copy says v3 got no update and to move to 4.45.0 or later. |
Braintree's iOS Drop-in setup and customization pages say iOS SDK 6.17.0 or later, which Drop-in can't use; the Drop-in overview's fix, Drop-in 9.13.0 or later, is the one that fits a Drop-in app.
Braintree's developer docs give these Drop-in dates:
The Drop-in READMEs on GitHub, last changed in September 2025, say September 1, 2026 and September 1, 2027. Plan for the earlier date.
Drop-in also holds you on old SDK lines. iOS Drop-in 9.x requires iOS SDK 5.x (its podspec pins ~> 5.27), and Braintree says the iOS v6 and v7 SDKs aren't supported via Drop-in. The latest Android Drop-in, 6.17.0, is built on Android SDK 4.50.0, and Android v5 doesn't support Drop-in. Leaving Drop-in and upgrading the SDK are one project.
Status and dates from the SDK READMEs (months as Braintree gives them), latest versions from the changelogs (iOS 7.14.0 and Android 5.35.0 came out on November 10, 2026):
| SDK | Status | Deprecated | Unsupported | Latest |
|---|---|---|---|---|
| iOS 7.x | Active | TBA | TBA | 7.14.0 |
| iOS 6.x | Inactive | November 2026 | November 2027 | 6.41.0 |
| iOS 5.x | Unsupported | June 2024 | June 2025 | – |
| Android 5.x | Active | TBA | TBA | 5.35.0 |
| Android 4.x | Deprecated | October 2025 | October 2026 | – |
| iOS Drop-in 9.x | Inactive | September 2026 | September 2027 | 9.14.0 |
| Android Drop-in 6.x | Inactive | September 2026 | September 2027 | 6.17.0 |
Some status cells lag behind their own dates. Per Braintree's deprecation policy, Inactive gets security updates only; Deprecated gets none, with processing supported for a year after the deprecation date; Unsupported can have processing suspended at any time.
Read the resolved version (lockfile or Gradle's dependency tree), not the range in your Podfile or build file, at the tag of every release users still run:
# iOS, Swift Package Manager
find . -name Package.resolved -path '*swiftpm*' -exec grep -i -A6 braintree {} +
# iOS, CocoaPods (ios/Podfile.lock in React Native and Flutter apps)
grep -i braintree Podfile.lock
# iOS, Carthage
grep -i braintree Cartfile.resolved
# Android (run from the android/ folder in React Native and Flutter apps)
./gradlew :app:dependencies --configuration releaseRuntimeClasspath | grep com.braintreepayments
# A shipped release: replace v3.4.0 with its tag
git show v3.4.0:ios/Podfile.lock | grep -i braintree
Look for the core SDK (Braintree pods, braintree_ios, or com.braintreepayments.api modules such as card and braintree-core) and for BraintreeDropIn or drop-in. For React Native, Flutter and .NET apps, check the native versions the plugin or binding resolves.
Every Drop-in notice points to the core Braintree iOS and Android SDKs, where each payment method is a separate module called from your own checkout screen. Your server still receives a payment method nonce.
iOS, to v7. Braintree has one guide per major step (v5 to v6, v6 to v7); an app leaving Drop-in starts on v5 and needs both. In v7:
BTCardClient(authorization:), and request properties are set only through initializers.startPaymentFlow(with:completion:) to start(with:completion:).paypal in LSApplicationQueriesSchemes.BraintreeCard, BraintreeThreeDSecure, BraintreePayPal (needs BraintreeDataCollector), BraintreeVenmo, BraintreeApplePay, BraintreeUIComponents.Android, to v5. All Braintree modules move to 5.x together; v4 and v5 aren't compatible.
BraintreeClient: create each client from a context and your authorization.PayPalLauncher handles the browser switch and VenmoLauncher the Venmo app switch.appLinkReturnUrl. The browser-switch scheme must start with your package ID and end with .braintree.// Before: Drop-in, built on Android SDK v4
implementation("com.braintreepayments.api:drop-in:6.17.0")
// After: only the v5 modules your checkout uses, all on one version
implementation("com.braintreepayments.api:card:5.35.0")
implementation("com.braintreepayments.api:three-d-secure:5.35.0")
implementation("com.braintreepayments.api:paypal:5.35.0")
implementation("com.braintreepayments.api:venmo:5.35.0")
implementation("com.braintreepayments.api:google-pay:5.35.0")
implementation("com.braintreepayments.api:data-collector:5.35.0")
implementation("com.braintreepayments.api:ui-components:5.35.0")
Replacing Drop-in's screens. UI components now cover part of them: on iOS, PayPalButton and VenmoButton (7.2.0), CardFields (7.8.0) and PayPalPayLaterButton (7.14.0); on Android, PayPalButton and VenmoButton (5.21.0), CardFields (5.29.0, Compose in 5.33.0) and PayLaterButton (5.35.0). Still yours: the saved payment methods Drop-in showed for a client token with a customer_id. On PCI, Drop-in's overview says Drop-in typically qualifies you for the SAQ A form and a custom integration with the native mobile SDKs typically can too, with you responsible for tokenizing cards, PayPal and Venmo.
// iOS v7: tokenize a card from your own form
let cardClient = BTCardClient(authorization: clientTokenOrTokenizationKey)
let card = BTCard(number: number, expirationMonth: month, expirationYear: year, cvv: cvv)
let cardNonce = try await cardClient.tokenize(card)
// send cardNonce.nonce to your server
// Android v5
val cardClient = CardClient(context, clientTokenOrTokenizationKey)
val card = Card(number = number, expirationMonth = month, expirationYear = year, cvv = cvv)
cardClient.tokenize(card) { result ->
when (result) {
is CardResult.Success -> sendToServer(result.nonce.string)
is CardResult.Failure -> showError(result.error)
}
}
paypal query scheme on iOS; the registered App Link and .braintree scheme on Android. Move iOS off CocoaPods to get releases after 7.13.1.