免费
免费
每月 $0。无需信用卡。
- 免费 KYC 套件（身份验证 + 被动活体检测 + 人脸匹配 + 设备与 IP 分析）, 每月 500 次，永久有效
- 黑名单用户
- 重复检测
- 每次会话 200+ 欺诈信号
- Didit 网络中可重复使用的 KYC
- 案件管理平台
- 工作流构建器
- 公开文档、沙盒、SDK、MCP（模型上下文协议）服务器
- 社区支持
全球2,000多家组织信赖。
体育场 · 音乐节 · 公共交通 · 会议
无需二维码。直接通行。
无需掏出手机，告别电量焦虑，杜绝转售欺诈。购票时一次性注册，费用为 $0.25，此后每次闸机扫描都是免费的 1:N 人脸搜索匹配, 在音乐节规模下也能实现亚秒级响应。该流程适用于体育场、音乐节、公共交通枢纽和会议等多种场景。
工作原理
从注册到验证用户，仅需四步。
- 步骤 01
创建工作流
选择您需要的验证项, 身份、活体、人脸匹配、制裁名单、地址、年龄、电话、邮箱、自定义问题。在控制台中拖拽构建流程，或通过 API 发布。支持条件分支和 A/B 测试，无需代码。
- 步骤 02
集成
通过我们的 Web、iOS、Android、React Native 或 Flutter SDK 进行原生嵌入。也可重定向到托管页面。或者，只需通过电子邮件、短信、WhatsApp 等方式向用户发送链接。选择最适合您技术栈的集成方式。
- 步骤 03
用户完成流程
Didit 负责摄像头、灯光提示、移动设备切换和无障碍功能。在用户进行流程时，我们实时评估 200 多种欺诈信号，并根据权威数据源验证每个字段。两秒内即可获得结果。
- 步骤 04
接收结果
实时签名的 Webhook 可在用户通过、拒绝或需要审核时立即同步您的数据库。您也可以按需轮询 API。或打开控制台检查每个会话、每个信号，并按您的方式管理案例。
01 · 购票时注册
结账时一张自拍。永久可用。
将 Sessions API 会话集成到您的购买流程中。身份验证确认买家身份，被动活体检测拒绝所有呈现攻击检测 (PAD) 类型，并将生成的人像存储为买家的活动索引模板, 绑定到您的 vendor_data，可在同一买家参加的未来所有活动中重复使用。
身份验证模块Didit · Enrolment
Enrol at purchase. One selfie.
Order #18472
Capture your face
- Buyer identity verified
- Passive Liveness
- Face template enrolled
- Order bound to template
Reusable across every future event the same buyer attends.
02 · 刷脸即门票
无需手机。无需打印。无需条码。
在闸机处，摄像头捕捉一帧画面，访客即可通行。无需掏出手机（告别电量焦虑），无需打印（无纸化，杜绝转售欺诈），完全没有二维码。买家的脸部就是通行凭证，Face Search 1:N 在所有套餐中均免费。
人脸搜索 1:N 模块Didit · Face Search 1:N
The face is the ticket.
- No QR codeNo phone-out, no battery anxiety
- No printoutNo paper, no resale fraud
- Look at the cameraGate captures one frame
- Verdict in ~1sMatch against the event index
Sub-1-second match at the gate.Free per scan
03 · 闸机决策矩阵
入场。再入场。阻止。可配置。
匹配负载会为您提供匹配的买家参考和 similarity_score。您的闸机逻辑将进行分支：有效票 + 首次扫描 = 入场；已在场内 = 再入场策略；票已过期或取消 = 引导至工作人员；转售或不匹配 = 阻止。可按活动、闸机、票务等级进行配置。
工作流编排器Didit · Gate decision
What happens at the gate.
Scan outcomeAction
- Face matched · ticket validEntry
- Face matched · already insideRe-entry policy
- Face matched · expired ticketRoute to staff
- Face matched · resold to another buyerBlock
- No match · unknown faceBlock
Configurable per event, per gate, per ticket tier.
04 · 体育场、音乐节、公共交通
一次注册。适用于所有场馆类型。
一个面部模板可覆盖足球场、多日音乐节、公共交通季票和大型会议。买家只需向您注册一次，此后他们参加的每个由 Didit 提供支持的场馆都可零成本使用该凭证, 将可重用凭证语义应用于访问控制。
访问控制工作流Didit · Venue coverage
Stadium. Festival. Transit. Same gate.
- Stadium eventsFootball, concerts, championships
- FestivalsMulti-day, multi-gate, reusable
- Transit corridorsSeason passes, daily commuters
- ConferencesSessions, lounges, expo halls
One enrolment. Every event.220+ countries
05 · 音乐节规模容量
节庆规模下，匹配时间低于 1 秒。
经过数万张注册人脸的活动索引测试，单帧匹配时间约为一秒，每个闸机每分钟可处理约 30 次入场。平台正常运行时间达到 99.99%, 与所有其他 Didit 模块使用相同的 /v3/ API，因此您现有的 KYC 操作手册也适用于闸机。
性能基准Didit · Capacity
Sub-1-second at festival scale.
Match latency · single gate~1 second
Throughput per gate~30 / minute
Index size per event10,000s of faces
Platform uptime99.99%
Same /v3/ API as every other Didit module.
06 · 闸机处免费
一次性 $0.25。每次扫描免费。每月 500 次免费。
公开定价，无最低消费，无合同。身份验证 $0.15，加上被动活体检测 $0.10，买家一次性注册费用为 $0.25。后续每次闸机扫描的人脸搜索 1:N 免费。考虑到欺诈和转售损失，这比纸质票务流程更划算。
查看定价Didit · Public pricing
$0.25 enrolment. Free at the gate.
ID Verification (enrol)$0.15 one-time
Passive Liveness (enrol)$0.10 one-time
Face Search 1:N at gateFree / scan
Cheaper than the printed-paper ticket pipeline.
集成
一个注册端点。一个闸机端点。
在结账时通过 Sessions API 调用注册买家。在闸机处通过独立的 Face Search 1:N 调用匹配摄像头画面。与所有其他 Didit 模块使用相同的 /v3/ 接口。
POST /v3/session/注册
$ curl -X POST https://verification.didit.me/v3/session/ \
-H "x-api-key: $DIDIT_API_KEY" \
-d '{
"workflow_id": "wf_event_enrol",
"vendor_data": "buyer-42",
"metadata": { "event_id": "evt_1234" }
}'201已创建{ "session_url": "verify.didit.me/..." }
运行
ID_VERIFICATION + LIVENESS；将肖像绑定到 vendor_data。文档 →POST /v3/face-search/闸机 · 免费
$ curl -X POST https://verification.didit.me/v3/face-search/ \
-H "x-api-key: $DIDIT_API_KEY" \
-F "image=@gate-frame.jpg" \
-F "metadata={'event_id':'evt_1234'}"200确定{ "status": "Approved", "matches": […] }
每次扫描免费。匹配返回 vendor_data + similarity_score。文档 →
代理就绪集成
通过一个提示，快速部署生物识别票务。
粘贴到 Claude Code、Cursor、Codex、Devin、Aider 或 Replit Agent 中。填写您的技术栈。Agent 将配置 Didit，构建注册工作流，连接闸机扫描端点，并完成部署。
didit-integration-prompt.md
You are integrating Didit's biometric event-ticketing into <my_stack>. The face IS the ticket — no QR code, no barcode, no printout. Two phases:
1. Enrol the buyer ONCE at ticket purchase. A Sessions API call runs ID Verification + Passive Liveness and stores the buyer's portrait as the event-index template.
2. At every gate scan, call the standalone Face Search 1:N endpoint with the camera frame. Sub-1-second match against the event index. Verdict returned inline.
Pricing (public):
- Enrolment (one-time per buyer): $0.15 ID Verification + $0.10 Passive Liveness = $0.25
- Face Search 1:N at the gate: free per scan
- 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.
HMAC-SHA256 verification MUST run against the raw body bytes (the raw payload as Didit sent it) BEFORE any JSON parsing — re-serialising the parsed body changes whitespace and key order, which invalidates the signature. - A workflow_id from the Workflow Builder. The workflow MUST contain ID_VERIFICATION + LIVENESS (and optionally Anti-Money Laundering (AML) if you sell age-restricted access).
- One Didit account = one face index. Tag every enrolment with metadata.event_id so the gate-side search filters by the right event.
STEP 1 — Enrol at ticket purchase
POST https://verification.didit.me/v3/session/
Headers:
x-api-key: <your api key>
Content-Type: application/json
Body:
{
"workflow_id": "<your enrolment workflow>",
"vendor_data": "<your buyer id — must be unique per buyer>",
"callback": "https://<your-app>/ticketing/enrol/callback",
"metadata": {
"order_id": "<your order reference>",
"event_id": "<the event the buyer is entering>",
"ticket_tier": "<GA | VIP | accessible | etc>"
}
}
Response: 201 Created with the hosted session_url. Redirect the buyer. After the buyer completes ID Verification + Passive Liveness, the portrait is stored as their face template and bound to vendor_data.
STEP 2 — Read the signed verdict on enrolment completion
Body (excerpted):
{
"session_id": "<uuid>",
"vendor_data": "<your buyer id>",
"status": "Approved",
"id_verification": { "status": "Approved", "document_type": "Passport" },
"liveness": { "status": "Approved", "method": "PASSIVE", "score": 94 }
}
Verify X-Signature-V2 BEFORE trusting the body. On Approved, mark the order as enrolled and bind the order to vendor_data in your application database.
Session status enum (exact case): Approved | Declined | In Review | Resubmitted | Expired | Not Finished | Kyc Expired | Abandoned.
STEP 3 — At every gate scan, match the face against the event index
POST https://verification.didit.me/v3/face-search/
Headers:
x-api-key: <your api key>
Body (multipart/form-data):
image <the camera frame captured at the gate>
vendor_data <optional — restrict the search to a specific buyer>
metadata <optional JSON — e.g. { "event_id": "<...>" } to filter>
Response (excerpted):
{
"status": "Approved",
"matches": [
{
"vendor_data": "<buyer id>",
"similarity_score": 0.96
}
]
}
Match outcomes the gate logic should handle:
- Match found, ticket valid, no prior scan → grant entry, mark scanned
- Match found, already inside → apply re-entry policy
- Match found, ticket expired or canceled → route to staff
- Match found, ticket resold to another buyer → block, route to staff
- No match (similarity below threshold) → block, fall back to backup ticket flow
STEP 4 — Reusable across every event the same buyer attends
Because the buyer's face template is bound to vendor_data, the SAME enrolment works for every future event the same buyer holds a ticket for. No re-enrolment, no re-payment. Reusable Credential semantics applied to the venue use case.
CONSTRAINTS
- Base URL for /v3/* endpoints is verification.didit.me (NOT apx.didit.me).
- Feature enum is UPPERCASE: 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.
- The face template is irreversible (a one-way hash). End users can request deletion via the standard data-subject-request path.
ACCESS CONTROL CONSIDERATIONS
- For minor-attended events, run AGE_ESTIMATION during enrolment to gate age-restricted areas. See /solutions/age-verification.
- For high-value VIP areas, gate behind a Biometric Authentication step-up. See /solutions/biometric-2fa.
- For accessibility lanes, surface the ticket-tier metadata on the verdict payload and route the gate UI accordingly.
DATA-PROTECTION NOTES
- The enrolment selfie produces an irreversible face template; raw images are deleted unless retention is explicitly enabled.
- The gate frame is processed in memory and not persisted by default.
- Display the privacy notice (didit.me/terms/verification-privacy-notice) to the buyer before the enrolment selfie. EU GDPR Article 13 requires it.
Read the docs:
- https://docs.didit.me/core-technology/face-search/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多个国家/地区，每个季度进行审计和渗透测试, 是唯一一个被欧盟成员国政府正式认定比线下验证更安全的身份提供商。
阅读安全与合规性档案欧盟金融沙盒
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每位购票者只需一次注册。此后每次入场扫描均免费。
- ~1s在大型活动索引中实现单帧人脸匹配。
- 0.00%平台正常运行时间, 与所有其他 Didit 模块使用相同的 /v3/ API。
- 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.
What is "face-as-ticket"?
A ticket where the access token is the buyer's face, not a Quick Response (QR) code, a barcode, or a paper printout.
The buyer takes a selfie at purchase. The face template is stored against the order. At the gate, a camera captures one frame and 1:N face search matches it against the event's enrolled templates. Sub-1-second verdict, walk through.
Why are venues moving away from QR codes?
Three problems with QR-based ticketing:
- Resale fraud. A screenshot of a QR code is the ticket. Once a buyer screenshots and resells, every copy is valid until the first scan invalidates it, chaos at the gate.
- Battery anxiety. Phones die mid-day; users argue with stewards.
- Throughput. A QR scanner takes 2-4 seconds per scan plus fumble time. A face camera takes one frame at walking pace.
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.
What about people who don't want to be enrolled?
Always ship a non-biometric fallback, a printed PDF, an email-delivered QR code, or a staffed gate. The European Union Artificial Intelligence Act and most national consumer-protection regimes require an alternative path.
In practice, venues running biometric ticketing report 70-85% opt-in because the face lane is dramatically faster. The non-biometric lane stays open for the rest.
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.
How fast is the match at the gate?
Sub-1-second per scan against event indexes in the tens of thousands of enrolled faces. Throughput at a single gate sits around 30 entries per minute at a comfortable walking pace, comparable to the fastest QR scanner pipelines without the fumble time. Platform uptime is 99.99%, with the same operations playbook as every other Didit module.
Do we need an on-premise camera or special hardware?
Any commodity IP camera or tablet works, POST /v3/face-search/ accepts a single JPEG frame over HTTPS. Most venues use existing entry kiosks, ticket-scanner replacements, or a tablet on a stand. No custom Software Development Kit (SDK), no special drivers, no on-premise inference box.
For edge-cached gates (transit, large venues without reliable connectivity), Didit ships an on-premise face-search appliance, talk to sales.
What about minors and age-restricted events?
Run AGE_ESTIMATION at enrolment for age-gated zones (over-18 areas at a festival, alcohol bars at a stadium). The signed verdict carries an age band per buyer, and your gate logic surfaces the right wristband colour or wristband-free lane.
For minors attending family events, a parent / guardian completes the enrolment on the minor's ticket and consents to the template on the minor's behalf, the EU General Data Protection Regulation requires explicit parental consent under age 16 in most member states.