無料
無料
月額$0。クレジットカード不要。
- 無料KYCバンドル（本人確認 + パッシブ・ライブネス + 顔照合 + デバイス＆IP分析）, 毎月500回まで
- ブロックリストユーザー
- 重複検出
- すべてのセッションで200以上の不正シグナル
- Diditネットワーク全体でのKYC再利用
- ケース管理プラットフォーム
- ワークフロービルダー
- 公開ドキュメント、サンドボックス、SDK、MCP (Model Context Protocol) サーバー
- コミュニティサポート
世界中の2,000以上の組織から信頼されています。
英国Ofcom · フランスSREN · EU DSA
1秒で年齢確認。必要な場合のみ書類確認。
すべての訪問者にドキュメントアップロードを強制すると、完了率は25〜40%低下します。 Diditのアダプティブフローは、まず年齢推定を実行し、境界ケースのみを ドキュメントフォールバックにルーティングします。セルフィー判定は2秒未満、$0.10/チェックで、 ユーザーあたりの平均コストは約$0.115です。毎月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 · セルフィーのみの初回パス
1枚のパッシブセルフィーで年齢を推定。
1枚の静止画で、モーションチャレンジや書類アップロードは不要です。エントリーレベルのAndroid端末でも2秒未満で判定し、1回のチェックにつき$0.10。英国オンライン安全法やフランスSRENへの最小限のデータで対応します。
年齢推定モジュールDidit · Age Estimation
Estimate age in one passive selfie.
Step 1 / 1
Centre your face
Estimate27 yrs
ConfidenceHigh
LivenessPass
Sub-2-second verdict on entry-level Android.
02 · ボーダーライン層のルーティング
範囲を調整。残りはDiditがルーティング。
ワークフローごとにボーダーラインの範囲を設定できます。明確な合格・不合格はセルフィーで完結し、ボーダーライン層はドキュメントによるフォールバックにエスカレートします。ノーコードのWorkflow Builderで、再デプロイなしにカットポイントを編集可能です。
ワークフローオーケストレーターDidit · Workflow Builder
Route only the borderline cases to ID.
Estimated bandPathVerdict
- 30+ yrsSelfie onlyApproved
- 22 - 29 yrsSelfie onlyApproved
- 16 - 21 yrsSelfie + documentReview
- 13 - 15 yrsDocument requiredReview
- Under 13Document requiredBlock
Edit the band in the no-code Workflow Builder.
03 · ドキュメントによるフォールバック
14,000以上の書類。220以上の国に対応。
ボーダーライン層のみが書類をアップロードします。パスポート、国民IDカード、運転免許証、在留許可証に対応し、OCR（光学文字認識）とMRZ（機械読取可能ゾーン）の完全な解析を行います。通常、このステップに到達するのは全体の約10%です。
ID検証モジュールDidit · ID Verification
14,000+ documents. Only when needed.
- PassportMRZ + photo page
- National identity cardFront + back, OCR
- Driving licencePer-state rules in US, CA, AU
- Residence permitSchengen + UK BRP
220+ countries · 48+ languages~10% traffic
04 · 国別の年齢ルール
米国では21歳から飲酒可能。EUでは18歳。韓国では19歳。
国ごとに最低年齢を設定し、必要に応じて州レベルでの上書きも可能です（ミシシッピ州21歳、アラバマ州19歳、米国デフォルト18歳）。ドキュメントによるフォールバックは、発行国のルールに基づいて生年月日を自動的に検証します。
国別リファレンスDidit · Country Rules
Per-country minimum age, out of the box.
CountryRuleMin age
- United KingdomOSA, adult content18
- FranceSREN, adult content18
- GermanyJuSchG / JMStV18
- United StatesAlcohol (federal)21
- South KoreaAlcohol / gaming19
State-level overrides (Mississippi 21, Alabama 19) included.
05 · 規制対応
英国Ofcom、フランスCNIL、EU DSA、ドイツJuSchG。
高度な年齢確認基準に対応するために構築されています。スペインのTesoroとSEPBLACは、Diditのリモートフローが対面認証よりも安全であると正式に認定しました。これは現在、EU加盟国政府による唯一の認定です。監査パックにはiBeta Level 1 PAD、ISO/IEC 27001、SOC 2 Type 1が含まれます。
コンプライアンスドキュメントDidit · Compliance Matrix
Regulator-ready out of the box.
RegulatorMethod acceptedDidit
- UK Ofcom (OSA)Estimation or documentShips
- France CNIL / Arcom (SREN)Estimation or documentShips
- EU DSA, VLOPsRisk-proportionateShips
- Germany JuSchGDocument or KYCShips
Tesoro / SEPBLAC attestation included in the audit pack.
06 · 公開価格
$0.10 selfie. $0.15 document. Only when needed.
セルフィーでクリアする約90%のユーザーには、年齢推定が$0.10で適用されます。ドキュメントチェックは、ボーダーライン層の約10%にのみ$0.15で実行されます。ユーザーあたりのブレンドコストは約$0.115です。毎月500回の検証が永続的に無料です。
料金を見るDidit · Public pricing
Blended cost: ~$0.115 per user.
Selfie age estimation~90% · $0.10
Document fallback~10% · $0.15
Blended per user~$0.115
500 verifications free every month, forever.
連携
1つのワークフロー。1つのセッション。1つのWebhook。
適応型ワークフローに対してセッションを開始します。Diditが検証を自動実行し、署名付きの検証結果がコールバックで返されます。
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_age_gate_uk_fr",
"vendor_data": "user-42",
"callback": "https://app/age-gate/cb"
}'201作成済み{ "session_url": "verify.didit.me/..." }
境界線上のケースでは、ワークフローが
AGE_ESTIMATIONからID_VERIFICATIONに連携します。ドキュメント →GET /v3/session/{sessionId}/decision/判定
$ curl https://verification.didit.me/v3/session/<id>/decision/ \
-H "x-api-key: $DIDIT_API_KEY"
# Returns the path taken
{
"status": "Approved",
"liveness": { "age_estimation": 27.3 }
}200OKステータス：承認済み・審査中・却下・未完了
署名済みWebhookは同じ形式です。まず
X-Signature-V2を確認してください。ドキュメント →エージェント対応統合
年齢確認機能をプロンプト一つで実装。
Claude Code、Cursor、Codex、Devin、Aider、またはReplit Agentに貼り付けてください。お使いのスタックに合わせて設定するだけで、エージェントが適応型ワークフローを構築し、セッションを開き、Webhookを接続し、5分でデプロイします。
didit-integration-prompt.md
You are integrating Didit's Age Verification recipe into <my_stack>. Selfie-first age estimation with an adaptive document fallback for the borderline tail. One Didit workflow. Two real endpoints.
1. Verify age on a selfie. ONE call to the Sessions API runs Age Estimation + Passive Liveness on the same passive frame.
2. Fall back to a document check ONLY when the estimate sits in the borderline band you define. Same Sessions API workflow handles the fallback automatically.
Bundle pricing (public):
- Age Estimation: $0.10 per check (Sessions API or standalone)
- ID Verification fallback: $0.15 per check, only when triggered
- Typical blended cost lands near $0.115 per user (~90% finish on the selfie, ~10% touch the document fallback)
- 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 and your webhook secret.
- A workflow_id from the Workflow Builder. The workflow must contain the AGE_ESTIMATION feature, and (recommended) the ID_VERIFICATION feature with adaptive_id_verification enabled so the borderline tail routes through automatically.
STEP 1 — Build the adaptive workflow once
POST https://verification.didit.me/v3/workflows/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_label": "age_gate_uk_fr",
"features": [
{ "feature": "AGE_ESTIMATION" },
{ "feature": "ID_VERIFICATION" }
],
"age_estimation_decline_threshold": 18,
"face_liveness_score_decline_threshold": 30,
"adaptive_id_verification": true
}
Notes:
- "AGE_ESTIMATION" and "ID_VERIFICATION" are exact, case-sensitive feature names.
- age_estimation_decline_threshold defaults to 18; set 21 for US alcohol, 19 for South Korea, etc.
- adaptive_id_verification = true tells Didit to invoke the document fallback automatically when the estimate sits inside the borderline band.
STEP 2 — Open an age-verification 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>/age-gate/callback",
"metadata": {
"purpose": "age_gate",
"surface": "<the page or feature being gated>"
}
}
Response: 201 Created with the hosted session_url. Redirect the user to it. The hosted flow opens the front camera, captures one passive frame, runs Age Estimation + Passive Liveness in sub-2-seconds, and either returns a verdict or routes the user into the document fallback automatically.
STEP 3 — Read the signed webhook on session completion
Didit POSTs to your callback. Session statuses are exact Title Case With Spaces.
Body (excerpted for an Age Estimation only finish):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"liveness": {
"status": "Approved",
"method": "PASSIVE",
"score": 92,
"age_estimation": 27.3,
"warnings": []
}
}
Body (excerpted when the document fallback fired):
{
"session_id": "<uuid>",
"vendor_data": "<your user id>",
"status": "Approved",
"liveness": { "status": "Approved", "age_estimation": 17.9, "warnings": [{ "code": "AGE_NOT_DETECTED" }] },
"id_verification": {
"status": "Approved",
"date_of_birth": "1998-03-21",
"age": 27,
"document_type": "Passport",
"issuing_state": "GBR"
}
}
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.
Warning catalog:
- AGE_BELOW_MINIMUM estimated or computed age below the threshold
- AGE_NOT_DETECTED unable to estimate age (lighting / quality)
- LOW_LIVENESS_SCORE passive-liveness score below threshold
- NO_FACE_DETECTED no face in the capture
- LIVENESS_FACE_ATTACK presentation attack suspected
- POSSIBLE_DUPLICATED_FACE same face previously verified
STEP 4 — Branch your surface on the final verdict
Approved → grant access to the gated surface.
Declined → render the regulator-required age-gate notice.
In Review → hold; an analyst case is open in the Business Console.
Not Finished → user abandoned; safe to re-prompt.
STEP 5 — Alternate path (server-to-server, when you already have the selfie)
POST https://verification.didit.me/v3/age-estimation/
Headers:
x-api-key: <your api key>
Body (multipart/form-data):
user_image <single passive selfie>
age_estimation_decline_threshold 18 (optional, integer)
face_liveness_score_decline_threshold 30 (optional, integer)
Branch on the borderline band yourself, then optionally call:
POST https://verification.didit.me/v3/id-verification/
Body (multipart/form-data):
front_image <required>
back_image <optional>
vendor_data <optional, your user id>
This path is useful for native onboarding apps that capture the selfie locally.
CONSTRAINTS
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: AGE_ESTIMATION, ID_VERIFICATION, LIVENESS, FACE_MATCH, AML, IP_ANALYSIS.
- 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.
- Reference image URLs are signed and expire in 60 minutes. Store only the verdict + score; never the biometric media unless retention is explicitly enabled for fraud defence.
- 200+ fraud signals are evaluated on every session at no extra cost — surface the score via the session decision payload, do not re-query.
WEBHOOK EVENT NAMES
- Sessions: status changes flow through the standard session webhook.
- Verify X-Signature-V2 on every payload.
Read the docs:
- https://docs.didit.me/core-technology/age-estimation/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.さらに詳しい情報が必要ですか？モジュールの全ドキュメントをご覧ください。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.000ユーザーあたりの平均コスト, セルフィーと、10%の境界線上のドキュメントフォールバックを含む。
- ~90%ユーザーの多くは、受動的なセルフィーのみで完了します, ドキュメントのアップロードは不要です。
- <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 does "age verification" actually require?
Most regulators ask for highly effective age assurance on adult content, online gambling, alcohol, and sometimes social platforms. That means a method good enough that the average minor can't trivially pass, not a self-declared birth-date checkbox.
The two methods almost every regulator accepts are age estimation (a selfie scored by a model) and age verification by document (the user uploads a passport or national identity card). Most teams ship both, with the estimation step gating the cheaper, lower-friction selfie path.
Which laws drive age-gating in 2026?
The two new rules pulling teams in are the UK Online Safety Act (Ofcom started enforcement in July 2025 for any service that lets users in the UK encounter pornography) and France's SREN law (CNIL + Arcom rules in force for sites accessed from France).
Alongside those, the EU Digital Services Act asks very-large platforms to mitigate risks to minors, and several US states (Utah, Texas, Louisiana) have age-gate statutes for adult content. They all accept the same toolkit: selfie age estimation, government identity document upload, or a third-party identity 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.
Why pair age estimation with a document fallback?
Two reasons. First, regulators care about the tail, not the median. A model is statistically fine at 17 vs 19 but the regulator wants you to be confident on the 16-year-old who looks 20. The document check is your evidence on those cases.
Second, conversion. Forcing every visitor to upload a passport drops finish rates by 25-40%. A selfie-first flow with document fallback typically routes 90% of users through the cheaper, friction-free path and 10% to the document step, far better business outcomes, same compliance posture.
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 attestations should I show my regulator?
Didit ships with the certifications UK Ofcom and CNIL most often ask to see on a vendor questionnaire:
- iBeta Level 1 PAD on the passive-liveness module (the NIST-referenced anti-spoof bar).
- ISO/IEC 27001 information-security certification.
- SOC 2 Type 1 on the platform.
- Spain's Tesoro / SEPBLAC formal attestation that Didit's remote flow is safer than in-person verification, currently the only EU member-state government attestation of this kind for any identity provider.
All four sit in the audit pack, ready to attach to the platform's transparency notice.
How do you handle the user's biometric data?
Data minimisation by default. The selfie is processed in memory, the age verdict and a liveness score are persisted, and the raw image is deleted unless retention is explicitly enabled for fraud defence. The retention window is per-workflow and per-region, and an end user can request deletion via the standard data-subject-request path.
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.
What if a user fails the age check?
The selfie returns one of three outcomes:
- Approved, clearly above the threshold. Continue.
- Declined, clearly below. Block the surface; show the regulator-required age-gate notice.
- In Review, borderline, low liveness, or no face detected. The flow auto-routes to the document fallback. The user uploads a passport or national identity card; Didit returns the date-of-birth read off the document and verdict in under two seconds.
A signed webhook lands at every state change so you only render the gate against the latest verdict, not a guess.