Skip to main content
Didit Yakusanya $7.5M Kujenga Miundombinu ya Utambulisho na Udanganyifu
Didit
Face Match 1:1

Unganisha uso na kitambulisho.
Ndani ya nusu sekunde.

Thibitisha kuwa mtu aliye kwenye kamera anafanana na picha kwenye kitambulisho chake. Matokeo ya haraka sana. $0.05 kwa kila ukaguzi, 500 bila malipo/mwezi, au imejumuishwa kwenye KYC kamili ya $0.33 (know your customer).

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 Face Match 1:1, selfie ikilinganishwa na picha ya kitambulisho na alama ya kufanana chini ya sekunde 2.

Ukaguzi wa mtu yule yule

Linganisha selfie
na picha ya kitambulisho.

Alama ya kufanana chini ya sekunde 2 na kinga dhidi ya udanganyifu. $0.05 kwa kila ukaguzi, ulinganishaji wa uso wa bei nafuu zaidi sokoni.

Jinsi inavyofanya kazi

Kutoka kujisajili hadi mtumiaji aliyethibitishwa kwa hatua nne.

  1. Hatua 01

    Unda mtiririko wa kazi

    Chagua ukaguzi unaotaka, kitambulisho, uhai, ulinganishaji wa 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 moja kwa moja 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 kipindi, kila ishara, na kudhibiti kesi kwa njia yako.

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

Uwezo sita. Bendera moja ya kipengele. FACE_MATCH.

Kila uwezo hapa chini ni swichi kwenye moduli moja. Hakuna viwango vya kuongeza mauzo, hakuna SKU tofauti, hakuna simu za nyongeza. Washa Face Match kwa kila mtiririko wa kazi, au piga endpoint ya pekee moja kwa moja.
Soma nyarakaPata API key
01 · Uunganishaji

Selfie ya moja kwa moja. Picha ya hati. Utambulisho mmoja.

Face Match inakamilisha mzunguko kati ya hati aliyopakia mtumiaji na mtu aliye mbele ya kamera. Ndani ya kipindi cha KYC (know your customer) inaendeshwa kiotomatiki dhidi ya picha ya kitambulisho. Kwa pekee, unapitisha picha mbili, chanzo na lengo, na tunarudisha alama ya kufanana.
02 · Alama ya kufanana

Alama moja. Kutoka sifuri hadi mia.

Kila ulinganishaji unarudisha alama ya kufanana ya 0–100, URL za picha mbili, na rejeleo la kipindi linalounganisha matokeo na uthibitishaji uliotoa selfie. Hifadhi alama na hali; URL za picha huisha baada ya dakika 60 ili uhifadhi tu kile kinachohitajika na sera yako ya ukaguzi.
03 · Matokeo ya haraka sana

Chini ya sekunde moja kwenye hardware ya kawaida.

Modeli ya upachikaji wa uso inayotolewa na edge. Hakuna upakuaji wa modeli, hakuna dhana ya kuongeza kasi kwenye kifaa, hakuna uzoefu uliopungua kwenye Android za kiwango cha chini. Injini na latency sawa iwe unapitia UI ya mtiririko wa kazi iliyopangishwa au endpoint ya pekee. Imara dhidi ya mkao, mwanga, mtindo wa nywele, miwani, na uzee wa kawaida.
04 · Vizingiti vinavyoweza kurekebishwa

Amua. Kagua. Idhinisha. Kwa kila kiwango cha alama.

Onyo moja linaloweza kusanidiwa, kufanana kidogo, linaendana na vizingiti viwili unavyoweka kwa kila programu. Chini ya kizingiti cha kukataa hukataa kiotomatiki; katikati hupeleka kwa ukaguzi wa mikono; juu ya kizingiti cha ukaguzi hukubali kiotomatiki. Kichochezi kimoja cha kukataa kiotomatiki (hakuna picha ya marejeleo) hubaki kutekelezwa na sisi bila kujali.
05 · Muundo wa moduli

Washa kwenye workflow yoyote. Bila kuandika upya capture.

Face Match ni feature flag kwenye workflow builder sawa na ID Verification, Liveness, na AML (anti-money laundering). Iongeze kwenye onboarding flow iliyopo na session inayofuata itaijumuisha, hakuna SDK upgrade, hakuna skrini mpya ya kukamata, hakuna webhook tofauti. Iondoe na flow iliyobaki itaendelea kufanya kazi.
06 · Bei ya uwazi

$0.05 per match. 500 free every month. No SKU.

$0.05 kwa kila Face Match call inayojitegemea. Ikiunganishwa ndani ya full KYC workflow na ID Verification, Liveness, na Device & IP Analysis, session inagharimu $0.33, Face Match imejumuishwa. Verifications 500 za kwanza kwa mwezi ni bure kwenye kila akaunti, milele. Hakuna kiwango cha chini cha kila mwezi, hakuna ada ya jukwaa, hakuna SKU ya kujadiliana.
Unganisha

Endpoints mbili. JSON sawa. Bei sawa.

Unda kipindi unapotaka UI yetu iliyopangishwa kunasa selfie na kuvuta picha ya kumbukumbu kutoka kwa kitambulisho cha kipindi hicho hicho. Piga endpoint ya pekee unapo tayari una picha zote mbili, chanzo na lengo, na tutarudisha ripoti ya face_match.
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_face_match_kyc",
    "vendor_data": "user-42"
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Tunakaribisha upigaji picha. Picha ya kitambulisho inakuwa target_image kiotomatiki.nyaraka →
POST /v3/face-match/Server kwa server
$ curl -X POST https://verification.didit.me/v3/face-match/ \
  -H "x-api-key: $DIDIT_API_KEY" \
  -F "source_image=@selfie.jpg" \
  -F "target_image=@portrait.jpg"
200Sawa{ "status": "Imeidhinishwa", "score": 87 }
Unapitisha jozi. Tunarudisha alama papo hapo.nyaraka →
Ujumuishaji tayari kwa agent

Tuma Face Match kwa prompt moja.

Bandika block iliyo hapa chini kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza placeholder ya my_stack na framework yako, lugha, na matumizi. Agent inasanidi Didit, inajenga workflow na Face Match imewezeshwa, inaunganisha webhook, na inatuma.
didit-integration-prompt.md
# Didit Face Match 1:1 — integrate in 5 minutes

You are integrating Didit's Face Match 1:1 (selfie vs. reference image)
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 selfie capture, real-time framing,
mobile handoff, and accessibility for you. Inside a Know Your Customer (KYC) workflow,
Face Match runs automatically against the portrait extracted from the
ID document the user uploads in the same session.

1. Create a workflow that contains the FACE_MATCH feature:
   POST https://verification.didit.me/v3/workflows/
   Authorization header:  x-api-key: <your-api-key>
   Body: workflow_label, features array with FACE_MATCH plus any
         other features the same session needs (typically
         ID_VERIFICATION and LIVENESS for full KYC). Feature names
         are UPPERCASE — strict enum.
   Optional config: review_threshold and decline_threshold for the
         LOW_FACE_MATCH_SIMILARITY warning (numbers 0–100).

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 two face images and just need a similarity
score (re-auth at sensitive actions, employee badge access, cross-app
identity binding, periodic re-verification).

POST https://verification.didit.me/v3/face-match/
Content-Type: multipart/form-data
Body fields:
  - source_image  (required, file — the live selfie)
  - target_image  (required, file — the reference image, e.g. ID portrait
                   or a stored enrollment frame)
  - vendor_data   (optional string, your user id)

Response: synchronous JSON report with the similarity score and warnings
array. No webhook needed.

## 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 face_match object includes:
- status: "Approved" | "Declined" | "In Review" | "Not Finished"
- score: number 0-100 (normalized similarity score)
- source_image_session_id: the verification session that produced the
  live selfie (Path A) or null (Path B)
- source_image: signed URL to the live selfie (expires in 1 hour)
- target_image: signed URL to the reference image (expires in 1 hour)
- warnings: Array<{ risk, log_type, short_description, long_description }>

Auto-decline risks (always enforced by Didit, not configurable):
- NO_REFERENCE_IMAGE   (no reference image available to compare against)

Configurable risks (action per workflow — Decline, Review, or Approve):
- LOW_FACE_MATCH_SIMILARITY
    Tune two thresholds per application:
      review_threshold  → score below this goes to "In Review"
      decline_threshold → score below this is auto-declined

## 5. Hard rules — do not change
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: FACE_MATCH, ID_VERIFICATION, LIVENESS, 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",
  "Not Finished" (title-cased, space-separated).
- Reference and source image URLs in the response expire in 60 minutes.
  Persist only the score and status; re-fetch images on demand if your
  audit policy needs them.

## 6. Pricing reference (public)
- Standalone POST /v3/face-match/: $0.05 per match.
- Bundled inside a full KYC workflow with ID Verification + Passive
  Liveness + Device & IP Analysis: $0.33 per session (Face Match included).
- 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 a mismatched pair).
- Switch to live: flip the application's environment toggle in console.

When in doubt: https://docs.didit.me/core-technology/face-match/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
  • 0 – 100
    Alama ya kufanana inarudishwa kwa kila mechi.
  • <0s
    End-to-end inference kwa kila face match.
  • $0.00
    Kwa kila simu ya Face Match inayojitegemea.
  • 0
    Uthibitishaji wa bure kila mwezi, milele, 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
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 Face Match 1:1 accept?
Two face images. Path A, Workflow Builder: the source image is the live selfie our hosted UI captures, the target image is the portrait we extracted from the ID (identification) document the user uploaded in the same session, both sides come for free. Path B, Standalone API: you pass both images yourself as source_image and target_image on a multipart POST /v3/face-match/. Accepted formats: JPG, JPEG, PNG, up to 5 MB per image. Both paths return the same face_match JSON shape.
What is the response shape?
A root-level face_match object with status (Approved, Declined, In Review, or Not Finished), a 0-100 score, a source_image_session_id that ties the result back to the verification session that produced the live selfie, signed source_image and target_image URLs that expire after 60 minutes, and a warnings array. Each warning has risk, log_type (information, warning, or error), short_description, and long_description. Same shape whether you called the Workflow Builder or the standalone API.
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 face-match fraud?
Face Match never runs alone in a KYC flow, it pairs with LIVENESS so the source image is always a verified-live human, not a presentation attack. Liveness is iBeta Level 1 Presentation Attack Detection (PAD) certified against printed photos, screen replays, masks, morph attacks, and AI deepfakes. On top of that, the face embedding model is trained to be resilient to pose, lighting, hairstyle, glasses, and ageing within a normal window, so a real face still matches even when the document portrait is years old.
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