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
+11Lines changed: 11 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,17 @@
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 5.0.3
5
+
*[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](https://github.com/sumup/sumup-android-sdk#retry-policy-configuration) for more)
6
+
* Both `pollingInterval` and `maxWaitingTime` should be provided in milliseconds.
7
+
* If `disableBackButton` is set to true, the Android device's back button will be disabled while the retry screen is shown.
8
+
* If `maxWaitingTime` elapses without a response, `SumUpAPI.ResultCode.ERROR_UNKNOWN_TRANSACTION_STATUS` will be returned.
9
+
* 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`.
10
+
* If `pollingInterval` is greater than `maxWaitingTime`, the value of `maxWaitingTime` will be adjusted to match `pollingInterval`.
11
+
* If either `pollingInterval` or `maxWaitingTime` is passed as a negative value, it will default to 0.
12
+
* 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.
13
+
* Default values are 2000 ms for the `pollingInterval` and 60000 ms for the `maxWaitingTime`.
14
+
4
15
## Version 5.0.2
5
16
*[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
6
17
*[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
* Description: A human readable message describing the result of the payment
@@ -207,6 +209,24 @@ A tip amount can be prompted directly in the card reader by using `tipOnCardRead
207
209
> Note: Not all card readers support this feature. To find out if the feature is supported for the last-saved card reader, you should always check `SumUpApi.isTipOnCardReaderAvailable()`. You must handle this case yourself in order to avoid no tip from being prompted.
208
210
Please also note that if both `tip` and `tipOnCardReader` are called then only `tipOnCardReader` amount will be considered during checkout if available.
209
211
212
+
#### Retry Policy Configuration
213
+
The `configureRetryPolicy()` feature allows you to set custom retry parameters for transaction result retrieval, using `pollingInterval`, `maxWaitingTime`, and `disableBackButton`.
214
+
* Parameters: Both `pollingInterval` and `maxWaitingTime` should be provided in milliseconds, with default values of 2000 ms and 60000 ms, respectively. Setting `disableBackButton` to true disables the back button during retries.
215
+
* Timeout: If `maxWaitingTime` elapses with no result, the SDK returns `SumUpAPI.ResultCode.ERROR_UNKNOWN_TRANSACTION_STATUS`. Pressing the back button (if enabled) during retries will also trigger this error.
216
+
* Adjustments: If `pollingInterval` exceeds `maxWaitingTime`, `maxWaitingTime` will automatically be adjusted to match. Negative values for either parameter default to 0.
217
+
* Default: If `configureRetryPolicy()` is not used, the SDK defaults to returning `SumUpAPI.ResultCode.ERROR_TRANSACTION_FAILED`.
If there are connectivity issues and the transaction status can not be retrieved, the API will return `ERROR_UNKNOWN_TRANSACTION_STATUS`. In such cases, you can query the transaction status by calling [SumUp transaction status API](https://developer.sumup.com/api/transactions/get) using the specified `foreignTransactionId`.
210
230
211
231
#### Transaction identifier
212
232
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.
0 commit comments