Use Cases

One KYC Mobile SDK integration supports many KYC journeys across industries. It combines document capture, OCR, document verification, liveness, and face match in a single flow. Below are three common patterns.

At a glance

Use case	Goal	Typical users
New user onboarding	Verify a new customer during registration and activate the account instantly	E-wallets, digital banks, P2P lending, BNPL, crypto, investment
Account tier upgrade	Move an existing user to a higher KYC level	Wallets with basic and premium tiers, remittance
Periodic KYC refresh	Keep customer data current and meet re-verification rules	Regulated financial services, platforms migrating from legacy KYC

---

1. New user onboarding (Full eKYC)

Goal: Verify a new customer's identity during registration and activate their account instantly.

1

User starts registration

The user installs or opens your app and begins signing up.

2

Your app launches the SDK

Launch the SDK with the Full KYC flow (document + selfie + liveness + face match) and the appropriate region, such as Indonesia or Malaysia.

3

The SDK guides the user

The user captures their ID (KTP, Driving License, Passport, MyKAD, etc.). The SDK runs OCR and document checks, then moves to selfie capture for liveness and face match.

4

Your backend decides

Your backend receives one unified response and decides to approve, reject, or route to manual review.

Typical use cases

• E-wallets and digital banks

• P2P lending and BNPL apps

• Crypto exchanges and investment platforms

---

2. Account tier upgrade / limit increase

Goal: Upgrade an existing user to a higher KYC level, for example for higher transaction limits or additional features.

1

User requests an upgrade

The user is already registered and wants higher limits, such as a top-up or transfer limit.

2

Your app launches the SDK

From the profile or "Upgrade account" screen, launch the SDK with the verification level you require, for example extra fields or an additional document type.

3

The SDK re-verifies

The SDK re-runs document verification and liveness as needed.

4

You update the account

Map the response to your internal tier or level, then update the account status.

Typical use cases

• Moving users from basic to premium wallets

• Enabling high-value transfers or cross-border remittance

---

3. Periodic KYC refresh / re-verification

Goal: Keep customer data current and comply with periodic KYC refresh or re-verification requirements.

1

Prompt the user before expiry

Before the KYC expiration date, ask the user to update their details.

2

Your app launches the SDK

From an in-app banner or notification, open the SDK with a refresh flow. Use the same documents, or an updated set if regulations changed.

3

The SDK collects new data

The SDK collects the updated document and selfie, then returns new verification results and OCR data.

4

Your backend compares and updates

Compare the new data with previously stored data, then update the customer record.

Typical use cases

• Regulatory KYC refresh (for example, every 2-3 years)

• Migrating users from legacy KYC methods to VIDA KYC

---

And many more. The same integration works for any journey that needs document verification, liveness, or face match. Ready to start? See the Mobile SDK Quickstart.