Buruta na udondoshe KYC, AML, KYB, biometric step-up. Panga kwa ishara. Jaribu A/B. Toleo salama. Lipa tu kwa moduli zilizokamilika, Workflow Builder yenyewe ni bure.
Robinhood Ventures
Inaaminika na mashirika 2,000+ duniani kote.
Wajibu wa wamiliki wa bidhaa
Buruta modules kwenye canvas, ziunganishe na kingo, ongeza branching, chapisha toleo, kisha upe app yako workflow_id. Sheria zikibadilika, product manager anahariri rasimu na kuchapisha, hakuna ticket ya uhandisi, hakuna redeploy. Ujumuishaji unabaki kuwa `POST /v3/session/` moja tu.
Chagua checks unazotaka, ID, liveness, face match, sanctions, address, age, phone, email, maswali maalum. Ziburute kwenye flow kwenye dashboard, au tuma flow hiyo hiyo kwenye API yetu. Fanya branching kulingana na masharti, fanya A/B tests, hakuna code inayohitajika.
Jumuisha moja kwa moja na SDK zetu za Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako link, kwa email, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.
Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Mtumiaji akiwa kwenye flow, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. Matokeo yanapatikana chini ya sekunde mbili.
Webhooks zilizosainiwa kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API inapohitajika. Au fungua console kukagua kila session, kila ishara, na kudhibiti kesi kwa njia yako.
Didit · Canvas
Didit · Branching
Didit · Templates
Didit · A/B
Didit · Versioning
Ya sasa
Rasimu
Didit · /v3/ + MCP
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"workflow_id": "wf_signup_v12",
"vendor_data": "user-42",
"callback": "https://app/cb"
}'Didit humwongoza mtumiaji kupitia kila tawi upande wa server.$ curl -X POST https://verification.didit.me/v3/workflows/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_label": "Signup KYC",
"features": [
{ "feature": "OCR" },
{ "feature": "LIVENESS" },
{ "feature": "FACE_MATCH" },
{ "feature": "AML" }
]
}'Inarudisha uuid ya mtiririko wa kazi · tayari kutumika kama workflow_id.You are integrating Didit's no-code Workflow Builder into a product. The product manager, the compliance officer, or the founder can change identity rules in the Business Console; your app only ever hands Didit a workflow_id, gets a verdict back, and routes the user.
Three pillars:
1. Compose the workflow in the visual builder — drag ID, Liveness, Face Match, AML, NFC, KYB modules onto the canvas, connect them with edges, add conditional branches.
2. Publish a version — the published version is immutable; sessions reference the exact version they were created with.
3. Open POST /v3/session/ with the published workflow_id. Didit handles every module and every branch server-side.
Cost:
- Pay per completed module per session (e.g. ID $0.15 + Liveness $0.10 + Face Match $0.05 + AML $0.20 = $0.50, or bundle = $0.33)
- Workflow Builder itself is free
- MCP server (for AI coding agents to manage workflows programmatically) is free, included
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60s, no card).
- Webhook endpoint with HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- Access to the Business Console's Workflow Builder (every account has it).
- The 11 seeded templates are a good starting point:
"ID + Face Match"
"ID + Liveness + Face Match" (the $0.33 KYC bundle)
"ID + IP risk-based" (extra Liveness on VPN / Tor)
"Phone risk-based verification"
"High-risk country review"
"Two ID documents"
"Driver verification"
"EU Company Verification" (KYB)
... plus four more
- Plus "Start from Scratch" for fully bespoke flows.
STEP 1 — Compose the workflow
Console → Workflows → New → pick a template OR Start from Scratch:
- Drag modules from the sidebar onto the canvas
- Connect them with edges (the user moves left-to-right through them)
- Add branching conditions (right-click a node → Add condition)
- Set per-workflow options: Include custom style (white label), retention override, callback URL
Click Save Draft. The draft is fully editable; only published versions are immutable.
STEP 2 — Publish a version
Click Publish on the draft. The version receives a number (v1, v2, v3…) and becomes immutable.
Versioning rules:
- Sessions reference the exact published version they were created with
- You can iterate on a new draft while sessions on the old version continue to use it
- Past versions are kept; you can inspect any past session's configuration
- To change a published workflow, create a new draft from it, edit, publish
STEP 3 — Open a session with the workflow_id
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your published workflow id>",
"vendor_data": "<your user id, max 256 chars>",
"callback": "https://<your-app>/identity/callback"
}
Response: 201 Created with the hosted session URL. Didit walks the user through every module and every branch defined in the workflow.
STEP 4 — Read the signed webhook on completion
Didit POSTs to your callback when the session reaches a terminal status. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"workflow_id": "<the workflow id>",
"workflow_version": "<v3>",
"vendor_data": "<your user id>",
"status": "Approved",
"id_verification": { "status": "Approved" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"aml": { "status": "Approved", "hits": [] }
}
Status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.
Verify the X-Signature-V2 header BEFORE reading the body — HMAC SHA-256 of the raw bytes with your webhook secret.
Each module that ran inside the workflow returns its own sub-status; the top-level status is the rolled-up verdict.
STEP 5 — Iterate without redeploying
When the rules need to change — a new country flagged as high-risk, a tighter age threshold, a new module added to the bundle — the workflow owner edits the draft in the Console and publishes. New sessions automatically use the new version.
Your app doesn't change. You don't redeploy. The workflow_id is the same; the underlying behaviour is updated.
STEP 6 — Run A/B tests
Built-in A/B testing splits traffic across variant workflows. Configure variants in the Console (e.g. variant A uses Passive Liveness, variant B uses Active Liveness), set the split percentage, and read the variant id back on every session webhook.
Measure conversion + verdict mix per variant in the Business Console's analytics. Promote the winner; the loser becomes a previous version retained for audit.
STEP 7 — Drive the Workflow Builder from AI coding agents
The Didit MCP (Model Context Protocol) server (free, included) exposes the Workflow management primitives as MCP tools. Any MCP-compatible host — Claude Code, Cursor, Codex, Replit Agent, Devin, Aider — can list workflows, create new drafts, edit nodes, and publish versions on your behalf.
Useful for ops teams that want to script tenant-specific workflow provisioning, A/B-variant generation, or per-customer-brand template materialisation.
WEBHOOK EVENT NAMES
- Sessions: status changes flow through the standard session webhook.
- Verify X-Signature-V2 on every payload.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review). Don't transform them.
- Published workflow versions are immutable. To change behaviour, publish a new version.
- Conditional branches are unlimited in depth; keep flows readable for the next operator.
- The cost model is pay-per-completed-module — adding a module that runs only conditionally only costs you on the branches that hit it.
Read the docs:
- https://docs.didit.me/console/workflows
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/retrieve-session
- https://docs.didit.me/integration/webhooks
Start free at https://business.didit.me — sandbox key in 60 seconds, 500 verifications free every month, no credit card.$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.
Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.
MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.
Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.
Didit ni miundombinu ya utambulisho na udanganyifu, jukwaa tulilotamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi, na rafiki kwa watengenezaji, ili ifanye kazi kama sehemu halisi ya stack yako badala ya sanduku jeusi unalounganisha.
API moja inashughulikia kuthibitisha watu (KYC, mjue mteja wako), kuthibitisha biashara (KYB, mjue biashara yako), kuchunguza pochi za crypto (KYT, mjue muamala wako), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:
Alama ya chini: aina 14,000+ za hati katika lugha 48+, vyanzo vya data 1,000+, na ishara za udanganyifu 200+ kwenye kila kikao. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila kikao na inaboresha kila siku.
Ni njia ya kubuni nini mtiririko wako wa KYC / AML / KYB unachunguza, kwa mpangilio gani, na chini ya masharti gani, yote katika turubai ya kuona ya kuburuta na kuacha badala ya code.
Kwa vitendo:
workflow_idworkflow_id hiyo kwenye POST /v3/session/, imekamilikaWakati sheria zinahitaji kubadilika, meneja wa bidhaa anahariri rasimu na kuchapisha. Programu haisambazwi upya.
Mnaweza. Timu nyingi zinazojaribu hujifunza masomo matatu:
Workflow Builder huangusha zote tatu kwenye turubai moja ya kuburuta na kuacha. Sheria zinakuwa usanidi wa bidhaa; code inakuwa simu moja ya POST /v3/session/.
Mtiririko kamili kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga picha ya selfie, imekamilika. Hiyo ndiyo kasi zaidi sokoni. Watoa huduma wa zamani wa KYC kwa kawaida huchukua zaidi ya sekunde 90 kwa mtiririko huo huo.
Kwa upande wa nyuma, Didit inarudisha matokeo kwa chini ya sekunde mbili kwa p99, ikipimwa kutoka wakati mtumiaji anamaliza selfie hadi wakati webhook yako inawaka. Upigaji picha wa simu umeundwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa kitengo cha ukuzaji wa programu, na uhamishaji wa kugusa mara moja kutoka kompyuta hadi simu kupitia msimbo wa QR ikiwa mtumiaji anaanza kwenye wavuti.
Kila primitive ya Didit inasafirishwa kama node:
$0.15), Usomaji wa NFC ($0.15), Uthibitisho wa Anwani ($0.20), Uthibitishaji wa Hifadhidata (inabadilika), Maswali Maalum ($0.10)$0.10), Active Liveness ($0.15), Face Match 1:1 ($0.05), Face Search 1:N (bure), Age Estimation ($0.10), Biometric Authentication ($0.10)$0.20, orodha 1,300+), Ongoing AML ($0.07/mtumiaji/mwaka), Uchambuzi wa Kifaa & IP ($0.03)$0.03), Uthibitishaji wa Simu (kuanzia $0.03)Pamoja na nodes za matawi (ikiwa/vinginevyo, swichi) na nodes za mwisho (Idhinisha, Kataa, Kagua).
Kila kikao huishia kwenye mojawapo ya hali saba zilizo wazi, kwa hivyo code yako inajua nini cha kufanya kila wakati:
Approved, kila ukaguzi umefaulu. Endeleza mtumiaji.Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kutuma upya hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kuendesha tena mtiririko mzima.In Review, imewekwa alama kwa ukaguzi wa kufuata sheria. Fungua kesi kwenye console, angalia kila ishara, amua kuidhinisha au kukataa.In Progress, mtumiaji yuko katikati ya mtiririko.Not Started, kiungo kimetumwa, mtumiaji bado hajafungua. Tuma ukumbusho ikiwa inakaa muda mrefu sana.Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Mshirikishe tena au muda wake uishe.Expired, kiungo cha kikao kimeisha muda wake. Unda kikao kipya.Webhook iliyosainiwa inawaka kwenye kila mabadiliko ya hali, kwa hivyo hifadhidata yako inabaki sawa kila wakati. Vikao vilivyoachwa na vilivyokataliwa ni bure.
Data ya uzalishaji inachakatwa na kuhifadhiwa katika Umoja wa Ulaya kwa chaguo-msingi, kwenye Amazon Web Services. Mikataba ya biashara inaweza kuomba maeneo mbadala kwa mamlaka ambazo wasimamizi wao wanahitaji.
Usimbaji fiche kila mahali. AES-256 ikiwa imetulia kwenye kila hifadhidata, hifadhi ya kitu, na chelezo. Transport Layer Security 1.3 ikiwa inasafiri kwenye kila simu ya API, webhook, na kikao cha Business Console. Data ya kibayometriki imesimbwa kwa ufunguo tofauti wa Mteja Mkuu.
Uhifadhi ni wako kudhibiti. Uhifadhi wa chaguo-msingi ni usio na kikomo (unlimited) isipokuwa ukisanidi mfupi zaidi, kati ya siku 30 na miaka 10 kwa kila programu, na unaweza kufuta kikao chochote cha kibinafsi wakati wowote kutoka kwenye dashibodi au API.
Vyeti: SOC 2 Type 1 (ukaguzi wa Aina ya 2 unaendelea), ISO/IEC 27001:2022, iBeta Level 1 PAD, na uthibitisho wa umma kutoka Tesoro / SEPBLAC / CNMV ya Uhispania kwamba uthibitishaji wa utambulisho wa mbali wa Didit ni salama zaidi kuliko kumthibitisha mtu ana kwa ana. Ripoti kamili inapatikana kwenye /security-compliance.
Didit inatoa huduma zinazozingatia sheria kwa chaguo-msingi kwa wasimamizi muhimu wa miundombinu ya utambulisho:
Memo ya kina, kila cheti, kila barua ya mdhibiti: /security-compliance.
Njia tatu za kuunganisha, chagua inayofaa stack yako:
Dashibodi ileile, bili ileile, bei ileile ya kulipa-kwa-mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana kwenye docs.didit.me/integration/integration-prompt.
Hali mbili kwa kila mtiririko wa kazi:
Ili kubadilisha mtiririko wa kazi uliopachikwa, unaunda rasimu mpya kutoka kwake, unahariri, unachapisha. Toleo jipya lililochapishwa linakuwa v3 (au lolote); v2 inabaki mahali pake milele kama rekodi ya kihistoria. Vikao vya zamani vinaweza kuzalishwa kikamilifu, mzigo wa kikao unajumuisha workflow_version halisi iliyotumika.
Hii inalingana na kile mdhibiti anataka kwa ukaguzi: "nionyeshe usanidi halisi wa mtiririko wa kazi ambao mtumiaji huyu alitumia, tarehe hii". Kila akaunti ya Didit inaupata bure, hakuna usanidi.
Kila kitu kinasafirishwa chini ya mkataba uleule wa /v3/.
workflow_id na kumwongoza mtumiaji kupitia uratibu uleule wa upande wa seva. Bure.workflow_id ileile, uratibu uleule.Matokeo: workflow_id moja inapita kutoka Console → ndani ya programu yako → ndani ya SDK au UI iliyopangishwa → uratibu wa upande wa seva → webhook iliyosainiwa. Hakuna code ya kuunganisha zaidi ya simu moja ya POST /v3/session/.
Waya tatu, alasiri moja:
business.didit.me, funguo ya sandbox kwa sekunde 60, hakuna kadi ya mkopo inayohitajikaPOST /v3/session/ ukitumia workflow_id iliyochapishwa na unganisha webhook iliyosainiwa (X-Signature-V2, HMAC SHA-256) kwenye mantiki yako ya uamuziHuo ndio ujumuishaji mzima. Sheria zinapobadilika, mmiliki wa workflow anahariri rasimu kwenye Console na kuchapisha, app yako haibadiliki.
Kwa usimamizi wa workflow kwa kutumia script, server ya Didit MCP ni bure na inaruhusu wakala yeyote anayepatana na MCP (Claude Code, Cursor, n.k.) kuendesha Workflow Builder kwa programu.
API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.