You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: CHANGELOG.md
+11-1Lines changed: 11 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,8 +1,18 @@
1
1
# Changelog
2
2
3
3
For more information, see the [README](https://github.com/sumup/Android-MerchantSDK/blob/master/README.md)
4
+
## Version 7.0.0
5
+
*[ADDED]`successScreenTimeout` in the payment builder to configure the duration of the success screen.
6
+
*[ADDED]`getSavedCardReaderDetails()` to retrieve details of the saved card reader (serial number, type, and battery percentage).
7
+
*[ADDED]`isCardReaderConnected()` to check if a card reader is currently connected.
8
+
*[IMPROVEMENT] Offline transaction V2
9
+
* Changes the API and behavior about how offline transactions work.
10
+
* Explicit APIs to start and stop the offline session.
11
+
* Removal of Security Patch Validity API.
12
+
*[OFFLINE_PAYMENTS_V2.md](https://github.com/sumup/sumup-android-sdk/blob/master/OFFLINE_PAYMENTS_V2.md) for more information.
13
+
4
14
## Version 6.0.0
5
-
*[ADDED] Introduces Offline payments with Solo lite, please refer to the dedicated section in [OFFLINE_PAYMENTS.md](https://github.com/sumup/sumup-android-sdk/blob/master/OFFLINE_PAYMENTS.md) for more information.
15
+
*[ADDED] Introduces Offline payments with Solo lite, please refer to the dedicated section in [OFFLINE_PAYMENTS_V1.md](https://github.com/sumup/sumup-android-sdk/blob/master/OFFLINE_PAYMENTS.md) for more information.
6
16
* Please contact integrations@sumup.com for enabling offline payments on your SumUp merchant account.
7
17
*[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.
@@ -22,7 +22,7 @@ For more information about SumUp developer products, please refer to <a href="ht
22
22
3. Created an Affiliate Key in [SumUp Dashboard](https://developer.sumup.com/terminal-payments/sdks/android-sdk)
23
23
4. SumUp SDK requires `minSdkVersion` 26 or later
24
24
5. SumUp SDK ensures support for
25
-
-`targetSDK` 35 or later
25
+
-`targetSDK` 35
26
26
- AGP 8.8.0 or later
27
27
- Kotlin version 1.9.0 or later
28
28
- Java 17 and later
@@ -52,7 +52,7 @@ allprojects {
52
52
Add the dependency to a module:
53
53
54
54
```groovy
55
-
implementation 'com.sumup:merchant-sdk:6.0.0'
55
+
implementation 'com.sumup:merchant-sdk:7.0.0'
56
56
```
57
57
58
58
@@ -107,6 +107,8 @@ Once logged in, you can start using the SumUp SDK to accept card payments. If no
107
107
.foreignTransactionId(UUID.randomUUID().toString()) // can not exceed 128 chars
108
108
// optional: skip the success screen
109
109
.skipSuccessScreen()
110
+
// optional: time out for the success screen
111
+
.successScreenTimeout(3)
110
112
// optional: skip the failed screen
111
113
.skipFailedScreen()
112
114
.build();
@@ -125,7 +127,7 @@ Once logged in, you can start using the SumUp SDK to accept card payments. If no
125
127
```
126
128
127
129
### 6. Offline payments
128
-
* For offline payments support, please refer to the [Offline payments](https://github.com/sumup/sumup-android-sdk/blob/master/OFFLINE_PAYMENTS.md) documentation.
130
+
* For offline payments support, please refer to the [Offline payments](https://github.com/sumup/sumup-android-sdk/blob/master/OFFLINE_PAYMENTS_V2.md) documentation.
129
131
130
132
## II. Additional features
131
133
@@ -247,6 +249,9 @@ If there are connectivity issues and the transaction status can not be retrieved
247
249
The `foreignTransactionID` identifier will be associated with the transaction and can be used to retrieve details related to the transaction. See [API documentation](https://developer.sumup.com/rest-api/#tag/Transactions) for details. Please make sure that this ID is unique within the scope of the SumUp merchant account and sub-accounts. It must not be longer than 128 characters.
248
250
The foreignTransactionID is available when the callback activity is called: `SumUpAPI.Param.FOREIGN_TRANSACTION_ID`
249
251
252
+
#### Timeout on success screen
253
+
Use `.successScreenTimeout(int seconds)` to configure the success screen duration (must be > 0), which automatically dismisses the screen after the specified time if the user has not closed it manually.
254
+
250
255
#### Skip success screen
251
256
To skip the success screen shown at the end of a successful transaction, the `skipSuccessScreen` parameter can be used. When using this parameter your application is responsible for displaying the transaction result to the customer. In combination with the Receipts API your application can also send your own receipts, see [API documentation](https://developer.sumup.com/rest-api/#tag/Receipts) for details. Please note success screens will still be shown when using the SumUp Air Lite readers.
252
257
@@ -278,13 +283,31 @@ If a merchant account is currently logged in, it is possible to retrieve the dat
278
283
}
279
284
```
280
285
281
-
### 7. Log out SumUp account
286
+
### 7. Retrieve connected card reader's data
287
+
288
+
You can use the following methods to check the connection status and retrieve details about the saved card reader:
289
+
290
+
***`isCardReaderConnected()`**: Returns a `boolean` indicating if a card reader is currently connected.
291
+
***`getSavedCardReaderDetails()`**: Returns an object containing the reader's serial number, type, and last known battery percentage.
292
+
293
+
#### Supported Reader Types
294
+
The reader type will be one of the following constants:
295
+
*`SOLO`
296
+
*`SOLO_LITE`
297
+
*`AIR`
298
+
*`THREE_G`
299
+
*`PIN_PLUS`
300
+
*`UNKNOWN` (Returned only if the SDK encounters an issue and cannot identify the reader type)
301
+
302
+
> **Note on Battery Level:** The `lastKnownBatteryPercentage` is **not** real-time. It reflects the battery level recorded during the last transaction performed. As a result, this value is an approximation and may not match the current battery level exactly if the reader has been idle or charged since the last payment.
303
+
304
+
### 8. Log out SumUp account
282
305
```java
283
306
SumUpAPI.logout();
284
307
```
285
308
286
309
287
-
### 8. Enable ProGuard
310
+
### 9. Enable ProGuard
288
311
```groovy
289
312
buildTypes {
290
313
release {
@@ -295,7 +318,7 @@ If a merchant account is currently logged in, it is possible to retrieve the dat
295
318
}
296
319
```
297
320
298
-
### 9. Use Google Location Services
321
+
### 10. Use Google Location Services
299
322
300
323
The SDK supports Google Location Services, to improve location accuracy and reduce power consumption.
0 commit comments