PayControl SDK version 5.0 5.0.7 Initial release of PC SDK 5.0 5.0.139 [Mar 13, 2020] Transaction binary data is now downloaded separately for keys which support interaction with PC External by API level 3 5.0.141 [Apr 6, 2020] Interaction with android LocationManager is improved 5.0.145 [Apr 21, 2020] Fixed usage of Bouncy Castle Provider for Android 4.3 and lower 5.0.147 [Apr 30, 2020] Permission android.permission.BLUETOOTH is no longer required to access device name 5.0.152 [Jul 23, 2020] Fixed issue with encryption and decryption via RSA for some phones running Android 4.4 and 5.x 5.0.154 [Aug 3, 2020] Scoring data is now sent only if scoring is enabled in key flags PayControl SDK version 5.2 5.2.206 [Mar 16, 2021] Brings some significant changes from version 5.0, including the following: - Spongy Castle is removed as a dependency. Now crypto providers are taken from Android SDK. - Now binary data for transactions is stored in file system (app cache directory), not in RAM. Thus, there are almost no restrictions for attachment sizes. - Operations are introduced. Operation is generally a bunch of related transactions which can be processed altogether. Refer to documentation on PCOperationsManager and PCOperation for more details. - eKYC module is added. This module provides functionality for remote identification which can be used as a preliminary step before issuing the keys. Refer to documentation on PCKYCManager and PCKYCSession for more details. - Key backups are introduced. Now, the key can be backed up and restored later (provided that the server supports this functionality and backups are enabled). Refer to documentation on PCUserBackupData and PCUserRestore for more details. - Key pair is now generated and stored in Android KeyStore for devices running Android 6 or newer. 5.2.208 [Mar 29, 2021] Function PCSDK.clearCaches() is not called automatically anymore at SDK initialization and should be called by the app in an appropriate phase