Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Uthibitishaji wa Kitambulisho

Thibitisha kitambulisho chochote,
popote duniani.

Thibitisha pasipoti, kitambulisho cha taifa, leseni ya udereva, au kibali cha kuishi kutoka nchi yoyote. Hati 14,000+, uamuzi chini ya sekunde 2, $0.15 kwa kila ukaguzi, 500 bila malipo/kwa mwezi.

Anza bila malipoSoma nyaraka
Inaungwa mkono na
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Inaaminika na mashirika 2,000+ duniani kote.

Uthibitishaji wa Kitambulisho wa Didit, kunasa hati, OCR, na ukaguzi wa uhalisi papo hapo.

Ufikiaji wa kimataifa

Hati 14,000+.
Nchi 220+.

DNI ya Uhispania, My Number ya Japani, pasipoti ya Uingereza. Hati mpya huongezwa kila mwezi, bado $0.15 kwa kila ukaguzi, muundo wa uamuzi uleule, majibu chini ya sekunde 2.

Jinsi inavyofanya kazi

Kutoka 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. Gawanya kulingana na masharti, fanya majaribio ya A/B, hakuna code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika kiasili 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 mchakato

    Didit huandaa 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 mamlaka. Matokeo 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. Piga API inapohitajika. Au fungua console kukagua kila kikao, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa ajili ya waendelezaji · Imejengwa dhidi ya udanganyifu · Wazi kwa muundo

Uwezo sita. Feature flag moja. ID_VERIFICATION .

Kila uwezo hapa chini ni swichi kwenye moduli moja. Hakuna viwango vya kuongeza mauzo, hakuna SKU tofauti, hakuna simu za nyongeza. Ziwasha kwa kila mtiririko wa kazi kwenye console, au zipitishe papo hapo unapopiga endpoint huru.
Soma nyarakaPata API key
01 · Ufikiaji

Nchi 220+. Aina za hati 14,000+.

Pasi za kusafiria, vitambulisho vya kitaifa, leseni za udereva, vibali vya kuishi. Lugha 130+, hati 50+ (Kilatini, Kiarabu, Kisirili, CJK, Kidevanagari, Kiebrania, Kithai, Kijojia). Nyaraka mpya huongezwa kila mwezi. Udhibiti wa aina ndogo kwa kila nchi, kubali Leseni ya Udereva ya Indiana na New York Enhanced kando ikiwa sera inahitaji.
02 · Uchimbaji wa data

Sehemu zinazoonekana, MRZ, na barcode, zimekaguliwa kwa pamoja.

Kila sehemu inayoonekana, MRZ (eneo linaloweza kusomwa na mashine), na sehemu ya barcode hutolewa kwa mpigo mmoja. Hizi tatu hukaguliwa kwa pamoja kabla ya jibu kuondoka kwenye mfumo wetu. Kutofautiana huonekana kama maonyo ili uweze kuelekeza kesi hiyo kwenye ukaguzi wa mikono.
03 · Uhalisi

Hati ni halisi. Picha iko sawa. Hakuna picha ya skrini.

Kulinganisha template dhidi ya database iliyothibitishwa. Kugundua hologram na microprint. Ukaguzi wa uadilifu wa picha. Uhai wa hati hushinda mbinu nne za kawaida za mashambulizi, picha za skrini, picha za simu, nakala zilizochapishwa, na ubadilishaji wa picha kwenye hati halisi.
04 · Ubora wa upigaji picha

Kataa ukungu na mng'ao kabla hazijafika kwenye ukaguzi.

Umakini, mwangaza, na azimio hupimwa 0–100 kwa kila uwasilishaji, pamoja na alama ya jumla iliyopimwa. Pembe zilizo nje ya fremu na pande zilizoangaziwa kupita kiasi huonyeshwa wazi. Vizingiti vinavyoweza kurekebishwa hukataa upigaji picha wa ubora wa chini mapema ili zisifike kwenye foleni yako ya ukaguzi wa mikono.
05 · Sera ya hatari

Amua. Kagua. Idhinisha. Kwa kila hatari. Kwa kila programu.

Kila kategoria ya hatari, mtumiaji anayerudiwa, MRZ batili, kutofautiana kwa data, uhai mdogo wa hati, huwekwa kwenye kukataa, kukagua, au kuidhinisha. Rekebisha sera kwa kila programu, nchi, na aina ya hati. Vianzisha vya kukataa kiotomatiki (imeisha muda, imezuiwa, haitumiki) hubaki kutekelezwa bila kujali mipangilio yako.
06 · KYC inayoendelea

Hati huisha muda. Zigundue kabla mdhibiti hajagundua.

Tunafuatilia muda wa kuisha kwa kila hati unayohifadhi. Hati inapokwisha muda, hali ya KYC ya mtumiaji hubadilika kiotomatiki na tunakutumia arifa kupitia webhook. Hakuna kazi ya batch, hakuna mradi wa robo mwaka wa kuingiza upya, usasishaji wa KYC unabaki kuendelea na unazingatia Maelekezo ya AML.
Unganisha

Endpoints mbili. JSON sawa. Bei sawa.

Unda kikao unapotaka UI yetu iliyopangishwa ishughulikie kunasa, au piga endpoint huru unapo tayari una picha. Zote mbili hurejesha ripoti sawa ya id_verification.
POST /v3/session/Hosted UI
$ 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_3daf4c64",
    "vendor_data": "user-42"
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Tunakaribisha UI ya kukamata data. Unaelekezwa kwenye session_url.nyaraka →
POST /v3/id-verification/Server kwa server
$ curl -X POST https://verification.didit.me/v3/id-verification/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "front_image=@front.jpg" \
  -F "back_image=@back.jpg"
200OK{ "status": "Imeidhinishwa", "document_type": "Passport" }
Wewe unamiliki mchakato wa kukamata data. Tunakurudishia ripoti kamili papo hapo.nyaraka →
Ujumuishaji tayari kwa agent

Weka Uthibitishaji wa Kitambulisho kwa prompt moja.

Bandika kizuizi kilicho hapa chini kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza kishikilia nafasi cha my_stack na framework yako, lugha, na matumizi. Agent itaweka Didit, itajenga workflow na Uthibitishaji wa Kitambulisho umewezeshwa, itaunganisha webhook, na kuweka mambo sawa.
didit-integration-prompt.md
# Didit ID Verification — integrate in 5 minutes

You are integrating Didit's ID Verification 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. Two integration paths — pick one

### Path A — Workflow Builder (hosted UI)
Best when you want Didit to handle camera, lighting cues, retries,
mobile handoff, and accessibility for you.

1. Create a workflow that contains the ID_VERIFICATION feature:
   POST https://verification.didit.me/v3/workflows/
   Authorization header:  x-api-key: <your-api-key>
   Body: workflow_label, features array with the single entry
         { feature: "ID_VERIFICATION" }   (UPPERCASE — strict enum)

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 server-to-server API
Best when you already have the document image (mobile SDK capture, native
onboarding app, reseller pipeline).

POST https://verification.didit.me/v3/id-verification/
Content-Type: multipart/form-data
Body fields:
  - front_image  (required, file)
  - back_image   (optional, file)
  - vendor_data  (optional string, your user id)

Response: JSON report with extracted fields, image quality scores,
warnings array, and the verdict.

## 3. Webhooks (Path A only — Path B returns synchronously)
- 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", "kyc_expired"]
- 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.

## 4. Reading the report (both paths return the same shape)
The id_verification object includes:
- status: "Approved" | "Declined" | "In Review" | "Expired" | "Not Finished"
- document_type: "Passport" | "Identity Card" | "Driver's License" | "Residence Permit" | null
- document_number, personal_number
- front_image, back_image, portrait_image (signed URLs, expire in 1 hour)
- date_of_birth (YYYY-MM-DD), age (number)
- expiration_date, date_of_issue (YYYY-MM-DD)
- issuing_state, issuing_state_name (ISO 3166-1 alpha-3 + display name)
- first_name, last_name, full_name
- gender ("M" | "F" | "U"), nationality (ISO 3166-1 alpha-3)
- address, formatted_address, parsed_address (street_1, street_2, city,
  region, postal_code, geometry { lat, lng })
- front_image_quality_score / back_image_quality_score (focus, brightness,
  resolution, overall, each 0-100)
- warnings: Array<{ risk, log_type, short_description, long_description }>

## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: ID_VERIFICATION, LIVENESS, FACE_MATCH, AML, IP_ANALYSIS.
- 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", "Declined", "In Review",
  "Expired", "Not Finished" (title-cased, space-separated).

## 6. Pricing reference (public)
- Path A bundled in a full KYC workflow: $0.33 per session
- Path B standalone /v3/id-verification/ call: $0.15 per call
- 500 free verifications every month, forever, on every account.

## 7. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test docs: deterministic synthetic IDs returned in sandbox.
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/id-verification/overview
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 kuthibitisha

Namba za kuthibitisha
  • 0+
    Nchi na maeneo yanayoungwa mkono.
  • 0+
    Aina za hati za utambulisho katika database iliyothibitishwa.
  • <0s
    Uchunguzi wa mwisho hadi mwisho kwa kila uthibitishaji.
  • $0.00
    Kwa kila ukaguzi wa ID unaojitegemea. 500 bure kila mwezi.
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
Anza bure
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
Tazama orodha kamili ya beiAnza bure
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
Wasiliana nasi

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.

Which document types and countries are supported?
Passports, national ID cards, driver's licenses, and residence permits across 220+ countries and territories, 14,000+ distinct document templates in total, with text recognition in 130+ languages and 50+ scripts (Latin, Arabic, Cyrillic, CJK, Devanagari, Hebrew, Thai, Georgian). The full catalog is browsable at docs.didit.me/core-technology/id-verification/supported-documents-id-verification, and the same data feeds the searchable table on this page.
What is the response shape?
A single id_verification JSON object. Top-level status is one of Approved, Declined, In Review, Expired, or Not Finished. The object also includes document_type, document_number, full_name, first_name, last_name, date_of_birth (YYYY-MM-DD), age, expiration_date, date_of_issue, issuing_state (ISO 3166-1 alpha-3), nationality, gender, address, a structured parsed_address with street, city, region, postal_code, and geometry coordinates, signed URLs for portrait_image / front_image / back_image / front_video / back_video, image quality scores for focus / brightness / resolution / overall (each 0–100), and a warnings array. Full reference at docs.didit.me/core-technology/id-verification/report-id-verification.
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 Didit defeat document fraud?
Five layers, every layer enabled by default: (1) template matching against the certified document database, (2) security-feature detection (holograms, microprint, watermarks), (3) tamper detection on the portrait and biographic data, (4) document liveness that rejects screen captures, printed copies, and digital edits, (5) cross-reference between visual zone, MRZ, and barcode. Auto-decline triggers, DOCUMENT_EXPIRED, MINIMUM_AGE_NOT_MET, DOCUMENT_NOT_SUPPORTED_FOR_APPLICATION, ID_DOCUMENT_IN_BLOCKLIST, PORTRAIT_IMAGE_NOT_DETECTED, stay enforced regardless of your risk policy.
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.

Related

Moduli zinazohusiana

Miundombinu ya utambulisho na udanganyifu.

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

Anza bila malipoZungumza nasi
Uliza AI ifupishe ukurasa huu