> For the complete documentation index, see [llms.txt](https://docs.vida.id/identity-stack/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vida.id/identity-stack/verify/kyc-mobile-sdk/use-cases.md).

# Use Cases

VIDA KYC Mobile SDK can support many KYC journeys across industries by combining document capture, OCR, document verification, liveness, and face match in a single flow. This section highlights common patterns you can implement with the same SDK integration.

### 1. New User Onboarding (Full eKYC)

**Goal**\
Verify a new customer’s identity during registration and activate their account instantly.

**How it works with KYC Mobile SDK**

1. User installs or opens your mobile app and starts registration.
2. Your app launches the KYC Mobile SDK with a **KYC flow** (document + selfie + liveness + face match) and the appropriate **region** (e.g., Indonesia, Malaysia).
3. The SDK guides the user to capture their ID (KTP, Driving License, Passport, MyKAD, etc.), runs OCR and document checks, then transitions to selfie capture for liveness and face match.
4. Your backend receives a unified response and decides whether 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 (e.g., higher transaction limits or additional features).

**How it works with KYC Mobile SDK**

1. The user is already registered but wants to increase limits (e.g., top-up/transfer limit).
2. From the profile or “Upgrade account” screen, your app launches the KYC Mobile SDK with the required **verification level** (for example, extra fields or an additional document type).
3. The SDK re-runs document verification and liveness as needed.
4. You map the response to your internal “tier” or “level” and 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.

**How it works with KYC Mobile SDK**

1. Before the KYC expiration date, you ask the user to update their details.
2. From an in-app banner or notification, your app opens the SDK with a **refresh flow** (same documents, or updated set if regulations changed).
3. The SDK collects the updated document + selfie and returns new verification results and OCR data.
4. Your backend compares new data with previously stored data and updates customer records.

**Typical use cases**

* Regulatory KYC refresh (e.g., every 2–3 years)
* Migrating users from legacy KYC methods to VIDA KYC

<sub>and many more use cases.</sub>&#x20;