Zuia udhibiti wa akaunti kwa ukaguzi wa uso. Ongeza usalama wakati hatari inapoongezeka.
Hatua ya kibayometriki katika nyakati halisi ambazo washambuliaji hulenga — uhamishaji, kuweka upya nenosiri, kuingia kwa kifaa kipya. Uamuzi wa chini ya sekunde mbili, karibu $0.13 kwa tukio. Uthibitishaji 500 bila malipo kila mwezi.
Nywila zilizoibiwa. Vipindi vilivyoibiwa. Chagua uso badala yake.
Ujazaji wa vitambulisho, ubadilishaji wa SIM, na mashambulizi ya kuki za kikao zilizoibiwa zote hupita
nywila na misimbo ya mara moja. Zibadilishe kwa hatua ya Didit wakati wa
kitendo — $0.10 kwa simu, uamuzi wa chini ya sekunde mbili, 500 bila malipo kila mwezi.
Jinsi inavyofanya kazi
Kutoka kujisajili hadi mtumiaji aliyethibitishwa katika hatua nne.
Hatua 01
Unda mtiririko wa kazi
Chagua ukaguzi unaotaka — kitambulisho, uhai, ulinganishaji wa uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna msimbo unaohitajika.
Hatua 02
Unganisha
Pachika kiasili na SDK yetu ya Wavuti, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo — kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa mrundikano wako.
Hatua 03
Mtumiaji anapitia mtiririko
Didit huandaa kamera, vidokezo vya mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapata alama 200+ za ishara za ulaghai kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vyenye mamlaka. Matokeo chini ya sekunde mbili.
Hatua 04
Unapokea matokeo
Webhooks zilizotiwa saini kwa wakati halisi huweka hifadhidata yako ikiwa sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga kura API inapohitajika. Au fungua koni ili kukagua kila kikao, kila ishara, na kudhibiti kesi kwa njia yako.
Imejengwa kwa mapishi · Bei kama miundombinu
Uwezo sita. Hatua moja ya juu. ~$0.13 kwa kila tukio.
Ulinzi wa ATO ni muundo, sio ukaguzi mmoja. Washa kila uwezo kwa kila mtiririko wa kazi katika Mjenzi wa Mtiririko wa Kazi, au uziunganishe moja kwa moja kupitia API.
Sera ya kuongeza hatua inakaa katika Mjenzi wa Mtiririko wa Kazi — uhamisho wa thamani ya juu, kuweka upya nenosiri, malipo kwa eneo jipya, kuingia kwa kifaa kipya, hitilafu ya kijiografia. Weka lango la awali na Uchambuzi wa Kifaa na IP ikiwa unataka tu ukaguzi wa uso wakati ishara za mtandao zinaonekana hatari. Hakuna kupeleka upya kubadili sheria.
Uhamisho wa waya · > kikomo cha kila siku> $5,000Step up
Weka upya nenosiri · IP yenye hatari ndogoAnyStep up
Kuingia kwa kifaa kipyaImeonekana mara ya kwanzaStep up
Malipo kwa akaunti mpya ya benkiAnyStep up
Ingia · kifaa kinachoaminika + hatari ndogo ya IPAlama ya IP < 20Pass
Hariri vichochezi katika Kijenzi cha Mtiririko wa Kazi. Hakuna usambazaji upya.
02 · Kuongeza hatua kwa biometriska
Kuongeza hatua moja. Uamuzi chini ya sekunde mbili.
Injini ileile ya biometriska ambayo mtumiaji alipitia wakati wa kujisajili — iBeta Level 1 Presentation Attack Detection (PAD) pamoja na kulinganisha uso 1:1 dhidi ya picha iliyohifadhiwa. $0.10 kwa kila kikao. Inastahimili hadaa na inastahimili ubadilishaji wa SIM. Chini ya sekunde mbili kutoka mwanzo hadi mwisho kwenye Android ya kiwango cha chini.
iBeta Level 1 PAD · ISO/IEC 30107-3< 2s mwisho-hadi-mwisho
03 · Kulinganisha uso 1:1 dhidi ya kujisajili
Lengo la kulinganisha ni picha ya mtumiaji iliyohifadhiwa.
Kulinganisha Uso 1:1 kulinganisha kila selfie ya kuongeza hatua dhidi ya picha ya mtumiaji iliyohifadhiwa wakati wa kujisajili. Inarudisha alama ya kufanana ya 0–1.0 pamoja na maonyo; kizingiti kinaweza kurekebishwa kwa kila mtiririko wa kazi. Selfie iliyoibiwa haiwezi kupita — lengo limefungwa kwa usajili wa awali, sio picha iliyopigwa upya.
Kizingiti kinachoweza kurekebishwa kwa kila mtiririko wa kazi.0–1.0 ufanano
04 · Ulinzi dhidi ya deepfake
Chapisha. Rudia. Barakoa. Deepfake. Zote zimezuiwa.
Imejaribiwa kwa uhuru katika iBeta na kuthibitishwa katika Kiwango cha 1 PAD dhidi ya katalogi kamili ya ISO/IEC 30107-3. Inazuia picha zilizochapishwa, marudio ya skrini, barakoa za karatasi / silikoni / mpira, mashambulizi ya morph, na deepfake zinazozalishwa na AI za mmiliki wa akaunti. Inajaribiwa upya kila mwaka.
Picha iliyochapishwa · leseni ya kuendesha gari99Block
Marudio ya skrini (simu / kifuatiliaji)97Block
Barakoa ya silikoni / mpira95Block
AI deepfake ya mmiliki wa akaunti92Block
Mtumiaji halisi — yupo + bado4Pass
Hujaribiwa tena iBeta kila mwakaISO/IEC 30107-3
05 · IP + kifaa kabla ya kuangalia
VPN, kituo cha data, Tor — zimewekwa alama kabla ya ukaguzi wa uso.
Pima anwani ya IP (Internet Protocol) ya mtumiaji na alama ya kidole ya kifaa kabla ya kuongeza hatua kuanza. Inarudisha alama ya hatari ya 0–100 pamoja na bendera za VPN, proksi, Tor, kituo cha data, nchi, na ASN. $0.03 kwa kila ukaguzi, chini ya 100ms. Ruka kuongeza hatua kwenye kifaa kinachoaminika + mtandao wenye hatari ndogo.
Kulinganisha alama ya kidole ya kifaaiOS InayoaminikaPass
Hurejesha alama, bendera, ASN, nchi, jiji — chini ya 100ms.
06 · Uamuzi wa Webhook
Webhook moja. Matawi matatu. Imekamilika.
Webhook iliyosainiwa inafika na uamuzi — Imeidhinishwa, Imekataliwa, Inapitiwa, Haijakamilika. Thibitisha X-Signature-V2 na HMAC SHA-256 kabla ya kusoma mwili. Malipo sawa kwenye kila kuongeza hatua; tawi hatua ya awali ipasavyo. Ishara 200+ za udanganyifu zimefichuliwa bila gharama ya ziada.
Thibitisha X-Signature-V2 kabla ya kusoma malipo.nyaraka →
Ujumuishaji tayari kwa wakala
Tuma ulinzi wa kuchukua akaunti kwa haraka.
Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza safu yako. Wakala huunganisha kichochezi, hufungua kikao cha hatua-juu, huthibitisha webhook, na kugawa hatua asili.
didit-integration-prompt.md
You are integrating Didit account-takeover defence into an application that already has the user signed in. Your job: when a sensitive action fires (large transfer, password reset, payout to a new destination, new-device login, geo anomaly), gate it on a Didit biometric step-up. One API call. One signed webhook. Three branches.
WHY THIS SHAPE
- Credential stuffing, SIM-swap, and stolen-session-cookie attacks all walk past passwords and SMS one-time codes. A face check at the moment of the sensitive action does not.
- Didit runs Passive Liveness (the user is alive, present, not a deepfake) plus 1:1 Face Match against the portrait captured at sign-up. A stolen selfie cannot pass — the comparison target is locked to the original enrollment.
- $0.10 per step-up (Biometric Authentication module) + $0.03 IP pre-check (optional) = around $0.13 per event. Sub-two-second verdict on entry-level Android. 500 verifications free every month.
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
- A webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header using your webhook secret.
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. - A Workflow Builder workflow that bundles Passive Liveness + Face Match 1:1 (with the user's stored sign-up portrait as the comparison target). Optionally compose Device & IP Analysis ahead of the step-up to pre-gate the check.
- Persist the user's sign-up portrait — either base64 on your side, or rely on Didit's stored enrollment via vendor_data lookup.
STEP 1 — Decide WHEN to step up (your code, not Didit's)
Run your usual fraud signals. Common triggers worth a biometric step-up:
- Wire / crypto transfer above the user's daily limit
- Password / email reset on a session less than 24h old
- Payout to a bank account or wallet seen for the first time
- Login from a new device or new country
- Velocity anomaly — N actions of type T within window W
Cheap pre-check (optional, ~100ms, $0.03):
- Score the user's IP via Device & IP Analysis. If the IP is a residential trusted address with a low risk score AND the device fingerprint matches the user's trusted device, skip the step-up. Otherwise run Step 2.
STEP 2 — Create a biometric step-up session
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<wf id bundling Passive Liveness + Face Match 1:1>",
"vendor_data": "<your user id, max 256 chars>",
"callback": "https://<your-app>/ato/step-up/callback",
"metadata": {
"trigger": "high_value_transfer",
"action_id": "<your internal action reference>"
},
"portrait_image": "<base64 JPEG of the user's stored sign-up portrait, ≤ 1 MB — REQUIRED when the workflow has FACE_MATCH active; the step-up matches the new live selfie against this stored reference>"
}
Response: 201 Created with a hosted session URL. Redirect the user there inline (or open it in a webview / Didit mobile SDK). The action stays BLOCKED on your side until the signed webhook lands.
STEP 3 — Read the signed webhook on completion
Didit POSTs the decision to your callback. Verify X-Signature-V2 (HMAC SHA-256 of the raw request body using your webhook secret) BEFORE reading the JSON.
Payload (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"ip_analysis": { "status": "Approved", "score": 11 }
}
Session status enum (exact case, Title Case With Spaces): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.
STEP 4 — Branch the original action on status
Approved → unblock the sensitive action. Log session_id + similarity score on the audit trail.
In Review → hold the action, route to a human review queue.
Declined → block the action, log liveness warnings (mask / deepfake / replay / morph), alert the user.
Not Finished → invite the user to retry with a fresh session URL.
Expired → resend the link; the original session has timed out.
Abandoned → the user closed the flow before completing; resend the link.
STEP 5 — (Optional) Pull the full decision payload
GET https://verification.didit.me/v3/session/{session_id}/decision/
Headers:
x-api-key: <your api key>
Returns the same payload as the webhook plus the structured signals (liveness warnings, face-match similarity, IP / device flags). Use for analyst review.
WEBHOOK EVENT NAMES
- Sessions: standard session webhook (one endpoint, status field tells you where in the lifecycle).
- Verify X-Signature-V2 (HMAC SHA-256) on every payload.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review). Never use UPPER_SNAKE_CASE for session verdicts — that's the Transactions API and lives in a different surface.
- 1:1 face match's comparison target is the user's STORED sign-up portrait, not a freshly captured one. A stolen selfie cannot pass.
- iBeta Level 1 Presentation Attack Detection (PAD) certified against the full ISO/IEC 30107-3 catalogue — print, replay, paper / silicone / latex mask, deepfake, morph.
- The Workflow Builder is where you choose the modules in the step-up — change them in the console without redeploying.
- 200+ fraud signals are surfaced on every session at no extra cost — read them off the decision payload, don't re-query.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/core-technology/biometric-auth/overview
- https://docs.didit.me/core-technology/ip-analysis/overview
- 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.
Unahitaji maelezo zaidi? Tazama nyaraka kamili za moduli.docs.didit.me →
Inatii kwa muundo
Fungua nchi mpya kwa kubofya mara moja. Tunafanya kazi ngumu.
Tunafungua kampuni tanzu za ndani, tunapata leseni, tunafanya majaribio ya kupenya, tunapata vyeti, na tunalingana na kila kanuni mpya. Ili kusafirisha uthibitishaji katika nchi mpya, geuza swichi. Nchi 220+ zinafanya kazi, zinakaguliwa na kujaribiwa kila robo mwaka — mtoa huduma pekee wa utambulisho ambaye serikali ya nchi mwanachama wa EU imemwita rasmi kuwa salama zaidi kuliko uthibitishaji wa ana kwa ana.
Utambuzi wa Mashambulizi ya Uwasilishaji uliothibitishwa kwa kujitegemea — hujaribiwa tena kila mwaka.
<0s
Uamuzi wa hatua-juu mwisho-hadi-mwisho kwenye Android ya kiwango cha kuingia.
~$0.13
Kwa kila tukio — $0.10 hatua-juu ya biometriska pamoja na $0.03 ukaguzi wa awali wa IP wa hiari.
0
Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
Ngazi tatu, orodha moja ya bei
Anza bure. Lipa kwa matumizi. Panua hadi Biashara.
Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, makazi ya data, na SLA (Mikataba ya Kiwango cha Huduma) kwenye Biashara.
Bure
Bure
$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.
Kifurushi cha KYC cha bure (Uthibitishaji wa Kitambulisho + Uhai Usio na Kazi + Kulinganisha Uso + Uchambuzi wa Kifaa na IP) — 500 / mwezi, kila mwezi
Watumiaji Waliozuiliwa
Kugundua Marudio
Ishara 200+ za udanganyifu kwenye kila kipindi
KYC inayoweza kutumika tena kwenye mtandao wa Didit
Jukwaa la Usimamizi wa Kesi
Mjenzi wa Mtiririko wa Kazi
Hati za umma, sandbox, SDKs, seva ya MCP (Model Context Protocol)