Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Passive Liveness

Thibitisha uso wowote.
Bila kuwaomba wafanye chochote.

Thibitisha kuwa mtu aliye kwenye kamera ni halisi na yuko hai. Anti-spoof iliyothibitishwa na iBeta, inashinda deepfakes, barakoa, replays, na mashambulizi ya morph chini ya sekunde 2. Passive kwa $0.10, active kwa $0.15. 500 bure/mwezi.

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

Inaaminika na mashirika 2,000+ duniani kote.

Didit Liveness, upatikanaji wa uhai usio na juhudi na uamuzi wa chini ya sekunde 2 kwenye kifaa.

Imethibitishwa na iBeta

Passivu. Flash.
Amilifu. Zote zimethibitishwa.

Gundua barakoa za 3D, deepfakes, mashambulizi ya kurudia, na picha zilizochapishwa. Imethibitishwa na iBeta, uamuzi wa chini ya sekunde 2, $0.10 kwa kila ukaguzi, 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, ID, liveness, 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 code inayohitajika.

  2. Hatua 02

    Unganisha

    Pachika asili na SDK yetu ya Web, iOS, Android, React Native, au Flutter. Elekeza kwenye ukurasa uliopangishwa. Au tuma tu mtumiaji wako kiungo, 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. Mtumiaji akiwa 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. Piga API inapohitajika. Au fungua console kukagua kila session, 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. LIVENESS.

Kila uwezo hapa chini ni swichi kwenye moduli moja. Hakuna viwango vya upsell, hakuna SKU tofauti, hakuna simu za nyongeza. Ziwashe kwa kila mtiririko wa kazi kwenye console, au zipitishe moja kwa moja kwenye endpoint huru.
Soma nyarakaPata API key
01 · Njia

Passive, 3D Flash, 3D Action. Chagua kulingana na hatari.

Njia tatu kwenye moduli moja. Passive (frame moja, hakuna hatua ya mtumiaji) kwa usajili rahisi. 3D Flash (mlolongo mfupi wa mwanga unanasa kina kutoka kwenye mwangaza) kwa mtiririko wa passive wa thamani ya juu. 3D Action & Flash (mwendo + flash) kwa masoko nyeti kwa udhibiti na usajili wa thamani kubwa.
02 · Anti-spoof iliyothibitishwa

Imejaribiwa dhidi ya orodha kamili ya mashambulizi ya uwasilishaji.

Imejaribiwa kwa kujitegemea na kuthibitishwa na iBeta, kiwango ambacho NIST na Open Identity Exchange wanataja. Inazuia picha zilizochapishwa, marudio ya skrini, barakoa za karatasi, barakoa za silikoni, barakoa za mpira, mashambulizi ya morph, na deepfakes zinazozalishwa na AI. Inajaribiwa upya kila mwaka kadri orodha ya mashambulizi inavyokua.
03 · Uamuzi wa chini ya sekunde 2

Inference ya mwisho hadi mwisho chini ya sekunde mbili.

Inference inayotolewa na edge. Hakuna upakuaji wa modeli, hakuna dhana ya kuongeza kasi kwenye kifaa, hakuna uzoefu uliopungua kwenye Android za kiwango cha chini. Passive inakamilika chini ya sekunde moja kwenye vifaa vingi. Flash inaongeza ~600ms. Active 3D inaongeza ~1.5s, bado chini ya sekunde 2 mwisho hadi mwisho.
04 · Maonyo

Sera ya hatari inayoweza kurekebishwa kwa kila mtiririko wa kazi.

Maonyo saba yanayoweza kusanidiwa, alama ya chini, uwezekano wa kurudia, uso uliorudiwa, nyuso nyingi, ubora wa chini wa uso, mwanga hafifu, mwanga mkali, kila moja ikiwa imepangwa kukataa, kukagua, au kuidhinisha kwa kila programu. Vianzishi vitatu vya kukataa kiotomatiki (hakuna uso, shambulio limegunduliwa, uso uliozuiliwa) vinabaki kutekelezwa bila kujali.
05 · Makadirio ya umri

Upatikanaji mmoja, ishara mbili.

Washa Makadirio ya Umri kwenye mtiririko wa liveness na selfie hiyo hiyo inarudisha uamuzi wa liveness pamoja na bendi ya umri iliyokadiriwa. Imejengwa kwa Sheria ya Usalama Mtandaoni ya Uingereza na age-gating ya EU, binadamu halisi-NA-mzee-wa-kutosha bila kumlazimisha mtumiaji kupitia upakiaji wa ID. $0.10 kwa kila ukaguzi.
06 · Uthibitishaji wa kibayometriki

Injini ileile unayotumia wakati wa kujisajili. Sasa kila unapoingia.

Liveness ni msingi wa Uthibitishaji wa Kibayometriki, tumia tena modeli hiyo hiyo ya anti-spoof kuthibitisha watumiaji wanaorudi kwenye kila hatua nyeti: uhamishaji wa thamani ya juu, kuweka upya nenosiri, uondoaji mkubwa. $0.10 kwa kila uthibitishaji, drop-in kwa SMS 2FA, hakuna bili ya mtoa huduma, hakuna hatari ya SIM-swap.
Unganisha

Endpoints mbili. JSON moja. Bei moja.

Unda session unapotaka UI yetu iliyopangishwa ishughulikie upatikanaji (inahitajika kwa njia tendaji), au piga endpoint huru isiyo tendaji unapo tayari una selfie. Zote mbili zinarudisha ripoti sawa ya liveness.
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_liveness_3d",
    "vendor_data": "user-42"
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Tunakaribisha UI ya kunasa. Inahitajika kwa FLASHING na ACTIVE_3D.nyaraka →
POST /v3/passive-liveness/Server kwa server
$ curl -X POST https://verification.didit.me/v3/passive-liveness/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "image=@selfie.jpg"
200OK{ "status": "Imeidhinishwa", "score": 98 }
Wewe unamiliki upigaji picha. Sisi tunarudisha uamuzi papo hapo.nyaraka →
Ujumuishaji tayari kwa agent

Weka Liveness hewani kwa amri moja.

Bandika kizuizi kilicho hapa chini kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza kishika nafasi cha my_stack na mfumo wako, lugha, na matumizi. Agent itaweka Didit, itajenga workflow na Liveness imewashwa, itaunganisha webhook, na kuweka hewani.
didit-integration-prompt.md
# Didit Liveness — integrate in 5 minutes

You are integrating Didit's Liveness (presentation-attack detection) 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, motion prompts, low-light
fallback, mobile handoff, and accessibility for you.

1. Create a workflow that contains the LIVENESS 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: "LIVENESS" }   (UPPERCASE — strict enum)
   Optional config: liveness_method ("PASSIVE" | "FLASHING" | "ACTIVE_3D")
   and per-warning threshold overrides.

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 a selfie image (mobile SDK capture, native
onboarding app, reseller pipeline). Standalone is single-frame
PASSIVE only — for ACTIVE_3D or FLASHING you must use Path A.

POST https://verification.didit.me/v3/passive-liveness/
Content-Type: multipart/form-data
Body fields:
  - image        (required, file — single selfie)
  - vendor_data  (optional string, your user id)

Response: JSON report with liveness score, method, and warnings array.

## 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"]
- 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 liveness object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- method: "PASSIVE" | "FLASHING" | "ACTIVE_3D"
- score: number 0-100 (normalized liveness score)
- reference_image: signed URL to the captured selfie (expires in 1 hour)
- video_url: signed URL to the capture video, present only for FLASHING
  and ACTIVE_3D (expires in 1 hour)
- age_estimation: { age, age_range } when enabled in the workflow
- warnings: Array<{ risk, log_type, short_description, long_description }>

Auto-decline risks (always enforced by Didit, not configurable):
- NO_FACE_DETECTED
- LIVENESS_FACE_ATTACK
- FACE_IN_BLOCKLIST

Configurable risks (action per workflow — Decline, Review, or Approve):
- LOW_LIVENESS_SCORE
- POSSIBLE_DUPLICATED_FACE
- DUPLICATED_FACE
- MULTIPLE_FACES_DETECTED
- LOW_FACE_QUALITY
- LOW_FACE_LUMINANCE
- HIGH_FACE_LUMINANCE

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

## 6. Pricing reference (public)
- PASSIVE method: $0.10 per check (standalone or bundled)
- FLASHING / ACTIVE_3D methods: $0.15 per check
- Bundled in a full KYC workflow: $0.33 per session (includes Liveness)
- 500 free checks every month, forever, on every account.

## 7. Verify your integration
- Sandbox starts on signup at https://business.didit.me — no separate flag.
- Test images: deterministic synthetic faces returned in sandbox (Approved
  by default; trigger Declined by sending the canonical "spoof" test image).
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/liveness/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 uthibitisho

Namba za uthibitisho
  • iBeta
    Imethibitishwa kwa uhuru dhidi ya udanganyifu (utambuzi wa shambulio la uwasilishaji).
  • 0
    Mbinu za Liveness, passive, 3D flash, 3D action + flash.
  • <0s
    Uamuzi wa mwisho hadi mwisho kwa kila uthibitisho.
  • $0.00
    Kwa kila ukaguzi wa passive liveness. 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.

What inputs does Liveness accept?
A single selfie. Path A, Workflow Builder: the hosted UI captures the selfie inside the user's session, passive needs no user action, 3D Flash plays a short colour sequence, 3D Action prompts a head movement. Comes for free with the session, no extra capture work on your side. Path B, Standalone API: you pass the image yourself as user_image on a multipart POST /v3/passive-liveness/. Accepted formats: JPG, JPEG, PNG, up to 5 MB. Both paths return the same liveness JSON shape.
What is the response shape?
A root-level liveness object with status (Approved, Declined, In Review, or Not Finished), a 0–100 score, the method used (PASSIVE, FLASHING, or ACTIVE_3D), an age_estimation float (optional, when bundled), a signed reference_image URL, a signed video_url for active methods, a matches array surfacing any face-search hits (each with session_id, similarity_percentage, is_blocklisted), and a warnings array. Each warning carries risk, log_type (information, warning, or error), short_description, and long_description. Same shape whether you called the Workflow Builder or the standalone API. Full reference at docs.didit.me/core-technology/liveness/report-liveness.
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 deepfakes, masks, and replay attacks?

Three methods, one module, iBeta Level 1 Presentation Attack Detection (PAD) certified across the full attack catalogue:

  • Passive, one frame, zero user action. Catches printed photos, screen replays, and basic morph attacks. Best for low-friction sign-up.
  • 3D Flash (`FLASHING`), plays a short colour sequence on the phone screen and measures the reflection on the face. Defeats 2D screen replays and high-fidelity printed masks.
  • 3D Action (`ACTIVE_3D`), combines a head-movement prompt with the flash sequence. Defeats 3D silicone masks and AI-generated deepfake video. Best for high-value onboarding and regulator-sensitive markets.

Seven configurable warnings (low score, low light, high light, possible duplicate, duplicate face, multiple faces, low face quality) map to decline / review / approve per application. Three auto-decline triggers (no face, attack detected, blocklisted face) are always enforced.

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