Skip to main content
Didit Raises $7.5M to Build the Infrastructure for Identity and Fraud
Didit
Proof of Human

Prove a real human. Not a deepfake. Not an LLM.

Block AI agents, generated faces, deepfakes, and duplicate accounts from human-only surfaces. iBeta Level 1 PAD-certified passive liveness plus free 1:N dedupe. $0.10 per check, 500 free every month.

Backed by
Y CombinatorRobinhood Ventures
GBTC Finance
Bondex
Crnogorski Telekom
UCSF Neuroscape
Shiply
Adelantos

Trusted by 2,000+ organizations worldwide.

Dark cinematic Proof of Human stack, four floating translucent glass panels in 3D perspective on pure black, threaded by a luminous Didit Blue line and framed by glowing scanner brackets. Each panel carries a small pale-white motif representing a single human silhouette, a network of nodes, a heartbeat waveform, and a unique face-match oval pair.

Block agents · Stop deepfakes · Dedupe Sybil

Prove the user is human. Prove they only signed up once.

Passive Liveness rejects every Presentation Attack Detection (PAD) category, print, screen, mask, AI-generated face. Face Search 1:N then catches the same person attempting to register twice. Sub-2-second verdict. $0.10 per check. 500 verifications free every month, forever.

How it works

From sign-up to verified user in four steps.

  1. Step 01

    Create the workflow

    Pick the checks you want, ID, liveness, face match, sanctions, address, age, phone, email, custom questions. Drag them into a flow in the dashboard, or post the same flow to our API. Branch on conditions, run A/B tests, no code required.

  2. Step 02

    Integrate

    Embed natively with our Web, iOS, Android, React Native, or Flutter SDK. Redirect to a hosted page. Or just send your user a link, by email, SMS, WhatsApp, anywhere. Pick what fits your stack.

  3. Step 03

    User goes through the flow

    Didit hosts the camera, the lighting cues, the mobile hand-off, and accessibility. While the user is in the flow, we score 200+ fraud signals in real time and verify every field against authoritative data sources. Result in under two seconds.

  4. Step 04

    You receive the results

    Real-time signed webhooks keep your database in sync the moment a user is approved, declined, or sent to review. Poll the API on demand. Or open the console to inspect every session, every signal, and manage cases your way.

Block every agent · Issue a credential a human can carry

Six capabilities. One signed Proof of Human.

One workflow, one verdict, one credential. Toggle each module per surface. No upsell tiers, no add-on SKUs, no separate APIs.
01 · iBeta Level 1 PAD

Block every spoof category on the same selfie.

Independently certified at iBeta Presentation Attack Detection (PAD) Level 1, the bar the United States National Institute of Standards and Technology (NIST) cites. Blocks every ISO/IEC 30107-3 category: printed photos, screen replays, paper, silicone and latex masks, morph attacks, AI-generated deepfakes. Re-tested annually.
Liveness module
02 · Generated-face detection

Tell a real face from a generated one.

Edge inference under two seconds on entry-level Android. The same model that defeats printed photos rejects Generative Adversarial Network (GAN) faces, diffusion-model portraits, and real-time deepfake video. No model download, no degraded experience on cheap hardware.
Liveness methods
03 · Face Search 1:N, free

Same face surfaces. Same human caught.

Every approved Proof of Human adds a face template to your private account index. The next attempt by the same person surfaces at the top with a match score. Tune the auto-decline threshold per workflow; route borderline matches to review. Free on every plan.
Face Search 1:N module
04 · Reusable Credential

One proof. Every surface. Free.

Bind a Reusable Credential to every approved user. The next Didit-powered surface that needs the same gate consumes the credential at zero cost. The human holds the proof; you verify the signature. Network effect compounds across every customer that ships Reusable Credentials.
Reusable KYC module
05 · Where it ships

Anywhere a human is the unit of trust.

Social signup, online voting, contests, surveys, marketplace seller registration, gig-worker onboarding, dating-app trust badges, exchange sign-up, online gambling. Anywhere AI agents or duplicates erode the value of being human, Proof of Human is the gate.
See use cases
06 · Three methods, one price

Passive $0.10. Active 3D $0.15. Face Search free.

Passive (one frame, zero user action) for low-friction signup. Active 3D Flash captures depth from a short flash sequence. Active 3D Action + Flash adds a motion challenge for the highest-sensitivity surfaces. Face Search 1:N is free and always-on. 500 verifications free every month, forever.
See pricing
Integrate

Two endpoints. Same JSON. Same price.

Use the hosted session when Didit handles capture (required for Active 3D), or call the standalone passive-liveness and face-search endpoints when you already have the selfie.
POST /v3/session/Hosted
$ 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_proof_of_human",
    "vendor_data": "user-42"
  }'
201Created{ "session_url": "verify.didit.me/..." }
Hosted UI runs LIVENESS + FACE_MATCH in one capture.docs →
GET /v3/session/{sessionId}/decision/Verdict
$ curl https://verification.didit.me/v3/session/<id>/decision/ \
  -H "x-api-key: $DIDIT_API_KEY"

# Sample verdict
{
  "status": "Approved",
  "liveness": { "score": 96 }
}
200OKstatus Approved · In Review · Declined · Not Finished
Verify X-Signature-V2 on the signed webhook first.docs →
Agent-ready integration

Ship Proof of Human in one prompt.

Paste into Claude Code, Cursor, Codex, Devin, Aider, or Replit Agent. Fill in your stack. The agent provisions Didit, builds the workflow, wires the webhook, and ships the gate in five minutes.
didit-integration-prompt.md
You are integrating Didit's Proof of Human gate into <my_stack>. Block AI agents, deepfakes, masks, and duplicate accounts from human-only surfaces — signup, voting, contests, marketplaces, dating. Two endpoints, one verdict.

  1. Prove a real human is present (Liveness). ONE call to the Sessions API runs a Presentation Attack Detection (PAD)-certified passive selfie and returns a verdict in sub-2-seconds.
  2. Prove the human is unique (Face Search 1:N). Same Sessions API workflow runs Face Search 1:N against your account's private face index.

Pricing (public):
  - Passive Liveness: $0.10 per check
  - Active 3D Liveness: $0.15 per check (motion challenge — use for high-sensitivity flows)
  - Face Search 1:N: free, included
  - First 500 verifications free every month, forever

PRE-REQUISITES
  - Production API key from https://business.didit.me (sandbox key in 60s, no card).
  - Webhook endpoint with Hash-based Message Authentication Code (HMAC) SHA-256 verification using the X-Signature-V2 header.
  - A workflow_id from the Workflow Builder that contains the LIVENESS feature, and (recommended) FACE_MATCH and IP_ANALYSIS so Sybil dedupe + agent / bot signals come in on the same verdict.

STEP 1 — Build the Proof of Human workflow once

  POST https://verification.didit.me/v3/workflows/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_label": "proof_of_human",
      "features": [
        { "feature": "LIVENESS", "config": { "method": "PASSIVE" } },
        { "feature": "FACE_MATCH" },
        { "feature": "IP_ANALYSIS" }
      ],
      "face_liveness_score_decline_threshold": 30
    }

  Notes:
    - LIVENESS, FACE_MATCH, IP_ANALYSIS are exact, case-sensitive feature names.
    - method enum: PASSIVE (one frame) · FLASHING (3D flash) · ACTIVE_3D (action + flash). Use ACTIVE_3D for the highest-sensitivity surfaces (large-value account creation, voting, contest finals).

STEP 2 — Open a Proof of Human session per user

  POST https://verification.didit.me/v3/session/
  Headers:
    x-api-key: <your api key>
    Content-Type: application/json
  Body:
    {
      "workflow_id": "<the workflow_id from step 1>",
      "vendor_data": "<your internal user id>",
      "callback": "https://<your-app>/proof-of-human/callback",
      "metadata": {
        "surface": "<signup | vote | contest | marketplace | dating>"
      }
    }

  Response: 201 Created with the hosted session_url. Redirect the user. The hosted UI opens the front camera, captures one passive frame (or a short motion challenge for ACTIVE_3D), runs Liveness + Face Search 1:N, returns the verdict in sub-2-seconds.

STEP 3 — Read the signed verdict on the webhook

  Body (excerpted for a clean human):
    {
      "session_id": "<uuid>",
      "vendor_data": "<your user id>",
      "status": "Approved",
      "liveness": {
        "status": "Approved",
        "method": "PASSIVE",
        "score": 96,
        "warnings": []
      },
      "face": {
        "status": "Approved",
        "similarity_score": null,
        "matches": []
      },
      "ip_analysis": { "status": "Approved" }
    }

  Body (excerpted for a duplicate):
    {
      "status": "In Review",
      "liveness": { "status": "Approved", "score": 94 },
      "face": {
        "status": "In Review",
        "matches": [
          { "vendor_data": "user_8124", "similarity_score": 0.97 }
        ],
        "warnings": [{ "code": "POSSIBLE_DUPLICATED_FACE" }]
      }
    }

  Verify X-Signature-V2 BEFORE trusting the body — HMAC SHA-256 of the raw bytes with your webhook secret.

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

  Liveness warning catalog:
    - LIVENESS_FACE_ATTACK     PAD attack suspected (print / replay / mask / GAN)
    - LOW_LIVENESS_SCORE       score below threshold
    - NO_FACE_DETECTED         no face in the capture
    - AGE_NOT_DETECTED         capture quality too low for age signal
    - POSSIBLE_DUPLICATED_FACE same face previously verified on your account

STEP 4 — Branch your surface on the final verdict

  Approved      → grant access to the human-only surface.
  Declined      → block; log the rejected agent / spoof attempt.
  In Review     → hold; show a review-pending banner, route to ops queue.
  Not Finished  → user abandoned; safe to re-prompt.

STEP 5 — Alternate path (server-to-server, when you have the selfie)

  POST https://verification.didit.me/v3/passive-liveness/
  Headers:
    x-api-key: <your api key>
  Body (multipart/form-data):
    image    <single front-camera selfie>

  Then dedupe:

  POST https://verification.didit.me/v3/face-search/
  Body (multipart/form-data):
    image          <same selfie>
    vendor_data    <your user id>

  Use the standalone path for native onboarding apps that capture the selfie locally. Active 3D liveness REQUIRES the hosted session — it needs the motion challenge to run.

CONSTRAINTS
  - Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
  - Feature enum is UPPERCASE: LIVENESS, FACE_MATCH, IP_ANALYSIS, ID_VERIFICATION, AML, AGE_ESTIMATION.
  - 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).
  - Status casing matches exactly: Approved, Declined, In Review, Expired, Not Finished, Resubmitted, Kyc Expired, Abandoned.
  - 200+ fraud signals are evaluated on every session at no extra cost.

PRO TIP
  - Bind a Reusable Credential to each approved user. The next Didit-powered surface that needs the same gate consumes the credential at zero cost — the Proof of Human "compounds" across the network.

Read the docs:
  - https://docs.didit.me/core-technology/liveness/overview
  - https://docs.didit.me/core-technology/face-search/overview
  - https://docs.didit.me/sessions-api/create-session
  - 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.
Need more context? See the full module docs.docs.didit.me →
Compliant by design

Open a new country in one click. We do the hard work.

We open the local subsidiaries, secure the licenses, run the penetration tests, earn the certifications, and align with every new regulation. To ship verifications in a new country, flip a toggle. 220+ countries live, audited and pen-tested every quarter, the only identity provider an EU member-state government has formally called safer than in-person verification.
Read the security & compliance dossier
EU financial sandbox
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
Information security · 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 by design

Proof numbers

Proof numbers
  • iBeta L1
    Independently certified Presentation Attack Detection on every passive selfie.
  • <0%
    Real users rejected at the certified test point.
  • <0s
    End-to-end liveness and face-search inference on entry-level Android.
  • $0.00
    Per passive liveness check. Face Search 1:N is free.
Three tiers, one price list

Start free. Pay per usage. Scale to Enterprise.

500 free verifications every month, forever. Pay-as-you-go for production. Custom contracts, data residency, and SLAs (Service Level Agreements) on Enterprise.
Free

Free

$0 / month. No credit card required.

  • Free KYC bundle (ID Verification + Passive Liveness + Face Match + Device & IP Analysis), 500 / month, every month
  • Blocklisted Users
  • Duplicate Detection
  • 200+ fraud signals on every session
  • Reusable KYC across the Didit network
  • Case Management Platform
  • Workflow Builder
  • Public docs, sandbox, SDKs, MCP (Model Context Protocol) server
  • Community support
Most popular
Pay per usage

Usage Based

Pay only for what you use. 25+ modules. Public per-module pricing, no monthly minimum fee.

  • Full KYC at $0.33 (ID + Biometric + IP / Device)
  • 10,000+ AML datasets, sanctions, PEPs, adverse media
  • 1,000+ government data sources for Database Validation
  • Transaction Monitoring at $0.02 per transaction
  • Live KYB at $2.00 per business
  • Wallet Screening at $0.15 per check
  • Whitelabel verification flow, your brand, our infrastructure
Enterprise

Enterprise

Custom MSA & SLA. For large volumes and regulated programs.

  • Annual contracts
  • Custom MSA, DPA, and SLA
  • Dedicated Slack and WhatsApp channel
  • Manual reviewers on demand
  • Reseller and white-label terms
  • Exclusive features and partner integrations
  • Named CSM, security review, compliance support

Start free → pay only when a check runs → unlock Enterprise for a custom contract, SLA, or data residency.

FAQ

Common questions

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 "proof of human" mean in practice?

A short challenge that proves three things at once:

  • A real person is on the other side, captured in real time, not a stored photo, replay, or video file.
  • The person is not a printout, screen, silicone mask, or AI-generated face.
  • The person is unique, they haven't already passed the same gate on your platform.

The first two are called liveness and Presentation Attack Detection (PAD). The third is 1:N face deduplication. Together they're what most platforms now mean when they say "proof of human".

Why does this matter in 2026?

Two reasons.

  • Generative AI shipped. A teenager with a free image model can mint a photorealistic face in seconds. Headless agents can spin up thousands of accounts overnight. Old defences (a CAPTCHA, a phone number, an email) don't bind to a real person anymore.
  • Platforms are accountable for what humans on them say. The EU Digital Services Act, the UK Online Safety Act, and several state-level rules treat platforms as responsible for harms caused by inauthentic behaviour. "We didn't know" stopped being a defence in 2024.
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 liveness detect a deepfake or generated face?

The model is trained on real captures vs. every known spoof class, print, screen replay, mask, morph, Generative Adversarial Network (GAN) portrait, diffusion render. Real captures carry tiny artefacts no spoof has: micro-motion of the head, sub-pixel skin texture, reflections that match the device's flash spectrum, depth cues from a single passive frame.

The iBeta Level 1 PAD certification, the bar the US National Institute of Standards and Technology cites, measures exactly this performance, and Didit holds it across every passive-liveness session.

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's the integration story?

Two paths.

  • Hosted workflow, POST /v3/session/ with the workflow_id you built in the Business Console. We host the capture UI, run Liveness + Face Search 1:N, return a signed verdict to your webhook. Five-minute integration.
  • Server-to-server, call POST /v3/passive-liveness/ with the selfie you already captured locally, then POST /v3/face-search/ for Sybil dedupe.

Full cURL example, response shape, and the agent-pastable prompt are above. The Model Context Protocol (MCP) server speaks both surfaces to Claude, Cursor, and any other agent.

How do you handle the user's biometric data?

Data minimisation by default. The selfie is processed in memory; the verdict, liveness score, and an irreversible face template are persisted; the raw image is deleted unless retention is explicitly enabled. The face template is a one-way hash, you cannot reconstruct the underlying face from it.

We never sell, share, or train third-party models on a customer's biometric data. The full data-processing terms live at didit.me/terms/business; the privacy notice the end user sees is at didit.me/terms/verification-privacy-notice.

What if a user fails the check?

The session returns one of four outcomes:

  • Approved, clean human. Issue the Reusable Credential and grant access.
  • Declined, clear spoof signal (print, screen, mask, generated face). Block.
  • In Review, high-similarity match in Face Search 1:N or a low liveness score. Hold the surface, route to your ops queue. The Business Console gives the analyst the selfie, the match, and the score.
  • Not Finished, user abandoned the capture. Safe to re-prompt.

A signed webhook lands at every state change, so you only render against the latest verdict.

Infrastructure for identity and fraud.

One API for KYC, KYB, Transaction Monitoring, and Wallet Screening. Integrate in 5 minutes.

Ask an AI to summarise this page