Each SDK is released independently, so versions differ per platform. Pin the version listed below for your platform, and confirm the latest in Nexus before upgrading.
Current versions
| Platform | Package | Version |
|---|
| Android | mbkyc-android | 0.7.0 |
| Desktop (Kotlin) | mbkyc-kotlin-desktop | 0.7.0 |
| Desktop (Java) | mbkyc-java-desktop | 0.7.0 |
| Browser | @mbkyc/sdk | 0.6.0 |
| macOS (Swift) | MBKYCSDK.xcframework | 0.5.0 |
| .NET | MBKYC.Sdk | 0.5.0 |
| C | mbkyc-capi / MBKYC.Capi | 0.8.0 |
Android hardware service AARs
| Service | Version |
|---|
service-smartcard-ccid-android · -smartcard-nfc · -fingerprint-morpho | 0.4.0 |
service-fingerprint-suprema-android · -fingerprint-zhiang | 0.1.0 |
Always confirm the latest published version in Nexus before pinning — these are current at the time of writing.
Async model
| Platform | Language | Async model |
|---|
| macOS | Swift / Obj-C | async/await + callbacks |
| Windows / Linux | C# | Task (async/await) |
| Windows / Linux / macOS | C | callbacks |
| Android / Desktop | Kotlin | suspend + coroutines |
| Desktop | Java | CompletableFuture |
| Browser | TypeScript | Promises |
Identifying the running build
Each request the SDK sends to the Validation Gateway identifies the SDK build, so you can confirm which version a device is running from your logs. On the web, getInfo() returns the host version and capabilities.
Compatibility notes
- The Kotlin and Java desktop packages share a Java namespace — depend on exactly one.
- The web SDK requires a compatible browser extension and native host installed on the machine; keep all three in step when upgrading.