Skip to main content
Each package manager needs to know the Nexus repository URL and your credentials. Replace https://repo.client.ae with the URL your ICP contact gives you, and use your issued service-account username and password.
Never commit Nexus credentials. Use environment variables, a credentials file outside the repo, or your CI secret store.

Gradle (Android / Desktop JVM)

Add the Maven repository and credentials. Keep the username/password in ~/.gradle/gradle.properties, not in the build file.
Then add the dependency:
On Android, mbkyc-android transitively pulls rustls:rustls-platform-verifier (the JNI layer calls into it for TLS certificate verification on every MBKYC.create). It’s declared as an api dependency, so you don’t list it yourself — but it is not on Maven Central or Google; it’s served from the same mbkyc-maven Nexus repository under the rustls group. Don’t restrict that repository to a single includeGroup (e.g. only ae.gov.icp.mbkyc), or the rustls artifact won’t resolve and you’ll hit a ClassNotFoundException for org.rustls.platformverifier.CertificateVerifier at runtime.

npm / pnpm (Web)

Scope the @mbkyc registry to Nexus in an .npmrc:

NuGet (.NET)

Add the Nexus source, then reference the package:
If Nexus sits behind a TLS-terminating proxy, the reverse proxy must rewrite Nexus’s http:// package URLs to https:// (via sub_filter). Without it, NuGet and Chocolatey downloads fail. This is an infrastructure concern handled by whoever operates your Nexus.

apt (Debian / Ubuntu)

yum / dnf (RHEL / CentOS / Fedora)

Swift (macOS)

There is no SwiftPM or CocoaPods feed. Download the XCFramework from the raw repository and link it in Xcode:
See the Swift guide for adding it to your project.

Now build your integration

Head to the SDK guide for your platform.