無料
無料
月額$0。クレジットカード不要。
- 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
- ブロックリストユーザー
- 重複検出
- すべてのセッションで200以上の不正シグナル
- Diditネットワーク全体でのKYC再利用
- ケース管理プラットフォーム
- ワークフロービルダー
- 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
- コミュニティサポート
世界中の2,000以上の組織から信頼されています。
ガバナンスが果たすべきこと
ウォレットは人ではありません。人が人なのです。
一人の人間が、ウォレット、メールアドレス、使い捨て携帯を 何百も作成できます。しかし、それだけでは、その人が百人の別人であることの証明にはなりません。Diditは、投票を実際の顔と実際の書類に紐付け、Face Search 1:N（無料）で同一人物の再試行を検出します。毎月500件の認証が無料です。
仕組み
サインアップから認証済みユーザーまで、4つのステップで完了。
- ステップ 01
ワークフローを作成
ID、生体認証、顔照合、制裁リスト、住所、年齢、電話番号、メールアドレス、カスタム質問など、必要なチェック項目を選択します。ダッシュボードでフローにドラッグ＆ドロップするか、同じフローをAPIにポストします。条件分岐やA/Bテストも、コード不要で実行できます。
- ステップ 02
連携
Web、iOS、Android、React Native、Flutter SDKでネイティブに組み込むことができます。ホストされたページにリダイレクトすることも、メール、SMS、WhatsAppなど、どこからでもユーザーにリンクを送ることも可能です。お使いのスタックに合った方法をお選びください。
- ステップ 03
ユーザーがフローを完了
Diditは、カメラ、照明の指示、モバイル連携、アクセシビリティをホストします。ユーザーがフローを実行している間、200以上の不正シグナルをリアルタイムでスコアリングし、すべてのフィールドを信頼できるデータソースと照合して検証します。結果は2秒以内に得られます。
- ステップ 04
結果を受け取る
リアルタイムの署名付きWebhookにより、ユーザーが承認、拒否、またはレビューに送られた瞬間にデータベースが同期されます。必要に応じてAPIをポーリングすることも可能です。または、コンソールを開いてすべてのセッション、すべてのシグナルを検査し、ケースを自由に管理できます。
01 · ユニークな投票者
一人の実在する人間。一つの認証済みID。
iBetaレベル1アンチスプーフィング認定KYCバンドル, ID検証、パッシブ生体認証、顔照合1:1、AMLスクリーニング。2秒未満で判定、220以上の国と地域で14,000以上の書類に対応。
ユーザー認証モジュールDidit · Unique voter
One person. One vote. Proven.
Voter · step 3 / 4
Face check vs cohort
- ID Verification$0.15
- Passive Liveness$0.10
- Face Match 1:1$0.05
- Face Search 1:N · cohortFree
- Vote eligibility · rulesFree
02 · 重複検出
コホート内での顔検索1:N。
すべての登録は、以前に登録されたすべての投票者と照合されます。類似性しきい値を超えた場合、投票が記録される前にブロックされます。無料、お客様のデータセットのみにスコープされます。
Face Search 1:NDidit · Face Search 1:N
Catch duplicates before the ballot.
Voter candidateCohort matchScoreAction
- voter-12871voter-911297Block
- voter-12872voter-744084Review
- voter-12873voter-632862Review
- voter-12874no match9Pass
Free per cohort · scoped to your dataset1:N
03 · プライバシー保護
ユニーク性を証明。それ以外の情報は開示しません。
投票プラットフォームは`unique: true`、仮名PID（Pseudonymous Identifier）、年齢層、地域のみを認識します。書類と生体認証データはDidit内に残り、保存時に暗号化されます。GDPR準拠、ISO/IEC 27001、SOC 2 Type 1。
本人確認プライバシー通知Didit · Privacy contract
Prove uniqueness. Reveal nothing else.
Platform sees
uniquetrue
voter_pidvh_8f3a…21bc
age_band18+
regionEU
Didit holds (encrypted)
document.image[encrypted]
face.template[encrypted]
full_name[encrypted]
retentionpolicy-driven
GDPR-aligned · ISO/IEC 27001 · SOC 2 Type 1.
04 · 再利用可能な認証情報
一度認証すれば、どこでも投票可能。
再利用可能なKYC（無料、付属）により、認証済み投票者は、セルフィーのみでその後のすべての投票でユニーク性を証明できます。書類の再取得は不要です。すべてのDidit対応プラットフォームで機能します。eIDAS2準拠。
再利用可能なKYCDidit · Reusable KYC
Verify once. Vote everywhere.
- First vote · full KYC$0.33 bundle once
- Next vote · selfie onlyFree · Reusable KYC
- Cross-platformSame identity, every Didit platform
- Soulbound, optionalPair with on-chain attestations
eIDAS2-aligned. The user owns the credential.
05 · 管轄区域ルール
すべての投票者に対して地域ごとの適格性を確認。
国別ホワイトリスト、最低年齢、制裁/PEP除外、書類の有効期限、類似性しきい値, これらすべてが1つのワークフローで適用されます。コード不要のワークフロービルダーでルールを編集でき、再デプロイは不要です。
AMLスクリーニングモジュールDidit · Voter eligibility
Per-region eligibility rules.
RuleTestAction
- Country of issue · whitelistES · FR · DE · ITPass
- Minimum age≥ 18Pass
- Sanctions / PEP hit1,300+ listsBlock
- Document expiryValid on vote dayReview
- Face Search 1:N · cohort≥ 0.85 similarityBlock
Edit eligibility in the no-code Workflow Builder.
06 · 監査パック
暗号化された投票整合性証明。
署名付き登録レシート（X-Signature-V2、HMAC SHA-256）、仮名投票者PID、改ざん防止ログ（デフォルトで5年間保持）。透明性ポータルやDAOのスナップショットにエクスポートできます。
WebhookドキュメントDidit · Vote integrity
Cryptographic audit · per vote.
- Signed enrolmentX-Signature-V2 · HMAC SHA-256
- Pseudonymous voter PIDNo raw PII in the tally
- Tamper-evident logs5-year retention default
- Public-portal exportPipe to your transparency site
One pack. Every voter. Every round.
連携
1セッション。1コホート。1つの署名済み判定。
投票者を登録。署名済みWebhookを読み込み。重複をブロック。投票を記録。
POST /v3/session/登録
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"workflow_id": "wf_voter_enrol",
"vendor_data": "voter-12871",
"metadata": { "cohort_id": "round-2026-05" }
}'201作成済みホストされたセッションURLを返します。完了後2秒以内に判定。
Webhookが
status: Approvedを返すまで投票をブロックします。ドキュメント →GET /v3/session/{sessionId}/decision/判定
$ curl https://verification.didit.me/v3/session/$SID/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Returns:
{
"status": "Approved",
"face_search": { "matches": [] }
}200OKステータス 承認済み · 却下 · レビュー中 · 再提出 · 期限切れ
0.85を超える空でない一致 → 重複、ブロック。ドキュメント →
エージェント対応統合
プロンプト一つでアンチシビル投票を実装。
Claude Code、Cursor、Codex、Devin、Aider、またはReplit Agentに貼り付けてください。スタック情報を入力すると、エージェントが登録ワークフローを構築し、重複をブロックし、判定に署名し、次のラウンドの準備を行います。
didit-integration-prompt.md
You are integrating Didit anti-Sybil identity into a voting / governance / survey / airdrop / quadratic-funding platform. The recipe ensures each real human can be counted exactly once — no duplicates, no bots, no farmed accounts.
Two pillars:
1. Verify the voter is a real human with a real identity. ONE call to POST /v3/session/ with ID Verification + Liveness + Face Match.
2. Check the voter has not already been enrolled in this cohort. Face Search 1:N runs the voter's face against every previously-enrolled voter and returns a similarity score. Above threshold → duplicate, block.
Cost:
- Voter Know Your Customer (KYC) bundle: $0.33 per voter (Sessions API)
- Face Search 1:N: free (included)
- Re-vote / next round with Reusable KYC: free (the user proves uniqueness without re-doing KYC)
- 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.
- A workflow_id from the Workflow Builder that bundles ID Verification + Passive Liveness + Face Match 1:1 + Face Search 1:N + your jurisdiction rules (age, country, sanctions).
STEP 1 — Enrol the voter with the Sessions API
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 + Face Search 1:N>",
"vendor_data": "<your voter id, max 256 chars>",
"callback": "https://<your-app>/vote/enrolment/callback",
"metadata": {
"purpose": "vote_enrolment",
"cohort_id": "<your election / round / airdrop id>"
}
}
Response: 201 Created with the hosted session URL. Redirect the voter to it. Sub-2-second median verdict on completion.
STEP 2 — Read the signed webhook on enrolment completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your voter id>",
"status": "Approved",
"id_verification": { "status": "Approved" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"face_search": { "status": "Approved", "matches": [] }
}
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.
STEP 3 — Block duplicates
When face_search.matches is non-empty AND the top match's similarity is above your threshold (typical: 0.85), DO NOT add the voter to the cohort. The voter has likely been enrolled already, possibly under a different document or alias.
Recommended handling:
similarity ≥ 0.95 → block automatically, log the match
similarity 0.85–0.95 → route to manual review
similarity < 0.85 → enrol normally
STEP 4 — Privacy-preserving storage
The platform stores ONLY:
- voter_pid (pseudonymous identifier — a UUID, NOT the raw document number)
- unique (boolean)
- age_band (e.g. "18+", "25-34") — never the raw birth date unless your eligibility rule needs it
- region (e.g. "EU", "ES") — never the raw address
Documents, biometrics, and full names stay inside Didit, encrypted at rest. Default retention 5 years post-relationship; configurable per workflow.
STEP 5 — Read the decision on demand
GET https://verification.didit.me/v3/session/{sessionId}/decision/
Headers:
x-api-key: <your api key>
Returns the full decision JSON. Use this when the tally service needs to confirm a voter is still eligible at vote time.
STEP 6 — Reusable KYC for subsequent rounds
Once a voter is verified, the next vote / round / airdrop can reuse the verification at no extra cost. The user proves uniqueness with a selfie only — no document re-capture. Same workflow, different cohort id.
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.
- Face Search 1:N is scoped to YOUR cohort by default — Didit doesn't share faces across customers.
- Always check the duplicate score BEFORE recording the ballot, never after.
- The platform never sees the raw ID document or the raw face template — only the verdict and the pseudonymous PID.
- Default record retention is 5 years post-relationship per the EU AML package; extend per your governing body's rules.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/retrieve-session
- https://docs.didit.me/integration/webhooks
- https://docs.didit.me/core-technology/reusable-kyc/overview
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投票者ごとに, 完全なKYCバンドル、コホート内での顔検索1:Nが含まれます。
- Free再利用可能なKYC, 以降のラウンドではセルフィーのみでユニーク性を証明します。
- <0sエントリーレベルのAndroidで、投票者ごとのエンドツーエンド登録判定。
- 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's the anti-Sybil problem, in plain English?
A Sybil attack is when one human pretends to be many, by spinning up wallets, email addresses, burner phones, or fake IDs, to game a system that counts each account as one vote, one entry, one share.
It shows up everywhere voting or scarcity matter:
- DAO governance, a whale opens 1,000 wallets and skews every proposal
- Airdrops, a farmer creates 50,000 accounts and drains the token allocation
- Quadratic funding, fake identities multiply a single donor's matched funds
- Citizen surveys and polls, coordinated brigading manufactures consent
- Content-moderation votes, sock-puppet accounts swing what gets boosted or removed
The only durable defence is to bind each vote to a real human. That's what this recipe ships.
Why do wallets and email addresses fail as identity?
They prove control of a resource, not control of a body.
- A wallet proves you hold a private key. You can hold a hundred private keys.
- An email address proves you registered with an SMTP provider. SimpleLogin, gmail.com, and a thousand others mint addresses in seconds.
- A phone number proves a SIM card. SIM farms and virtual-number providers sell them in bulk.
- An IP address proves a network connection. VPNs, residential proxies, and datacenter pools rotate them on demand.
A face plus a government document is harder. There is exactly one face per body, and one valid government ID per face per country. Forging at scale costs orders of magnitude more than spinning up a wallet.
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 actually catch duplicates?
When a voter enrols, Didit creates a privacy-preserving face template (a vector, not the image) and compares it against every other voter template in your cohort. The output is a list of matches, each with a similarity score from 0 to 1.
A typical policy:
- ≥ 0.95 similarity, almost certainly the same person, block automatically
- 0.85 – 0.95, likely the same person, route to manual review
- < 0.85, different person, enrol normally
The cohort is scoped to YOUR dataset, Didit does not share faces across customers. The template is encrypted at rest, never exposed to the voting platform, and falls under the privacy notice the user agreed to at enrolment.
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 about voters across multiple rounds, do they pay every time?
No. Once a voter is verified by Didit, Reusable KYC (free, included) lets them prove uniqueness on every subsequent round with a selfie only, no document re-capture.
In practice:
- Round 1, full KYC bundle at $0.33
- Round 2, 3, 4, …, the user opens a new session against the next cohort id, takes a selfie, and Didit re-matches against the original verified template. Free.
The credential is portable across every Didit-powered platform, aligned with eIDAS2 (the EU's digital-identity regulation). The voter owns the credential, they re-present it on demand, you never re-pay.
What does the audit trail look like for a regulator or a transparency portal?
Every enrolment produces a signed receipt you can export to your audit log or your DAO's transparency portal:
session_id, Didit's verifiable identifier for the enrolmentvoter_pid, your pseudonymous voter idverdict,Approved,Declined,In Review, etc. (status enum:Approved,Declined,In Review,Resubmitted,Expired,Not Finished,Kyc Expired,Abandoned)cohort_id, which round / election / airdropsignature,X-Signature-V2HMAC SHA-256 of the payload with your webhook secrettimestamp
Pair with the on-chain attestation (if used) and you have a tamper-evident trail from "this real human enrolled" to "this ballot was cast". Default retention 5 years, extendable per your governing body's rules.
What does the integration look like for a small team?
Four steps, one afternoon:
- Open the sandbox at
business.didit.me, sandbox key in 60 seconds, no credit card - Build a workflow in the Workflow Builder that bundles ID + Liveness + Face Match + Face Search 1:N + your eligibility rules
- Wire
POST /v3/session/to enrol voters and the signed webhook to receive verdicts - Block the ballot until the webhook says
status: Approvedandface_search.matchesis empty (or below your threshold)
The Didit MCP (Model Context Protocol) server is included free, paste the integration prompt above into Claude Code, Cursor, Codex, Replit Agent, Devin, or Aider and the agent scaffolds the whole thing against the live /v3/ API.