--- title: "Overview of the Device Binding SDK" slug: "device-binding-sdk-ig-overview-of-the-sdk-5-8-0" updated: 2026-10-22T16:45:37Z published: 2026-10-22T16:45:37Z canonical: "docs.onespan.com/device-binding-sdk-ig-overview-of-the-sdk-5-8-0" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.onespan.com/llms.txt > Use this file to discover all available pages before exploring further. # Overview of the Device Binding SDK With the Device Binding SDK, a unique identifier for a given mobile device can be generated. This unique identifier, called Device fingerprint in the API, is a hexadecimal string of 64 characters. It is a securely computed SHA-256 hash of the device-specific data and salts. As an integrator, you must provide a salt which will be used to diversify the generation of the device fingerprint. > Different salts must be used, if the device fingerprint is used for different purposes (e.g. one salt to protect a storage and another to protect a Digipass instance). ## Supported platforms The Device Binding SDK supports the following platforms: Android devices: - Minimum Android 7 (API level 24) - Target Android 16 (API level 36) iOS devices: - iOS 16 and later - Swift 6 and later - Xcode 16 and later ## SDK package contents The Device Binding SDK package includes the following: - MSSDeviceBinding.xcframework for iOS - DeviceBindingSDK.aar for Android - Maven repository with transitive dependencies for Android - Documentation jar file to view the technical documentation in Android Studio (to be used in conjunction with Maven repository) ## Upgrading the SDK > This is an advance notice, you can still upgrade directly to the current version. Beginning with the upcoming version 6.x, migration support for device fingerprints created with SDK versions **4.27.1 and earlier** is removed. Apps using Device Binding SDK version 4.27.1 or earlier must first upgrade to 5.x before upgrading to version 6.x. ### Supported upgrade paths - From 4.x: upgrade to the latest 5.x version first, then upgrade to version 6.x - From 5.x: direct upgrade to version 6.x > Upgrading directly from version 4.27.1 or earlier is not supported and will cause the device fingerprint migration to fail. On iOS, before you upgrade to version 6.x, migrate the fingerprints. To migrate fingerprints 1. (If you use a version 4.x of the SDK) Upgrade to the latest 5.x version. 2. Call a fingerprint for every salt your app uses. 3. Release this app version to your customers, and allow time for the migrations to complete. 4. Upgrade to version 6.X. Your fingerprints are now migrated. Fingerprints that are not called before the upgrade may not migrate. If a fingerprint is not migrated, the SDK will generate a new one. For more information, see also [Obtain the device fingerprint](/mobile/docs/device-binding-sdk-ig-obtain-the-device-fingerprint-5-8-0).