Toa kitambulisho kilichosainiwa na Didit baada ya KYC moja ya $0.33. Mtumiaji huwasilisha kwenye majukwaa mengine yote yanayotumia Didit kwa ufichuzi teule — bure, milele, inalingana na kitabu cha sheria cha mkoba wa kitambulisho cha EU.
Kile ambacho kitambulisho kinachoweza kutumika tena hufungua
Kitambulisho kwenye mfuko wa mtumiaji. Bure kwa kila anayekubali.
Kila KYC ya Didit husafirisha kitambulisho kinachoweza kutumika tena kilichotiwa saini kwenye pochi ya mtumiaji.
Kila jukwaa linalopokea hulithibitisha bila malipo kwa ufichuzi teule.
Uthibitishaji mmoja, kila biashara inayokubali Didit. Uthibitishaji 500
bila malipo kila mwezi.
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 chapisha mtiririko huo huo kwenye API yetu. Tawi kwenye masharti, endesha majaribio ya A/B, hakuna msimbo unaohitajika.
Hatua 02
Unganisha
Pachika kiasili na SDK yetu ya Wavuti, iOS, Android, React Native, au Flutter. Elekeza upya kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo — kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa mrundikano wako.
Hatua 03
Mtumiaji hupitia 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 zilizotiwa saini 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 kitambulisho kinachoweza kutumika tena · Bei kama miundombinu
KYC moja. Kila jukwaa baada ya hapo, bila malipo.
Kitambulisho halisi kinachoweza kutumika tena si kipengele kimoja — ni mfumo. Utoaji, umiliki, uwasilishaji, ufichuzi teule, kuonyesha upya, kubatilisha. Yote chini ya kipindi kimoja cha /v3/.
Mtumiaji huendesha kifurushi cha kawaida cha $0.33 mara ya kwanza. Baada ya kukamilika, Didit hutia saini kitambulisho na kukisukuma kwenye programu ya Didit au Pochi yoyote ya Kitambulisho cha Dijitali ya EU inayozungumza Mfumo wa Marejeleo ya Usanifu.
Kitambulisho kinatua kwenye programu ya Didit au EUDI Wallet.
02 · Ufichuzi teule
Fichua tu kile ambacho mhakiki anahitaji.
Thibitisha umri zaidi ya miaka 18 bila kufichua tarehe ya kuzaliwa. Thibitisha nchi bila kufichua anwani. Ishara za Wavuti za JSON za Ufichuzi Teule (SD-JWT) huweka kila ufichuzi ukiwa umetiwa saini kwa njia ya kriptografia.
Umri zaidi ya miaka 18Boolean trueTarehe ya kuzaliwa
Nchi ya makaziESAnwani kamili
Jina kamiliJ. PérezNambari ya hati
Binadamu aliyethibitishwaBoolean truePicha ya binafsi
Hayumo kwenye orodha ya vikwazoAML safiMaelezo ya PEP
Imetiwa saini na mtoaji; mthibitishaji anathibitisha kwenye sehemu zilizofichuliwa.
03 · Ushirikiano wa pochi
Kila pochi inayooana na EUDI.
Vitambulisho vilivyotolewa na Didit hufanya kazi katika programu ya Didit na Pochi yoyote ya Kitambulisho cha Dijitali ya EU (Cartera Digital, IT Wallet, pochi za kitaifa za nchi wanachama). Mtiririko sawa wa uwasilishaji wa OpenID kwa Vitambulisho Vinavyoweza Kuthibitishwa kwenye kila sehemu.
Mtiririko sawa wa OpenID kwa Vitambulisho Vinavyoweza Kuthibitishwa kwenye kila sehemu.
04 · Mtoaji · Mmiliki · Mthibitishaji
Majukumu matatu. Kitambulisho kimoja.
Mtoaji hutia saini kitambulisho baada ya KYC. Mtumiaji hukishikilia kwenye pochi yake. Mthibitishaji huthibitisha saini ya mtoaji kwenye sehemu zilizofichuliwa tu. Pembetatu ya uaminifu ya kitambulisho kinachoweza kuthibitishwa.
Mtoaji anatia saini kitambulisho → mshikiliaji anakihifadhi kwenye pochi → mhakiki anaomba sehemu
→ mshikiliaji anakubali kufichua → mhakiki anathibitisha saini kwenye sehemu zilizofichuliwa pekee.
05 · Usasa wa kitambulisho
Usasa wa kitambulisho, otomatiki.
AML inayoendelea huchunguza upya mtumiaji kila siku. Muda wa kuisha kwa hati, mabadiliko ya jina, vikwazo — yote huonekana kwenye kitambulisho kiotomatiki. Vitambulisho vilivyopitwa na wakati hukataliwa wakati wa uwasilishaji.
Mabadiliko ya Jina / Tarehe ya KuzaliwaKwa ombiKYC kamili upya
Kuhama nchiKwa ombiKYC kamili upya
Mwenye hati anafutaWakati wowoteImefutwa
Vitambulisho vilivyopitwa na wakati vinakataliwa wakati wa kuwasilishwa.
06 · Bure kupokea
Bure kwa kila jukwaa linalopokea.
Utoaji umejumuishwa na kila KYC. Uhifadhi wa pochi uko kwenye kifaa cha mtumiaji. Uwasilishaji, ufichuzi teule, na uthibitishaji wa saini zote ni bure, milele. Usasishaji wa AML unaoendelea kwa $0.07 kwa kila mtumiaji kwa mwaka kwenye akaunti zenye kiasi kikubwa.
201Imeundwamtiririko uliopangishwa hugundua kitambulisho au huendesha KYC kamili
Bure wakati kitambulisho cha Didit kinawasilishwa. $0.33 wakati KYC kamili inaendeshwa.nyaraka →
GET /v3/session/{sessionId}/decision/Soma
$ curl https://verification.didit.me/v3/session/$SID/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Inarudisha sehemu zilizofichuliwa + mnyororo wa mtoaji
# wakati reusable_identity.presented ni kweli.
# Inarudisha kifurushi kamili cha ushahidi wa KYC
# wakati KYC mpya iliendeshwa.
200OKhali Imeidhinishwa · Inapitiwa · Imekataliwa · Imeisha muda
Kifurushi kilekile cha ushahidi iwe kitambulisho kiliwasilishwa au KYC ilikuwa mpya.nyaraka →
Ujumuishaji tayari kwa wakala
Tuma mtiririko wa kitambulisho kinachoweza kutumika tena kwa haraka.
Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Wakala huunda mtiririko wa kazi, huweka ugunduzi wa pochi, hutangaza sehemu zilizofichuliwa, na huunganisha webhook.
didit-integration-prompt.md
You are integrating Didit's Reusable Identity / eIDAS 2.0 acceptance into your platform. Two flows:
1. Issue — when a new user runs a full KYC on your platform, they leave with a Didit-signed Reusable Identity credential in their wallet (the Didit app or any EU Digital Identity Wallet).
2. Accept — when a user arrives at your platform already holding a Didit-signed credential, the session detects it and short-circuits, returning Approved without re-running the full KYC.
Bundle pricing (verified live 2026-05-16):
- First verification (issuance side): $0.33 per user (Sessions API full KYC bundle)
- Issuance: free — the signed credential is included with every KYC
- Reuse on the verifying side: free, forever
- Selective disclosure: free
- Continuous Anti-Money Laundering (AML) refresh: $0.07 per user per year (automatic)
- First 500 verifications free every month, forever
PRE-REQUISITES
- Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
- Webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header.
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_id from the no-code Workflow Builder with:
* ID Verification + Passive Liveness + Face Match 1:1 + Device & IP Analysis + AML Screening (for issuance)
* Reusable Identity acceptance turned on (for acceptance — toggle in the Workflow Builder)
- Optional: the Didit mobile SDK (iOS / Android / React Native / Flutter) for native deep-link wallet handoff.
STEP 1 — Open a session that accepts a Reusable Identity if presented
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<wf id with Reusable Identity acceptance on>",
"vendor_data": "<your user id>",
"callback": "https://<your-app>/onboarding/callback",
"metadata": {
"purpose": "platform_onboarding",
"request_fields": ["full_name", "age_over_18", "country_of_residence"]
}
}
Optional in body: declare the exact fields you need disclosed via metadata.request_fields. Didit's hosted flow will prompt the user to approve only those specific fields when they present a Reusable Identity credential.
Response: 201 Created with the hosted session URL. Redirect the user.
STEP 2 — The hosted flow detects (or runs) the verification
Two paths from this one endpoint:
Path A — User has a Didit-signed credential
- The hosted flow detects the credential via a wallet-handoff prompt (universal link on mobile, popup-bridge on desktop)
- The user approves the disclosure of the requested fields
- Didit validates the issuer signature + credential freshness server-side
- Session returns Approved with the disclosed fields populated on the decision payload
- Cost: $0 on the verifying side
Path B — User does NOT have a credential
- The hosted flow runs the full KYC bundle (ID + Liveness + Face Match + Device & IP + AML)
- At completion, Didit issues a Reusable Identity credential to the user's wallet
- Session returns Approved with the full decision payload
- Cost: $0.33 on the verifying-and-issuing side
Same endpoint, same webhook, same status enum. The path is transparent to your back-end.
STEP 3 — Read the signed webhook
Didit POSTs to your callback. Session statuses (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 },
"ip_analysis": { "status": "Approved" },
"aml": { "status": "Approved", "hits": [] },
"reusable_identity": {
"presented": true,
"issuer": "<issuing-platform name>",
"issued_at": "<timestamp>",
"disclosed_fields": ["full_name", "age_over_18", "country_of_residence"]
}
}
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.
When reusable_identity.presented is true, the user re-presented an existing credential and the verification was free; when false, a fresh KYC was run and billed at $0.33.
STEP 4 — Retrieve the full decision later
GET https://verification.didit.me/v3/session/{sessionId}/decision/
Headers:
x-api-key: <your api key>
Returns the full payload including: document scan + extracted Machine-Readable Zone (MRZ) data, biometric similarity, AML hits, device + IP risk signals, 200+ fraud signals, HMAC signature, and (if presented) the credential issuance chain.
Same evidence pack regardless of issuance vs reuse — the verifier never sees less than a fresh KYC would deliver.
STEP 5 — Continuous AML monitoring is automatic
Every approved user (issued OR presented) is re-screened daily against 1,300+ sanctions, PEP, and adverse-media lists at $0.07 per user per year on heavy-volume accounts. When a previously-clean user crosses an AML threshold, the credential's AML field is updated automatically; every receiving platform sees the refreshed status on next presentation.
When the user revokes a credential from their wallet, your receiving platform's webhook fires with status: Expired and the credential is dropped from the user's account.
STEP 6 — Selective disclosure at presentation time
Pass the exact fields you need via metadata.request_fields at session creation. Recommended minimum-disclosure patterns:
- Age-gate (UK Online Safety Act, France SREN): ["age_over_18"]
- Country-gate: ["country_of_residence"]
- Full name + verified-human: ["full_name", "verified_human"]
- AML-clear gate (lending): ["aml_clear", "full_name"]
- Full identity (banking, payments): ["full_name", "date_of_birth", "address", "document_number", "aml_clear"]
The user sees a single approval prompt listing the requested fields. Anything not listed is never disclosed to your platform.
WEBHOOK EVENT NAMES
- Sessions: status changes flow through the standard session webhook (verify X-Signature-V2 HMAC SHA-256).
- Credential lifecycle: status: Expired fires when a holder revokes the credential.
CONSTRAINTS
- Session statuses use Title Case With Spaces. Don't UPPER_SNAKE_CASE them.
- Reusable Identity acceptance is OFF by default; turn it on in the Workflow Builder.
- Selective disclosure is the privacy default — fields not in metadata.request_fields are never returned, even if the credential carries them.
- Default record retention is 5 years post-relationship per the EU AML package.
- 200+ fraud signals are evaluated on every session, issued or presented, at no extra cost.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/retrieve-session
- https://docs.didit.me/core-technology/reusable-kyc/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.
Kwa uthibitishaji wa kwanza — mara pekee mtumiaji hulipa kifurushi cha Didit KYC.
Free
Kwenye kila jukwaa linalopokea. Kila utumiaji tena, kila uwasilishaji, kila ufichuzi teule.
0
Nchi wanachama wa EU. Kitambulisho cha Didit kinafanya kazi na kila EUDI Wallet iliyojengwa kwenye Mfumo wa Marejeleo ya Usanifu.
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)