Skip to content

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented May 22, 2024

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Type Update Change Age Adoption Passing Confidence
actions/cache action major v4v5 age adoption passing confidence
actions/checkout action major v4v6 age adoption passing confidence
actions/setup-java action major v4v5 age adoption passing confidence
github/codeql-action action major v3v4 age adoption passing confidence
gradle (source) major 8.149.3.0 age adoption passing confidence
gradle/actions action major v4v5 age adoption passing confidence
com.stripe:stripeterminal-core dependencies major 3.10.25.1.1 age adoption passing confidence
io.insert-koin:koin-androidx-compose (source) dependencies major 3.5.64.1.1 age adoption passing confidence
com.github.triplet.play plugin major 3.9.14.0.0 age adoption passing confidence
androidx.compose:compose-bom dependencies major 2025.05.002026.01.00 age adoption passing confidence
com.android.library (source) plugin major 8.9.29.0.0 age adoption passing confidence
com.android.application (source) plugin major 8.9.29.0.0 age adoption passing confidence
co.touchlab.kmmbridge plugin major 0.5.51.2.1 age adoption passing confidence
org.orbit-mvi:orbit-core dependencies major 8.0.011.0.0 age adoption passing confidence
org.orbit-mvi:orbit-compose dependencies major 8.0.011.0.0 age adoption passing confidence
io.insert-koin:koin-android (source) dependencies major 3.5.64.1.1 age adoption passing confidence
io.insert-koin:koin-core (source) dependencies major 3.5.64.1.1 age adoption passing confidence

Release Notes

actions/cache (actions/cache)

v5

Compare Source

actions/checkout (actions/checkout)

v6

Compare Source

v5

Compare Source

actions/setup-java (actions/setup-java)

v5

Compare Source

github/codeql-action (github/codeql-action)

v4

Compare Source

gradle/gradle (gradle)

v9.3.0

Compare Source

v9.2.1: 9.2.1

Compare Source

The Gradle team is excited to announce Gradle 9.2.1.

Here are the highlights of this release:

  • Windows ARM support
  • Improved publishing APIs
  • Better guidance for dependency verification failures

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Adam,
Björn Kautler,
hasunzo,
HYEON,
Hyunjoon Park,
HYUNJUN SON,
Jendrik Johannes,
Kirill Gavrilov,
Madalin Valceleanu,
Martin Bonnin,
Matthew Haughton,
Mikhail Polivakha,
Na Minhyeok,
Philip Wedemann,
Philipp Schneider,
Róbert Papp,
Simon Marquis,
TheGoesen,
Vincent Potucek,
Xin Wang.

Upgrade instructions

Switch your build to use Gradle 9.2.1 by updating your wrapper:

./gradlew wrapper --gradle-version=9.2.1 && ./gradlew wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v9.2.0

Compare Source

v9.1.0: 9.1.0

Compare Source

The Gradle team is excited to announce Gradle 9.1.0.

Here are the highlights of this release:

  • Full Java 25 support
  • Native task graph visualization
  • Enhanced console output

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Eng Zer Jun,
EunHyunsu,
Gaëtan Muller,
HeeChul Yang,
Jendrik Johannes,
Johnny Lim,
Junho Lee,
Kirill Gavrilov,
Matthew Haughton,
Na Minhyeok,
Philip Wedemann,
Philipp Schneider,
Pradyumna C,
r-a-sattarov,
Ryszard Perkowski,
Sebastian Schuberth,
SebastianHeil,
Staffan Al-Kadhimi,
winfriedgerlach,
Xin Wang.

Upgrade instructions

Switch your build to use Gradle 9.1.0 by updating your wrapper:

./gradlew wrapper --gradle-version=9.1.0 && ./gradlew wrapper

See the Gradle 9.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v9.0.0: 9.0.0

Compare Source

The Gradle team is excited to announce Gradle 9.0.0.

Here are the highlights of this release:

  • Configuration Cache is the recommended execution mode
  • Gradle requires JVM 17 or higher to run
  • Build scripts use Kotlin 2.2 and Groovy 4.0
  • Improved Kotlin DSL script compilation avoidance

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aaron Matthis,
Adam E,
Adam S,
Björn Kautler,
Daniel Lacasse,
Eng Zer Jun,
EunHyunsu,
FlorianMichael,
Francisco Prieto,
Gaëtan Muller,
Jake Wharton,
Kengo TODA,
Kent Kaseda,
Madalin Valceleanu,
Marc Philipp,
Mark S. Lewis,
Matthew Haughton,
Mycroft Wong,
Na Minhyeok,
Nelson Osacky,
Olivier "Oli" Dagenais,
ploober,
Radai Rosenblatt,
Róbert Papp,
Sebastian Schuberth,
Victor Merkulov.

Upgrade instructions

Switch your build to use Gradle 9.0.0 by updating your wrapper:

./gradlew wrapper --gradle-version=9.0.0 && ./gradlew wrapper

See the Gradle 9.0.0 upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.4

Compare Source

v8.14.3: 8.14.3

Compare Source

The Gradle team is excited to announce Gradle 8.14.3.

This is a patch release for 8.14. We recommend using 8.14.3 instead of 8.14.

Here are the highlights of this release:

  • Java 24 support
  • GraalVM Native Image toolchain selection
  • Enhancements to test reporting
  • Build Authoring improvements

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.3 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.3 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.2: 8.14.2

Compare Source

The Gradle team is excited to announce Gradle 8.14.2.

Here are the highlights of this release:

  • Java 24 support
  • GraalVM Native Image toolchain selection
  • Enhancements to test reporting
  • Build Authoring improvements

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.2 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.2 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

v8.14.1: 8.14.1

Compare Source

The Gradle team is excited to announce Gradle 8.14.1.

Read the Release Notes

We would like to thank the following community members for their contributions to this release of Gradle:
Aurimas,
Ben Bader,
Björn Kautler,
chandre92,
Daniel Hammer,
Danish Nawab,
Florian Dreier,
Ivy Chen,
Jendrik Johannes,
jimmy1995-gu,
Madalin Valceleanu,
Na Minhyeok.

Upgrade instructions

Switch your build to use Gradle 8.14.1 by updating your wrapper:

./gradlew wrapper --gradle-version=8.14.1 && ./gradlew wrapper

See the Gradle 8.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading.

For Java, Groovy, Kotlin and Android compatibility, see the full compatibility notes.

Reporting problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines.
If you're not sure you're encountering a bug, please use the forum.

We hope you will build happiness with Gradle, and we look forward to your feedback via Twitter or on GitHub.

gradle/actions (gradle/actions)

v5

Compare Source

stripe/stripe-terminal-android (com.stripe:stripeterminal-core)

v5.1.1

Tap to Pay
Updates
  • Updated list of root certificates for Stripe domains based on the latest updates to Stripe's policy on pinning TLS Certificates. This supports the root certificate chain migration for api.stripe.com and other Stripe domains. See the announcement for more details.

v5.1.0

Core
New
  • Added simulated reader support for Mail Order / Telephone Order payments.
  • Added QR payment support for mobile readers.
Tap to Pay
Fixes
  • Added missing -dontwarn rules for Tap to Pay Proguard configuration. Fixes issue 590.
  • Prevent unexpected reader disconnects when a card cannot be properly read. Fixes issue 649.
  • Resolved issue preventing usage of simulated Tap to Pay reader. Fixes issue 652.

v5.0.0

5.0.0 includes breaking changes in both APIs and behavior. See the migration guide for more details.

⚠️ Breaking changes required
New Features and Previews
New
  • Simplified payment integration - Added Terminal.processPaymentIntent, Terminal.processSetupIntent and Terminal.processRefund. These new methods combine the collect and confirm steps into a single operation.
  • Coroutine support for Kotlin - A new optional module, com.stripe:stripeterminal-ktx:5.0.0 is now available. This module provides suspend function wrappers for asynchronous Terminal APIs, allowing you to write simple, sequential code instead of nesting callbacks.
  • Streamlined Connection flow - For Tap to Pay, smart readers, and Apps on Devices integrations, you can now use Terminal.easyConnect which combines the discovery and connection steps into a single method call.
  • RECONNECTING status - Added a new enum value RECONNECTING to ConnectionStatus. This new status is used specifically when an auto-reconnect operation is in progress.
Preview
  • Collect NFC and swiped data - The SDK now returns new, specific subclasses for this data: CollectData.Magstripe and CollectData.NfcUid.
  • Mail Order / Telephone Order (MOTO) Payments - The moto booleans on CollectConfiguration and SetupIntentConfiguration have been removed. To enable MOTO payments, you must now pass a non-null MotoConfiguration object to your collect configuration.
    • As past of this change, MotoConfiguration::skipCvv has been renamed to MotoConfiguration::skipCvc.
    • To request access to the this private preview, please contact Stripe Support.
Platform & Initialization
  • Terminal.init has replaced Terminal.initTerminal. The new method now requires a nullable OfflineListener parameter.
  • Consolidated Reader serial number fields. Please use serialNumber across all reader types. The duplicative serial and rawSerialNumber fields have been removed.
  • Terminal::clearCachedCredentials now requires that no reader is connected. It now returns a ClearCachedCredentialsResult object, and will fail with an UNEXPECTED_OPERATION error if called while connected to a reader.
Reader Discovery & Connection
  • Internet reader discovery now supports filtering by Reader::id or Reader::serialNumber. You can set the new discoveryFilter property on the InternetDiscoveryConfiguration to discover a specific reader.
  • The InternetConnectionConfiguration constructor parameters have been reordered, moving the required internetReaderListener parameter first to better support optional parameters.
  • The Terminal.connectedReader property will now remain null until the connection completes successfully. Previously, the property would be populated while the connection was still in progress.
Payment & Data Collection
  • Customer-initiated cancellation is now enabled by default on Smart readers during all relevant flows: payment collection, setup intents, refunds, and data collection flows. This feature can be disabled by setting customerCancellation to DISABLE_IF_AVAILABLE in the relevant collect configuration.
  • The PaymentStatus logic has been refined. After collectPaymentMethod succeeds, the status will transition to READY. However, if you call confirmPaymentIntent immediately from within the onSuccess callback of the collect, the status will skip READY and transition directly to PROCESSING.
  • The Cancelable::onSuccess callback is now guaranteed to be invoked after the operation being cancelled has failed, providing a single, reliable signal that the cancellation operation is complete.
  • Key configuration classes have been renamed to better reflect their purposes:
    • ConfirmConfiguration -> ConfirmPaymentIntentConfiguration
    • CollectConfiguration -> CollectPaymentIntentConfiguration
    • SetupIntentConfiguration -> CollectSetupIntentConfiguration
    • RefundConfiguration -> CollectRefundConfiguration
Tap to Pay
  • Increased the minimum OS version requirement to 33 (Android 13).
  • Tap to Pay on Android 5.0.0 requires that your Android device's KeyStore supports hardware-backed key agreements. This is checked automatically for you by Terminal.supportsReadersOfType(), but can also be verified by checking that your device's FEATURE_HARDWARE_KEYSTORE version is >= 100. This may not be supported if your device was released with Android 12 or lower, even if it has been upgraded to meet the Android 13 runtime requirement.
  • For production environments, reader discovery will now fail with a TAP_TO_PAY_INSECURE_ENVIRONMENT error if developer options, USB/Wi-Fi debugging, or other debug options are enabled on the device.
    • This does not apply to usage of the simulated Tap to Pay reader.
  • The TapToPayUxConfiguration.TapZone class has been refactored. The indicator and position fields have been replaced by a single TapZone object. You can now position the tap zone to the left or right side of the screen using TapZone.Left and TapZone.Right. The TapZone.Above and TapZone.Below options now also respect the horizontal bias value.
  • Added Discover payment method support for Tap to Pay on Android (Public Preview).
Apps on Devices
  • The Maven coordinates for this feature has changed to com.stripe:stripterminal-appsondevices:5.0.0. Please update your build dependencies.
  • "Handoff" has been renamed to "Apps on Devices" to better reflect the feature's functionality. The following classes have been renamed:
    • HandoffReaderListener -> AppsOnDevicesReaderListener
    • HandoffConnectConfiguration -> AppsOnDevicesConnectionConfiguration
    • HandoffDiscoveryConfiguration -> AppsOnDevicesDiscoveryConfiguration
    • HandoffConnectionTokenProvider -> AppsOnDevicesConnectionTokenProvider
Removal & Deprecation
  • Support for Stripe Reader P400 has been removed.
  • Terminal.collectRefundPaymentMethod and Terminal.confirmRefund are now deprecated. Please use the new Terminal.processRefund method instead.

v4.7.6

Core
Fixes
  • Addresses an issue where Tap & Chip devices may return a truncated device info, causing random firmware updates. This issue only takes place when connecting with an external USB channel.

v4.7.5

Core
Fixes
  • Fixes a duplicate class issue with kotlinx.datetime. Fixes issue 644.

v4.7.4

Core
Fixes
  • Resolves compatibility issues with kotlinx.datetime 0.7.0+. Fixes issue 611.

v4.7.3

Tap to Pay
Fixes
  • Addresses issues where a device may erroneously report as not being compatible with Tap to Pay on Android, or fail during the Tap to Pay on Android connection process with a KEY_ERROR. Fixes issue 629.

v4.7.2

Core
Fixes
  • Fixes an issue that caused the "Application Not Responding" (ANR) error that occurred during Terminal SDK initialization on certain Android devices.

v4.7.1

Tap to Pay
Fixes
  • Addresses 16KB page alignment issue. Fixes issue 577.

v4.7.0

Core
New
Fixes
  • Fixed an issue where the SDK fails to forward offline payments due to expired connection tokens. The SDK will now automatically refresh the connection token when it expires, allowing offline payments to be forwarded without interruption.

v4.6.0

Tap to Pay
Updates
  • For tablets, the payment collection screen now respects the device's orientation, and is no longer restricted to landscape. For phones, the orientation will still be locked to portrait. Fixes issue 565.
Fixes
  • Resolved a KeyStore issue that would result in an "Error setting key entry during secure import" message when attempting to connect to the Tap to Pay reader on certain devices. Fixes issue 561.
  • Resolved a network connectivity callback registration leak that could result in TooManyRequestsException after a long period of use. Fixes issue 576.
Apps on Devices: Handoff mode
Updates
  • Operations that require a connected reader will fail with NOT_CONNECTED_TO_READER when the application is no longer connected to the reader.
  • The SDK will automatically disconnect from the reader when a command results in a READER_COMMUNICATION_ERROR.
Fixes
  • Fixed spurious error logs Handoff client received Legacy callback. Fixes issue 481.

v4.5.1

Tap to Pay
Fixes
  • Addresses an issue that resulted in significantly reduced authorization rates for payments made with Tap to Pay on Android. Stripe highly discourages using Tap to Pay on Android 4.5.0 in any production environments. Fixes issue 596.

v4.5.0

Core
New
Updates
  • The Terminal.collectInputs method to display forms and collect information from customers is now generally available, and it no longer requires an opt-in annotation.
  • Preview: The ConfirmConfiguration.amountSurcharge field has been renamed to ConfirmConfiguration.surcharge.amount.
    • If you are interested in joining this preview, please contact Stripe support.
Tap to Pay
Updates
  • Improved messaging for Play Integrity API failures during the reader connection process. Fixes issue 580.

v4.4.0

Core
New
Fixes
  • Terminal operations that require a connected reader (e.g. collectPaymentMethod) will now fail with TerminalErrorCode.NOT_CONNECTED_TO_READER when no reader is connected.
Tap to Pay
New
Fixes
  • Gracefully handle device-to-device restore for apps that use the android:allowBackup="true" manifest tag. Fixes issue 513.
  • Terminal.supportsReadersOfType() will now return false when checking Tap to Pay on Android compatibility for host devices that do not support certain hardware-backed KeyStore operations. Fixes issue 553.
  • Prevent Tap to Pay reader connections from failing on devices without an accelerometer. Fixes issue 562.

v4.3.1

Core
  • Fix: Prevent crashes in applications using newer versions of Sentry. Fixes issue 566.

v4.3.0

Core
Tap to Pay
  • New: On-screen PIN entry is now generally available on Tap to Pay Android.
  • Breaking: When Tap to Pay Android PIN throws a TerminalException due to an insecure condition the exception will have a correct errorCode of TAP_TO_PAY_INSECURE_ENVIRONMENT instead of TAP_TO_PAY_DEVICE_TAMPERED.
  • Fix: Prevent a StringIndexOutOfBoundsException crash on certain device models prior to showing the Tap to Pay payment screen. Fixes issue 533.
  • Update: Improved error messaging when Tap to Pay on Android PIN fails due to an insecure condition.

v4.2.0

Core
  • New: Added error code READER_TAMPERED for detecting if a mobile reader is tampered on connection.
  • Fix: Addressed an issue where readers lose optional software updates after auto-reconnecting.
Tap to Pay
  • New: HIDE_OVERLAY_WINDOW permission is now required for Tap to Pay to ensure a secure environment while operating.
  • Fix: Allow the Tap to Pay reader to connect from applications that have enabled installer checks in Google Play. Fixes issue 866.
  • Fix: Localization issues for Tap to Pay on Android PIN preview.

v4.1.0

Core
  • Preview: Affirm support for smart readers is now available in private preview.
  • New: Added a returnUrl parameter to ConfirmConfiguration to specify a desired URL to redirect to upon completion of a redirect payment method (such as Affirm).
  • Update: Added support for operating offline with simulated Bluetooth and USB readers.
  • Preview: Added a new enum value Manual to CardPresentCaptureMethod which will override the top level captureMethod set on the Paymentintent specifically for card_present transactions.
  • Preview: Terminal::collectData will be supported on Smart readers.
  • Fix: Fixed an issue where, if the SDK was initialized offline and a user immediately attempts to pair a reader offline, the first attempt fails with "The selected reader requires a software update", despite the reader being up-to-date.
Tap to Pay

v4.0.0

4.0.0 includes breaking changes in both APIs and behavior. See the migration guide for more details.

Core

Add support for apps built with targetSdkVersion = 35 targeting Android 15 devices.

  • Note: This update includes support for Tap to Pay on Android. Users who were previously advised not to upgrade can now safely target version 35.
New Features
  • Mail order / telephone order (MOTO) payment support for smart readers.
    • Contact Stripe support to enable this feature on your account.
  • Global card saving after payment support by updating customer consent capture. The following breaking changes are required:
    • Removed the customerConsentCollected parameter from Terminal::collectSetupIntentPaymentMethod and replaced it with allowRedisplay.
    • A valid allowRedisplay value is now required to be set in collectConfiguration when using setupFutureUsage for Terminal::collectPaymentMethod.
⚠️ Breaking changes required
Reader discovery
  • New: Added a new enum value DISCOVERING to ConnectionStatus to represent when discovery is running.
  • Update: InternetDiscoveryConfiguration now supports an optional timeout value, specifying the timeout in seconds for discover readers request. If the online discovery attempt fails, the operation automatically fall back to offline discovery.
  • Update: If a new discover operation is initiated while one is already in progress, the SDK will now cancel the ongoing operation with a CANCELED_DUE_TO_INTEGRATION_ERROR error and start the new operation.
  • Update: Internet and Tap to Pay discovery will now call the Callback.onSuccess method as part of discoverReaders when the operation completes since these are not long running discovery operations.
  • Update: Fields on the Location object are no longer mutable.
Reader connection
  • Update: There is now a single Terminal::connectReader method for all connection types. This replaces the previous methods: connectBluetoothReader, connectUsbReader, connectInternetReader, connectLocalMobileReader, and connectHandoffReader.
    • For mobile readers, the readerListener parameter has been removed from the old connectBluetoothReader, connectUsbReader methods and moved into the respective ConnectionConfiguration object, replacing ReaderReconnectionListener.
    • For Tap to Pay readers, the TapToPayConnectionConfiguration now takes in a TapToPayReaderListener parameter, replacing ReaderReconnectionListener.
    • For smart readers, InternetConnectionConfiguration now takes in an InternetReaderListener parameter, which will alert your integration of events such as reader disconnects.
    • For Apps on devices in handoff mode, HandoffReaderListener has been removed from the old connectHandoffReader method as a parameter, and moved into the HandoffConnectionConfiguration object.
  • Update: Auto reconnect on unexpected disconnect is now enabled by default for mobile readers and Tap to Pay readers.
    • For mobile readers, ReaderListener has been renamed to MobileReaderListener and now extends ReaderReconnectionListener to provide a single interface for handling reader reconnection events.
    • For Tap to Pay readers, TapToPayReaderListener extends ReaderReconnectionListener to provide a single interface for handling reader reconnection events.
    • The ReaderReconnectionListener parameter has been removed from the connection configurations: LocalMobileConnectionConfiguration, BluetoothConnectionConfiguration, and UsbConnectionConfiguration.
    • Auto-reconnect is now supported for simulated mobile readers. Users can now trigger events, such as ReaderReconnectionListener::onReaderReconnectStarted, by invoking Terminal::rebootReader.
    • The ReaderReconnectionListener::onReaderReconnectStarted event has been updated to always include the DisconnectReason parameter, indicating the possible reasons for a mobile reader disconnection. For other reader types, UNKNOWN will be returned.
  • Update: The method for handling reader disconnects has changed.
    • The TerminalListener::onUnexpectedReaderDisconnect has been removed. Implement onDisconnect on any of the following listeners to be informed of their corresponding reader disconnects: InternetReaderListener, MobileReaderListener, TapToPayReaderListener, or HandoffReaderListener.
    • When auto-reconnect on unexpected disconnect is enabled, both onDisconnect and onReaderReconnectFailed methods will be called if the SDK fails to reconnect to the reader and it becomes disconnected.
Payment acceptance
  • Update: Terminal::confirmPaymentIntent, Terminal::confirmSetupIntent, and Terminal::confirmRefund now return a Cancelable, which allows you to cancel the

Configuration

📅 Schedule: Branch creation - "after 10pm every weekday,before 4am every weekday,every weekend" in timezone Europe/Vienna, Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot force-pushed the renovate/major-risky-update branch from 5627b9a to c42c701 Compare May 23, 2024 09:58
@renovate renovate bot changed the title renovate: update major-risky-update to v2 renovate: update major-risky-update May 23, 2024
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 30778d8 to 46f3010 Compare June 5, 2024 23:16
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 46f3010 to d8eb979 Compare June 11, 2024 17:15
@renovate renovate bot changed the title renovate: update major-risky-update renovate: update major-risky-update to v2 Jun 11, 2024
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from ab84ea0 to d674793 Compare June 17, 2024 13:23
@renovate renovate bot force-pushed the renovate/major-risky-update branch from d674793 to 245d32e Compare June 27, 2024 11:06
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 245d32e to 123ff68 Compare July 5, 2024 19:02
@renovate renovate bot changed the title renovate: update major-risky-update to v2 renovate: update major-risky-update Jul 5, 2024
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from d8e7be7 to 6ba9da4 Compare July 12, 2024 16:04
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 4d7a812 to ce2119d Compare August 4, 2024 00:14
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from ea7a18e to 6777311 Compare August 6, 2024 23:48
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from b1f0c5d to c148487 Compare August 27, 2024 22:24
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 6935fa9 to 0ecbde6 Compare September 5, 2024 22:58
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 3cb1ad6 to 0ac54aa Compare September 17, 2024 11:57
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 0341a42 to 6f4f517 Compare October 10, 2024 10:04
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 6f4f517 to 1e8dbb7 Compare October 11, 2024 06:46
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from a7626f5 to 63a26a0 Compare June 10, 2025 19:31
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 63a26a0 to 100e721 Compare July 9, 2025 23:15
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 9edb014 to 37c0b94 Compare August 5, 2025 19:18
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 37c0b94 to 646759f Compare August 11, 2025 13:05
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 646759f to f3464f6 Compare August 21, 2025 06:31
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 2e402b0 to f713597 Compare September 5, 2025 21:12
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 955b6ed to 2f8fe1c Compare September 16, 2025 18:02
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 0a7604d to c229b43 Compare September 23, 2025 17:53
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 5e7dc32 to 7d94405 Compare October 1, 2025 20:49
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 7d94405 to 31ad30f Compare October 7, 2025 16:33
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from 3a17818 to b2a8193 Compare November 3, 2025 19:51
@renovate renovate bot force-pushed the renovate/major-risky-update branch from b2a8193 to bd1df20 Compare November 8, 2025 12:44
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 49c77b1 to 681a8c3 Compare November 20, 2025 16:36
@renovate renovate bot force-pushed the renovate/major-risky-update branch from 681a8c3 to c71a0cb Compare December 4, 2025 02:48
@renovate renovate bot force-pushed the renovate/major-risky-update branch 2 times, most recently from 7570df9 to fced171 Compare December 17, 2025 04:10
@renovate renovate bot force-pushed the renovate/major-risky-update branch 3 times, most recently from a3a290c to efbfe4a Compare January 17, 2026 02:55
@renovate renovate bot force-pushed the renovate/major-risky-update branch from efbfe4a to 141332b Compare January 25, 2026 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants