ID Verification (KYC)

Verify customer identities with iDenfy using document checks, liveness detection, and AI plus human review in a three-step KYC flow.

The Flow

Your server                    iDenfy                      Your user
    │                            │                            │
    │── POST /api/v2/token ─────>│                            │
    │<── authToken, redirectUrl ─│                            │
    │                            │                            │
    │── redirect user ──────────>│── show verification UI ───>│
    │                            │<── uploads doc + selfie ───│
    │                            │                            │
    │<── POST webhook ──────────│── AI + human review        │
    │   (APPROVED/DENIED)        │                            │

Quick Integration (3 Steps)

1. Create a session

   curl -X POST https://ivs.idenfy.com/api/v2/token \
     -u "API_KEY:API_SECRET" \
     -H "Content-Type: application/json" \
     -d '{"clientId": "user-123", "firstName": "John", "lastName": "Doe"}'
   

   Response includes authToken and redirectUrl. Full parameter reference →

2. Send user to verification

   Simplest — redirect to redirectUrl:

   window.location.href = data.redirectUrl;
   

   Embedded — use iFrame:

   <iframe src="https://ui.idenfy.com/?authToken=TOKEN" allow="camera; fullscreen" allowFullScreen
     style="width:670px; height:800px; border:none;"></iframe>
   

   Mobile — pass authToken to Android or iOS SDK.

3. Handle the webhook

   {
     "status": { "overall": "APPROVED" },
     "data": { "docFirstName": "JOHN", "docLastName": "DOE" },
     "scanRef": "d2714c8a-...",
     "clientId": "user-123",
     "final": true
   }
   

   When final: true — this is the definitive result. Full webhook reference →

---

What Happens During Verification

Step	What iDenfy does
Document capture	User selects country + document type, takes photo (or uploads)
Liveness check	3D face liveness prevents spoofing (selfie with depth analysis)
AI analysis	OCR extracts data, validates document authenticity, matches face
Human review	Expert reviews edge cases — blurry docs, unusual documents
Result	APPROVED, DENIED, or SUSPECTED delivered via webhook

Result Statuses

A verification resolves to APPROVED, DENIED, or SUSPECTED. SUSPECTED does not mean failure — it means checks passed but flags were found for you to review. See Status Handling for what to do with each status.

---

Features You Can Enable

All configured via session parameters or Dashboard settings:

Feature	Parameter	What it does
Data comparison	firstName, lastName	Cross-checks your data against the document
Country restriction	country	Limit accepted document countries
Document types	documents	Limit accepted document types
AML screening	checkAml	Auto-screen against sanctions/PEPs
Proxy detection	checkIpProxy	Flag VPN/proxy usage
Duplicate detection	checkDuplicateFaces	Detect same person verifying twice
Face blacklist	checkFaceBlacklist	Block known fraudsters
NFC chip reading	nfcRequired	Read document NFC chip for high assurance
Age limit	ageLimit	Minimum age requirement
Additional documents	additionalSteps	Request utility bills, bank statements

---

Pages in This Section

Page	When you need it
Create Session	Creating a verification session
Redirect & iFrame	Showing the verification UI on web
Webhooks	Receiving verification results
Data Retrieval	Fetching results after verification
Additional Steps	Requesting extra documents
Direct Processing	Sending images via API (no UI)
Dummy Results	Testing with fake data
Deletion	GDPR data deletion

Next Steps

Create Session

Create a verification session via API.

Redirect & iFrame

Show the verification UI on your website.

Webhooks

Receive verification results in real-time.

Mobile SDKs

Native iOS and Android integration.