무료
월 $0. 신용카드 정보가 필요 없습니다.
- 무료 KYC 번들 (신분증 확인 + 패시브 라이브니스 + 얼굴 매칭 + 기기 및 IP 분석), 매월 500건 제공
- 차단된 사용자
- 중복 감지
- 모든 세션에서 200개 이상의 사기 신호 감지
- Didit 네트워크 전반에 걸쳐 재사용 가능한 KYC
- 사례 관리 플랫폼
- 워크플로 빌더
- 공개 문서, 샌드박스, SDK, MCP(Model Context Protocol) 서버
- 커뮤니티 지원




전 세계 2,000개 이상의 기관에서 신뢰합니다.

$0.33 전체 번들
모든 KYC(본인 인증) 플로우에 필요한 4가지 검증을 하나의 가격으로 제공합니다. 현재 사용 중인 공급업체보다 3~5배 저렴하며, 220개 이상의 국가, 14,000개 이상의 문서, 48개 이상의 언어를 지원하고 2초 이내에 결과를 받아볼 수 있습니다.
신분증, 라이브니스, 얼굴 매칭, 제재 목록, 주소, 나이, 전화번호, 이메일, 맞춤 질문 등 필요한 검증을 선택하세요. 대시보드에서 드래그 앤 드롭으로 플로우를 만들거나, API를 통해 동일한 플로우를 게시할 수 있습니다. 조건에 따라 분기하고 A/B 테스트를 실행할 수 있으며, 코딩은 필요 없습니다.
Web, iOS, Android, React Native, Flutter SDK를 사용하여 네이티브로 임베드하거나, 호스팅된 페이지로 리디렉션할 수 있습니다. 또는 이메일, SMS, WhatsApp 등 어디든 사용자에게 링크를 보내세요. 스택에 맞는 방식을 선택하세요.
Didit은 카메라, 조명 안내, 모바일 핸드오프, 접근성을 호스팅합니다. 사용자가 플로우를 진행하는 동안 200개 이상의 사기 신호를 실시간으로 분석하고, 모든 필드를 신뢰할 수 있는 데이터 소스와 대조하여 검증합니다. 2초 이내에 결과를 받아볼 수 있습니다.
실시간 서명된 웹훅을 통해 사용자가 승인, 거부되거나 검토를 위해 전송되는 즉시 데이터베이스를 동기화합니다. 필요에 따라 API를 폴링하거나, 콘솔을 열어 모든 세션, 모든 신호를 검사하고 케이스를 직접 관리할 수 있습니다.
OCR · MRZ · Barcode
Countries
Document types
P99 inference
Standalone
iBeta Level 1 · ISO/IEC 30107-3
Document portrait vs live selfie
1,300+ lists · ongoing $0.07/yr
200+ fraud signals · per session
Fraud signals
Standalone
IP lookup
Drag-and-drop · branching · A/B
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_id": "wf_full_kyc",
"vendor_data": "user-42"
}'// Your endpoint receives a signed payload
앱.post("/webhooks/didit", (req, res) => {
const sig = req.headers["x-signature-v2"];
const expected = crypto.createHmac("sha256", SECRET)
.update(req.rawBody).digest("hex");
if (sig !== expected) return res.sendStatus(401);
const { status, decision, vendor_data } = req.body;
// status: Approved · Declined · In Review · ...
res.sendStatus(200);
});# Didit User Verification — integrate KYC in 5 minutes
You are integrating Didit's User Verification product line (KYC) into the_my_stack_block. Follow these steps exactly. Every URL, header, and enum value below is canonical — do not paraphrase or "improve" them.
## 1. Provision an account
- Sign up: https://business.didit.me (no credit card required).
- Or provision programmatically: POST https://apx.didit.me/auth/v2/programmatic/register/
(returns an API key bound to the workspace + application).
## 2. Compose the workflow
A workflow is an ordered list of features the user runs through in a single hosted session. The canonical full-KYC bundle is four features:
- ID_VERIFICATION — document capture, OCR, MRZ, barcode, authenticity, liveness
- LIVENESS — Passive Liveness (iBeta Level 1 PAD certified)
- FACE_MATCH — 1:1 match between the document portrait and the live selfie
- IP_ANALYSIS — VPN / proxy / Tor / hosting / ASN / abuse-score signals
This bundle bills at $0.33 per completed session (was $0.30 pre-2026-05).
To compose a custom workflow, add or remove features from the array. Every feature in the catalog is independently priced — see Section 5.
POST https://verification.didit.me/v3/workflows/
Headers:
x-api-key: <your-api-key>
Content-Type: application/json
Body:
{
"workflow_label": "Full KYC",
"features": [
{ "feature": "ID_VERIFICATION" },
{ "feature": "LIVENESS" },
{ "feature": "FACE_MATCH" },
{ "feature": "IP_ANALYSIS" }
]
}
Response: { "workflow_id": "wf_..." }
Feature enums are UPPERCASE_SNAKE_CASE — strict. Available enums:
ID_VERIFICATION, NFC, LIVENESS, FACE_MATCH, FACE_SEARCH, AGE_ESTIMATION,
BIOMETRIC_AUTHENTICATION, AML, ONGOING_AML, IP_ANALYSIS, PROOF_OF_ADDRESS,
DATABASE_VALIDATION, PHONE_VERIFICATION, EMAIL_VERIFICATION,
QUESTIONNAIRES, REUSABLE_KYC, WHITE_LABEL.
You can also build the workflow visually in the Business Console — the Console emits the same workflow_id and the same payload shape.
## 3. Create a session for an end user
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your-api-key>
Content-Type: application/json
Body:
{
"workflow_id": "wf_...",
"vendor_data": "<your-own-stable-user-id>",
"callback": "https://your-app.example/callback"
}
Response 201:
{
"session_id": "ses_...",
"session_url": "https://verify.didit.me/...",
"expires_at": "..."
}
Redirect the user to session_url. Didit handles capture (camera, lighting cues, mobile handoff, accessibility) and runs every feature in the workflow.
## 4. Webhooks
Register a destination once per workspace:
POST https://verification.didit.me/v3/webhook/destinations/
Body:
{
"url": "https://your-app.example/webhooks/didit",
"subscribed_events": [
"session.verified",
"session.review_started",
"session.declined",
"kyc_expired"
]
}
Response: { ..., "secret_shared_key": "wsk_..." }
Every delivery carries an X-Signature-V2 header you MUST verify before trusting the payload. HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature.Algorithm:
1. sortKeys(payload) recursively
2. shortenFloats (truncate trailing zeros after the decimal point)
3. JSON.stringify the result
4. HMAC-SHA256 with the secret_shared_key
5. Hex-encode, compare to the X-Signature-V2 header
## 5. Reading the report
Fetch the full session report after the webhook fires:
GET https://verification.didit.me/v3/session/<session_id>/decision/
Header: x-api-key: <your-api-key>
The response carries one sub-object per feature in the workflow. Top-level status is one of:
"Approved" | "Declined" | "In Review" | "Expired" | "Not Finished"
Sub-objects you will see on the full-KYC bundle:
- id_verification: document_type, document_number, full_name,
first_name, last_name, date_of_birth (YYYY-MM-DD),
age, expiration_date, date_of_issue, issuing_state
(ISO 3166-1 alpha-3), nationality, gender, address,
parsed_address (street, city, region, postal_code,
geometry coordinates), image quality scores, warnings
- liveness: score (0-100), method (Passive/Flash/Active), warnings
- face_match: match (true/false), score (0-100), warnings
- ip_analysis: vpn, proxy, tor, hosting, asn, abuse_score, country
If you add more features to the workflow you get more sub-objects in the report — same JSON shape, same warning catalog, same risk-policy hooks.
## 6. Pricing reference (public, per success)
- Full KYC bundle (ID + LIVENESS + FACE_MATCH + IP_ANALYSIS) — $0.33 per session
- 500 sessions free every month, forever, on every workspace
- Standalone module prices on https://didit.me/pricing
- ID Verification $0.15
- Passive Liveness $0.10
- Active Liveness $0.15
- Face Match 1:1 $0.05
- Face Search 1:N Free
- AML Screening $0.20
- Ongoing AML Monitoring $0.07 per user / year
- NFC Reading $0.15
- Device & IP Analysis $0.03
- Proof of Address $0.20
- Phone Verification From $0.03
- Email Verification $0.03
- Custom Questionnaires $0.10
- Age Estimation $0.10
- Biometric Authentication $0.10
- Database Validation Variable
- White Label $0.20
- Reusable KYC Free
Every module bills only on successful completion — abandoned and rejected sessions are free.
## 7. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE_SNAKE_CASE.
- Auth header is x-api-key (lowercase, hyphenated).
- Webhook signature header is X-Signature-V2 (NOT X-Signature).
- Always verify webhook signatures before trusting payload data.
- Status casing matches exactly: "Approved", "Declined", "In Review",
"Expired", "Not Finished" (title-cased, space-separated).
## 8. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test docs: deterministic synthetic IDs returned in sandbox.
- Switch to live: flip the application's environment toggle in console.
When in doubt: https://docs.didit.me/sessions-api/create-session
월 $0. 신용카드 정보가 필요 없습니다.
사용한 만큼만 지불하세요. 25개 이상의 모듈. 모듈별 공개 가격, 월 최소 요금 없음.
맞춤형 MSA 및 SLA. 대규모 볼륨 및 규제 프로그램에 적합합니다.
무료로 시작 → 확인 실행 시에만 지불 → 맞춤형 계약, SLA 또는 데이터 상주를 위해 엔터프라이즈 잠금 해제.
Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.
One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:
The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.
Four checks run in one session at the $0.33 bundle price:
All four run in parallel. Result in under two seconds. The first 500 every month are free, forever. You only pay on a successful verification, abandoned and rejected sessions are free.
220+ countries and territories. 14,000+ identity documents. 48+ user-facing languages. Passports, national identity cards, driver''s licences, residence permits, refugee documents, and voter cards, read across 130+ document languages and 50+ scripts including Latin, Arabic, Cyrillic, CJK, Devanagari, Hebrew, Thai, and Georgian.
Need to confirm a specific document or country? Browse the searchable catalogue at didit.me/supported-documents.
When you turn on Database Validation as an extra check in your flow, Didit cross-checks the user against direct government-registry connections in 18+ countries, Spanish DNI, Brazilian CPF, Mexican CURP, Indian Aadhaar, Singapore MyInfo, and more.
The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.
On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.
200+ fraud signals on every session, running in parallel with the document and selfie checks:
Every session lands on one of seven clear statuses, so your code always knows what to do:
Approved, every check passed. Move the user forward.Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.In Progress, user is mid-flow.Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.Abandoned, user opened the link but did not finish in time. Re-engage or expire.Expired, the session link aged out. Create a new session.A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.
Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.
Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.
Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.
Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.
Didit ships compliant by default for the regulators that matter to identity infrastructure:
Detailed memo, every certificate, every regulator letter: /security-compliance.
Three integration paths, pick whichever fits your stack:
Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.