Uliza swali lolote ambalo timu yako ya compliance inahitaji, Source of Funds, occupation, expected volume, PEP (politically exposed person) self-declaration, na majibu yaliyokaguliwa kwenye session moja. Kiunda kisicho na code, conditional branching, upakiaji wa faili. $0.10 kwa kila submission, 500 bure/mwezi.
Robinhood Ventures
Inaaminika na mashirika 2,000+ duniani kote.
Source-of-funds, PEP self-disclosure
Weka dodoso maalum kwenye workflow, source of funds, PEP self-disclosure, occupation, expected volume. Majibu yanaingia kwenye ripoti ya session. $0.10 kwa kila submission.
Chagua ukaguzi unaotaka, ID, liveness, face match, sanctions, address, age, phone, email, maswali maalum. Ziburute kwenye mtiririko kwenye dashboard, au tuma mtiririko huo huo kwenye API yetu. Branch kwenye masharti, endesha A/B tests, hakuna code inayohitajika.
Pachika kiasili na Web, iOS, Android, React Native, au Flutter SDK yetu. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.
Didit inasimamia kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapima ishara 200+ za udanganyifu kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. Matokeo chini ya sekunde mbili.
Webhooks zilizosainiwa kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Piga API kwa mahitaji. Au fungua console kukagua kila session, kila ishara, na kudhibiti kesi kwa njia yako.
Rahisi · Advanced · buruta na dondosha
Hali ya juu · kihariri cha grafu
Mianzo tayari kwa kufuata kanuni
Templates
Aina za elementi
Lugha
Dakika ya kusafirisha
POST /v3/session/decision · umbo lilelile kwenye webhook
{
"questionnaire_id": "q_9f7485e0",
"element_type": "DROPDOWN",
"is_required": true,
"title": "Source of funds",
"answer": { "value": "salary" }
}Ukaguzi wa lazima wa mikono · webhook kwa kila idhini
POST /v3/session/ · wf_kyc_sof
$ 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_kyc_sof",
"vendor_data": "user-42"
}'{ "session_url": "verify.didit.me/..." }$ curl -X POST https://verification.didit.me/v3/questionnaires/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"title": "Customer Onboarding",
"languages": ["en"],
"default_language": "en",
"form_elements": [
{ "id": "occupation", "element_type": "short_text", "label": { "en": "Kazi yako ni nini?" } }
]
}'{ "questionnaire_id": "q_…" }# Didit Custom Questionnaires — integrate in 5 minutes
You are integrating Didit's Custom Questionnaires module into <my_stack>.
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. Build the questionnaire — Console OR API
### 2a. Visual builder in the Console (no code)
Questionnaires are authored visually — no schema upload, no SDK required.
1. Open https://business.didit.me, go to Questionnaires, click New.
2. Pick a mode:
- Simple Mode — single-language drag-and-drop builder. Best for fast
forms, internal surveys, single-locale flows.
- Advanced Mode — visual node-based graph editor. Required for
conditional branching, multi-language translations, choice-driven
follow-up text, and forced manual review.
3. Drag elements onto the canvas (input, choice, upload, layout — full
element catalog in section 5 below).
4. Optionally start from a pre-built template (Source of Funds,
Employment Details, Purpose of Account, Beneficial Ownership, Tax
Residency, Risk Assessment).
5. Localize titles, descriptions, placeholders, and choice labels for
every supported language; set a default_language.
6. Publish — the questionnaire is now addressable by its questionnaire_id.
### 2b. Create the questionnaire programmatically (Management API)
Use this path when you want the form to live in code, ship via CI, or be
authored by an LLM. Endpoint:
POST https://verification.didit.me/v3/questionnaires/
Headers: x-api-key: <your-api-key>
Content-Type: application/json
Required body:
- title — internal questionnaire name (string).
- languages — array of locale codes; MUST include "en".
- default_language — the default locale (string, e.g. "en").
- form_elements — ordered array of questions (≥1 entry).
Each form element requires id, element_type (lowercase OR uppercase enum
— "short_text", "multiple_choice", "email", "file_upload", "date_picker",
etc.), and a translated label keyed by locale. For dropdown,
single_choice, and multiple_choice add options: [{ value, label }].
Hard constraints:
- This endpoint supports SIMPLE LINEAR questionnaires only. Do NOT send
graph, branches, next, required_if, or conditional rules — use the
Console (section 2a) for those.
Example body:
{
"title": "Customer Onboarding",
"languages": ["en"],
"default_language": "en",
"form_elements": [
{
"id": "occupation",
"element_type": "short_text",
"label": { "en": "What is your occupation?" },
"is_required": true
},
{
"id": "source_of_funds",
"element_type": "multiple_choice",
"label": { "en": "Source of funds" },
"is_required": true,
"options": [
{ "value": "employment", "label": { "en": "Employment" } },
{ "value": "business", "label": { "en": "Business" } },
{ "value": "investments", "label": { "en": "Investments" } }
]
}
]
}
Response includes questionnaire_id — store it; you'll use it as
questionnaire_uuid when you wire the questionnaire into a workflow in
section 3 below. Full reference:
https://docs.didit.me/management-api/questionnaires/create
## 3. Two integration paths — pick one
### Path A — Workflow Builder (hosted UI, recommended)
Best when you want Didit to host the form, the file-upload UX, the
multi-language routing, the keyboard handling, and the mobile responsive
layout.
1. Create a workflow that contains the QUESTIONNAIRE feature:
POST https://verification.didit.me/v3/workflows/
Authorization header: x-api-key: <your-api-key>
Body: workflow_label, features array with the entry
{ feature: "QUESTIONNAIRE", questionnaire_id: "<id>" }
(UPPERCASE — strict enum)
Optional: chain QUESTIONNAIRE after ID_VERIFICATION + LIVENESS in the
same workflow to collect Source of Funds as part of a full Know Your Customer (KYC).
2. Create a verification session for an end user:
POST https://verification.didit.me/v3/session/
Body: workflow_id (from step 1), vendor_data (your own user id).
Response: session_url — redirect the user to it.
3. Listen for webhook callbacks (see "Webhooks" below).
### Path B — Standalone Questionnaire Verification
Run a questionnaire as its own verification — no KYC required.
Use a workflow whose only feature is QUESTIONNAIRE. Everything else is
identical to Path A. Useful for ongoing-due-diligence pulses,
post-onboarding declarations, periodic re-attestations.
## 4. Webhooks
- Register a webhook destination once via
POST https://verification.didit.me/v3/webhook/destinations/
Body: url, subscribed_events: ["session.verified", "session.review_started",
"session.declined"]
- Response includes secret_shared_key — store it.
- Every webhook 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. Element catalog (use these in the builder)
Input elements:
SHORT_TEXT, LONG_TEXT, NUMBER, EMAIL, PHONE, ADDRESS, DATE_PICKER, TIME
Choice elements:
DROPDOWN, SINGLE_CHOICE, MULTIPLE_CHOICE, COUNTRY, CONSENT
- DROPDOWN and SINGLE_CHOICE support per-option requires_text_input —
selecting "Other" can demand a free-text follow-up.
Upload elements:
IMAGE, FILE_UPLOAD
- max_files (1-5) per element.
Layout elements:
PARAGRAPH, SECTION_HEADER, SEPARATOR (read-only, not answerable).
## 6. Reading the report
The session report contains a questionnaire_responses array (one entry
per questionnaire step in the workflow graph). Each entry has:
- node_id: identifies the questionnaire step in the workflow graph
- questionnaire_id: which questionnaire this response is for
- title, description, languages, default_language, is_active
- sections: array of { title, description, items[] }
- each item: { uuid, order, element_type, is_required, title,
description, placeholder, choices, max_files, answer }
- answer: { value, text, files[] } — only the fields relevant to the
element_type are present.
- status: "Approved" | "In Review" | "Not Finished"
Status semantics:
- Not Finished — user has not completed the questionnaire yet.
- In Review — submitted, pending manual review. The Console flag
"force manual review" pins every response to this state until a human
approves it.
- Approved — reviewed and accepted.
Note: questionnaires do NOT emit risk warnings. Governance is achieved
through required fields, validation, manual review, and the workflow
graph (branching nodes route compliance-sensitive answers to In Review).
## 7. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: QUESTIONNAIRE, ID_VERIFICATION, LIVENESS,
FACE_MATCH, AML, IP_ANALYSIS.
- Element type enums are UPPERCASE + underscored: SHORT_TEXT, LONG_TEXT,
FILE_UPLOAD, SINGLE_CHOICE, etc.
- 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", "In Review", "Not Finished"
(title-cased, space-separated).
## 8. Pricing reference (public)
- $0.10 per questionnaire submission (Path A or Path B).
- No minimums. No per-language surcharge. No per-element surcharge.
Conditional branching, file uploads, manual review — all included at
the same per-submission price.
## 9. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Use one of the pre-built templates (Source of Funds, Employment
Details, Purpose of Account, Beneficial Ownership, Tax Residency, Risk
Assessment) to ship a draft in under a minute, then customise.
- Switch to live: flip the application's environment toggle in console.
When in doubt: https://docs.didit.me/core-technology/questionnaires/overview
$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 ambalo tulitamani lingekuwepo tulipokuwa tukijenga bidhaa sisi wenyewe: wazi, rahisi, na rafiki kwa watengenezaji, ili lifanye kazi kama sehemu halisi ya stack yako badala ya sanduku jeusi unalounganisha.
API moja inashughulikia kuthibitisha watu (KYC, mjue mteja wako), kuthibitisha biashara (KYB, ijue biashara yako), kuchunguza pochi za crypto (KYT, ijue muamala wako), na kufuatilia miamala kwa wakati halisi, kwenye stack iliyojengwa kuwa:
Msingi wake: aina 14,000+ za nyaraka katika lugha 48+, vyanzo vya data 1,000+, na ishara 200+ za udanganyifu kwenye kila kipindi. Miundombinu ya Didit hujifunza kwa nguvu kutoka kila kipindi na inaboresha kila siku.
Maswali Maalum ni fomu zinazoendeshwa na schema unazokusanya ndani ya kipindi kilekile cha uthibitishaji kama Uthibitishaji wa Hati ya Utambulisho na selfie, Chanzo cha Fedha, kazi, kiasi kinachotarajiwa, matamko ya PEP (Mtu Aliye Wazi Kisiasa), Makazi ya Kodi, Umiliki Halisi.
Kiunda cha kuona kisicho na code huruhusu kiongozi wa kufuata kanuni kuwasilisha dodoso jipya kwa chini ya dakika 5 na matawi yenye masharti, tafsiri za lugha nyingi, upakiaji wa faili, na ukaguzi wa lazima wa mikono. Kila jibu huwekwa kwenye njia ileile ya ukaguzi kama data ya Know Your Customer (KYC).
$0.10 kwa kila uwasilishaji. Marejeleo kamili: docs.didit.me/core-technology/questionnaires/overview.
$0.10 kwa kila uwasilishaji wa dodoso, kwenye njia yoyote ya kuunganisha (ndani ya mtiririko au pekee).
Hakuna kiwango cha chini, hakuna malipo ya ziada kwa lugha, hakuna malipo ya ziada kwa kila kipengele, hakuna ada ya ziada kwa matawi yenye masharti, upakiaji wa faili, au ukaguzi wa lazima wa mikono, kila uwezo umejumuishwa kwa bei ileile ya kila uwasilishaji. Bei ya umma: didit.me/pricing.
Mtiririko kamili kwa kawaida huchukua chini ya sekunde 30 kuanzia mwanzo hadi mwisho, chukua kitambulisho, piga picha hati, piga selfie, imekamilika. Huu ndio 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 inapoanza. Upigaji picha wa simu umeboreshwa kwa simu za polepole na mitandao ya polepole: ukandamizaji wa picha unaoendelea, upakiaji wa polepole wa software development kit, na uhamishaji wa kugusa mara moja kutoka kompyuta hadi simu kupitia QR code ikiwa mtumiaji anaanza kwenye wavuti.
Ripoti ya kipindi hubeba safu ya questionnaire_responses, ingizo moja kwa kila hatua ya dodoso kwenye grafu ya mtiririko wa kazi. Kila ingizo linajumuisha questionnaire_id, title, languages, default_language, is_active, safu ya sections, na status ya kiwango cha juu ya Approved, In Review, au Not Finished.
Kila safu ya items[] hubeba uuid, order, element_type, is_required, title, description, placeholder, choices, max_files, na kitu cha answer chenye value, text, au files kulingana na aina ya kipengele.
Umbo lilelile kwenye Application Programming Interface (API) ya kipindi na kwenye kila utoaji wa webhook.
Kila kipindi huwekwa kwenye mojawapo ya hali saba zilizo wazi, hivyo code yako inajua nini cha kufanya:
Approved, kila ukaguzi umepita. Endeleza mtumiaji.Declined, ukaguzi mmoja au zaidi umeshindwa. Unaweza kumruhusu mtumiaji kuwasilisha upya hatua maalum iliyoshindwa (kwa mfano, piga tena selfie) bila kurudia mtiririko mzima.In Review, imewekwa alama kwa ukaguzi wa kufuata kanuni. 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 itakaa muda mrefu sana.Abandoned, mtumiaji alifungua kiungo lakini hakumaliza kwa wakati. Mshirikishe tena au muda wake uishe.Expired, kiungo cha kipindi kimeisha muda wake. Unda kipindi kipya.Webhook iliyosainiwa huwaka kwenye kila mabadiliko ya hali, hivyo database yako inabaki sawa. Vipindi 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 wadhibiti wao wanahitaji.
Usimbaji fiche kila mahali. AES-256 ikiwa imetulia kwenye kila database, hifadhi ya vitu, na chelezo. Transport Layer Security 1.3 ikiwa inahamishwa kwenye kila simu ya API, webhook, na kipindi cha Business Console. Data ya kibayometriki imesimbwa kwa ufunguo tofauti wa Customer Master Key.
Uhifadhi ni wako kudhibiti. Uhifadhi chaguomsingi ni usio na kikomo isipokuwa ukisanidi mfupi, kati ya siku 30 na miaka 10 kwa kila programu, na unaweza kufuta kipindi chochote cha kibinafsi wakati wowote kutoka kwenye dashboard au API.
Vyeti: SOC 2 Type 1 (ukaguzi wa Type 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 inatii kanuni muhimu za miundombinu ya utambulisho kiwango cha juu:
Memo ya kina, kila cheti, kila barua ya mdhibiti: /security-compliance.
Njia tatu za kuunganisha, chagua inayofaa stack yako:
Dashboard moja, bili moja, bei sawa ya kulipa-kwa-mafanikio kwa zote tatu. Mwongozo wa hatua kwa hatua unapatikana kwenye docs.didit.me/integration/integration-prompt.
API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.