SDK User Journey
Document Verification & Liveness via KYC SDK
From your app's perspective, there is one entry point: the KYC SDK. Once your app starts the KYC flow, the SDK calls Document Capture, Liveness, and Face Match in the right order and returns a single result.
You don't need to integrate separate "document SDK" and "liveness SDK" flows yourself.
Host App → KYC SDK → Document Capture → Liveness → Face Match → KYC SDK → Host App
└──────── handled inside the SDK ────────┘Step 1: Choose the flow
When building the KYC configuration (VidaKycRequest on Android, VIDAKYCConfig on iOS), choose which checks the SDK runs.
ID Verification
ID_VERIFICATION
.idVerification
Document capture, OCR, document verification
Full KYC
KYC
.kyc
Document capture, OCR, document verification, selfie, liveness, face match
For Full KYC, you must also attach a liveness configuration: livenessConfig (Android) / VIDALivenessConfig (iOS).
Once the flow type is set, the same startFlow() call runs all the required components automatically.
Step 2: How the SDK runs the flow
When your app calls startFlow():
All of these hops happen inside the SDK according to your chosen flow. The user experiences one continuous journey.
Step 3: Get the combined result
When all internal steps finish, the SDK returns one response object in the success callback.
onSuccess(VidaKycResponse)
getVidaCardVerificationDetails()
Document and OCR results
getVidaFaceMatchDetails()
Liveness and face match details
onSuccess(response: VIDAKYCResponse)
ocrIdVerificationResponse
Document and OCR results
livenessResponse
Liveness results
faceVerificationResponse
Face match results
Summary: You don't call document verification or liveness separately. Configure what you need in the KYC request, call startFlow(), and the SDK handles the rest.
Last updated
