Release 5.0.3

• [ADDED] Introduces "configureRetryPolicy()" in the payment builder to configure the retry policy when the result of a transaction can not be retrieved at the end of a transaction. (see dedicated section in README here for more)
  • Both pollingInterval and maxWaitingTime should be provided in milliseconds.
  • If disableBackButton is set to true, the Android device's back button will be disabled while the retry screen is shown.
  • If maxWaitingTime elapses without a response, SumUpAPI.ResultCode.ERROR_UNKNOWN_TRANSACTION_STATUS will be returned.
  • If disableBackButton is set to false, pressing the back button while the retry screen is displayed will also return SumUpAPI.ResultCode.ERROR_UNKNOWN_TRANSACTION_STATUS.
  • If pollingInterval is greater than maxWaitingTime, the value of maxWaitingTime will be adjusted to match pollingInterval.
  • If either pollingInterval or maxWaitingTime is passed as a negative value, it will default to 0.
  • If configureRetryPolicy() is not called, the SDK will default to returning the SumUpAPI.ResultCode.ERROR_TRANSACTION_FAILED error code, and default values will be used while trying to get the status of the transaction.
  • Default values are 2000 ms for the pollingInterval and 60000 ms for the maxWaitingTime.

Release 5.0.2

• [FIXED] An issue where successful transactions were returned without all the relevant information in the SumUpAPI.Response.TX_INFO object, e.g. the card type
• [FIXED] A bug where initiating a checkout while the Card Reader payment method was disabled in the merchant settings resulted in a transaction failure. The SDK now enables it intrinsically
• [KNOWN BEHAVIOR]
  • Declined/failed transactions may sometimes not return the card data (only) - SumUpAPI.Response.TX_INFO will still be populated with all the remaining metadata. This would depend on the exact moment any connectivity issue happened, that is whether card data from the reader was sent to the back-end or not.

Release 5.0.1

• [FIXED] "duplicate class" issue (due to R8 obfuscation) possibly happening when integrating with other external libraries

Release 5.0.0

• [ADDED] Support for the Solo Lite card reader (beta phase)
• [ADDED] Support for the Australian Dollar and Mexican Pesos currencies: SumUpPayment.Currency.AUD, SumUpPayment.Currency.MXN
• [ADDED] New Troubleshooting flow for all our readers
• [ADDED] Introduction of a unified Black and White theme that represents "One Design Language" across all SumUp products
• [FIXED] A crash that was happening due to the Play Services location version incompatibility
• [IMPROVEMENT] Updates about the technical stack:
  • Minimum supported targetSDK is upgraded to 31
  • Minimum Kotlin is upgraded to 1.7.21
  • Minimum Kotlin Coroutine is upgraded to 1.6.4
  • Minimum AndroidX Activity is upgraded to version 1.5.1
  • Minimum AndroidX Fragment is upgraded to version 1.5.7
  • Minimum AppCompat is upgraded to 1.4.2
  • Minimum Material Components is upgraded to 1.6.1
  • Minimum Moshi is upgraded to 1.14.0
  • Minimum Hilt is upgraded to 2.44.2
  • Minimum AGP is upgraded to 7.3.0
  • Building with AGP 7.3.0
  • Play services location upgraded to 21.0.1

Release 4.3.0

• [REMOVED] Dropping support for Android 7 (API 25) and below
• [ADDED] Solo USB under 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 limitation: 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 the Card Reader page.

Release 4.2.0

• [ADDED] Support for Peruvian Sol currency – SumUpPayment.Currency.PEN
• [IMPROVEMENT] Enhanced tablet view UI in card reader setup when multiple card readers are discovered.

Release 4.1.1

• [FIXED] A misbehavior that could lead to isolated cases of rescanning for a card reader before a checkout
• [FIXED] A crash that can occur when finalizing a firmware update on an Air card reader

Release 4.1.0

• [ADDED] Introduction of the tip on card reader feature, which allows the customer to add a tip directly on the card reader instead of the Android device with tipOnCardReader (see dedicated section in README here for more)
• [IMPROVEMENT] Retain BLE connection at the end of a transaction is now default - SumUpExperimentalAPI.prepareForCheckout(boolean retainBLEConnection) is deprecated accordingly in favor of SumUpAPI.prepareForCheckout()
• [IMPROVEMENT] Enhanced reader UI during checkout
• [IMPROVEMENT] Miscellaneous bug fixes and enhancements

Release 4.0.3

• [FIXED] "duplicate class" issue (due to R8 obfuscation) possibly happening when integrating with other external libraries

Release 4.0.1

• [FIXED] A crash after successful transaction if one of the receiptEmail or mobilePhone is missing from the SumUpPayment.builder()