--- title: "Overview of the Device Binding SDK" slug: "device-binding-sdk-ig-overview-of-the-sdk-5-7-0" updated: 2026-09-03T13:19:25Z published: 2026-09-03T13:19:25Z canonical: "docs.onespan.com/device-binding-sdk-ig-overview-of-the-sdk-5-7-0" excludeFromSearch: true --- > ## 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). 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 The Device Binding SDK package includes the following: - MSSDeviceBinding.xcframework for iOS - DeviceBindingSDK.aar for Android > As of OneSpan Mobile Security Suite 4.20.0, the integration of the Device Binding SDK has changed for Android and iOS. For instructions on how to integrate the SDK, see [Integrate the Device Binding SDK](/mobile/docs/device-binding-sdk-ig-integrate-the-sdk-5-7-0).