KYC, AML, KYB, authentification biométrique renforcée par glisser-déposer. Branche sur signal. Fais des tests A/B. Versionne en toute sécurité. Paye uniquement pour les modules complétés, le Workflow Builder est gratuit.
Robinhood Ventures
Approuvé par plus de 2 000 organisations dans le monde entier.
Ce que les chefs de produit doivent
Fais glisser des modules sur un canevas, connecte-les, ajoute des embranchements, publie une version, et donne le `workflow_id` à ton app. Quand les règles changent, le chef de produit modifie le brouillon et publie, pas de ticket d'ingénierie, pas de redéploiement. L'intégration reste à un `POST /v3/session/` près.
Choisis les vérifications que tu veux, ID, liveness, correspondance faciale, sanctions, adresse, âge, téléphone, email, questions personnalisées. Fais-les glisser dans un flux sur le tableau de bord, ou poste le même flux à notre API. Crée des embranchements conditionnels, lance des tests A/B, aucun code requis.
Intègre nativement avec nos SDK Web, iOS, Android, React Native ou Flutter. Redirige vers une page hébergée. Ou envoie simplement un lien à ton utilisateur, par email, SMS, WhatsApp, n'importe où. Choisis ce qui convient à ta stack.
Didit héberge la caméra, les indications lumineuses, le transfert mobile et l'accessibilité. Pendant que l'utilisateur est dans le flux, nous évaluons plus de 200 signaux de fraude en temps réel et vérifions chaque champ par rapport à des sources de données fiables. Résultat en moins de deux secondes.
Des webhooks signés en temps réel maintiennent ta base de données synchronisée dès qu'un utilisateur est approuvé, refusé ou envoyé en révision. Interroge l'API à la demande. Ou ouvre la console pour inspecter chaque session, chaque signal, et gérer les cas à ta manière.
Didit · Canvas
Didit · Branching
Didit · Templates
Didit · A/B
Didit · Versioning
Current
Draft
Didit · /v3/ + MCP
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"workflow_id": "wf_signup_v12",
"vendor_data": "user-42",
"callback": "https://app/cb"
}'$ curl -X POST https://verification.didit.me/v3/workflows/ \
-H "x-api-key: $DIDIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"workflow_label": "KYC Inscription",
"features": [
{ "feature": "OCR" },
{ "feature": "LIVENESS" },
{ "feature": "FACE_MATCH" },
{ "feature": "AML" }
]
}'You are integrating Didit's no-code Workflow Builder into a product. The product manager, the compliance officer, or the founder can change identity rules in the Business Console; your app only ever hands Didit a workflow_id, gets a verdict back, and routes the user.
Three pillars:
1. Compose the workflow in the visual builder — drag ID, Liveness, Face Match, AML, NFC, KYB modules onto the canvas, connect them with edges, add conditional branches.
2. Publish a version — the published version is immutable; sessions reference the exact version they were created with.
3. Open POST /v3/session/ with the published workflow_id. Didit handles every module and every branch server-side.
Cost:
- Pay per completed module per session (e.g. ID $0.15 + Liveness $0.10 + Face Match $0.05 + AML $0.20 = $0.50, or bundle = $0.33)
- Workflow Builder itself is free
- MCP server (for AI coding agents to manage workflows programmatically) is 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 HMAC SHA-256 verification using the X-Signature-V2 header and your webhook secret.
- Access to the Business Console's Workflow Builder (every account has it).
- The 11 seeded templates are a good starting point:
"ID + Face Match"
"ID + Liveness + Face Match" (the $0.33 KYC bundle)
"ID + IP risk-based" (extra Liveness on VPN / Tor)
"Phone risk-based verification"
"High-risk country review"
"Two ID documents"
"Driver verification"
"EU Company Verification" (KYB)
... plus four more
- Plus "Start from Scratch" for fully bespoke flows.
STEP 1 — Compose the workflow
Console → Workflows → New → pick a template OR Start from Scratch:
- Drag modules from the sidebar onto the canvas
- Connect them with edges (the user moves left-to-right through them)
- Add branching conditions (right-click a node → Add condition)
- Set per-workflow options: Include custom style (white label), retention override, callback URL
Click Save Draft. The draft is fully editable; only published versions are immutable.
STEP 2 — Publish a version
Click Publish on the draft. The version receives a number (v1, v2, v3…) and becomes immutable.
Versioning rules:
- Sessions reference the exact published version they were created with
- You can iterate on a new draft while sessions on the old version continue to use it
- Past versions are kept; you can inspect any past session's configuration
- To change a published workflow, create a new draft from it, edit, publish
STEP 3 — Open a session with the workflow_id
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your published workflow id>",
"vendor_data": "<your user id, max 256 chars>",
"callback": "https://<your-app>/identity/callback"
}
Response: 201 Created with the hosted session URL. Didit walks the user through every module and every branch defined in the workflow.
STEP 4 — Read the signed webhook on completion
Didit POSTs to your callback when the session reaches a terminal status. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"workflow_id": "<the workflow id>",
"workflow_version": "<v3>",
"vendor_data": "<your user id>",
"status": "Approved",
"id_verification": { "status": "Approved" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"aml": { "status": "Approved", "hits": [] }
}
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 bytes with your webhook secret.
Each module that ran inside the workflow returns its own sub-status; the top-level status is the rolled-up verdict.
STEP 5 — Iterate without redeploying
When the rules need to change — a new country flagged as high-risk, a tighter age threshold, a new module added to the bundle — the workflow owner edits the draft in the Console and publishes. New sessions automatically use the new version.
Your app doesn't change. You don't redeploy. The workflow_id is the same; the underlying behaviour is updated.
STEP 6 — Run A/B tests
Built-in A/B testing splits traffic across variant workflows. Configure variants in the Console (e.g. variant A uses Passive Liveness, variant B uses Active Liveness), set the split percentage, and read the variant id back on every session webhook.
Measure conversion + verdict mix per variant in the Business Console's analytics. Promote the winner; the loser becomes a previous version retained for audit.
STEP 7 — Drive the Workflow Builder from AI coding agents
The Didit MCP (Model Context Protocol) server (free, included) exposes the Workflow management primitives as MCP tools. Any MCP-compatible host — Claude Code, Cursor, Codex, Replit Agent, Devin, Aider — can list workflows, create new drafts, edit nodes, and publish versions on your behalf.
Useful for ops teams that want to script tenant-specific workflow provisioning, A/B-variant generation, or per-customer-brand template materialisation.
WEBHOOK EVENT NAMES
- Sessions: status changes flow through the standard session webhook.
- Verify X-Signature-V2 on every payload.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review). Don't transform them.
- Published workflow versions are immutable. To change behaviour, publish a new version.
- Conditional branches are unlimited in depth; keep flows readable for the next operator.
- The cost model is pay-per-completed-module — adding a module that runs only conditionally only costs you on the branches that hit it.
Read the docs:
- https://docs.didit.me/console/workflows
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/retrieve-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.0 $ / mois. Aucune carte de crédit requise.
Payez uniquement ce que vous utilisez. Plus de 25 modules. Tarification publique par module, sans minimum mensuel.
MSA et SLA personnalisés. Pour les gros volumes et les programmes réglementés.
Commence gratuitement → ne paie que lorsqu'une vérification est effectuée → débloque l'Enterprise pour un contrat personnalisé, un SLA ou la résidence des données.
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:
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.
It's a way to design what your KYC / AML / KYB flow checks, in what order, and under which conditions, all in a visual drag-and-drop canvas instead of code.
In practice:
POST /v3/session/, doneWhen the rules need to change, the product manager edits the draft and publishes. The app doesn't redeploy.
You could. Most teams that try learn three lessons:
The Workflow Builder collapses all three into one drag-drop canvas. The rules become product configuration; the code becomes one POST /v3/session/ call.
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.
Every Didit primitive ships as a node:
$0.15), NFC Reading ($0.15), Proof of Address ($0.20), Database Validation (variable), Custom Questionnaires ($0.10)$0.10), Active Liveness ($0.15), Face Match 1:1 ($0.05), Face Search 1:N (free), Age Estimation ($0.10), Biometric Authentication ($0.10)$0.20, 1,300+ lists), Ongoing AML ($0.07/user/yr), Device & IP Analysis ($0.03)$0.03), Phone Verification (from $0.03)Plus branching nodes (if/else, switch) and terminal nodes (Approve, Decline, Review).
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.
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.
Didit ships compliant by default for the regulators that matter to identity infrastructure:
Detailed memo, every certificate, every regulator letter: /security-compliance.
Three integration paths, pick whichever fits your stack:
Same dashboard, same billing, same pay-per-success price for all three. Step-by-step guide at docs.didit.me/integration/integration-prompt.
Two states per workflow:
To change a published workflow, you create a new draft from it, edit, publish. The new published version becomes v3 (or whatever); v2 stays in place forever as the historical record. Past sessions are fully reproducible, the session payload includes the exact workflow_version it ran on.
This matches what a regulator wants for audit: "show me the exact configuration of the workflow this user ran on, on this date". Every Didit account gets it for free, no setup.
Everything ships under the same /v3/ contract.
workflow_id and walk the user through the same orchestration server-side. Free.workflow_id, same orchestration.The net: one workflow_id flows from the Console → into your app → into the SDK or hosted UI → server-side orchestration → signed webhook. Zero glue code beyond the single POST /v3/session/.
Three wires, one afternoon:
business.didit.me, sandbox key in 60 seconds, no credit cardPOST /v3/session/ with the published workflow_id and wire the signed webhook (X-Signature-V2, HMAC SHA-256) into your decision logicThat's the entire integration. When rules change, the workflow owner edits the draft in the Console and publishes, your app doesn't change.
For scripted workflow management, the Didit MCP server is free and lets any MCP-compatible agent host (Claude Code, Cursor, etc.) drive the Workflow Builder programmatically.
Une seule API pour le KYC, le KYB, la surveillance des transactions et le screening de portefeuilles. Intégration en 5 minutes.