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

Kamata udanganyifu wa madai kwa ishara tano za udanganyifu. Mtiririko mmoja wa kazi wakati wa taarifa ya kwanza ya hasara.

Thibitisha mdai ni mwenye sera, zuia ushahidi wa video wa deepfake, gundua nyaraka bandia, chunguza dhidi ya orodha za vikwazo, tafuta vikundi vya majeraha vilivyopangwa, katika kikao kimoja cha /v3/. $0.53 kwa kila dai, 500 bure kila 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.

Mkusanyiko wa madai ya ulaghai usioeleweka, paneli nne zinazoelea, zisizo na uwazi za kioo cheusi katika mtazamo wa 3D kwenye rangi nyeusi kabisa, zikipitishwa na mstari wima wa Didit Blue unaong'aa na kuwekewa fremu na mabano ya skana yanayong'aa. Kila paneli ina motifu moja ndogo nyeupe isiyo dhahiri (fomu ya madai, uwekaji wa uso wa deepfake, picha iliyohaririwa na kikuza, chati ya pau inayopanda na alama ya hatari kubwa iliyotengwa).

Kinacholipwa kisichostahili

Wadai hewa. Ripoti zilizopangwa. Ushahidi wa video wa Deepfake.

Muungano Dhidi ya Ulaghai wa Bima unakadiria kuwa wabebaji wa Marekani hupoteza karibu $308 bilioni kwa mwaka. Mengi ya haya hutokana na madai yasiyo na uhakiki wa utambulisho wa mdai na hakuna uchunguzi wa ushahidi. Didit huziba mapengo yote mawili katika mfumo mmoja wa kazi, $0.53 kwa kila dai, 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, face match, sanctions, address, age, phone, email, maswali maalum. Ziburute kwenye mtiririko katika 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 Web, iOS, Android, React Native, au Flutter SDK yetu. Elekeza upya 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 huandaa kamera, ishara za mwanga, uhamishaji wa simu, na ufikiaji. Wakati mtumiaji yuko kwenye mtiririko, tunapima ishara 200+ za ulaghai kwa wakati halisi na kuthibitisha kila sehemu dhidi ya vyanzo vya data vya kuaminika. Matokeo chini ya sekunde mbili.

  4. Hatua 04

    Unapokea matokeo

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

Imejengwa kwa madai · Bei kama miundombinu

Ishara tano za ulaghai. Mtiririko mmoja wa kazi. $0.53 kwa kila dai.

Ulaghai wa madai ni mchanganyiko, utambulisho wa mdai, uchunguzi wa nyaraka, ulinzi wa deepfake, uchunguzi wa vikwazo, utafutaji wa madai mtambuka. Washa kila moduli kwa kila aina ya biashara katika Workflow Builder.
Soma nyarakaPata API key
01 · Aina za madai

Mifumo ambayo timu ya udanganyifu huona kila siku.

Madai ya upotevu wa magari ambapo uharibifu ulitokea kabla ya sera. Madai ya mzimu ambapo mdai si mmiliki wa sera. Ushahidi wa video ya Deepfake. Ripoti za polisi za template zilizotumiwa tena na sehemu zilizohaririwa. Ankara za Biashara Zilizovurugika (BI) zilizopandishwa bei. Vikundi vilivyopangwa vya majeraha vinavyowasilisha upotevu sawa kwa wabebaji tofauti. Mtiririko wa kazi wa Workflow Builder huonyesha kila aina.
Moduli ya Workflow Orchestrator
02 · KYC ya Mdai

Mdai ndiye mwenye bima.

Simu moja ya /v3/session/ hunasa Uthibitishaji wa Kitambulisho ($0.15), Passive Liveness ($0.10), na Face Match 1:1 dhidi ya picha ya mmiliki wa sera kwenye faili ($0.05). Kifurushi kinauzwa kwa $0.33. iBeta Level 1 PAD imethibitishwa, uamuzi chini ya sekunde mbili kwenye Android ya kiwango cha chini. Hunasa kila jaribio la madai ya mzimu ambapo mdai si mmiliki wa sera.
Moduli ya User Verification
03 · Uchunguzi wa nyaraka

Kuharibu. Template. Metadata. Zote zimekaguliwa.

Utambuzi wa Tabia za Macho (OCR) hutoa kila sehemu kutoka kwa ushahidi unaounga mkono, ripoti za polisi, nukuu za ukarabati, ankara za matibabu, picha za upotevu. Utambuzi wa uharibifu wa kiwango cha pikseli huashiria maeneo yaliyohaririwa, ulinganishaji wa template hunasa mifupa ya PDF iliyotumiwa tena, ukaguzi wa metadata ya EXIF hunasa tarehe zisizolingana na tukio la upotevu. Alama ya juu ya uharibifu = badilisha kuwa In Review kiotomatiki.
Moduli ya ID Verification
04 · Ulinzi wa Deepfake

Deepfakes hazipiti Passive Liveness.

iBeta Level 1 Presentation Attack Detection (PAD) imethibitishwa dhidi ya orodha kamili ya ISO/IEC 30107-3. Huziba deepfakes zinazozalishwa na AI za mmiliki wa sera, barakoa za silikoni au mpira, marudio ya skrini ya selfie ya awali, na picha zilizochapishwa. Mfumo hujaribiwa tena katika iBeta kila mwaka kadri njia mpya za mashambulizi zinavyoonekana.
Moduli ya Liveness
05 · Vikwazo + utafutaji wa madai mtambuka

Vikwazo vimegonga + kugundua mtandao uliopangwa.

AML Screening ($0.20 kwa kila ukaguzi) huangalia kila mdai dhidi ya vikwazo 1,300+, Watu Walio Wazi Kisiasa (PEP), na orodha za habari mbaya katika lugha 14, zikiboreshwa kila siku. Face Search 1:N (bure kwa kila utafutaji) hulinganisha selfie ya mdai dhidi ya ghala lako la wadai wa awali, vikundi vilivyopangwa vya majeraha huonekana kama makundi ya mechi zenye kufanana sana katika kwingineko.
Moduli ya AML Screening
06 · Uamuzi wa Webhook + kifurushi cha ukaguzi

Uamuzi uliotiwa saini. Ishara za kila moduli. Kifurushi cha ukaguzi.

Webhook iliyotiwa saini inafika na Approved, In Review, au Declined pamoja na ishara za kila moduli, kufanana kwa uso, orodha ya AML, orodha ya mechi ya utafutaji wa uso. Thibitisha X-Signature-V2 na Hash-based Message Authentication Code (HMAC) SHA-256. Payload ya uamuzi ni kifurushi cha ukaguzi, vuta toleo kamili wakati wowote kupitia GET /v3/session/[id]/decision/.
Marejeleo ya Webhook
Unganisha

Session moja. Uamuzi mmoja uliotiwa saini. Ishara tano za ulaghai.

Fungua session ya dai dhidi ya mtiririko wa kazi wa kifurushi. Soma uamuzi uliotiwa saini. Ishara za kila moduli + orodha ya mechi ziko pale pale kwenye payload.
POST /v3/session/Dai
$ 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_claim_verify",
    "vendor_data": "claim-8821",
    "metadata": { "policy_id": "POL-44120" }
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Zuia malipo hadi webhook itue status: Approved.nyaraka →
POST /webhooks/diditUamuzi
// X-Signature-V2 verified upstream
if (payload.status === "Imeidhinishwa") {
  releasePayout(payload.vendor_data);
} else if (payload.status === "In Review") {
  routeToSiu(payload.face_search.matches);
}
200OKhali Imeidhinishwa · Imekataliwa · Inapitiwa · Haijakamilika
Thibitisha X-Signature-V2 kabla ya kusoma payload.nyaraka →
Ujumuishaji tayari kwa agent

Tuma ulinzi wa udanganyifu wa madai kwa haraka.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent huunganisha workflow, hufungua session, husoma ishara za kila moduli, na kuelekeza madai ya "In Review" kwa Kitengo chako cha Uchunguzi Maalum.
didit-integration-prompt.md
You are integrating Didit into an insurance carrier's claim workflow at first notice of loss (motor, health, property, travel, business interruption). Goal: catch ghost claims, deepfake video evidence, forged supporting documents, sanctions hits on the claimant, and organised-injury rings before the payout enters the queue. One API call. One signed webhook. Five fraud signals.

WHY THIS SHAPE
  - The Coalition Against Insurance Fraud estimates fraud costs the US industry around $308 billion / year (2022 figures). Most of that walks in through claims with no identity check on the claimant and no document forensics on the evidence.
  - Five signals settle the question on most claims: (1) the claimant is the policyholder, (2) the claimant is alive and present (not a deepfake), (3) the supporting documents are not tampered or templated, (4) the claimant is not on a sanctions list, (5) the claimant has not already filed N near-identical claims across your portfolio.
  - One Didit /v3/session/ call bundles all five. $0.33 KYC + $0.20 AML = $0.53 per claim. Face Search 1:N is free per search. 500 verifications free every month.

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60 seconds, no credit card).
  - A webhook endpoint with HMAC SHA-256 verification of the X-Signature-V2 header using your webhook secret.
  - A Workflow Builder workflow bundling ID Verification + Passive Liveness + Face Match 1:1 (with the policyholder portrait as comparison target) + AML Screening + Face Search 1:N (gallery scoped to prior claimants on your account).
  - Reference to the policy ID and policyholder portrait on file from your Policy Administration System (PAS) — passed as metadata on the session.

STEP 1 — Open the claim-verification session
  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<wf id bundling ID + Liveness + Face Match + AML + Face Search 1:N>",
      "vendor_data": "<your claim id, max 256 chars>",
      "callback": "https://<your-app>/claims/verify/callback",
      "metadata": {
        "policy_id": "<your policy id>",
        "line_of_business": "motor",
        "loss_date": "2026-04-12"
      }
    }

  Response: 201 Created with a hosted session URL. Send it to the claimant by email / Short Message Service (SMS) / inside the claims app. The claim stays in HOLD on your side until the signed webhook lands.

STEP 2 — Read the signed webhook
  Didit POSTs the verdict. Verify X-Signature-V2 (HMAC SHA-256 of the raw body) BEFORE reading the JSON.

  Payload (excerpted):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your claim id>",
      "status": "In Review",
      "id_verification": { "status": "Approved" },
      "liveness": { "status": "Approved" },
      "face":     { "status": "Approved", "similarity_score": 0.92 },
      "aml":      { "status": "In Review", "hits": [{ "list": "PEP" }] },
      "face_search": {
        "matches": [
          { "session_id": "claim-7710", "similarity": 0.94, "vendor_data": "claim-7710" }
        ]
      }
    }

  Session status enum (exact case, Title Case With Spaces): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.

STEP 3 — Branch on the verdict
  Approved      → release the claim into the standard payout queue.
  In Review     → route to the Special Investigations Unit (SIU) with the per-module signals + face-search match list as the case file.
  Declined      → decline + open file. Block the payout. The decision payload is the audit pack.
  Not Finished  → resend the session link.

STEP 4 — Document forensics on supporting evidence (separate sub-flow)
  For each supporting PDF / image uploaded (police report, repair quote, medical invoice, photo of loss), run Didit Document Optical Character Recognition (OCR). The OCR response surfaces:
    - Field-level extracted text (claim amount, names, dates)
    - Tamper score per region (pixel-level edits)
    - Template match against prior submissions (reused PDF skeleton)
    - EXIF / metadata mismatch (date in photo vs date of loss)

  A high tamper score or a template match against a prior claim flips the case status to In Review.

STEP 5 — Pull the full decision for the case file
  GET https://verification.didit.me/v3/session/{session_id}/decision/
  Headers:
    x-api-key: <your api key>

  Returns the full decision payload — per-module signals, raw face-similarity scores, AML hit list with source list per match, face-search candidate list with scores. Use this as the audit pack for any dispute.

WEBHOOK EVENT NAMES
  - Sessions: standard session webhook. One endpoint, status field tells you the lifecycle.
  - Verify X-Signature-V2 (HMAC SHA-256) on every payload.

CONSTRAINTS
  - Session statuses use Title Case With Spaces. Never UPPER_SNAKE_CASE — that's the Transactions API.
  - The Face Match comparison target is the policyholder portrait from your Policy Administration System (PAS). A deepfake of the policyholder cannot pass when Passive Liveness is also in the workflow.
  - Face Search 1:N gallery is scoped to YOUR account — Didit does not search across carriers. To collaborate across an industry pool, use a shared workflow_id pointing at a multi-carrier gallery you own.
  - 200+ fraud signals are surfaced on every session at no extra cost — read them off the decision payload, don't re-query.
  - Default retention is the standard 5-year insurance horizon; adjust per workflow if your jurisdiction differs.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/core-technology/face-match/overview
  - https://docs.didit.me/core-technology/aml-screening/overview
  - https://docs.didit.me/core-technology/face-search/overview
  - https://docs.didit.me/integration/webhooks

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 dai lililochunguzwa kikamilifu, kifurushi cha KYC cha $0.33 + AML ya $0.20. Utafutaji wa Sura ni bure kwa kila utafutaji.
  • 0+
    Vikwazo, Watu Walio Wazi Kisiasa (PEP), na orodha za habari hasi, zinazosasishwa kila siku.
  • iBeta L1
    Passive Liveness dhidi ya deepfakes, barakoa, na marudio. Inajaribiwa upya kila mwaka.
  • 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
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.

How big is insurance claim fraud?

The Coalition Against Insurance Fraud estimated US insurers lose around \$308.6 billion a year to fraud across all lines (2022 study). The European insurance body Insurance Europe reports similar share-of-premium loss across the EU.

Most of it is opportunistic, small inflated amounts on otherwise legitimate claims. A smaller share is professional rings filing the same loss across carriers. Both shapes share one weakness: nobody checks who the claimant is at first notice of loss.

What is a ghost claim?

A ghost claim is when the person filing the claim is not the policyholder. Typical pattern: an attacker buys leaked customer data from a breach, calls the carrier impersonating the policyholder, files a small loss claim, and asks for the payout to a new bank account.

The attack succeeds when there is no biometric check tying the caller to the person on the policy. Face Match 1:1 against the policyholder portrait closes this gap in two seconds.

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.

What does document forensics actually check?

On every supporting document the claimant uploads, police report, repair quote, medical invoice, photo of the loss, Didit runs:

  • Field-level Optical Character Recognition (OCR), extracts amounts, names, dates, reference numbers
  • Pixel-level tamper detection, flags edited regions (covered scratches, swapped totals)
  • Template matching, catches reused PDF skeletons across prior claims
  • EXIF / metadata check, flags photos whose timestamp doesn't match the loss date

A high tamper score or a template match flips the claim from Approved to In Review automatically.

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 does the recipe cost?

Per claim:

  • User Verification bundle (ID + Liveness + Face Match): \$0.33
  • AML Screening: \$0.20
  • Face Search 1:N against prior claimants: \$0.00 (free per search)
  • Document OCR on each supporting file: included in the User Verification price

Around \$0.53 per fully-screened claim. The first 500 verifications every month are free on every account, pilot the workflow inside the free tier.

No minimums, no annual commitment, no per-seat pricing.

How does it integrate with my Special Investigations Unit?

The signed webhook is the routing signal. On status: In Review, your back-end routes the case to the Special Investigations Unit (SIU) with the per-module signals + face-search match list as the opening case file.

Pull the full decision payload via GET /v3/session/[id]/decision/ for the analyst, face similarity scores, AML hit list with source list per match, face-search candidate list with scores, document forensics output. The decision payload is the audit trail for any dispute.

What about General Data Protection Regulation (GDPR) and Anti-Money-Laundering (AML) retention?

Biometric vectors are special-category data under the EU's General Data Protection Regulation (GDPR). The lawful basis is the standard claims-investigation legitimate interest plus the consent flow at session start.

Default retention is the standard 5-year insurance horizon, adjust per workflow if your jurisdiction or supervisor differs. The gallery for Face Search 1:N is scoped to your account by design, no cross-carrier search unless you join a consortium and run a shared workflow_id.

Related

Moduli zinazohusiana + workflows

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