eKYC SDK Sample Apps

Developer Reference App UI Design — Android & iOS · Maven Distribution · 4 Screens

Android · Kotlin iOS · Swift Shared taxonomy
01 — Capability Catalogue
9:41▪▪▪ ᯤ 🔋
Sample App
eKYC SDK
Integration Reference
Each entry is the shortest working integration for one capability — copy it straight into your app.
sdk 1.0.0 minSdk 26 maven
Android iOS
Ready Made · drop-in UI
📄
Document Capture
Auto-detect & crop
Ready
🙂
Smile Liveness
Active challenge
Ready
🔄
Full Onboarding
End-to-end flow
Ready
Custom Made · bring your own UI
📷
Face Auto Capture
Raw callbacks
Custom
📡
Passport NFC
MRZ → chip read
Custom
📍
Landmark Check V1
Superseded by V2
Retired
02 — Integration Snippet
9:41▪▪▪ ᯤ 🔋
Launch the ready-made capture screen and receive a cropped document image plus a quality report.
Kotlin ⧉ Copy
// 1 — configure once, at app start
Ekyc.init(
    context = this,
    licence = Licence.fromAssets()
)

// 2 — launch the ready-made flow
val launcher = registerForActivityResult(
    DocumentCapture.Contract()
) { result ->
    when (result) {
        is Success -> onCaptured(
            image   = result.croppedImage,
            quality = result.qualityReport
        )
        is Cancelled -> finish()
        is Failure -> showError(result.reason)
    }
}

launcher.launch(
    DocumentCaptureConfig(
        docType   = DocType.ID_CARD,
        autoCrop  = true,
        minQuality = 0.75f
    )
)
Gradle
build.gradle.kts
repositories {
    maven("https://maven.example.com/ekyc")
}
dependencies {
    implementation("com.example:ekyc-sdk:1.0.0")
}
03 — Ready-Made Capture Flow
9:41▪▪▪ ᯤ 🔋
🪪
✓ Hold steady — capturing…
0.91
Sharpness
0.04
Glare
86%
Fill
Quality metrics stream to your callback in real time —
the same values the Custom Made API exposes.
04 — Deprecated Capability Path
9:41▪▪▪ ᯤ 🔋
📍
Landmark Check V2
Current · recommended
Default
📍
Landmark Check V1
Discontinued
Retired
⚠️
V1 is no longer supported
Landmark Checking V1 has been discontinued and is not available in this SDK release.
Migrating? V2 accepts the same configuration object and returns a superset of the V1 result fields, so most integrations only change the enum value.