Kitambulisho kinachoweza kutumika tena, kimethibitishwa mara moja
Thibitisha mara moja. Tumia tena milele. Chapa sawa. Mshirika anayeaminika. Kitambulisho kilekile.
$0.33 uthibitishaji wa kwanza, uthibitishaji upya wa selfie pekee kwa kila kurudi bila malipo, kushiriki na washirika wengine kupitia tokeni zilizosimbwa kwa muda mfupi. Uthibitishaji 500 bila malipo kila mwezi.
Mtumiaji alithibitishwa mara moja. Hawapaswi kufanya hivyo mara mbili.
Mara tu mtumiaji anapothibitishwa kwa kiwango cha Didit — iBeta Level 1 anti-spoof,
uamuzi wa chini ya sekunde 2, hati 14,000+ — uthibitishaji huo unaweza kuhamishwa. Chapa
sawa, programu ya pili: uthibitishaji upya wa selfie pekee bila malipo. Mshirika anayeaminika, usajili mpya: tokeni fupi ya kushiriki iliyosimbwa huwasajili
mara moja. Mtumiaji anamiliki kitambulisho,
kinacholingana na eIDAS2.
Jinsi inavyofanya kazi
Kutoka kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.
Hatua 01
Unda mtiririko wa kazi
Chagua ukaguzi unaotaka — kitambulisho, uhai, kulinganisha uso, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko kwenye dashibodi, au tuma mtiririko huo huo kwa API yetu. Tawi kwenye masharti, endesha majaribio ya A/B, hakuna msimbo unaohitajika.
Hatua 02
Unganisha
Pachika asili na SDK yetu ya Wavuti, iOS, Android, React Native, au Flutter. Elekeza kwa ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo — kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.
Hatua 03
Mtumiaji anapitia mtiririko
Didit huandaa kamera, vidokezo vya mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapata alama za ishara 200+ za ulaghai kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya mamlaka. Matokeo chini ya sekunde mbili.
Hatua 04
Unapokea matokeo
Webhooks zilizosainiwa kwa wakati halisi huweka hifadhidata yako ikiwa sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API inapohitajika. Au fungua koni ili kukagua kila kipindi, kila ishara, na kudhibiti kesi kwa njia yako.
Imejengwa kwa matumizi tena · Bei kama miundombinu
Uthibitishaji mmoja. Usajili mwingi.
Kitambulisho kinachoweza kutumika tena si kipengele kimoja — ni viwili: KYC Inayoweza Kutumika Tena (bila malipo) na API ya Kushiriki Kipindi na washirika. Unda mojawapo au zote mbili.
Uthibitishaji wa kwanza unabaki ndani ya Didit, umesimbwa kwa njia fiche wakati wa kupumzika. Mtumiaji huwasilisha tena kitambulisho kwenye kila huduma inayotumia Didit — chapa sawa au mshirika anayeaminika — kwa kuthibitisha tena kwa selfie au kwa kukubali kushiriki.
Programu ya pili · selfie pekeeFree · Reusable KYC
Programu ya mshirika · shiriki tokeni/v3/session/{id}/share/
Programu mpya kabisa · imeagizwa/v3/session/import-shared/
02 · Kushiriki na washirika mbalimbali
Kubadilishana tokeni kati ya washirika wanaoaminika.
Mshirika A huzalisha tokeni ya kushiriki ya muda mfupi kupitia POST /v3/session/[id]/share/. Mshirika B huiingiza kupitia POST /v3/session/import-shared/. Imesimbwa kwa njia fiche kutoka mwanzo hadi mwisho, hadhira iliyotajwa pekee, uingizaji mmoja kwa kila mshirika.
Tokeni ya muda mfupi · uingizaji mmoja kwa kila mshirika · imekaguliwa.
03 · Sera ya uaminifu
ukaguzi_wa_uaminifu kwa kila mshirika.
Mshirika B anachagua: kuamini uamuzi wa Mshirika A (kuingia papo hapo) au kunakili data na kuelekeza kwenye ukaguzi wa mikono (njia za kupanda zilizodhibitiwa). Imesanidiwa kwa kila mtiririko wa kazi katika Dashibodi ya Biashara.
Hatua ya juu iliyodhibitiwa · baada ya kuingizafresh sessionBlock
Imesanidiwa kwa kila mtiririko wa kazi katika Dashibodi ya Biashara.
04 · Kurudi kwa selfie pekee
Mtumiaji anayerudi · selfie pekee · bila malipo.
Mtiririko wa kazi wa KYC unaoweza kutumika tena huendesha uthibitishaji upya bila kitambulisho — mtumiaji anafungua kipindi, anapiga picha ya selfie, Didit inalinganisha tena dhidi ya kiolezo kilichothibitishwa, inarudisha Imeidhinishwa chini ya sekunde mbili. Bila malipo, hakuna upigaji picha mpya wa hati.
Didit · Uthibitishaji upya wa KYC unaoweza kutumika tena
Selfie pekee · mtumiaji anayerudi.
Bure
Fungua kipindi kipyaMtiririko wa kazi wa KYC unaoweza kutumika tena
Picha ya kujipiga pekeeHakuna kunasa hati mpya
Seva inalingana tenaDhidi ya kiolezo kilichothibitishwa
Imeidhinishwa · chini ya sekunde 2Hali Imeidhinishwa kwenye webhook
API ya Vipindi Sawa. Mtiririko wa kazi wa KYC unaoweza kutumika tena. Bila malipo.
05 · Faragha + idhini
Idhini · upeo · uhifadhi · kwa kila ushiriki.
Kila ushiriki hurekodi idhini ya mtumiaji, madhumuni, hadhira, upeo, na tarehe ya mwisho wa matumizi. Didit huweka kumbukumbu zote — inalingana na GDPR (Kanuni Kuu ya Ulinzi wa Data), ISO/IEC 27001, SOC 2 Aina ya 1. Uhifadhi chaguomsingi miaka 5.
Inalingana na GDPR · SOC 2 Aina ya 1 · ISO/IEC 27001.
06 · Mtandao
Kitambulisho kimoja katika eneo lote la Didit.
Kitambulisho kinachoweza kutumika tena hufanya kazi kwenye kila jukwaa linaloendeshwa na Didit — fintech, crypto, masoko, iGaming, BNPL, huduma za afya, uhamaji. Mkataba sawa wa /v3/, Mjenzi wa Mtiririko wa Kazi sawa, unaolingana na eIDAS2.
Tuma kitambulisho kinachoweza kutumika tena kwa haraka.
Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Wakala huunda mtiririko wa uthibitishaji wa kwanza, mtiririko wa Reusable KYC reauth, na ushiriki wa washirika mtambuka + mtiririko wa kuingiza.
didit-integration-prompt.md
You are integrating Didit reusable identity. Your users get verified once with full KYC and then re-present that verification on every subsequent service — your own platforms (same-platform reuse via Reusable KYC) and trusted partner platforms (cross-partner Share Session API).
Three pillars:
1. Verify once with full KYC ($0.33 bundle) via POST /v3/session/.
2. On the SAME platform, returning users re-prove identity with a selfie only — free, via the Reusable KYC workflow.
3. To a TRUSTED PARTNER, the first platform generates a short-lived share token (POST /v3/session/{id}/share/); the partner imports it (POST /v3/session/import-shared/) and the user lands fully onboarded.
Cost:
- First verification: $0.33 (Sessions API)
- Same-platform selfie-only reauth: free (Reusable KYC workflow)
- Cross-partner import: priced per call, from $0.30 — Partner B pays the import fee
- 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.
- Two workflows in the Workflow Builder:
wf_first_verification — ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + Anti-Money Laundering (AML) Screening
wf_reusable_kyc — Reusable KYC (selfie-only reauth)
- For cross-partner: a pre-arranged backend channel with the partner (a webhook, a queue, or even an authenticated REST call between your services) so the share token can be transmitted out-of-band.
STEP 1 — First verification (Sessions API)
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<wf_first_verification>",
"vendor_data": "<your user id, max 256 chars>",
"callback": "https://<your-app>/identity/callback"
}
Response: 201 Created with the hosted session URL. Sub-2-second median verdict on completion.
STEP 2 — Read the signed webhook on verification completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"id_verification": { "status": "Approved" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 }
}
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.
Store the (user_id, session_id, status) tuple. session_id is the handle you reuse for shares.
STEP 3 — Same-platform reuse (Reusable KYC selfie-only reauth)
When the same user returns for a new flow:
POST https://verification.didit.me/v3/session/
Body:
{
"workflow_id": "<wf_reusable_kyc>",
"vendor_data": "<your user id>",
"callback": "https://<your-app>/identity/reauth-callback"
}
The hosted UI prompts the user for a selfie only — no document re-capture. Didit matches the selfie against the original verified template, returns Approved in under two seconds, free.
STEP 4 — Cross-partner share (Partner A generates a share token)
Only finished sessions (Approved / Declined / In Review) can be shared.
POST https://verification.didit.me/v3/session/{sessionId}/share/
Headers:
x-api-key: <Partner A's api key>
Content-Type: application/json
Body:
{
"audience": "<partner_b_identifier>",
"expires_in": 900
}
Response (excerpted):
{
"share_token": "eyJhbGciOiJIUzI1NiJ9...",
"session_kind": "kyc",
"expires_at": "<ISO8601>"
}
Transmit the share_token to Partner B via your pre-arranged backend channel.
STEP 5 — Cross-partner import (Partner B imports the session)
POST https://verification.didit.me/v3/session/import-shared/
Headers:
x-api-key: <Partner B's api key>
Content-Type: application/json
Body:
{
"share_token": "eyJhbGciOiJIUzI1NiJ9...",
"workflow_id": "<Partner B's workflow id>",
"vendor_data": "<Partner B's internal user id>",
"trust_review": true
}
trust_review options:
true — Partner B trusts Partner A's verdict (Approved / Declined). The imported session keeps the original status.
false — Partner B copies the data but sets status to "In Review" so Partner B's compliance team can apply their own thresholds.
Constraints (verified against mintlify-docs/core-technology/reusable-kyc/share-kyc-via-api.mdx):
- A specific session can be imported only ONCE into a given partner application.
- The share_token is short-lived (defaults to 15 minutes).
- End-to-end encrypted; only the named audience can import.
STEP 6 — Audit the consent + the share
Log every share + every import with:
- user_pid (the pseudonymous user identifier)
- audience (which partner)
- purpose (onboarding, lending, payments, etc.)
- scope (kyc, kyc + aml, kyc + kyb)
- share_token id + expiry
- import status
Default retention 5 years post-relationship per the EU AML package; longer under your supervisor's guidance.
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.
- Share tokens are scoped to the named audience and the named purpose — they're not bearer tokens for free reuse.
- The user must consent before a share happens. Capture explicit consent in your UI; Didit logs the consent against the session.
- Reusable KYC selfie-only reauth is free; cross-partner imports are priced at Partner B's account.
- 200+ fraud signals are evaluated on every fresh session at no extra cost.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/share-session/share
- https://docs.didit.me/sessions-api/share-session/import
- https://docs.didit.me/core-technology/reusable-kyc/overview
- https://docs.didit.me/core-technology/reusable-kyc/share-kyc-via-api
- 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.
Uthibitishaji wa kwanza — kifurushi kamili cha KYC. Kisha bure kwa kurudi kwenye jukwaa moja.
Free
KYC inayoweza kutumika tena — uthibitishaji upya wa selfie pekee katika kila kipindi cha chapa moja.
0 min
Muda wa kuisha wa tokeni ya kushiriki chaguomsingi · imesimbwa, imefungwa kwa hadhira, kuingiza mara moja tu.
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)