Use this page to find the exact artifact coordinates for your platform. Pin a specific version; see Versions for the current releases.
Core SDK packages
| Platform | Coordinate | Version | Repository |
|---|
| Android | ae.gov.icp.mbkyc:mbkyc-android | 0.7.0 | mbkyc-maven |
| Desktop JVM (Kotlin) | ae.gov.icp.mbkyc:mbkyc-kotlin-desktop | 0.7.0 | mbkyc-maven |
| Desktop JVM (Java) | ae.gov.icp.mbkyc:mbkyc-java-desktop | 0.7.0 | mbkyc-maven |
| Browser | @mbkyc/sdk | 0.6.0 | mbkyc-npm |
| .NET (Windows / Linux) | MBKYC.Sdk | 0.5.0 | mbkyc-nuget |
| macOS (Swift) | MBKYCSDK.xcframework.zip (download & link) | 0.5.0 | mbkyc-raw |
| C API NuGet (.NET / C++) | MBKYC.Capi | 0.8.0 | mbkyc-nuget |
| C (Linux) | libmbkyc-dev (apt) · mbkyc-capi (yum) | 0.8.0 | mbkyc-apt / mbkyc-yum |
| C (Windows) | .msi, MBKYC.Capi NuGet, or vcpkg port | 0.8.0 | mbkyc-raw / mbkyc-nuget |
There is no Swift Package Manager or CocoaPods distribution. The Swift SDK is a downloadable XCFramework — see the Swift guide. Note also that the C# SDK package is MBKYC.Sdk, distinct from the C API NuGet package MBKYC.Capi. The Java desktop package uses the group ae.gov.icp.mbkyc (note the trailing .mbkyc), distinct from the Kotlin/Android group ae.gov.icp.uaekyc. The Kotlin mbkyc-kotlin-desktop and Java mbkyc-java-desktop packages share the same Java package namespace — depend on exactly one, never both on the same classpath.
Android vendor service AARs
On Android, hardware support ships as separate service AARs. Always include service-common-android (shared by every service AAR), then add only the per-hardware AARs whose hardware you support:
| Coordinate | Version | Hardware |
|---|
ae.gov.icp.mbkyc:service-common-android | 0.4.0 | Required — shared runtime for all service AARs |
ae.gov.icp.mbkyc:service-smartcard-ccid-android | 0.4.0 | USB CCID smart card readers |
ae.gov.icp.mbkyc:service-smartcard-nfc-android | 0.4.0 | Built-in NFC |
ae.gov.icp.mbkyc:service-fingerprint-morpho-android | 0.4.0 | IDEMIA (Morpho) MSO 1350 fingerprint |
ae.gov.icp.mbkyc:service-fingerprint-suprema-android | 0.1.0 | Suprema (BioMini) fingerprint |
ae.gov.icp.mbkyc:service-fingerprint-zhiang-android | 0.1.0 | NEXUS / Zhiang fingerprint |
Desktop services & native host
Card-read and fingerprint flows on desktop require the signed services (and, for the browser, the native host) installed on the machine. These ship as OS packages from mbkyc-apt / mbkyc-yum / mbkyc-raw:
| Component | Distribution |
|---|
| PC/SC service | .deb / .rpm / .msi / Chocolatey mbkyc-pcsc-service |
| Morpho service | .deb / .rpm / .msi / Chocolatey mbkyc-morpho-service |
| Suprema service | .deb / .rpm / .pkg / .msi / Chocolatey mbkyc-suprema-service (Windows needs the WinUSB driver) |
| Zhiang service | .deb / .rpm / .pkg / .msi / Chocolatey mbkyc-zhiang-service (Windows needs the WinUSB driver) |
Web native host (mbkyc-web-host) | .deb / .rpm / .pkg / Chocolatey mbkyc-web-host |
| Browser extension | mbkyc-raw → extension/mbkyc-extension.tar.gz (or browser store) |
Each language package runs on its supported platforms out of the box — the Android AAR, the desktop JAR, the NuGet package, and the Swift XCFramework all carry what they need. You generally don’t install anything by hand beyond the package itself and (for card/fingerprint flows) the hardware support.
