Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Kura moja kwa kila mtu

Binadamu mmoja. Kura moja. Imethibitishwa, si ahadi.

Thibitisha kuwa kila mpiga kura ni mtu halisi, wa kipekee, na gundua mtu yule yule anayejaribu kupiga kura mara mbili. $0.33 kwa kila mpiga kura, marudio hugunduliwa bure. Uthibitishaji 500 bure kila mwezi.

Inaungwa mkono na
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Mchoro wa kupiga kura wa kupinga Sybil usioeleweka, wa giza, na wa sinema, paneli nne za glasi zinazoelea, zinazopitisha mwanga katika mtazamo wa 3D kwenye rangi nyeusi safi, zikipitishwa na mstari mweupe wa Didit Blue na kuwekwa ndani ya mabano manne ya skana yanayong'aa. Kila paneli ina motifu ndogo, nyeupe-nyeupe isiyo dhahiri inayowakilisha mtu mmoja-kura moja (sanduku la kura, kitanzi cha alama ya vidole, alama ya kuhesabu, silhouette moja ya binadamu).

Wajibu wa utawala

Wallets si watu. Watu ni watu.

Mwanadamu mmoja anaweza kuunda mamia ya pochi, anwani za barua pepe, au simu za muda mfupi. Hakuna hata moja kati ya hayo inayothibitisha kuwa wao ni wanadamu mia tofauti. Didit inaunganisha kura na uso halisi na hati halisi, na Utafutaji wa Uso 1:N (bila malipo) unagundua mtu yule yule anapojaribu tena. Uthibitishaji 500 bila malipo kila mwezi.

Jinsi inavyofanya kazi

Kuanzia kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. 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 kwenye API yetu. Panga masharti, fanya majaribio ya A/B, hakuna msimbo unaohitajika.

  2. Hatua 02

    Unganisha

    Pachika asili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu kiungo kwa mtumiaji wako, kwa barua pepe, SMS, WhatsApp, popote. Chagua kinachofaa stack yako.

  3. Hatua 03

    Mtumiaji anapitia mtiririko

    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 yanapatikana chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

    Webhooks zilizosainiwa kwa wakati halisi huweka database yako sawa mara tu mtumiaji anapoidhinishwa, kukataliwa, au kutumwa kwa ukaguzi. Uliza API inapohitajika. Au fungua console kukagua kila kikao, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa ajili ya utawala · Bei kama miundombinu

Vipengele sita. API moja. $0.33 kwa mpiga kura.

Utambulisho wa kupinga Sybil si ukaguzi mmoja, ni mapishi. KYC mpiga kura, tafuta dhidi ya kundi, tekeleza ustahiki, saini kifurushi cha ukaguzi, tumia tena katika raundi inayofuata.
01 · Mpiga kura wa kipekee

Binadamu halisi mmoja. Utambulisho uliothibitishwa mmoja.

Kifurushi cha KYC kilichothibitishwa na iBeta Level 1 cha kupinga udanganyifu, Uthibitishaji wa Kitambulisho, Uhai Usio na Nguvu, Kulinganisha Uso 1:1, Uchunguzi wa AML. Uamuzi chini ya sekunde mbili, hati 14,000+ katika nchi 220+.
Moduli ya Uthibitishaji wa Mtumiaji
02 · Kugundua nakala

Utafutaji wa Sura 1:N ndani ya kundi lako.

Kila usajili unalinganishwa na kila mpiga kura aliyesajiliwa hapo awali. Juu ya kizingiti cha kufanana → zuia kabla ya kura kurekodiwa. Bila malipo, imepunguzwa kwa data yako tu.
Utafutaji wa Uso 1:N
03 · Kuhifadhi faragha

Thibitisha upekee. Usifichue kingine chochote.

Jukwaa la kupiga kura linaona tu `unique: true`, PID ya uwongo (Kitambulisho cha Uwongo), kikundi cha umri, na eneo. Hati na biometriska hubaki ndani ya Didit, zimesimbwa kwa njia fiche wakati wa kupumzika. Inalingana na GDPR, ISO/IEC 27001, SOC 2 Aina ya 1.
Ilani ya faragha ya utambulisho
04 · Kitambulisho kinachoweza kutumika tena

Thibitisha mara moja. Piga kura kila mahali.

KYC inayoweza kutumika tena (bila malipo, imejumuishwa) inaruhusu mpiga kura aliyethibitishwa kuthibitisha upekee katika kila kura inayofuata kwa selfie tu, hakuna kukamata tena hati. Inafanya kazi katika kila jukwaa linalotumia Didit. Inalingana na eIDAS2.
KYC inayoweza kutumika tena
05 · Sheria za mamlaka

Ustahiki wa kila eneo kwa kila mpiga kura.

Orodha nyeupe ya nchi, umri wa chini, vikwazo / kutengwa kwa PEP, muda wa kuisha kwa hati, kizingiti cha kufanana, yote yametekelezwa katika mtiririko mmoja wa kazi. Hariri sheria katika Mjenzi wa Mtiririko wa Kazi usio na msimbo bila kupeleka tena.
Moduli ya Uchunguzi wa AML
06 · Kifurushi cha ukaguzi

Uthibitisho wa uadilifu wa kura kwa njia ya kriptografia.

Stakabadhi za usajili zilizosainiwa (X-Signature-V2, HMAC SHA-256), PIDs za mpiga kura za uwongo, kumbukumbu zisizoweza kubadilishwa na uhifadhi wa miaka 5 kwa chaguo-msingi. Hamisha kwenye lango lako la uwazi au snapshot ya DAO yako.
Nyaraka za Webhooks
Unganisha

Kikao kimoja. Kundi moja. Uamuzi mmoja uliosainiwa.

Sajili mpiga kura. Soma webhook iliyosainiwa. Zuia nakala. Rekodi kura.
POST /v3/session/Jisajili
$ curl -X POST https://verification.didit.me/v3/session/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -d '{
    "workflow_id": "wf_voter_enrol",
    "vendor_data": "voter-12871",
    "metadata": { "cohort_id": "round-2026-05" }
  }'
201ImeundwaInarudisha URL ya kipindi kilichopangishwa. Uamuzi wa chini ya sekunde 2 baada ya kukamilika.
Zuia kura hadi webhook iseme status: Approved.nyaraka →
GET /v3/session/{sessionId}/decision/Uamuzi
$ curl https://verification.didit.me/v3/session/$SID/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Returns:
{
  "status": "Approved",
  "face_search": { "matches": [] }
}
200OKhali Imeidhinishwa · Imekataliwa · Inapitiwa · Imewasilishwa tena · Imeisha muda
Mechi zisizo tupu zilizo juu ya 0.85 → rudufu, zuia.nyaraka →
Ujumuishaji tayari kwa agent

Tuma upigaji kura wa kuzuia Sybil kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent huunda mtiririko wa usajili, huzuia marudio, hutia saini uamuzi, na huandaa raundi inayofuata.
didit-integration-prompt.md
You are integrating Didit anti-Sybil identity into a voting / governance / survey / airdrop / quadratic-funding platform. The recipe ensures each real human can be counted exactly once — no duplicates, no bots, no farmed accounts.

Two pillars:

  1. Verify the voter is a real human with a real identity. ONE call to POST /v3/session/ with ID Verification + Liveness + Face Match.
  2. Check the voter has not already been enrolled in this cohort. Face Search 1:N runs the voter's face against every previously-enrolled voter and returns a similarity score. Above threshold → duplicate, block.

Cost:
  - Voter Know Your Customer (KYC) bundle: $0.33 per voter (Sessions API)
  - Face Search 1:N: free (included)
  - Re-vote / next round with Reusable KYC: free (the user proves uniqueness without re-doing KYC)
  - 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.
  - A workflow_id from the Workflow Builder that bundles ID Verification + Passive Liveness + Face Match 1:1 + Face Search 1:N + your jurisdiction rules (age, country, sanctions).

STEP 1 — Enrol the voter with the Sessions API

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id with KYC + Face Search 1:N>",
      "vendor_data": "<your voter id, max 256 chars>",
      "callback": "https://<your-app>/vote/enrolment/callback",
      "metadata": {
        "purpose": "vote_enrolment",
        "cohort_id": "<your election / round / airdrop id>"
      }
    }

  Response: 201 Created with the hosted session URL. Redirect the voter to it. Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook on enrolment completion

  Didit POSTs to your callback. Session statuses are Title Case With Spaces:

  Body (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your voter id>",
      "status": "Approved",
      "id_verification": { "status": "Approved" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "face_search": { "status": "Approved", "matches": [] }
    }

  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.

STEP 3 — Block duplicates

  When face_search.matches is non-empty AND the top match's similarity is above your threshold (typical: 0.85), DO NOT add the voter to the cohort. The voter has likely been enrolled already, possibly under a different document or alias.

  Recommended handling:
    similarity ≥ 0.95  → block automatically, log the match
    similarity 0.85–0.95 → route to manual review
    similarity < 0.85  → enrol normally

STEP 4 — Privacy-preserving storage

  The platform stores ONLY:
    - voter_pid (pseudonymous identifier — a UUID, NOT the raw document number)
    - unique (boolean)
    - age_band (e.g. "18+", "25-34") — never the raw birth date unless your eligibility rule needs it
    - region (e.g. "EU", "ES") — never the raw address

  Documents, biometrics, and full names stay inside Didit, encrypted at rest. Default retention 5 years post-relationship; configurable per workflow.

STEP 5 — Read the decision on demand

  GET https://verification.didit.me/v3/session/{sessionId}/decision/
  Headers:
    x-api-key: <your api key>

  Returns the full decision JSON. Use this when the tally service needs to confirm a voter is still eligible at vote time.

STEP 6 — Reusable KYC for subsequent rounds

  Once a voter is verified, the next vote / round / airdrop can reuse the verification at no extra cost. The user proves uniqueness with a selfie only — no document re-capture. Same workflow, different cohort id.

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.
  - Face Search 1:N is scoped to YOUR cohort by default — Didit doesn't share faces across customers.
  - Always check the duplicate score BEFORE recording the ballot, never after.
  - The platform never sees the raw ID document or the raw face template — only the verdict and the pseudonymous PID.
  - Default record retention is 5 years post-relationship per the EU AML package; extend per your governing body's rules.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/sessions-api/retrieve-session
  - https://docs.didit.me/integration/webhooks
  - https://docs.didit.me/core-technology/reusable-kyc/overview

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+ ziko hewani, zinakaguliwa na kupimwa 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.
Soma faili ya usalama na utiifu
EU financial sandbox
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Usalama wa habari · 2026
SOC 2 · Type I
AICPA · 2026
iBeta Level 1 PAD
NIST / NIAP · 2026
GDPR
EU 2016/679
DORA
EU 2022/2554
MiCA
EU 2023/1114
AMLD6 · eIDAS 2.0
EU-aligned kwa muundo

Namba za uthibitisho

Namba za uthibitisho
  • $0.00
    Kwa kila mpiga kura, kifurushi kamili cha KYC, Utafutaji wa Sura 1:N ndani ya kundi umejumuishwa.
  • Free
    KYC inayoweza kutumika tena, raundi zinazofuata zinathibitisha upekee kwa selfie tu.
  • <0s
    Uamuzi wa usajili wa mwisho hadi mwisho kwa kila mpiga kura, kwenye Android ya kiwango cha chini.
  • 0
    Uthibitishaji wa bure kila mwezi, kwenye kila akaunti.
Ngazi tatu, orodha moja ya bei

Anza bure. Lipa kulingana na matumizi. Panua hadi Enterprise.

Uthibitishaji 500 bila malipo kila mwezi, milele. Lipa kadri unavyotumia kwa uzalishaji. Mikataba maalum, uhifadhi wa data, na SLA (Service Level Agreements) kwenye Enterprise.
Bure

Bure

$0 / mwezi. Hakuna kadi ya mkopo inayohitajika.

  • Kifurushi cha bure cha KYC (Uthibitishaji wa Kitambulisho + Passive Liveness + Face Match + Uchambuzi wa Kifaa & IP), 500 / mwezi, kila mwezi
  • Watumiaji Waliozuiwa
  • Utambuzi wa Marudio
  • Ishara 200+ za udanganyifu kwenye kila session
  • KYC inayoweza kutumika tena kwenye mtandao wa Didit
  • Jukwaa la Usimamizi wa Kesi
  • Workflow Builder
  • Nyaraka za umma, sandbox, SDKs, server ya MCP (Model Context Protocol)
  • Usaidizi wa jamii
Maarufu zaidi
Lipa kulingana na matumizi

Kulingana na Matumizi

Lipa tu kwa unachotumia. Moduli 25+. Bei za umma kwa kila moduli, hakuna ada ya chini ya kila mwezi.

  • KYC kamili kwa $0.33 (Kitambulisho + Biometric + IP / Kifaa)
  • Data za AML 10,000+, vikwazo, PEPs, habari hasi
  • Vyanzo vya data vya serikali 1,000+ kwa Uthibitishaji wa Database
  • Ufuatiliaji wa Miamala kwa $0.02 kwa kila muamala
  • KYB ya moja kwa moja kwa $2.00 kwa kila biashara
  • Uchunguzi wa Wallet kwa $0.15 kwa kila ukaguzi
  • Mtiririko wa uthibitishaji wa Whitelabel, brand yako, miundombinu yetu
Biashara Kubwa

Biashara Kubwa

MSA & SLA maalum. Kwa idadi kubwa na programu zilizodhibitiwa.

  • Mikataba ya kila mwaka
  • MSA, DPA, na SLA maalum
  • Kituo maalum cha Slack na WhatsApp
  • Wakaguzi wa mikono wanapohitajika
  • Masharti ya muuzaji na white-label
  • Vipengele vya kipekee na ushirikiano wa washirika
  • CSM aliyetajwa, ukaguzi wa usalama, usaidizi wa kufuata

Anza bure → lipa tu wakati ukaguzi unafanyika → fungua Enterprise kwa mkataba maalum, SLA, au uhifadhi wa data.

FAQ

Maswali ya kawaida

What is Didit?

Didit is infrastructure for identity and fraud, the platform we wished existed when we were building products ourselves: open, flexible, and developer-friendly, so it works as a real part of your stack instead of a black box you integrate around.

One API covers verifying people (KYC, know your customer), verifying businesses (KYB, know your business), screening crypto wallets (KYT, know your transaction), and monitoring transactions in real time, on a stack built to be:

  • Fast, sub-2-second p99 on every session
  • Reliable, in production with 1,500+ companies across 220+ countries
  • Secure, SOC 2 Type 1, ISO 27001, GDPR-native, and formally attested by Spain's financial regulator as safer than verifying someone in person

The footprint underneath: 14,000+ document types in 48+ languages, 1,000+ data sources, and 200+ fraud signals on every session. The Didit infrastructure dynamically learns from every session and gets better every day.

What's the anti-Sybil problem, in plain English?

A Sybil attack is when one human pretends to be many, by spinning up wallets, email addresses, burner phones, or fake IDs, to game a system that counts each account as one vote, one entry, one share.

It shows up everywhere voting or scarcity matter:

  • DAO governance, a whale opens 1,000 wallets and skews every proposal
  • Airdrops, a farmer creates 50,000 accounts and drains the token allocation
  • Quadratic funding, fake identities multiply a single donor's matched funds
  • Citizen surveys and polls, coordinated brigading manufactures consent
  • Content-moderation votes, sock-puppet accounts swing what gets boosted or removed

The only durable defence is to bind each vote to a real human. That's what this recipe ships.

Why do wallets and email addresses fail as identity?

They prove control of a resource, not control of a body.

  • A wallet proves you hold a private key. You can hold a hundred private keys.
  • An email address proves you registered with an SMTP provider. SimpleLogin, gmail.com, and a thousand others mint addresses in seconds.
  • A phone number proves a SIM card. SIM farms and virtual-number providers sell them in bulk.
  • An IP address proves a network connection. VPNs, residential proxies, and datacenter pools rotate them on demand.

A face plus a government document is harder. There is exactly one face per body, and one valid government ID per face per country. Forging at scale costs orders of magnitude more than spinning up a wallet.

How fast is the verification for my end user?

The full flow normally takes under 30 seconds end-to-end, pick up the ID, snap the document, snap the selfie, done. That is the fastest in the market. Legacy KYC providers usually take more than 90 seconds for the same flow.

On the back end, Didit returns the result in under two seconds at p99, measured from the moment the user finishes the selfie to the moment your webhook fires. Mobile capture is tuned for slow phones and slow networks: progressive image compression, lazy software development kit load, and a one-tap hand-off from desktop to phone via QR code if the user starts on web.

How does Face Search 1:N actually catch duplicates?

When a voter enrols, Didit creates a privacy-preserving face template (a vector, not the image) and compares it against every other voter template in your cohort. The output is a list of matches, each with a similarity score from 0 to 1.

A typical policy:

  • ≥ 0.95 similarity, almost certainly the same person, block automatically
  • 0.85 – 0.95, likely the same person, route to manual review
  • < 0.85, different person, enrol normally

The cohort is scoped to YOUR dataset, Didit does not share faces across customers. The template is encrypted at rest, never exposed to the voting platform, and falls under the privacy notice the user agreed to at enrolment.

What happens if a user fails, abandons, or expires?

Every session lands on one of seven clear statuses, so your code always knows what to do:

  • Approved, every check passed. Move the user forward.
  • Declined, one or more checks failed. You can allow the user to resubmit the specific failed step (for example, re-take the selfie) without re-running the whole flow.
  • In Review, flagged for compliance review. Open the case in the console, see every signal, decide approve or decline.
  • In Progress, user is mid-flow.
  • Not Started, link sent, user has not opened it yet. Send a reminder if it sits too long.
  • Abandoned, user opened the link but did not finish in time. Re-engage or expire.
  • Expired, the session link aged out. Create a new session.

A signed webhook fires on every status change, so your database always stays in sync. Abandoned and declined sessions are free.

Where does my customer data live and how is it protected?

Production data is processed and stored in the European Union by default, on Amazon Web Services. Enterprise contracts can request alternative regions for jurisdictions whose regulators require it.

Encryption everywhere. AES-256 at rest across every database, object store, and backup. Transport Layer Security 1.3 in transit on every API call, webhook, and Business Console session. Biometric data is encrypted under a separate Customer Master Key.

Retention is yours to control. Default retention is indefinite (unlimited) unless you configure shorter, between 30 days and 10 years per application, and you can delete any individual session at any time from the dashboard or the API.

Certifications: SOC 2 Type 1 (Type 2 audit in progress), ISO/IEC 27001:2022, iBeta Level 1 PAD, and a public attestation from Spain''s Tesoro / SEPBLAC / CNMV that Didit''s remote identity verification is safer than verifying someone in person. Full report at /security-compliance.

Is Didit compliant for my industry?

Didit ships compliant by default for the regulators that matter to identity infrastructure:

  • GDPR + UK GDPR, controller / processor split, full Data Processing Agreement published, lead supervisory authority named (Spain''s AEPD).
  • AMLD6 + EU AML Single Rulebook, 1,300+ sanctions, politically exposed person, and adverse-media lists screened in real time.
  • eIDAS 2.0, EU Digital Identity Wallet aligned; reusable-identity ready.
  • MiCA (Markets in Crypto-Assets), ready for crypto on-ramps, exchanges, and custodians.
  • DORA, Digital Operational Resilience Act, EU financial-services operational resilience.
  • BIPA, CUBI, Washington HB 1493, CCPA / CPRA, US biometric privacy (Illinois, Texas, Washington) and California consumer privacy.
  • UK Online Safety Act, age-gating and child-safety obligations.
  • FATF Travel Rule, originator and beneficiary data on crypto transfers, IVMS-101 interoperable.

Detailed memo, every certificate, every regulator letter: /security-compliance.

How fast can I integrate and start verifying users?
  • 60 seconds to a sandbox account at business.didit.me, no credit card.
  • 5 minutes to a working verification through Claude Code, Cursor, or any coding agent via our Model Context Protocol (MCP) server.
  • A weekend to a production-ready integration with signed-webhook verification, retries, and a remediation flow when a user is declined.

Three integration paths, pick whichever fits your stack:

  • Embed natively with our Web, iOS, Android, React Native, or Flutter SDK.
  • Redirect the user to the hosted verification page, zero SDK.
  • Send a link by email, SMS, WhatsApp, or any channel, zero front-end work.

Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.

What about voters across multiple rounds, do they pay every time?

No. Once a voter is verified by Didit, Reusable KYC (free, included) lets them prove uniqueness on every subsequent round with a selfie only, no document re-capture.

In practice:

  • Round 1, full KYC bundle at $0.33
  • Round 2, 3, 4, …, the user opens a new session against the next cohort id, takes a selfie, and Didit re-matches against the original verified template. Free.

The credential is portable across every Didit-powered platform, aligned with eIDAS2 (the EU's digital-identity regulation). The voter owns the credential, they re-present it on demand, you never re-pay.

What does the audit trail look like for a regulator or a transparency portal?

Every enrolment produces a signed receipt you can export to your audit log or your DAO's transparency portal:

  • session_id, Didit's verifiable identifier for the enrolment
  • voter_pid, your pseudonymous voter id
  • verdict, Approved, Declined, In Review, etc. (status enum: Approved, Declined, In Review, Resubmitted, Expired, Not Finished, Kyc Expired, Abandoned)
  • cohort_id, which round / election / airdrop
  • signature, X-Signature-V2 HMAC SHA-256 of the payload with your webhook secret
  • timestamp

Pair with the on-chain attestation (if used) and you have a tamper-evident trail from "this real human enrolled" to "this ballot was cast". Default retention 5 years, extendable per your governing body's rules.

What does the integration look like for a small team?

Four steps, one afternoon:

  • Open the sandbox at business.didit.me, sandbox key in 60 seconds, no credit card
  • Build a workflow in the Workflow Builder that bundles ID + Liveness + Face Match + Face Search 1:N + your eligibility rules
  • Wire POST /v3/session/ to enrol voters and the signed webhook to receive verdicts
  • Block the ballot until the webhook says status: Approved and face_search.matches is empty (or below your threshold)

The Didit MCP (Model Context Protocol) server is included free, paste the integration prompt above into Claude Code, Cursor, Codex, Replit Agent, Devin, or Aider and the agent scaffolds the whole thing against the live /v3/ API.

Miundombinu ya utambulisho na udanganyifu.

API moja kwa KYC, KYB, Ufuatiliaji wa Miamala, na Uchunguzi wa Wallet. Unganisha ndani ya dakika 5.

Uliza AI ifupishe ukurasa huu