Where to get the SDK

MBKYC packages are published to a private Sonatype Nexus instance. This is how the repositories are laid out.

All MBKYC packages — Maven AARs, npm, NuGet, Debian/RPM, and raw binaries — are published to a private Sonatype Nexus instance. You configure your package manager to point at the relevant Nexus repository, authenticate with the credentials your ICP contact provides, and pull the dependency for your platform.

The repository is reached through your proxy, like every other ICP domain. Throughout these docs we use https://repo.client.ae as a placeholder for your proxied repository host — replace it with the actual host your ICP contact gives you. Credentials are issued per organization; do not commit them to source control.

Repository layout

Nexus hosts one repository per package format:

Repository	Format	Serves
mbkyc-maven	maven2 (hosted)	Android AAR + Desktop JVM JAR libraries
mbkyc-npm	npm (hosted)	@mbkyc/sdk (browser TypeScript SDK)
mbkyc-nuget	nuget (hosted)	MBKYC.Sdk (.NET SDK) · MBKYC.Capi (C API) + Chocolatey
mbkyc-apt	apt (hosted)	Debian/Ubuntu .deb packages (C lib + desktop services)
mbkyc-yum	yum (hosted)	RHEL/CentOS/Fedora .rpm packages
mbkyc-raw	raw (hosted)	Binaries, installers, archives (.msi, .exe, VCPkg, GPG keys, browser extension)

Which repository do I need?

Next

Package matrix

Exact artifact coordinates and versions for every platform.

Configure Nexus

Per–package-manager setup: Gradle, npm, NuGet, apt, yum.