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

Sajili mfanyakazi. Zuia wanaojaribu kujisajili tena walaghai.

Dereva, msafirishaji, mfanyakazi huru, mbunifu, kipindi kimoja cha Didit: kitambulisho, uhai, kulinganisha uso, AML. $0.53 kwa kila mfanyakazi. Ongeza rejista ya leseni kwa nchi unapoihitaji (+$0.20).

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.

Mchoro wa sinema, giza, dhahania wa uthibitishaji wa mfanyakazi wa gig, paneli nne za glasi zinazong'aa zikielea katika mtazamo wa 3D kwenye nyeusi safi, zikipitishwa na mstari mweupe wa Didit Blue na zikizungukwa na mabano manne ya skana yanayong'aa. Kila paneli ina motifu ndogo, nyeupe-nyepesi, dhahania (muhtasari wa leseni ya udereva, silhouette ya kofia ya kujifungua, alama za njia, mviringo wa uso).

Majukwaa ya gig yanapaswa kufanya nini

Thibitisha mfanyakazi. Angalia leseni. Mkamate anayeomba tena.

Madereva waliofutwa na wasafirishaji waliofungiwa wanajiandikisha tena kila siku kwa jina jipya. Didit inatoa uthibitisho wa utambulisho + AML katika kipindi kimoja kwa $0.53 kwa mfanyakazi (ongeza usajili wa leseni kwa kila nchi kwa $0.20 ya ziada), na Face Search 1:N inakamata sura ileile, kwenye hati mpya, jina jipya, barua pepe mpya, chini ya 200ms. Uthibitishaji 500 bure 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, vikwazo, anwani, umri, simu, barua pepe, maswali maalum. Ziburute kwenye mtiririko katika dashibodi, au tuma mtiririko huo huo kwenye API yetu. Panga masharti, endesha majaribio ya A/B, hakuna code inayohitajika.

  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 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. Wakati mtumiaji yuko kwenye mtiririko, tunapata alama za ishara 200+ za udanganyifu 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 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 kipindi, kila ishara, na kudhibiti kesi kwa njia yako.

Imejengwa kwa majukwaa ya gig · Bei kama miundombinu

Ukaguzi mitano. Simu moja. $0.53 kwa mfanyakazi.

Usajili wa gig unahitaji mambo machache kwa pamoja, thibitisha kuwa mtu ni halisi, angalia hawako kwenye orodha ya vikwazo, na hakikisha mfanyakazi aliyepigwa marufuku hapo awali hajajisajili tena kwa jina jipya. Didit inatoa yote hayo kwa simu moja, na inakuwezesha kuongeza ukaguzi wa usajili wa leseni unapoajiri madereva.
Soma nyarakaPata API key
01 · Kifurushi cha mfanyakazi

Utambulisho, liveness, face match, AML, simu moja.

KYC kamili kwa $0.33 kwa mfanyakazi pamoja na AML ($0.20). iBeta Level 1 Presentation Attack Detection (PAD) iliyothibitishwa, uamuzi chini ya sekunde mbili, ishara 200+ za udanganyifu zilizopimwa kwenye kila kipindi bila gharama ya ziada.
Moduli ya Uthibitishaji wa Mtumiaji
02 · Usajili wa leseni (si lazima)

Ongeza ukaguzi wa usajili unapoajiri madereva.

Kwa ride-share na delivery, washa Database Validation kuangalia leseni dhidi ya mamlaka ya usafiri ya nchi inayotoa, DGT nchini Hispania, DVLA nchini Uingereza, state DMV nchini Marekani, DENATRAN nchini Brazil. Nchi 20+ ziko hewani, $0.20 kwa simu, inatozwa tu inapotumika.
Moduli ya Uthibitishaji wa Database
03 · AML inayoendelea

Chunguza tena wafanyakazi kila siku.

Ufuatiliaji endelevu wa AML unachunguza tena kila mfanyakazi aliyethibitishwa dhidi ya vikwazo 1,300+, Watu Walio Wazi Kisiasa (PEP), na orodha za habari mbaya kila siku. Matukio mapya hufungua kesi kiotomatiki. $0.07 kwa mfanyakazi kwa mwaka, imejumuishwa katika kipindi cha awali, hakuna muunganisho wa ziada.
Moduli ya Uchunguzi wa AML
04 · Kuzuia maombi ya kurudia

Face Search 1:N, sura ileile, jina jipya, imezuiwa.

Kila usajili mpya unalinganisha selfie dhidi ya index yako ya kibinafsi ya wafanyakazi. Dereva aliyepigwa marufuku anayeomba tena na hati mpya + barua pepe mpya + IP mpya anatambuliwa chini ya 200ms. Kataa, Kagua, au Idhinisha inaweza kusanidiwa kwa kila programu. Bure, imejumuishwa katika kila mtiririko wa kazi.
Moduli ya Face Search 1:N
05 · Kila aina ya gig

Mchakato mmoja, kwa kila aina.

Ride-share, delivery, masoko ya waumbaji, huduma za nyumbani, wataalamu wa mahitaji, yote yanafuata mfumo uleule wa Didit. Panga mtiririko wa kazi kulingana na kategoria ya gig katika Workflow Builder isiyo na code.
Mifumo ya kazi ya sekta ya uhamaji
Unganisha

Kipindi kimoja. Webhook moja. Mwezeshe mfanyakazi.

Fungua kipindi wakati wa kujisajili. Soma uamuzi uliosainiwa. Washa au elekeza kwa shughuli.
POST /v3/session/Gig
$ 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_gig_rideshare",
    "vendor_data": "driver-9241"
  }'
201Imeundwa{ "session_url": "verify.didit.me/..." }
Zuia ufikiaji wa kazi ya kwanza hadi webhook iseme status: Approved.nyaraka →
POST /webhooks/diditUamuzi
// X-Signature-V2 verified upstream
if (payload.status === "Imeidhinishwa") {
  activateWorker(payload.vendor_data);
  indexFace(payload.face);
} vinginevyo ikiwa (payload.status === "Imekataliwa") {
  blockReapplication(payload.aml.hits);
}
200OKhali Imeidhinishwa · Imekataliwa · Inapitiwa · KYC Imeisha Muda
Thibitisha X-Signature-V2 kabla ya kusoma payload.nyaraka →
Ujumuishaji tayari kwa agent

Anzisha uthibitishaji wa wafanyakazi wa gig kwa amri moja.

Bandika kwenye Claude Code, Cursor, Codex, Devin, Aider, au Replit Agent. Jaza stack yako. Agent inajenga workflow, inatuma kiungo cha kujisajili, inasoma uamuzi, inaweka index ya uso, na inasajili ufuatiliaji unaoendelea.
didit-integration-prompt.md
You are integrating Didit into a gig marketplace to onboard drivers, couriers, freelancers, or creators. ONE Didit session, five checks:

  Verify the worker's identity (KYC) — ID document, liveness, face match, device + IP, AML against 1,300+ sanctions / Politically Exposed Person (PEP) / adverse-media lists — plus Face Search 1:N against your private worker index to block previously-banned workers re-applying under a new name. Add an OPTIONAL licence-registry cross-check when you onboard drivers.

Bundle pricing (verified live, 2026-05-17):
  - Full KYC bundle: $0.33 per worker (ID + Liveness + Face Match + Device & IP)
  - AML Screening: $0.20 per worker
  - Face Search 1:N against your private worker index: Free
  - Baseline total: $0.53 per worker — public price, no minimums
  - Optional Database Validation (licence registry): $0.20 per call, only billed when used
  - First 500 verifications free every month, forever
  - Ongoing AML on active workforce: $0.07 per worker per year (automatic)

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 + Device & IP + AML Screening. For drivers, ALSO add Database Validation and branch on country_of_work.

STEP 1 — Open the worker session at signup

  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 + AML (and Database Validation if driver)>",
      "vendor_data": "<your worker id, max 256 chars>",
      "callback_url": "https://<your-app>/gig/onboarding/callback",
      "metadata": {
        "gig_category": "rideshare",
        "country_of_work": "ES",
        "license_number": "<worker's licence number, OCR'd or self-entered>"
      }
    }

  Response: 201 Created with a hosted session URL on the `url` field. Redirect the worker (web or in-app webview). Sub-2-second median verdict on completion.

STEP 2 — Read the signed webhook when the worker finishes

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

  Body (excerpted, with optional Database Validation included for a driver):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your worker id>",
      "status": "Approved",
      "id_verification": { "status": "Approved", "document_type": "Driver License" },
      "liveness": { "status": "Approved" },
      "face": { "status": "Approved", "similarity_score": 0.94 },
      "ip_analysis": { "status": "Approved" },
      "aml": { "status": "Approved", "hits": [] },
      "database_validation": { "status": "Approved", "registry": "DGT" }
    }

  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 body bytes with your webhook secret. Re-serialising the parsed JSON breaks the signature.

STEP 3 — Branch on the verdict

  Approved          → activate the worker; let them pick up jobs.
  In Review         → route to ops queue; hold first job until disposition.
  Declined          → block; log the hit detail for compliance.
  Resubmitted       → applicant retried after a soft rejection — re-read.
  Kyc Expired       → session went stale; send a new session URL.

STEP 4 — Re-application defence (Face Search 1:N)

  Every onboarded worker is indexed in your app's private Face Search 1:N index. A banned worker re-applying under a different name + a different document + a different IP is caught in under 200ms on the same /v3/ call (Face Search runs as a workflow step). Set the action on duplicate match to Block, Review, or Approve per app.

STEP 5 — Ongoing AML on the active workforce is automatic

  Every Approved worker is re-screened DAILY by Didit's continuous AML monitoring at $0.07 per worker per year. NO separate endpoint to call — the original session is what gets monitored.

  When a previously-clean worker crosses an AML threshold (new sanction listing, new adverse-media hit, PEP status change), the session status changes to "In Review" or "Declined" automatically and your webhook fires the update. Disable the worker, route to ops.

STEP 6 — Optional licence registry for drivers

  For ride-share and delivery onboardings only, enable Database Validation in the workflow and branch on country_of_work:
    ES → DGT
    UK → DVLA
    US → state DMV (per state)
    BR → DENATRAN

  The check costs $0.20 and is only billed when the workflow step runs. If the country isn't supported yet, the step is skipped — no spurious decline.

WEBHOOK EVENT NAMES
  - Sessions: status changes flow through the standard session webhook.
  - Ongoing AML updates: same session webhook fires when the verdict flips post-onboarding.

  Verify X-Signature-V2 on every payload.

CONSTRAINTS
  - Session statuses use Title Case With Spaces (Approved, In Review). Do not lowercase or snake_case them.
  - Database Validation is country-specific — 20+ countries live for driver licences. If the country isn't live, the check is skipped (no spurious decline).
  - 200+ fraud signals are evaluated on every KYC session at no extra cost.
  - The session URL is single-use; if a worker abandons mid-flow, create a new session for the retry.

Read the docs:
  - https://docs.didit.me/sessions-api/create-session
  - https://docs.didit.me/core-technology/aml-screening/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

Thibitisha namba

Thibitisha namba
  • $0.00
    Kwa kila mfanyakazi, KYC + AML. Usajili wa leseni huongeza $0.20 inapotumika.
  • 0+
    Nchi zinazotumia usajili wa leseni za udereva; zaidi zinakuja kila robo mwaka.
  • <0ms
    Kwa kila Utafutaji wa Uso 1:N dhidi ya index yako ya kibinafsi ya wafanyakazi.
  • 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.

What does gig-worker verification actually cover?

Four obligations every gig platform owes on every new worker:

  • Identity, confirm the person who signed up is the one picking up jobs.
  • Right-to-work / professional licence, a driver's licence for ride-share, a delivery permit, a freelance-body registration for creators.
  • Background screening, at minimum anti-money-laundering (AML) against sanctions and Politically Exposed Persons (PEP) lists; in some markets a criminal-records check on top.
  • Re-application defence, make sure a banned worker can't re-sign-up under a new name + a new document + a new email.

Didit bundles all four into one /v3/session/ call.

Why is fraud so high on gig platforms?

Two structural reasons:

  • The signup is the entire relationship. A worker is verified once at onboarding and immediately starts taking jobs. There's no manager interview, no credit-check waiting period, no probation. Bad actors only need to defeat the signup flow.
  • Account-resale and identity-loaning markets are mature. Deactivated drivers sell their account to a new operator; couriers loan accounts to people who can't pass KYC. Both look like a legitimate active worker, until a passenger complaint triangulates a different face.

Face Search 1:N against your private worker index closes both holes.

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 catch a re-applying banned worker?

Every approved worker's enrolment selfie is indexed into your app's private one-to-many (1:N) face index, keyed on your vendor_data, isolated per Didit application, fully encrypted at rest. New onboardings cross-check the selfie against the index in under 200ms.

A banned driver re-applying with:

  • A new email address.
  • A new mobile number.
  • A new IP and device.
  • A different document (passport instead of driver's licence).
  • A slightly altered name (Maria L. → M. A. Lopez).

…still presents the same face. Face Search returns the original vendor_data of the banned record and the verdict flips to Block. Free, included in every workflow.

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 identity documents are accepted for international drivers?

Whatever the worker's country of employment requires:

  • Local driver's licence plus the issuing country's registry cross-check.
  • Passport for general identity verification.
  • National identity card (Documento Nacional de Identidad, Cédula, etc.) where the country supports it.
  • Residence permit + work-permit stamp for international workers.

Didit's classifier supports 14,000+ documents across 220+ countries. The Workflow Builder branches on country-of-work so a UK driver gets the DVLA check and a Spanish driver gets the DGT check, same flow, different registry.

What about device + IP fraud signals?

Device & IP Analysis runs in the same /v3/session/ call at $0.03 per check. 200+ fraud signals surface on every session at no extra cost:

  • Velocity fingerprints, same device used by 5 different vendor_data in 7 days.
  • IP reputation, residential vs data-center vs Tor exit node.
  • Device emulator detection, Bluestacks, NoxPlayer, Frida tooling.
  • Geolocation mismatch, passport country vs IP country vs device locale.

The verdict flips to In Review when the signal stack crosses a threshold you configure in the Workflow Builder.

Can I integrate Didit with my existing onboarding flow / mobile app?

Three integration patterns:

  • Hosted UI, Didit hosts the capture flow, you redirect the worker via the session_url. Zero front-end work, most common path.
  • Mobile Software Development Kit (SDK), embed the Didit capture experience natively in your React Native, Flutter, iOS, or Android app. Brand-customisable.
  • Server-to-server, POST the worker's document images to /v3/id-verification/ directly when you already own the capture experience.

All three speak the same workflow, return the same per-feature report shape, and hit the same webhook. Mix-and-match per gig category.

Related

Moduli zinazohusiana + mtiririko wa kazi

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