BestPaid guides · Mobile apps · Stripe Terminal

Stripe Terminal SDK end of life: 1.x to 3.x blocked from card readers in January 2027, 4.x in October 2027

Point-of-sale apps on the Stripe Terminal iOS or Android SDK 1.x, 2.x or 3.x can't connect to card readers or take payments once Stripe's January 2027 block starts, and Stripe says it can't grant extensions to that timeline; 4.x follows in October 2027. Here is Stripe's schedule, how to find the SDK version your app ships, and the path to 6.x.

Sources: Stripe's support article End of life status for Terminal card readers and SDKs; Stripe Docs: SDK versioning and support, the 6.0.0, v5, v4, v3 and React Native migration guides, SDK setup, Tap to Pay, Apps on Devices and the iOS API reference; Stripe's GitHub changelogs for iOS and Android, React Native releases and SUPPORT.md for iOS, Android and React Native; Android Developers' Gradle dependency resolution; Google Play's target API level requirements. Stripe's docs pages show no last-updated date; the support article's page metadata gives October 5, 2026 as its last change, and the SUPPORT.md files last changed on June 10, 2026 (iOS, Android) and October 28, 2026 (React Native). Checked on November 21, 2026. This page is our own summary; follow the vendor's documentation for every detail.

What Stripe says, and when

Stripe's policy gives each major version three one-year phases from its GA date: active development, maintenance (critical fixes only), then deprecated. The iOS and Android SUPPORT.md files say 1.x to 3.x entered the deprecated phase before the policy was formalized, so their dates don't follow that pattern. Stripe's schedule for the Terminal mobile SDKs:

VersionGACritical fixes onlyDeprecatedEnd of life
1.x.xOctober 2019—January 2024January 2027
2.x.xJune 2021—October 2024January 2027
3.x.xSeptember 2023—October 2025January 2027
4.x.xOctober 2024October 2025October 2026October 2027
5.x.xOctober 2025October 2026October 2027October 2028
6.x.xOctober 2026October 2027October 2028October 2029

After January 2027 the minimum SDK version that can connect to readers is 4.0.0; after October 2027 it is 5.0.0. The support article applies the January block to the iOS and Android SDKs v1.x through v3.x, says those users were to be told in June 2026 to plan a move to V5 or later, and adds: “We are unable to grant extensions or exemptions on migration timeline.” Stripe names months, not days, so treat January 1 and October 1, 2027 as the deadlines.

Stripe's pages differ on status: the docs table has 4.x deprecated and 5.x on critical fixes only since October 2026, while the iOS and Android SUPPORT.md files (last changed June 10, 2026) still list 4.x as in maintenance and 5.x as in active development, and have no 6.x row. Their patch-support end dates (October 2026 for 4.x, October 2027 for 5.x) and block dates match the docs table.

What happens at end of life

An end-of-life SDK can't discover readers, connect to them or process payments. Before that, in the deprecated phase (1.x to 3.x now, and 4.x by the docs table), it might keep working but gets no patches or support. Stripe says Tap to Pay's own security and compliance requirements might require SDK upgrades earlier. For readers, the support article says that from the P400's and WisePOS E's final dates the reader can't process transactions or store card information and gets no customer support.

React Native and JavaScript

React Native: Stripe's pages disagree. The versioning page calls the React Native SDK a public preview whose end-of-life schedule Stripe will publish at general availability; the repository's SUPPORT.md says that during public preview, enforcement follows the bundled native major version; the React Native migration guide calls 6.0.0 the first generally available release (GitHub release November 19, 2026, bundling native 6.0.0). Plan by the bundled native version: 0.0.1-beta.23 and earlier bundle native 2.x or 3.x, beta.24 to beta.28 bundle 4.x, beta.29 to beta.33 bundle 5.x, and beta.34 and 6.0.0 bundle 6.0.0.

JavaScript: Stripe's versioning policy names only the mobile SDKs (iOS, Android and React Native). Stripe says the JavaScript SDK script (https://js.stripe.com/terminal/v1/) must always load directly from js.stripe.com for compatibility with the latest reader software; a bundled or self-hosted copy might break the integration without warning.

Which readers are affected

The SDK block depends on the app's SDK version, not the reader model. Readers have separate dates in Stripe's support article, none in January or October 2027:

ReaderStripe's dates
Verifone P400No new orders or feature updates from September 14, 2021; critical software updates or maintenance from October 1, 2024; from February 9, 2026, it can't process transactions or store card information and gets no customer support. SDK 5.0.0 removed P400 support.
BBPOS WisePOS EEnd of sale September 1, 2026; deprecated February 1, 2028, when new SDK, firmware and ROM versions stop being backward compatible with it; end of life February 1, 2031.
BBPOS Chipper 2XNo new Stripe orders since January 31, 2022; Stripe says to migrate to Stripe Reader M2. No end-of-life date given.

List your readers in the Dashboard under Terminal > Readers, or through the API.

Find the SDK version your app ships

# iOS, CocoaPods
grep "StripeTerminal (" Podfile.lock

# iOS, Swift Package Manager (stripe-terminal-ios or stripe-terminal-ios-spm)
find . -name Package.resolved -exec grep -A6 stripe-terminal-ios {} +

# Android: Terminal artifacts start with com.stripe:stripeterminal
./gradlew app:dependencies | grep stripeterminal

# React Native
npm ls @stripe/stripe-terminal-react-native

The upgrade path to 6.x

The current major is 6.x: iOS and Android 6.0.0 shipped on October 7, 2026. Stripe's current guides start at 2.x and go one major at a time (v3, v4, v5, then the 6.0.0 guide); the 6.0.0 and v5 guides say to finish the previous one first. For 1.x, the 2.0.0 changelog entries (June 23, 2021) list the changes.

StepPlatform minimumsChanges that bite
3.0.0iOS 13; Android 8.0 (API 26)Reader-specific discovery configurations.
4.0.0iOS 14connectReader replaces the per-reader-type connect methods; auto-reconnect is on by default for mobile and Tap to Pay readers.
5.0.0iOS 15; Tap to Pay on Android needs Android 13clearCachedCredentials fails while a reader is connected; configuration classes renamed; customer cancellation on by default on supported readers; Android's Terminal.initTerminal becomes Terminal.init.
6.0.0iOS 16.0, Xcode 16.0, Swift Package Manager or a manual framework (no CocoaPods); Android compileSdk 35, built with Kotlin 2.3.21Capture defaults to automatic async, not manual; payment UI moves to ReaderPaymentInteractionDelegate / ReaderPaymentInteractionListener; two-step refunds removed (use processRefund); PaymentIntent.charges replaced by latestCharge and latestChargeId; Android's Terminal.init needs a LocaleConfig; narrower ProGuard rules.

On Android, the changelog's only minSdkVersion change is 3.0.0's move to 26 (Tap to Pay has its own OS minimum: Android 13 since 5.0.0), and Stripe's React Native requirements say minSdkVersion 26 or later. React Native 6.0.0 needs React Native 0.83 or later (New Architecture), React 19.2 or later, an iOS deployment target of 16.0 or later and Android compileSdkVersion 35 or later. In 6.0.0, automatic_async is the createPaymentIntent capture default (it was manual in beta.33) and StripeTerminalProvider requires a localeConfig prop.

Stopping at 4.x means another upgrade before October 2027, and stopping at 5.x another before October 2028; 6.x reaches end of life in October 2029. Devices that can't run iOS 16 can stay on 5.x, which supports iOS 15, until its October 2028 end of life, with critical fixes only until October 2027 and no patches after that; new 5.x patches no longer go to CocoaPods.

Order of work that keeps stores taking payments

  1. Inventory every app build in use, its SDK version, each reader model and the OS on each POS device. 6.x needs iOS 16 or later; Tap to Pay on Android needs Android 13 or later and a security update from the past 12 months, among Stripe's other device requirements.
  2. Replace what can't move: P400s haven't been able to process transactions since February 9, 2026; iPhones and iPads that can't run iOS 16 need replacing or, if they run iOS 15, a 5.x plan; Android devices below Android 13 can't use Tap to Pay on 5.x or 6.x.
  3. Upgrade on a branch, one Stripe guide at a time, building after each step.
  4. Check behavior, not just compile errors. In 6.0, set manual capture explicitly if you capture later (Stripe names on-receipt tipping and incremental and extended authorizations), and supply the payment interaction delegate or listener, or payments that need your app's UI fail.
  5. Test with physical readers in a sandbox: payments, refunds, reconnects and reader updates (testReaderUpdate is sandbox-only). With offline mode, test the upgrade with existing app data, including any stored offline payments, as Stripe's Android 6.0 checklist asks; on Android, test a minified release build.
  6. Meet today's store rules. Since August 31, 2026, Google Play updates must target Android 16 (API level 36) or higher (lower for Wear OS, Automotive OS, TV and XR apps). For App Store builds, see our App Store guide.
  7. Roll out to one store, then the rest, keeping a rollback build that can still connect: 4.0.0 or later after January 2027, 5.0.0 or later after October 2027. Move any 4.x apps before October 2027.
  8. Watch Tap to Pay: subscribe to Stripe's terminal-announce list. In the Android 6.0 SDK, TapToPayReaderListener.onUpdateRequirementsAvailable reports upcoming Android OS, security patch and SDK requirements so your app can warn users; Stripe calls it advisory: it doesn't install updates or block payments.
Point-of-sale app still on Stripe Terminal SDK 4.x or older? We update native, Unity, Flutter, React Native and Xamarin apps to current SDKs and store rules at a fixed price. You keep your signing keys. It starts with a $290 check and a fixed quote within 2 business days.
See the app update offer