無料
無料
月額$0。クレジットカード不要。
- 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
- ブロックリストユーザー
- 重複検出
- すべてのセッションで200以上の不正シグナル
- Diditネットワーク全体でのKYC再利用
- ケース管理プラットフォーム
- ワークフロービルダー
- 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
- コミュニティサポート
世界中の2,000以上の組織から信頼されています。
ギグプラットフォームが果たすべき責任
ワーカーを認証し、ライセンスを確認。再申請者を見つけ出す。
アカウント停止されたドライバーや利用禁止された配達員が、毎日新しい名前で再登録しています。Diditは、本人確認とAMLを1セッションで提供し、ワーカー1人あたり$0.53（国ごとのライセンス登録を追加する場合は別途$0.20）で利用可能です。Face Search 1:Nは、新しい書類、新しい名前、新しいメールアドレスであっても、同一人物の顔を200ミリ秒以内に検知します。毎月500件の認証が無料です。
仕組み
登録から認証済みユーザーまで、わずか4ステップ。
- ステップ 01
ワークフローを作成
本人確認、生体認証、顔照合、制裁リスト、住所、年齢、電話番号、メールアドレス、カスタム質問など、必要なチェック項目を選択します。ダッシュボードでフローにドラッグ＆ドロップするか、同じフローをAPIにPOSTします。条件分岐やA/Bテストも、コード不要で実行できます。
- ステップ 02
連携
Web、iOS、Android、React Native、Flutter SDKでネイティブに組み込むか、ホストされたページにリダイレクトします。または、メール、SMS、WhatsAppなど、どこからでもユーザーにリンクを送信するだけです。お使いのスタックに合った方法を選択してください。
- ステップ 03
ユーザーがフローを完了
Diditは、カメラ、照明の指示、モバイル連携、アクセシビリティをホストします。ユーザーがフローを実行している間、200以上の不正信号をリアルタイムでスコアリングし、すべてのフィールドを信頼できるデータソースと照合して検証します。結果は2秒以内に得られます。
- ステップ 04
結果を受け取る
リアルタイムの署名付きWebhookにより、ユーザーが承認、拒否、またはレビューに送られた瞬間にデータベースを同期します。必要に応じてAPIをポーリングすることも可能です。または、コンソールを開いてすべてのセッション、すべての信号を検査し、ケースを管理できます。
01 · ワーカーバンドル
本人確認、生体認証、顔照合、AML, 1回のAPIコールで。
ワーカー1人あたり$0.33でフルKYC、AMLは$0.20。iBeta Level 1 Presentation Attack Detection (PAD) 認定、2秒未満の判定、200以上の不正信号をすべてのセッションで追加費用なしでスコアリングします。
ユーザー認証モジュールDidit · Gig signup
Onboard a worker in one call.
Step 3 / 5
Hold still for liveness
- ID Verification$0.15
- Passive Liveness$0.10
- Face Match 1:1$0.05
- Device & IP$0.03
- AML Screening$0.20
02 · ライセンス登録（オプション）
ドライバーのオンボーディング時に登録情報のクロスチェックを追加。
ライドシェアやデリバリーの場合、データベース検証を有効にすると、運転免許証を発行国の運輸当局（スペインのDGT、英国のDVLA、米国の州DMV、ブラジルのDENATRANなど）と照合できます。20カ国以上で利用可能、1回あたり$0.20で、使用した場合のみ課金されます。
データベース検証モジュールDidit · Database Validation
Licence number, against the registry.
CountryRegistryStatusAction
- ESDirección General de Tráfico (DGT)ActivePass
- UKDriver and Vehicle Licensing Agency (DVLA)ActivePass
- USState DMV (per state)SuspendedBlock
- BRDENATRANExpiredReview
20+ countries live · more every quarter
03 · 継続的なAML
毎日、ワーカーを再スクリーニング。
継続的なAMLモニタリングは、承認されたすべてのワーカーを毎日、1,300以上の制裁リスト、政治的要人（PEP）リスト、ネガティブメディアリストと照合して再スクリーニングします。新たなヒットがあった場合は自動的にケースが作成されます。ワーカー1人あたり年間$0.07で、最初のセッションに含まれており、追加の連携は不要です。
AMLスクリーニングモジュールDidit · Ongoing AML
Daily re-screen, every worker.
UpdateSourceVerdict
- Worker · cleanAll 1,300+ listsPass
- New adverse media · fraud articleEU adverseReview
- New PEP · municipal officialDow Jones PEPReview
- OFAC sanction · added todayOFAC SDNBlock
Webhook fires on every flip14 languages
04 · 再申請ブロック
Face Search 1:N, 同一人物、別名義でもブロック。
新規オンボーディングでは、すべてのセルフィーがプライベートワーカーインデックスとクロスチェックされます。利用禁止されたドライバーが新しい書類、新しいメールアドレス、新しいIPで再申請した場合、200ミリ秒以内にフラグが立てられます。拒否、レビュー、承認はアプリごとに設定可能です。すべてのワークフローに無料で含まれています。
Face Search 1:NモジュールDidit · Face Search 1:N
Same face. Different name. Caught.
New applicant
Maria L.Banned · 2025-08-040.94Block
M. A. LopezSame face · new name0.92Block
Lopez, M.Same face · new doc0.91Block
<200ms per index lookup
05 · あらゆるギグの類型に対応
あらゆるカテゴリーで同じワークフロー。
ライドシェア、デリバリー、クリエイターマーケットプレイス、ホームケア、オンデマンドプロフェッショナルなど、すべて同じDiditのレシピで実行できます。ノーコードのワークフロービルダーで、ギグのカテゴリに基づいてワークフローを分岐させることが可能です。
モビリティ業界向けワークフローDidit · Coverage
Same workflow. Every gig.
- Ride-shareDriver licence · DMV registry
- DeliveryBackground AML + identity
- Freelance / creatorTax form + AML
- Home careBackground + biometric re-auth
One contract, every archetype
連携
1セッション。1Webhook。ワーカーを有効化。
登録時にセッションを開始。署名付きの判定結果を読み込み、ワーカーを有効化するか、運用チームにルーティングします。
POST /v3/session/ギグ
$ 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"
}'201作成済み{ "session_url": "verify.didit.me/..." }
ウェブフックが
status: Approvedを返すまで、最初のジョブへのアクセスを保留します。ドキュメント →POST /webhooks/didit判定
// X-Signature-V2 verified upstream
if (payload.status === "Approved") {
activateWorker(payload.vendor_data);
indexFace(payload.face);
} else if (payload.status === "Declined") {
blockReapplication(payload.aml.hits);
}200OKステータス 承認済み · 却下 · 審査中 · KYC期限切れ
ペイロードを読み取る前に
X-Signature-V2を検証してください。ドキュメント →エージェント対応統合
ギグワーカー認証をプロンプト一つで実装。
Claude Code、Cursor、Codex、Devin、Aider、Replit Agentに貼り付けてください。スタック情報を入力すると、エージェントがワークフローを構築し、サインアップリンクを送信し、判定を読み取り、顔情報をインデックス化し、継続的なモニタリングを登録します。
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.さらに詳しい情報が必要ですか？モジュールの全ドキュメントをご覧ください。docs.didit.me →
設計段階からのコンプライアンス
ワンクリックで新しい国に進出。 面倒な作業は私たちにお任せください。
私たちは現地法人を設立し、ライセンスを取得し、ペネトレーションテストを実施し、認証を取得し、新しい規制すべてに準拠します。新しい国で認証を提供するには、トグルを切り替えるだけです。220以上の国で稼働しており、四半期ごとに監査とペネトレーションテストを実施しています。EU加盟国の政府が対面認証よりも安全だと正式に認めた唯一のIDプロバイダーです。
セキュリティ＆コンプライアンス資料を読むEU金融サンドボックス
Tesoro · SEPBLAC · BdE
ISO/IEC 27001
情報セキュリティ · 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準拠
実績データ
実績データ
- $0.00ワーカー1人あたり, KYC + AML。ライセンス登録は利用時に$0.20追加。
- 0+運転免許証登録に対応している国々。四半期ごとにさらに多くの国に対応予定。
- <0ms顔検索1回あたり: プライベートワーカーインデックスに対する1:Nルックアップ。
- 0毎月、すべてのアカウントで無料認証をご利用いただけます。
3つのティア、1つの料金表
無料で開始。従量課金。エンタープライズまで対応。
毎月500回まで無料認証を永続的に提供。本番環境では従量課金。エンタープライズプランではカスタム契約、データレジデンシー、SLA（サービスレベルアグリーメント）に対応します。
最も人気
従量課金
従量課金
使った分だけお支払い。25以上のモジュール。モジュールごとの公開価格、月額最低料金なし。
- フルKYC（本人確認 + 生体認証 + IP / デバイス）が$0.33
- 10,000以上のAMLデータセット, 制裁、PEP、ネガティブ情報
- データベース検証のための1,000以上の政府データソース
- トランザクションモニタリングが1トランザクションあたり$0.02
- ライブKYBが1企業あたり$2.00
- ウォレットスクリーニングが1チェックあたり$0.15
- ホワイトラベル検証フロー, あなたのブランド、私たちのインフラ
エンタープライズ
エンタープライズ
カスタムMSA & SLA。大量利用や規制対象プログラム向け。
- 年間契約
- カスタムMSA、DPA、SLA
- 専用SlackおよびWhatsAppチャンネル
- オンデマンドの手動レビュー担当者
- リセラーおよびホワイトラベル条件
- 限定機能とパートナー連携
- 専任CSM、セキュリティレビュー、コンプライアンスサポート
無料で開始 → チェック実行時のみ支払い → カスタム契約、SLA、データレジデンシーが必要な場合はエンタープライズプランへ。
FAQ
よくある質問
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_datain 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.