# Stripe Terminal React Native SDK changelog

This document details changes made to the SDK by version.

## 6.0.0

Includes iOS native SDK [6.0.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/6.0.0) and Android native SDK [6.0.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#600---2026-10-07).

### New

- iOS: Added optional `onPaymentMethodSelectionRequired` and `onQrCodeDisplayRequired` callbacks to `ConnectTapToPayParams`, allowing integrations to supply payment-method selection and QR-code display handlers when connecting a Tap to Pay on iPhone reader with `connectReader`.
- **Preview:** Swish - Added `PaymentMethodType.Swish` and `SwishDetails`, and exposed optional `swishDetails` on `PaymentMethod.Type` and `PaymentMethodDetails`.
  - To request access to this feature, please contact [Stripe Support](https://support.stripe.com/).
- Added `overcaptureStatus` to charge `CardPresentDetails` to indicate whether overcapture is supported for a confirmed PaymentIntent. (from native 5.7.0)
- Exported the `DISCONNECT`, `UPDATE_BATTERY_LEVEL`, `REPORT_LOW_BATTERY_WARNING`, `REPORT_READER_EVENT`, and `ACCEPT_TERMS_OF_SERVICE` (iOS only) event-name constants from the package entry point, for use with the lower-level `emitter`/`useListener` API. The corresponding `UserCallbacks` props (`onDidDisconnect`, `onDidUpdateBatteryLevel`, `onDidReportLowBatteryWarning`, `onDidReportReaderEvent`, `onDidAcceptTermsOfService`) were already public; only these underlying constants were missing from the top-level exports.
- Exported `RequestAndroidPermissionsParams`, `RequestAndroidPermissionsResult`, and `StripeTerminalPluginProps` — types already referenced by `requestNeededAndroidPermissions` and the Expo config plugin but not previously part of the package's public exports.

### Updates

- **Breaking:** Removed the duplicate `Reader.ConnectionStatus` type. Use the top-level `ConnectionStatus` instead; `getConnectionStatus` and the `onDidChangeConnectionStatus` callback now share it (both declarations had identical values).
- **Breaking:** Aligned the card-present payment-method-options types with the native SDK and made the response fields optional. `CreatePaymentIntentParams.paymentMethodOptions` now uses `PaymentMethodOptionsParams` (was `PaymentMethodOptions`); `PaymentIntent` and `SetupIntent` `paymentMethodOptions` now use `PaymentMethodOptions` (was `PaymentMethodOptionsResponse`), whose `cardPresent` is the named `CardPresentOptions` type. `cardPresent` and its `requestExtendedAuthorization`, `requestIncrementalAuthorizationSupport`, and `requestPartialAuthorization` properties are now optional — Android and iOS omit missing native values instead of synthesizing `cardPresent`, `false`, or an empty string.
- **Breaking:** Removed the `'unspecified'` value from `CustomerCancellation` and `CollectionReason` to match the native SDKs, which define only `'enableIfAvailable'`/`'disableIfAvailable'` and `'saveCard'`/`'verify'` respectively. Passing `'unspecified'` previously fell through to the native default; omit the field instead to get that default (`'enableIfAvailable'` for customer cancellation, `'saveCard'` for collection reason).
- Made `customerCancellation` optional on `CollectDataParams`, matching the native SDKs and the other collect/process params types. When omitted, the native default (`'enableIfAvailable'`) is used.

### Fixes

- Android: Fixed offline SetupIntents failing with `STRIPE_API_CONNECTION_ERROR` while offline. The SDK now implements the native `onSetupIntentForwarded` listener callback, and forwards its result through the new `onDidForwardSetupIntent` callback.
- Android: `connectReader` now returns `INVALID_REQUIRED_PARAMETER` with supported values when `discoveryMethod` is missing, null, or invalid, instead of an unexpected SDK error or bridge type exception.
- iOS: `cancelCollectPaymentMethod` now returns `CANCEL_FAILED` after successful cancellation or reader disconnection instead of reusing a stale collection handle. Addresses [#1139](https://github.com/stripe/stripe-terminal-react-native/issues/1139).
- iOS: Repeated cancellation of payment, refund, and SetupIntent operations now returns `CANCEL_FAILED` after the operation is successfully canceled, and after SetupIntent collection or refund processing completes.
- iOS: Fixed an issue where reader events stopped reaching the app after a React Native reload while a reader remained connected. Fixes [#1142](https://github.com/stripe/stripe-terminal-react-native/issues/1142).
- Android: Fixed an issue where reader connections timed out when requesting a connection token after an in-process React Native reload, including development reloads and Expo over-the-air update reloads. Fixes [#1141](https://github.com/stripe/stripe-terminal-react-native/issues/1141).
- Android: Reinitializing the SDK now routes connection, payment status, and offline events to the current React Native runtime.
- Android: Fixed `Reader.isCharging` not being reported; it is now populated to indicate whether the connected reader is charging, matching iOS.
- Fixed `Wallet.type` being typed as required; it is now optional, matching the native iOS SDK where a card wallet's `type` can be absent.
- Android: Fixed a crash when confirming a PaymentIntent with a surcharge consent that omitted `notice`. `SurchargeConsent.notice` is now optional and uses the native default (no additional message) when omitted.
- Android: Fixed `useListener` registering a listener for event constants that are `undefined` on the current platform (e.g. the iOS-only `ACCEPT_TERMS_OF_SERVICE`); it now skips subscribing when the event name is `undefined`.

## 0.0.1-beta.34

### New

- **Preview:** Added support for Mexico installments (meses sin intereses, or MSI) for eligible card-present transactions. Set `paymentMethodOptions.installments.enabled` when creating a PaymentIntent. After payment method collection, `PaymentIntent.paymentMethodOptions.cardPresent.installments.availablePlans` contains the eligible installment plans; after confirmation, `PaymentIntent.paymentMethodOptions.cardPresent.installments.plan` contains the plan selected by the cardholder.
  - To request access to this feature, please contact [Stripe Support](https://support.stripe.com/).
- iOS: Added an optional `reader` argument to `onDidStartInstallingUpdate` and the `START_INSTALLING_UPDATE` event so integrations can read the reader's current software version while a required update is in progress.
- Added the `CANCELED_BY_READER` error code for payment flows canceled from the reader.
- Android: Added the `INVALID_INSTALLMENT_PLAN` error code.
- Android: Added `onDidUpdateRequirementsAvailable` for upcoming Tap to Pay Android OS, security-patch, and SDK requirements.
- Added `readMethod` to `CardPresentDetails`.
- Added `paymentAccountReference` to charge `CardPresentDetails` when available.
- Added `application` and `review` to `PaymentIntent` when available.
- Android: Added `authorizationCode` to MOTO `CardDetails` when available.

### Updates

- **Breaking:** `getConnectedReader` now returns `null` when no reader is connected and rejects native bridge errors with `StripeError` instead of returning error objects.
- **Breaking:** Removed `CollectDataType.UNKNOWN`. The `collectData` request now accepts only `CollectDataType.MAGSTRIPE` and `CollectDataType.NFC_UID`, matching the native SDK input contract.
- **Breaking:** Corrected eight public result contracts. Discovery result aliases now describe resolved values instead of promises; successful `disconnectReader`, `rebootReader`, and `clearReaderDisplay` calls no longer require an error field; and `getOfflineStatus`, `getPaymentStatus`, and `getConnectionStatus` now reject unexpected errors with `StripeError` instead of resolving error objects, matching their existing return types.
- **Breaking:** Aligned software-update callbacks and response fields with native SDK contracts.
  - `onDidReportReaderSoftwareUpdateProgress` now receives a number between `0` and `1` instead of a string.
  - `onDidFinishInstallingUpdate` now receives `(update, error)` as separate optional arguments. This preserves both values when an installation fails and permits both to be `undefined` when no update is available. The class-component event emitter uses the same arguments. The `UpdateSoftwareResultType` export has been removed.
  - `Reader.SoftwareUpdate` now includes `isTestUpdate`; `requiredAt` and `components` are now required.
- **Breaking:** Android: Renamed `TapToPayUxConfiguration.darkMode` to `theme` and `colors` to `colorScheme`. When `theme` is omitted, the Tap to Pay UI now follows the system theme instead of defaulting to light mode.
- **Breaking:** Removed the `StripeTerminalSdk` runtime export from the package entry point. Use `StripeTerminalProvider` with `useStripeTerminal` or `withStripeTerminal` instead.
- **Breaking:** Removed the `StripeTerminalSdkType` export. Use `WithStripeTerminalProps` for the public SDK methods and state.
- **Breaking:** React Native 0.83 or newer and React 19.2 or newer are now required.
- **Breaking:** iOS apps must now target iOS 16.0 or later.
- **Breaking:** Android apps must now use `compileSdkVersion` 35 or later.
- **Breaking:** Android apps must now use Kotlin Gradle Plugin 2.2.0 or later. See the [Android requirements](README.md#android) for configuration.
- **Breaking:** Renamed the `PRINTER_LOW_BATTERY` error code to `READER_BATTERY_LOW`.
- **Breaking:** PaymentIntent responses now expose the latest charge as `latestCharge` and `latestChargeId` instead of the `charges` array.
- **Breaking:** PaymentMethod `cardPresentDetails` and `interacPresentDetails` now use `PaymentMethodCardPresentDetails` instead of `CardPresentDetails`. Transaction-only fields remain on `Charge.paymentMethodDetails`; the new type exposes `brandProduct`, `networks`, and `paymentAccountReference`. Payment-method-specific detail objects, `customer`, and nullable card fields are now optional.
- **Breaking:** `collectSetupIntentPaymentMethod` and `processSetupIntent` now require `allowRedisplay` to be `always` or `limited`, matching the native SDK 6.0 SetupIntent collection contract.
- **Breaking:** `CardPresentDetails.expMonth` and `expYear` now use numbers, matching native SDK values. `preferredLocales`, `issuer`, `iin`, `description`, and `wallet` are now optional because native SDK responses may omit them.
- **Breaking:** `Refund.id` is now optional because native SDK 6.0 can return a Refund before Stripe assigns an ID.
- **Breaking:** `CreatePaymentIntentParams.captureMethod` now accepts and defaults to `automatic_async` instead of `manual`. Integrations that require separate capture must explicitly set `manual`.
- **Breaking:** `ReceiptDetails.accountType` and `ReceiptDetails.authorizationCode` are now optional because native SDK responses may omit them.
- **Breaking:** `PaymentIntent.paymentMethodOptions` and `SetupIntent.paymentMethodOptions` now use `PaymentMethodOptionsResponse`, which exposes response values under `cardPresent`. `PaymentMethodOptions` remains the flat input type for `CreatePaymentIntentParams.paymentMethodOptions`.
- **Breaking:** `SetupIntent.latestAttempt.paymentMethodDetails` is now optional, as are its `cardPresent` and `interacPresent` fields, because native SDK responses omit unavailable details. On Android, `paymentMethodDetails.type` now uses React Native payment method type values such as `cardPresent` and `interacPresent`.
- **Breaking:** Reader responses now align with native platform values: `id` and `serialNumber` are optional, `batteryStatus` is optional on the shared reader type, `isCharging` is a `boolean` instead of a `number`, and `Reader.NetworkStatus` can be `unknown` when connectivity cannot be determined.
- **Breaking:** Corrected reader reconnection, reader disconnection, and offline payment forwarding callback types to match their native values: `onDidStartReaderReconnect` and `onDidDisconnect` now always receive a `reason`, `onDidForwardingFailure` always receives an `error`, and the `error` argument of `onDidForwardPaymentIntent` is now optional because it's only set when forwarding fails.
- **Breaking:** Class components using the `StripeTerminalProvider` event emitter now receive `START_READER_RECONNECT` as `(reader, reason)` instead of `(reason)`, and `READER_RECONNECT_FAIL` as `(reader)` instead of `(error)`. Update listeners to read the new first argument.
- Verbose JavaScript console logs from `StripeTerminalProvider` now include only the SDK operation or event name and omit payload details. Public setup examples no longer enable verbose logging by default.
- Updated the bundled iOS and Android Terminal SDKs to version 6.0.0.
- iOS: The native Stripe Terminal SDK is now resolved with Swift Package Manager instead of the CocoaPods trunk. Continue running `pod install` as usual, directly or via `npx expo run:ios`/`yarn ios` (both also run `pod install` under the hood); the React Native CocoaPods integration configures and embeds the Swift package automatically. React Native prints a generic CocoaPods deprecation notice whenever `pod install` runs, regardless of how it's invoked — this isn't specific to Stripe Terminal.

### Fixes

- iOS: Fixed `cancelInstallingUpdate` and `cancelReaderReconnection` remaining pending when called without an active operation. They now return `CANCEL_FAILED`. 
- iOS: Retrying a failed `processPaymentIntent` or `processSetupIntent` now uses the updated intent returned in the error, when available.
- Android: Fixed invalid Tap to Pay UX color values causing an uncaught native exception. They now return an error with the `INVALID_REQUIRED_PARAMETER` code.
- iOS: Fixed `collectInputs` crashing when an input title or selection button style or text is missing or has the wrong type. It now returns an error with the `INVALID_REQUIRED_PARAMETER` code.
- Android: Fixed builds failing when using Android Gradle Plugin 9's built-in Kotlin support.
- Android: Fixed concurrent access to PaymentIntent and SetupIntent state, which could cause an intent returned by the SDK to become unavailable to a later SDK call.
- Fixed the `ReaderSupportResult` return type to distinguish supported readers, unsupported readers with a native error, and error-only parameter validation or native bridge failures from `supportsReadersOfType`.
- Android: Fixed a crash when a `collectInputs` input omitted its optional `required` field or set it to `null`. Other optional boolean and numeric parameters now also treat `null` as omitted instead of causing a native type error.
- Android: Fixed `onDidUpdateBatteryLevel.batteryStatus` returning uppercase values. The callback now returns the documented lowercase `Reader.BatteryStatus` values: `critical`, `low`, `nominal`, or `unknown`.
- Fixed response types to allow fields that native SDK 6.0 may omit, and fixed Android responses to omit those fields when unavailable. (from native 6.0.0)
- Fixed `PaymentIntent.paymentMethodTypes` and `SetupIntent.paymentMethodTypes` responses to consistently return React Native `PaymentMethodType` string values on both platforms.
- iOS: Fixed receipt responses omitting `ReceiptDetails.terminalVerificationResult`.
- Fixed Refund responses to preserve `canceled` and `requiresAction` statuses and expose required next-action details. (from native 6.0.0)
- iOS: Fixed payment method selection and QR code display callbacks for mobile and Tap to Pay readers with native SDK 6.0.
- iOS: Fixed `SetupIntent.paymentMethod` and `paymentMethodId` returning the wrong values with native SDK 6.0.
- Fixed a missing `package.json` error during Expo web export, including for apps that only use Terminal on native platforms. Fixes [#1136](https://github.com/stripe/stripe-terminal-react-native/issues/1136).
- iOS: Fixed `collectInputs` crashing when a toggle omits its optional `title` or `description`.
- Stopped logging raw errors from `tokenProvider` during SDK initialization and subsequent connection token requests, and when passing connection tokens to the native SDK.
- Stopped logging raw errors when diagnostic uploads fail unexpectedly.
- Fixed intermittent SDK initialization or reader connection failures where a configured `tokenProvider` was not invoked.
- Improved redaction of SDK diagnostic request, response, and exception logs and prevented diagnostic logging from interrupting SDK calls when values cannot be serialized.
- iOS: Fixed Tap to Pay reader error names being omitted from `StripeError.metadata`, including offline-mode failures. Use `StripeErrorMetadataKeys.IOS_TAP_TO_PAY_READER_ERROR_NAME` to read the value. (from native 5.5.0)
- iOS: Fixed `failQrCodeDisplay` and `failPaymentMethodSelection` reporting the failure as `UNEXPECTED_SDK_ERROR`, which made a deliberate cancellation indistinguishable from an internal error. Both now report `CANCELED`.
- Fixed `PaymentIntent`, `SetupIntent`, and `Refund` state attached to failed native operations being omitted from `StripeError`. Associated resources are now available as `error.paymentIntent`, `error.setupIntent`, or `error.refund` so integrations can inspect their state before retrying or canceling.

## 0.0.1-beta.33

Includes iOS native SDK [5.8.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.8.0) and Android native SDK [5.8.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#580---2026-08-17).

### New
- Added support for reading and setting the buzzer volume on supported readers through `getReaderSettings` and `setReaderSettings`. (from native 5.8.0)
  - Read `buzzerVolume.currentVolume` and `buzzerVolume.maxVolume` from `getReaderSettings`.
  - Set the volume to `low`, `high`, or a custom value between 1 and the reader's `maxVolume`.
  - Each `setReaderSettings` call accepts exactly one setting category: accessibility settings or buzzer volume.
  - Unsupported readers return `buzzerVolume.error`, and attempts to set their buzzer volume fail.
- Added the `PRINTER_LOW_BATTERY` error code, returned when the reader's battery is too low to complete a print operation. (from native 5.8.0)
- Added `automatic_delayed` capture method support for card-present `paymentMethodOptions.captureMethod` (with a new `captureDelayDays` option), for parity with other Stripe Terminal SDKs.

### Updates

- **Breaking:** Reader settings accessibility failures now omit `textToSpeechStatus` and return the error under `accessibility.error` on both platforms. Android previously returned these failures as a top-level `error`; the nested error preserves independently retrieved settings such as `buzzerVolume`.
- Android: Adopted the native 5.8.0 location/Bluetooth permission model. `requestNeededAndroidPermissions` now requests `ACCESS_COARSE_LOCATION` on Android 12 and later (and `ACCESS_FINE_LOCATION` on Android 11 and earlier, where BLE scanning still requires it), matching the native SDK which now declares `BLUETOOTH_SCAN` with `neverForLocation` and `ACCESS_FINE_LOCATION` with `maxSdkVersion="30"`. The Expo config plugin declares them the same way. If your app requires precise location for other purposes, request `ACCESS_FINE_LOCATION` yourself. (from native 5.8.0)
- iOS: A reader whose device type is not recognized by this version of the SDK is now surfaced with a `deviceType` of `unknown` instead of being omitted. (from native 5.8.0)
- The SDK is now built and tested against React Native 0.85, and the example app now uses Expo SDK 56. The iOS example app requires iOS 16.4 or later; the SDK remains compatible with apps targeting iOS 15.1 or later. `react-native` remains a `*` peer dependency, so the range of React Native versions your app can use is unchanged.

### Fixes

- iOS: Reader disconnect reasons are now accurate for Bluetooth mobile readers such as the Stripe Reader M2. A Bluetooth signal loss is reported as `bluetoothSignalLost`, selecting "Forget this device" in iOS Settings is reported as `peerRemovedPairingInformation`, and an unexpected internal disconnect is no longer misreported as `disconnectRequested`. (from native 5.8.0)
- iOS: Fixed a crash during Tap to Pay on iPhone `collectPaymentMethod` when the connected reader or reader account ID was unexpectedly unavailable. (from native 5.8.0)
- Android: Fixed a crash during `initialize` on devices with unsupported Android Keystore implementations. (from native 5.8.0)
- Android: Fixed mobile reader software updates timing out on slow network connections. (from native 5.8.0)
- Android (Tap to Pay): Fixed an issue causing PIN collection to fail on certain device models. (from native 5.8.0)

## 0.0.1-beta.32

Includes iOS native SDK [5.6.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.6.0) and [5.7.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.7.0), and Android native SDK [5.6.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#560---2026-06-08) and [5.7.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#570---2026-07-13).

### New

- Added `localeConfig` initialization support to configure localization of API error messages. Pass `{ type: 'cardLanguagePreferenceIfAvailable' }` to localize messages to the cardholder's preferred language when available, falling back to the device locale, or `{ type: 'hardcoded', locale: '<locale>' }` to use a fixed locale. API errors now include `localizationResult` when the native Terminal SDK provides localized error details.
- **Preview:** Surcharging is now supported on Tap to Pay readers (Tap to Pay on iPhone and Tap to Pay on Android). To request access to this preview, please contact [Stripe Support](https://support.stripe.com/). (from native 5.7.0)

### Updates

- Added a release and support lifecycle policy for the React Native SDK.
- Android: `onDidUpdateBatteryLevel` now only fires when the battery level, status, or charging state changes from the last reported value. Previously it fired on every battery poll (~every 10 minutes) regardless of whether the value changed. (from native 5.6.0)
- Android (Tap to Pay): API error messages from Tap to Pay attestation now default to English (`en-US`) instead of the application locale. (from native 5.6.0)
- Android (Tap to Pay): Discovered Tap to Pay readers that are already registered to a location now include their `location`, so it can be passed directly to `connectReader` without a separate location lookup. (from native 5.7.0)

### Fixes

- Android (Expo): Fixed the `tapToPayCheck` Expo config plugin option injecting the `TapToPay.isInTapToPayProcess()` guard in the wrong position in `MainApplication.kt` when other plugins that modify `onCreate()` are listed after `@stripe/stripe-terminal-react-native` in `app.config.ts`. The guard is now re-positioned immediately after `super.onCreate()` regardless of plugin order, ensuring code added by other plugins is correctly skipped in the Tap to Pay subprocess.
- iOS: Fixed crash when reloading the app in development or when the React Native bridge is torn down while a reader is connected or discovering. Events from the Terminal SDK were being sent to an invalidated bridge, causing an `NSInternalInconsistencyException` (`RCTCallableJSModules is not set`).
- Android: Fixed race condition where canceling a cancelable operation, such as calling `cancelCollectPaymentMethod()` within milliseconds of `collectPaymentMethod()`, could cause the operation to never resolve, leaving callers hanging indefinitely. (from native 5.6.0)
- Android: Fixed race condition where calling `cancelPaymentIntent()` or `cancelSetupIntent()` while `collectPaymentMethod` was in-flight on an internet reader could cause an unexpected disconnect after a 45-second timeout. (from native 5.6.0)
- Android: `onDidForwardPaymentIntent` offline callback now receives the up-to-date intent returned by the Stripe API rather than the stale locally-stored snapshot. (from native 5.6.0)
- Android: When programmatically canceling a payment on a smart reader, the error message is now `"Transaction is cancelled by the user."` instead of `"Job was canceled"`. (from native 5.6.0)
- Android (Tap to Pay): Fixed an issue where the immersive mode system overlay could cause the Tap to Pay collection screen to prematurely close. Fixes [#1120](https://github.com/stripe/stripe-terminal-react-native/issues/1120). (from native 5.6.0)
- iOS: Fixed a crash caused by a race condition during internal logging operations. (from native 5.6.0)
- iOS: Fixed a race condition where reader state could be mutated after a disconnect, leaving the SDK permanently stuck in the Connected state. (from native 5.6.0)
- iOS: **Preview:** Fixed an issue where `surchargeDetails.amount` was not included in the amount charged, which also caused an incorrect `maximumAmount` calculation. (from native 5.6.0)
- iOS: Fixed a mobile reader disconnect caused by a critically low battery being reported with the wrong reason. `onDidDisconnect` now receives `criticallyLowBattery` instead of `disconnectRequested`. (from native 5.7.0)
- Android: Fixed `collectPaymentMethod` not populating `PaymentIntent.paymentMethod` for non-card payment methods (e.g. Affirm) when `updatePaymentIntent` is enabled. (from native 5.7.0)
- Android (Tap to Pay): Fixed an issue where a reader could fail to connect when Keystore certificates registered to the device had expired. (from native 5.7.0)
- Android (Tap to Pay): Fixed `generatedCard` not being populated on `CardPresentDetails` after processing a `PaymentIntent`. (from native 5.7.0)
- Android (Tap to Pay): Fixed a crash when initiating payment collection in portrait orientation while the app was running in landscape. (from native 5.7.0)
- Android (Tap to Pay): Fixed a build issue where Terminal resource names could collide with those of certain third-party libraries. (from native 5.7.0)

## 0.0.1-beta.31 - 2026-05-28

Includes iOS native SDK [5.2.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.2.0), [5.3.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.3.0), [5.4.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.4.0), [5.5.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.5.0) and Android native SDK [5.5.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#550---2026-05-06), [5.5.1](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#551---2026-05-22).

### New

- Preview: Reauthorizations - Added support to authorize a `PaymentIntent` again after its capture window has lapsed.
  - Added `requestReauthorization` to `PaymentMethodOptions` for requesting reauthorization support when creating card-present PaymentIntents.
  - Added `reauthorizationStatus` and `reauthorizeBefore` response fields to `CardPresentDetails`.
  - To request access to this feature, please contact [Stripe Support](https://support.stripe.com/).
- Preview: Multicapture - Added multicapture support. The `collectPaymentMethod` params now accept a `requestMulticapture` field (`'ifAvailable' | 'never'`), and `CardPresentDetails` now exposes a `multicaptureStatus` field (`'available' | 'unavailable' | 'unknown'`).
  - To request access to this feature, please contact [Stripe Support](https://support.stripe.com/).
- Preview: Terminal Donations - Added support to skip donations flow per transaction by adding a `skipDonation` parameter to `CollectPaymentMethodParams` and `ProcessPaymentIntentParams`.
  - To request access to this private preview, please contact [Stripe Support](https://support.stripe.com/).
- Added `appTransitionAnimation` optional parameter to `ConnectAppsOnDevicesParams` and `EasyConnectAppsOnDevicesParams` (Android only). Controls the activity transition animation played when the reader app foregrounds during an [Apps on Devices](https://docs.stripe.com/terminal/features/apps-on-devices/overview) payment flow.
  - Accepts `{ type: 'systemDefault' }` (default), `{ type: 'preset', preset: AppTransitionPreset.SlideFromBottom }`, or `{ type: 'custom', enterAnim: number, exitAnim: number }`.
- Added support for [simulating software update scenarios](https://docs.stripe.com/terminal/references/testing#simulated-reader-updates) on physical mobile readers in sandbox or test mode.
  - Added `TestReaderUpdate` type and `UpdateComponent` enum. Set `testReaderUpdate` on `ConnectBluetoothReaderParams`, `ConnectBluetoothProximityReaderParams`, `ConnectUsbReaderParams`, or `ConnectTapToPayParams` (iOS only for Tap to Pay).
  - Added `components` field to `Reader.SoftwareUpdate` to expose which update components (firmware, config, keys, incremental) are included in an update.
  - **Breaking:** Removed `simulateReaderUpdate` function and `SimulateUpdateType` type in favor of this new per-connection API.
- Added Klarna as a supported payment method. `PaymentMethodType.Klarna` is now available and `klarnaDetails` is exposed on payment method details.
- Added `PaymentMethodType` const object with named values (`CardPresent`, `InteracPresent`, etc.) for use with `paymentMethodTypes` fields. String literals continue to work for backwards compatibility.
- Added the `captureBefore` response field to `CardPresentDetails`, previously only available via the server-side API.
- Added `lastSetupError` field to `SetupIntent`, exposing the error from the last failed setup attempt.
- Added `setupError` field to `SetupAttempt`, exposing the error from the setup attempt (available via `SetupIntent.latestAttempt`).
- Added new fields to `ApiErrorInformation`: `requestLogUrl`, `adviceCode`, `networkAdviceCode`, `networkDeclineCode`, `paymentMethod`, and `paymentMethodType`.

### Updates

- Preview: Surcharging - Expanded surcharge support: `amountDetails.surcharge` now includes `status` (`'available' | 'unavailable'`) and `maximumAmount` fields in addition to `amount`.
  - To request access to this feature, please contact [Stripe Support](https://support.stripe.com/).
- Updated `TapZoneFront` and `TapZoneBehind` types to enforce that `xBias` and `yBias` must be provided together or omitted together.
- Made `PaymentMethodOptions.requestedPriority` optional so `captureMethod` can be set independently.
- iOS + Android: Offline mode now falls back faster when the device cannot reach Stripe, with optimized per-request timeouts replacing the previous 15-second wait. (from native 5.5.0)
- Android: The simulated Tap to Pay payment collection screen UI was updated to match the livemode UI and can now be customized with [`setTapToPayUxConfiguration`](https://docs.stripe.com/terminal/payments/setup-reader/tap-to-pay?terminal-sdk-platform=android#user-interface). Pressing the screen simulates a successful payment; long pressing simulates a failed payment collection.

### Fixes

- Fixed `confirmPaymentIntent`, `processPaymentIntent`, `confirmSetupIntent`, and `processSetupIntent` invalidating unrelated intents on success, which could cause subsequent calls like `cancelPaymentIntent` to fail.
- Fixed `confirmPaymentIntent`, `processPaymentIntent`, `confirmSetupIntent`, and `processSetupIntent` not returning updated intent state on failure, preventing retry flows from working correctly.
- Fixed `disconnectReader`, `rebootReader`, and `clearCachedCredentials` not fully resetting SDK state for setup intents.
- Android: Fixed `disconnectReader` and `rebootReader` discarding intent state before the operation completes, which could lose intents if the call failed.
- Fixed `interacPresent` being silently dropped from `paymentMethodTypes` on iOS and Android when passed as a camelCase string.
- iOS: Fixed race condition causing Tap to Pay reader reconnection failures when the app returns to the foreground. (from native 5.2.0)
- iOS: Fixed race condition crash when connecting to readers. (from native 5.3.0)
- iOS: Fixed crash caused by delegate callbacks and completion handlers being dispatched on background threads under Swift concurrency. (from native 5.4.0)
- iOS: Fixed race condition crash during Bluetooth mobile reader discovery. (from native 5.5.0)
- Improved internal SDK telemetry to prevent OOM crashes during extended offline operation. The in-memory trace and event queues are now each capped at ~2 MB independently, and uploads are bounded, serialized, and time-limited so traces accumulating during long network outages can't grow unbounded or block on stuck requests. Set `logLevel: 'verbose'` on `StripeTerminalProvider` to print log upload diagnostics on the console.

## 0.0.1-beta.30 - 2026-04-23

Includes Android native SDK [5.2.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#520---2026-01-30), [5.3.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#530---2026-03-03), [5.4.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#540---2026-03-30), [5.4.1](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#541---2026-04-13).

### Fixes

- Fixed an issue with memory allocation causing connections to Tap to Pay on Android readers to fail. (from native 5.4.1)
- Fixed an issue where Tap to Pay connections failed with a `TAP_TO_PAY_INSECURE_ENVIRONMENT` error on certain devices even when developer options were not enabled. (from native 5.4.1)
- Fixed an issue where calling `discoverReaders()` while a reader is already connected incorrectly resets the internal connection status, causing subsequent operations to fail with a "You did not provide an API key" error. (from native 5.3.0)
- Fixed Bluetooth/USB auto-reconnection for a mobile reader hanging indefinitely, requiring a restart. (from native 5.4.0)
- Fixed issue where tap zone would change size on tablets depending on portrait or landscape orientation. (from native 5.4.0)
- Fixed `SecurityException` when user taps and removes a card quickly. (from native 5.4.0)
- Fixed stale network connectivity state in offline mode caused by multiple failed health checks polluting the connection pool. (from native 5.2.0)
- Fixed names of internal layout files to prevent conflicts when using both Tap to Pay and the Stripe SDK. (from native 5.2.0)

## 0.0.1-beta.29 - 2026-03-06

Includes iOS native SDK [5.0.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.0.0), [5.1.0](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.1.0), [5.1.1](https://github.com/stripe/stripe-terminal-ios/releases/tag/5.1.1) and Android native SDK [5.0.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#500---2025-11-03), [5.1.0](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#510---2025-12-03), [5.1.1](https://github.com/stripe/stripe-terminal-android/blob/master/CHANGELOG.md#511---2025-12-16).

### New

- **Preview:** Added Discover card acceptance for Tap to Pay on Android (Public Preview).
- **Preview:** Added simulated reader support for Mail Order / Telephone Order (MOTO) transactions.
- **Preview:** Added QR-based payment support on mobile readers (Public Preview).
- Added `processPaymentIntent` and `processSetupIntent` methods that combine the collect and confirm steps into a single operation. The existing `collectPaymentMethod`/`confirmPaymentIntent` and `collectSetupIntentPaymentMethod`/`confirmSetupIntent` methods continue to work but the unified methods are recommended.
- Added `easyConnect` API that combines reader discovery and connection into a single method call for smart readers and Tap to Pay integrations. Added `DiscoveryFilter` type to filter internet reader discovery by reader ID or serial number.
- Added `AppsOnDevicesTokenProvider` for serverless Apps-on-Devices mode. "Handoff" has been renamed to "Apps on Devices" across all class names.
- Added `RECONNECTING` connection status value, emitted during auto-reconnect operations for mobile readers (Bluetooth/USB) and Tap to Pay readers, providing better observability into reconnection state.
- Added missing `requiredForOffline` and `lowBatterySucceedConnect` in `SimulateUpdateType`.

### Updates

- **Breaking:** Changed customer cancellation to be enabled by default on supported readers. The previous `enableCustomerCancellation` boolean has been replaced with a `customerCancellation` parameter accepting `ENABLE_IF_AVAILABLE` (default) or `DISABLE_IF_AVAILABLE`. If your integration previously relied on customer cancellation being off, you must explicitly set `DISABLE_IF_AVAILABLE`.
- **Breaking:** Redesigned error handling. The SDK now provides a structured `StripeError` interface with standardized error codes, rich metadata (including decline codes, payment intent state), and TypeScript type safety. The legacy `CommonError` enum (`Failed`, `Canceled`, `Unknown`) has been removed. See the Error Handling section in README.md for details.
- **Breaking:** Replaced `collectRefundPaymentMethod`, `cancelCollectRefundPaymentMethod`, `confirmRefund`, and `cancelConfirmRefund` with `processRefund` and `cancelProcessRefund`.
- **Breaking:** Changed Interac refunds using a PaymentIntent ID to require the PaymentIntent's `clientSecret` parameter. You can alternatively continue using the charge ID, which doesn't require `clientSecret`.
- **Breaking:** Removed Stripe Reader P400 support.
- **Breaking:** Android Tap to Pay: Production environments now fail reader discovery with `TAP_TO_PAY_INSECURE_ENVIRONMENT` if developer options, USB/Wi-Fi debugging, or other debug options are enabled on the device. This does not apply to simulated readers.
- **Breaking:** Simplified `connectReader` API: `discoveryMethod` has been moved from a separate second parameter into `ConnectReaderParams`, consolidating connection configuration into a single object.
- **Breaking:** Refactored `TapToPayUxConfiguration`. The `tapZoneIndicator` and `tapZonePosition` fields have been replaced by a single `TapZone` union type object. Each tap zone variant now carries its own position parameters directly.
- Updated React Native version to 0.82.
- Minimum iOS deployment target updated from iOS 14.0 to iOS 15.0. (from native 5.0.0)
- Android Tap to Pay now requires that your Android device's KeyStore supports hardware-backed key agreements (FEATURE_HARDWARE_KEYSTORE version 100+) and Android 13 (API 33) as a minimum OS version. (from native 5.0.0)

### Fixes

- iOS: Fixed a crash that could occur when calling disconnectReader with internet-connected readers (from native 5.1.1).
- Android: Updated TLS root certificates for Stripe domains (from native 5.1.1).
- Android: Fixed missing ProGuard configuration rules affecting Tap to Pay compilation (from native 5.1.0).
- Android: Fixed unexpected reader disconnects when cards cannot be properly read (from native 5.1.0).
- Android: Fixed issue preventing simulated Tap to Pay reader usage (from native 5.1.0).
- Android: Added missing processing status in PaymentIntent.
- iOS: Fixed magstripe data collection errors on smart readers (from native 5.0.0).
