Android Changelog

We recommend updating to this version of the SDK for security enhancements.

New Features

• Added optional timeoutCardWaitSeconds to startPayment, allowing integrators to configure how long the SDK waits for card presentation.
• The default card-wait timeout is now 240 seconds. Supported values are clamped between 60 and 240 seconds.
• Updated SDK build support for Android 16 / API 36.
• Updated core security, attestation, obfuscation, and payment kernel dependencies.

Fixes

• Fixed an issue where rotating the device during an active transaction could interrupt the payment flow.
• Fixed a recovery issue where transactions could keep failing with “Could not connect to the server” after a temporary network failure until the app was restarted.
• Improved NFC card-read handling by retrying after supported L1 read errors.

Integration Notes

• Existing integrations continue to work without code changes.
• Integrators can optionally pass timeoutCardWaitSeconds when starting a payment to customize the card presentation timeout.

New Features

• Added support for SUNMI devices and other Android terminals that use internal (non-external) NFC adapters

Fixes

• Prevent fatal crash when the SDK performs an authenticated network request without an AuthTokenProvider configured

Fixes

• Reliability improvements
• Improved security

Android SDK(Opens in a new tab) 7.1.0 has been released(Opens in a new tab).

Added:

• Support for target SDK 36.
• Support for Android Gradle Plugin 9.x.
• SumUpLoginContract, SumUpCardReaderPageContract, and SumUpCheckoutContract to support Activity Result API integrations. Existing onActivityResult-based integrations remain unchanged. Please refer to the documentation for more information.

Improvements:

• Reduced SDK size by approximately 8 MB.
• In offline sessions, totalApprovedAmount now includes tip amounts.

Important: SDK v7.1.0 introduces internal changes that are not backward compatible. After upgrading and running the application with v7.1.0, downgrading to an earlier SDK version is not supported.

Fixes

• Fixed crashes caused by no network connection or authorization errors

New Features

• Improved security
• Improved transaction speed

Important

• Starting from this version, core library desugaring(Opens in a new tab) is required

New Features

• Improved test capabilities for the production environment
• WBC Rotation - January 2026
• The CardReadFailed -> UnexpectedOutcome error is caught, and the system smoothly retries reading the card

Android SDK(Opens in a new tab) 7.0.0 has been released(Opens in a new tab).

Added:

• successScreenTimeout in the payment builder to configure the duration of the success screen.
• getSavedCardReaderDetails() to retrieve details of the saved card reader (serial number, type, and battery percentage).
• isCardReaderConnected() to check if a card reader is currently connected.

Improvements:

Introduction of Offline transaction V2

• Changes the API and behavior about how offline transactions work.
• Explicit APIs to start and stop the offline session.
• Removal of Security Patch Validity API.
• Please have a look at OFFLINE_PAYMENTS_V2.md(Opens in a new tab) for more information.

Fixes

• Fixed an issue where the SecurePin Entry screen closes after the first digit is entered on Zebra TC77 and Honeywell CT45 devices

New Features

• Added clear error screens for common problems, such as attestation failures when USB debugging is turned on.

Fixes

• Fixed infinite loading when NFC is disabled or unavailable on the device.
• Security improvements.
• Small UI improvements and bug fixes.

Fixes

• Added security improvements and bug fixes to enhance overall stability and performance of the SDK.

Fixes

• Added support for 16 KB page sizes.

Fixes

• Fixed wrong currency code in Peru.

Android SDK(Opens in a new tab) 6.0.0 has been released(Opens in a new tab).

Offline payments

• Introduces Offline payments with Solo lite, please refer to the dedicated section in OFFLINE_PAYMENTS.md(Opens in a new tab) for more information.
  • Please contact us through the contact form to enable offline payments on your SumUp merchant account.

Added:

• Payment intent now also returns the card reader model and firmware version in new response fields SumUpAPI.Response.CARD_READER_MODEL and SumUpAPI.Response.CARD_READER_FIRMWARE_VERSION at the end of every transaction.

Improvements:

• Renames package of TransactionInfo: com.sumup.merchant.reader.models.TransactionInfo > com.sumup.checkout.core.models.TransactionInfo
• Renames package of SumUpState: import com.sumup.merchant.api.SumUpState > import com.sumup.reader.sdk.api.SumUpState
• Miscellaneous bug fixes and enhancements.

Updates about the technical stack:

• Minimum supported targetSDK is 35
• Minimum Kotlin is upgraded to 1.9.0
• Minimum Kotlin Coroutine is upgraded to 1.8.0
• Minimum Hilt is upgraded to 2.51.1
• Minimum Moshi is upgraded to 1.15.0
• Minimum AppCompat is upgraded to 1.7.0
• Minimum AndroidX Annotation is upgraded to version 1.8.0
• Minimum AndroidX Activity is upgraded to version 1.9.1
• Minimum AndroidX Fragment is upgraded to version 1.7.1
• Minimum AndroidX Lifecycle is upgraded to version 2.8.1
• Minimum AndroidX Browser is upgraded to version 1.4.0
• Minimum AndroidX Navigation is upgraded to version 2.7.7
• Minimum Material Components is upgraded to 1.12.0
• Minimum Play Services Location is upgraded to 21.3.0- Minimum AGP is upgraded to 8.8.0
• Building with AGP 8.8.0 and Java 17
• Introduces Jetpack Compose BOM version 2023.06.01
• Requires desugar_jdk_libs version 2.1.5

Fixes

• Decreased the SDK size by removing unused resources.
• Fixed an issue where the testing SDK build would not initialize.

New Features

• Added support of Online Pin SCA (Strong Customer Authentication).
• Added card data to PaymentEvent.TransactionDone event: card type, card scheme, last four digits, and merchant code.
• Transparent attestation process. The SDK now returns error details if attestation fails in PaymentEvent.TransactionFailed event. This helps developers understand and resolve attestation issues more effectively.
• API changes to make it more concise. Now TapToPay.startPayment() function returns Flow<PaymentEvent> instead of Flow<Result<PaymentEvent>>.

New Features

• Added Products to TapToPay.startPayment method.
• Enabled periodic monitoring and attestation.
• Now SDK uses Google Trusted Time API.

Fixes

• Fixed a crash that occurred when attempting to make a payment without explicitly setting skipSuccessScreen parameter.
• Fixed a bug in Pixel 8 and Pixel 9 devices with Android 16 where the payment would immediately fail a transaction with timeout error.

Fixes

• Fixed a bug with payment availability when using OkHttp 5.0.0 or higher.

Fixes

• Miscellaneous bug and crash fixes

Fixes

• NoBeanFoundDefinitionError exception that occurred in some cases when starting a payment
• Miscellaneous bug and crash fixes

New Features

• Faster Transactions – Reduced latency when initiating transactions, resulting in faster checkout.
• Mitigated Threats Filter – Attestation now excludes resolved threats for smoother processing and less transaction failures.
• Affiliate Key Support – Added support for affiliate key integration.
• Success Screen Skip Flag – New flag to bypass the success screen.
• Support for targetSDK 35
• Client-Side Certificate Verification – Enhanced security with device certificate checks during attestation.
• Pre-PIN Attestation – Attestation is initiated before displaying the PIN screen to enhance security.

Fixes

• Resolved an issue during TapToPay initialization.

Fixes

• Fixed the class duplication issue occurring after obfuscation.

Fixes

• Mitigated threats are now filtered out during attestation. If a threat has "mitigated": true, it is excluded from the threat list that is used to determine whether the COTS is attested.

New Features

• New events of the payment process: card requested, card presented, CVM requested, CVM presented - New PaymentException types

Fixes

• Cleanup PAN data from memory
• Disable NFC for other apps during the payment process. - Handling empty candidates list in payment processing

Android SDK(Opens in a new tab) 4.3.0 has been released(Opens in a new tab).

Solo USB (Beta)

The Solo card reader now supports connecting and transacting over USB cable. The minimum required Solo software version that supports the USB mode is 3.3.17.2.

If this version (3.3.17.2) is not yet available on your Solo when connected via Bluetooth, you can switch it to standalone mode (Menu -> Connection -> WiFi), login directly on the Solo, and update it to the latest version.

Solo USB is under beta phase which means that the feature still requires some optimization to ensure full stability.

Known limitations: currently, if the USB cable is unplugged, the USB permission on the mobile device will need to be regranted. As of now, Solo is not able to wake up automatically from sleep mode. A connection needs to be reestablished from

Removed:

• Dropping support for Android 7 (API 25) and below