免费
免费
每月 $0。无需信用卡。
- 免费 KYC 套件（身份验证 + 被动活体检测 + 人脸匹配 + 设备与 IP 分析）, 每月 500 次，永久有效
- 黑名单用户
- 重复检测
- 每次会话 200+ 欺诈信号
- Didit 网络中可重复使用的 KYC
- 案件管理平台
- 工作流构建器
- 公开文档、沙盒、SDK、MCP（模型上下文协议）服务器
- 社区支持
全球2,000多家组织信赖。
远程医疗平台应尽的职责
了解患者。确保每次复诊都是同一个人。且不影响就诊速度。
临床安全和药房滥用控制都依赖于值得信赖的患者身份。Didit 将入驻 KYC 和每次续药的生物识别重新认证作为两个简短的托管流程提供, 入驻 $0.33，每次续药 $0.10。每月免费500次验证，通过 SOC 2 Type 1 和 ISO/IEC 27001 认证，仅存储生物识别模板。
工作原理
从注册到验证用户，仅需四步。
- 步骤 01
创建工作流
选择您需要的检查项, 身份、活体、人脸比对、制裁名单、地址、年龄、电话、电子邮件、自定义问题。在仪表板中将它们拖入流程，或将相同的流程发布到我们的 API。根据条件进行分支，运行 A/B 测试，无需代码。
- 步骤 02
集成
通过我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。重定向到托管页面。或者直接通过电子邮件、短信、WhatsApp 等任何方式向您的用户发送链接。选择适合您技术栈的方式。
- 步骤 03
用户完成流程
Didit 提供摄像头、灯光提示、移动端切换和辅助功能。在用户操作流程中，我们实时评估 200 多个欺诈信号，并根据权威数据源验证每个字段。两秒内即可获得结果。
- 步骤 04
您接收结果
实时签名 Webhook 可确保用户通过、拒绝或发送审核时，您的数据库即时同步。您可以按需轮询 API，或打开控制台检查每个会话、每个信号，并按您的方式管理案例。
01 · 患者 KYC 套件
一次调用即可验证患者。
ID + 活体检测 + 人脸匹配, 套件价格 $0.33。通过 iBeta Level 1 反欺骗认证，两秒内出结果。捕获用于驱动未来每次续药认证的绑定生物识别模板。
用户验证模块Didit · Patient KYC
Verify the patient in one call.
Step 3 / 5
Hold still for liveness
- ID Verification$0.15
- Passive Liveness$0.10
- Face Match 1:1$0.05
- Age Estimation$0.10
- AML Screening$0.20
02 · 年龄路由
按年龄路由，无需暴露出生日期。
年龄估算 ($0.10) 返回患者的年龄段, 成年人、青年、青少年、儿童, 这样您的临床工作流程可以路由到正确的路径，而不会将出生日期泄露给每个下游服务。当估算结果不确定时，可回退到 ID 验证。
年龄估算模块Didit · Age Estimation
Route by age. No date of birth surfaced.
CohortEstimated ageRouting
- Adult care≥ 21Pass
- Young adult18-20Pass
- Adolescent13-17Review
- Pediatric (guardian)< 13Block
ID-fallback for adolescents · guardian flow for pediatric.
03 · 保险验证
读取卡片。验证付款人。
可选的数据库验证节点通过 OCR 识别保险卡（会员 ID、组、付款人），并根据美国付款人数据库（Aetna、BCBS、UHC、Cigna、Kaiser）或欧盟国家健康保险系统查找付款人。解析后，卡片图像将被丢弃。
数据库验证模块Didit · Database Validation
Read the insurance card. Validate the payer.
- US payer card OCRMember ID · group · payer name
- Payer database matchAetna, BCBS, UHC, Cigna, Kaiser
- EU EHIC / national idES SS · DE GKV · FR CPAM · IT SSN
- Eligibility ping270/271 if your stack supports it
Card image discarded after parse, only the validated payload stays.
04 · 受控物质门控
附表 II 电子处方前的强身份门控。
根据 SUPPORT 法案，美国缉毒局 (DEA) 附表 II/III/IV/V 药物分发需要防转移控制。Didit 续药工作流程强制执行：政府签发的 ID、人脸匹配分数 ≥ 0.85（与绑定模板匹配）、iBeta 认证的活体检测、每次续药时进行新鲜重新认证。
生物识别认证模块Didit · DEA / Schedule II policy
Strong-identity gate for controlled prescriptions.
SignalRequirementAction
- ID strength · government-issuedRequiredPass
- Face match to ID portraitScore ≥ 0.85Pass
- Passive liveness (anti-deepfake)iBeta L1Pass
- Re-auth at refill (biometric)Every refillReview
- Duplicate identity check (1:N)Across patientsReview
Anti-diversion controls run before the e-prescription fires.
05 · 同意书 + HIPAA 捕获
同意书、入院信息、HIPAA, 在流程中捕获。
自定义问卷 ($0.10) 可在同一托管会话中捕获 HIPAA 隐私惯例通知确认、远程医疗 + 电子处方临床同意书以及入院病史。所有内容均已版本化并带有时间戳，用于患者记录。
自定义问卷模块Didit · Custom Questionnaires
Consent, intake, HIPAA, captured in-flow.
- HIPAA notice ackNotice of Privacy Practices · v2025
- Clinical consentTelemedicine + EHR + e-prescription
- Intake historyConditions, allergies, current meds
- Payer assignment of benefitsOptional · per workflow
Versioned and timestamped for the patient record.
06 · 生物识别重新认证
每次续药都是同一患者。
不到 1 秒的自拍 + 活体检测与绑定模板匹配。每次认证 $0.10。在预约登录时取代用户名 + 密码，并门控受控物质的分发。仅保留生物识别模板, 不保留原始自拍。
生物识别认证模块Didit · Biometric Authentication
Same patient at every refill.
- Onboarding · binding selfieOne-time · stored as template
- Refill · same person?Selfie + liveness · 1s
- New visit · same person?Replaces username + password
- Audit trail · every authSigned + timestamped
Biometric template only, no raw selfie retained.
集成
两次会话。一个模板。每次续药都安全。
开启入驻会话。保存模板。每次续药时重新验证。
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_patient_onboarding",
"vendor_data": "patient-42"
}'201已创建绑定模板已存储在 Approved 上。
HIPAA + 临床知情同意在同一流程中完成。文档 →
POST /v3/session/重新认证
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"workflow_id": "wf_biometric_reauth",
"vendor_data": "patient-42",
"metadata": { "context": "controlled_substance_refill" },
// base64 enrolment selfie, ≤ 1MB
"portrait_image": "/9j/4AAQSkZJRgABAQE..."
}'201已创建状态为 Approved → 触发电子处方。
不到 1 秒完成与绑定模板的人脸匹配。文档 →
代理就绪集成
一键部署远程医疗患者入驻流程。
粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。Agent 将构建两个工作流，启动入驻会话，持久化绑定模板，并连接每次续药的重新认证 + webhook。
didit-integration-prompt.md
You are integrating Didit into a telehealth platform (Doctolib / Teladoc / Hims & Hers / Ro / Tessa Health archetype). You owe the clinical and pharmacy layers a trustworthy patient identity at onboarding and at every refill of a controlled prescription.
Three obligations at onboarding:
1. Verify the patient's identity — government ID + liveness + face match.
2. Confirm age — adult, adolescent, or pediatric — to route to the correct clinical pathway without surfacing date of birth on every downstream call.
3. Capture consent — HIPAA Notice of Privacy Practices acknowledgement, clinical consent (telemedicine + electronic health record + e-prescription), intake history.
One obligation at every refill or new appointment:
4. Biometric reauthentication — a 1-second selfie matched to the binding template established at onboarding. Anti-diversion control for US Drug Enforcement Administration (DEA) Schedule II-V medications.
Optional but recommended:
5. Insurance card capture + payer validation — OCR the card, look up the payer, ping eligibility if your stack supports 270/271 EDI.
Pricing (verified live):
- Onboarding Know Your Customer (KYC) bundle (ID + Liveness + Face Match + IP + AML): $0.33 per patient
- Age Estimation: $0.10 per patient
- Custom Questionnaire (HIPAA + clinical consent): $0.10 per submission
- Biometric Authentication (refill / new visit): $0.10 per auth
- First 500 KYC 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 for patient onboarding that bundles ID Verification + Passive Liveness + Face Match 1:1 + Age Estimation + Custom Questionnaire.
- A workflow_id for biometric reauthentication (selfie + liveness + 1:1 face match against the binding template).
STEP 1 — Create the patient onboarding session
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your patient onboarding workflow id>",
"vendor_data": "<your patient id, max 256 chars>",
"callback_url": "https://<your-app>/patients/kyc/callback",
"metadata": {
"patient_id": "<your internal id>",
"scheduling_context": "new_visit"
}
}
Response: 201 Created with the hosted session URL. Send it to the patient through your booking flow; they complete identity + consent on their phone in under five minutes.
STEP 2 — Read the signed webhook on onboarding completion
Didit POSTs to your callback. Session statuses are Title Case With Spaces:
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your patient id>",
"status": "Approved",
"id_verification": { "status": "Approved", "document_type": "drivers_license", "country_code": "US" },
"liveness": { "status": "Approved" },
"face": { "status": "Approved", "similarity_score": 0.94 },
"age_estimation": { "status": "Approved", "estimated_age_bucket": "ADULT" },
"questionnaire": { "status": "Approved", "responses": { "hipaa_ack": true, "telehealth_consent": true } }
}
Session 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 — Persist the binding biometric template
When the onboarding session is Approved, Didit stores a biometric template under the patient's vendor_data automatically. You don't need to fetch or store the raw selfie — it's discarded after the template is generated. The template lives in EU data centres and is used for every future face-match against this patient.
STEP 4 — Biometric reauthentication at refill / new appointment
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your biometric reauth workflow id>",
"vendor_data": "<the same patient id as onboarding>",
"callback_url": "https://<your-app>/patients/reauth/callback",
"metadata": {
"context": "controlled_substance_refill",
"prescription_id": "<your rx reference>"
}
}
The reauth workflow runs Passive Liveness + Face Match 1:1 against the binding template. Sub-1-second median verdict. $0.10 per auth. Use this BEFORE every controlled-substance e-prescription fires.
STEP 5 — Decide
Branch logic on the parent session status:
Approved → onboard the patient, allow scheduling.
In Review → hold the visit, wait for analyst webhook update.
Declined → refuse onboarding, log the decline reason.
Resubmitted → patient updated something; re-read the decision.
On the reauth session:
Approved → fire the e-prescription / book the visit.
Declined → refuse the refill, require in-person identity check.
STEP 6 — Insurance card capture (optional)
Add a Database Validation node to your onboarding workflow against the US payer database (Aetna, BCBS, UnitedHealthcare, Cigna, Kaiser) or the EU national health-insurance system (ES Seguridad Social, DE GKV, FR CPAM, IT SSN). The patient uploads the card; Didit OCRs the member id, group, and payer name, then validates against the payer database. The card image is discarded after parse — only the validated payload is retained.
WEBHOOK EVENT NAMES
- status.updated — session status changed.
- data.updated — session data changed (resubmission, consent re-collection).
Verify X-Signature-V2 on every payload. The webhook secret is per-environment — sandbox key is separate from production.
CONSTRAINTS
- Session statuses use Title Case With Spaces (Approved, In Review).
- The biometric template is the binding identity — once a patient is onboarded, every future reauth references it. If you delete the patient, delete the template too via the Business Console (GDPR / HIPAA right-to-deletion compliance).
- HIPAA-protected information (PHI) and biometric templates are stored in EU data centres for EU patients; US-specific deployments can request a US tenant.
- For controlled-substance dispense, run a fresh biometric reauth on every refill — this is the anti-diversion control US DEA Schedule II / III requires under the SUPPORT Act.
Read the docs:
- https://docs.didit.me/sessions-api/create-session
- https://docs.didit.me/sessions-api/retrieve-session
- https://docs.didit.me/core-technology/face-match/overview
- https://docs.didit.me/core-technology/age-estimation/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多个国家/地区，每个季度进行审计和渗透测试, 是唯一一个被欧盟成员国政府正式认定比线下验证更安全的身份提供商。
阅读安全与合规性档案欧盟金融沙盒
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
原生符合欧盟标准
数据证明
数据证明
- $0.00每位患者入驻, KYC 捆绑包 + 绑定模板。
- $0.00每次续药或新就诊的生物识别重新认证。
- <0s入门级 Android 设备上的中位人脸匹配结果。
- 0每个账户每月免费验证。
三个层级，一份价目表
免费开始。按使用量付费。可扩展至企业级。
每月 500 次免费验证，永久有效。生产环境按量付费。企业版提供定制合约、数据驻留和 SLA (Service Level Agreements)。
最受欢迎
按用量付费
按用量计费
按实际用量付费。25+模块。公开的模块定价，无每月最低费用。
- 完整KYC $0.33（身份+生物识别+IP/设备）
- 10,000+ AML数据集, 制裁、PEP、负面媒体
- 1,000+ 政府数据源用于数据库验证
- 交易监控 $0.02/笔交易
- 实时KYB $2.00/家企业
- 钱包筛选 $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.
Why does a telehealth visit need identity verification at all?
Three reasons that the in-person clinic gets for free:
- Clinical safety, the prescriber has to know the person on camera is the person on the chart. Wrong-patient prescriptions are a top safety event in remote care.
- Pharmacy diversion, prescription resale, especially for controlled substances, depends on identity slippage between the patient and the person collecting the script.
- Payer fraud, insurance billing for a member who isn't the one being treated is the largest single line of healthcare fraud in the US.
The in-person clinic asks for a driver's licence at check-in. Telehealth has to replace that with a remote identity check that's at least as strong. Didit ships it as a hosted flow the patient finishes on their phone in under five minutes, at $0.33 per patient.
What's HIPAA and how does it affect identity verification?
HIPAA is the US Health Insurance Portability and Accountability Act. The Privacy Rule and the Security Rule together require that protected health information (PHI) is handled with administrative, physical, and technical safeguards.
For identity verification specifically:
- Patient identity data is PHI the moment it's tied to a clinical record
- The vendor that does the verification is a Business Associate and needs a Business Associate Agreement (BAA) with your platform
- Biometric templates count as PHI under most state interpretations (Illinois BIPA, Texas CUBI, Washington Biometric Privacy Act)
- The patient's HIPAA Notice of Privacy Practices acknowledgement has to be on record before treatment
Didit ships a BAA with every paid plan and stores biometric templates only, the raw selfie is discarded after the template is generated. SOC 2 Type 1 and ISO/IEC 27001 attestations cover the security baseline. EU patients can request EU-only storage; US-specific deployments can request a US tenant.
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 Age Estimation help in healthcare?
Age routes care. A 14-year-old asking for a contraceptive consult triggers a different clinical and consent pathway than a 28-year-old. A 70-year-old asking for cognitive-decline screening triggers another. Surfacing the patient's date of birth on every downstream call leaks more than the routing decision needs.
Age Estimation returns the patient's cohort, adult, young adult, adolescent, pediatric, from the same selfie used for liveness, without exposing the date of birth. The clinical layer routes on the cohort; the audit trail keeps the date of birth in the patient record where it belongs.
$0.10 per check. Backed by an ID-fallback when the estimation is borderline. For pediatric patients, the workflow can branch to a guardian-consent flow automatically.
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.
Can the same identity work across providers?
Yes, Reusable KYC is a free distribution layer on top of the verification stack. Once a patient is onboarded, that identity can be presented to any other Didit-integrated provider with the patient's consent, eliminating re-verification fatigue.
Where this matters in healthcare:
- Multi-tenant pharmacy chains, one onboarding covers every pharmacy under the same parent
- Specialty referrals, primary care passes the verified identity to the specialist without re-onboarding
- Medicare / Medicaid networks, share verified identity across in-network providers without storing biometrics on each platform
- Cross-platform clinical research, the patient consents to share the verified identity with a registered trial
Reusable KYC is free forever. The patient owns the consent and can revoke per-provider sharing at any time via the Didit identity wallet.
How does Didit compare on price?
Most healthcare-identity providers price between $3 and $8 per check, often with minimums in the thousands per month and per-state surcharges for HIPAA tenancy. Add $0.30-$1.00 per biometric reauth.
Didit's published price is $0.33 per onboarding KYC bundle + $0.10 per biometric reauth. No floor, no minimum, no per-state surcharge. The first 500 verifications free every month absorbs most pilot and low-volume practices entirely.
That's roughly 10× cheaper than the incumbent stack on the same regulatory output. At a 5,000-patient telehealth practice with two refills per patient per year, the saving is around $12,000 per year, and the patient experience is faster, with the same selfie working across every refill. Full pricing at /pricing.
What records do I need to keep?
Healthcare retention is one of the longest of any vertical:
- US HIPAA, 6 years from creation or last effective date, whichever is later
- US state retention rules, typically 7-10 years for adult records, longer for pediatric (some states require until the patient is 21+)
- EU GDPR + national health rules, 10 years for clinical records; biometric templates only for as long as the patient is active
- DEA controlled-substance records, 2 years minimum, often longer per state
How Didit handles it:
- All evidence stored in the European Union by default, regulated EU data centres, no cross-border transfer for EU patients. US tenant available for US-only deployments.
- Every payload is signed and timestamped so chain-of-custody is provable for an examiner
- Retained indefinitely while your subscription is active, no per-record retention bill, no expiry surprises
- Configurable per workflow if your supervisor mandates a specific duration
- Patient deletion endpoint deletes the identity record AND the biometric template (HIPAA right to access + GDPR right to erasure)
ISO 27001, SOC 2 Type 1, and iBeta Level 1 anti-spoof certifications are all downloadable from /security-compliance. Business Associate Agreement (BAA) included with every paid plan.