> ## Documentation Index
> Fetch the complete documentation index at: https://docs.didit.me/llms.txt
> Use this file to discover all available pages before exploring further.
# 数据库核验 API：官方登记数据库 KYC
> Didit 提供高性价比且快速的按次付费政府登记处核验 API。低至 $0.05/check，覆盖 60+ 个上线国家/地区，支持在官方库留有照片时进行生物识别人脸比对。
Didit 的**数据库核验**根据相应国家/地区的权威数据源核验个人的身份数据，包括最初签发该证件的国家民事登记处、税务机关、选民名册、征信机构或生物识别登记处。每次核查都会返回逐字段匹配结果（`identification_number`、`first_name`、`last_name`、`date_of_birth`，以及该服务所使用的地址字段），并返回综合结果，以及在可用时返回底层记录详情。这是防范合成身份欺诈的最强防线：被盗用的真实 DNI 或 CPF 无法通过登记处核对，而伪造的号码根本不会出现在官方数据库中。在登记处保存有官方照片的国家/地区（阿根廷通过 RENAPER，巴拿马通过 Tribunal Electoral SIB / SIB Plus），数据库核验可与我们的生物识别人脸比对结合使用，因此您不仅可以确认号码的真实性，还可以确认**摄像头前的人就是该证件的所有者**。
数据库核验集成提示词
\
\````# Goal
Integrate Didit Database Validation (verify identity data against authoritative national registries) into your app. Pick ONE mode.
\# Mode A — Session-based
Use this when Database Validation runs as a step in a hosted Didit flow. Fields are auto-fed into the registry lookup from the steps in front of it — ID Verification, NFC, Liveness, Phone/Email Verification, Proof of Address, Document AI or a Questionnaire. An ID Verification step is not required.
1\. Add the DATABASE_VALIDATION feature to the workflow (Business Console or POST /v3/workflows/). Optionally pin specific services per country.
2\. Create a session — POST /v3/session/ with { workflow_id, vendor_data, callback }. See /sessions-api/create-session.
3\. Open session.url for the user (or mount the Web/Mobile SDK).
4\. Fetch the decision — GET /v3/session/{sessionId}/decision/ or subscribe to session.status.updated.
Decision surface: `database_validations[]` array on the decision payload.
\# Mode B — Standalone API (server-to-server)
Use when you already have the identity data and want a one-shot registry check.
POST https://verification.didit.me/v3/database-validation/
multipart/form-data — x-api-key: YOUR_API_KEY
curl example (Brazil CPF):
\```bash
curl -X POST 'https://verification.didit.me/v3/database-validation/' \
-H "x-api-key: $DIDIT_API_KEY" \
-F "issuing_state=BRA" \
-F "identification_number=00000000191" \
-F "first_name=Jane" \
-F "last_name=Doe" \
-F "date_of_birth=1990-01-15" \
-F "vendor_data=user-1234"
\```
Returns: { request_id, database_validation: { match_type: "full_match"|"partial_match"|"no_match", validation_type, services_used, match_score, validations: [{ service, status, matched_fields, record_details }], warnings: [...] } }.
\# Important behaviour
\- Use `identification_number` (universal field) — Didit maps it to CPF/RUT/CURP/DNI/etc. by issuing_state.
\- Omit `services` to run the country's default service only. Pass `services=["bra_cpf"]` (etc.) to choose which services run — list several to run more than one.
\- Argentina (`arg_renaper`) and Panama (`pan_sib`) take an extra `selfie` (JPG/PNG/WebP up to 2 MB) and `gender` for biometric face-match against the registry photo.
\- Services flagged `requires_consent=true` in the catalog require `consent=true` (HTTP 400 otherwise).
\- Billing is **per successful service hit** — multi-service requests can produce multiple usage events.
\# Status / match_type
status: "Approved" | "In Review" | "Declined" (per the partial-match / no-match actions configured on the workflow)
match_type: "full_match" | "partial_match" | "no_match"
\# Warnings (LogWarningChoices.DATABASE_VALIDATION)
warnings[] risk codes include:
DATABASE_VALIDATION_NO_MATCH, DATABASE_VALIDATION_PARTIAL_MATCH, COULD_NOT_PERFORM_DATABASE_VALIDATION (biometric outcomes surface via per-service outcome_code, e.g. BIOMETRIC_NO_MATCH).
Full catalogue: /core-technology/database-validation/database-validation-warnings.
\# Failure modes to handle
\- HTTP 400 — service id not eligible for issuing_state, missing required field, missing consent for PAYGO services.
\- HTTP 502 with validation_errors[] — every selected upstream service failed; request is **not billed** and a COULD_NOT_PERFORM_DATABASE_VALIDATION log is written. Retry later or fall back to OCR-only.
\- match_type="no_match" — record not in registry; treat as synthetic identity per policy.
\- match_type="partial_match" — some fields match, others don't (e.g. DOB matches, name doesn't); route to review.
\# See also
\- Canonical schema: /reference/data-models#database-validation
\- Per-feature report: /core-technology/database-validation/database-validation-report
\- Risk catalogue: /core-technology/database-validation/database-validation-warnings
\- Outcome codes: /core-technology/database-validation/database-validation-outcome-codes
\- Full integration playbook: /integration/integration-prompt````
\
## 为什么选择 Didit- **最便宜的按次计费价格。** 每次核查最低仅需 **\$0.05**（多米尼加共和国），最高为 **\$7.00**（最昂贵的专业数据源）。价格按服务而非按国家/地区设定：收取高批发费率的登记处其定价也相应调整（芬兰国民身份证为 **\$2.10**）。请务必查阅[各项服务定价表](https://docs.didit.me/zh/getting-started/database-validation-pricing.md)以了解您计划调用的具体服务的费率。无每月最低消费，无平台费用，无席位计费，仅对成功的查询收费。
- **最快集成。** [注册](https://business.didit.me/)，从控制台获取 API 密钥，几分钟内即可调用 `POST /v3/database-validation/`。无需销售沟通，无需采购周期，无需概念验证文档，Didit 完全支持自助服务。
- **直接对接权威数据源。** RENAPER、Receita Federal (SERPRO)、Tribunal Electoral、RENAPO、RENAP、RNP、RNPN、Junta Central Electoral、Registraduría Nacional、SEGIP、Servicio de Registro Civil、Tribunal Supremo de Elecciones、Dirección General de la Policía，而非聚合器抓取的数据。
- **在登记处存档有官方照片时提供生物识别人脸比对。** 无需额外的集成工作，即可获得高于 OCR 的置信度。
- **生产就绪的低延迟。** 端到端 p95 通常低于 1.5 s，季度可用性达 99.9%。Academy 中关于解读验证结果的课程在 11:05 处介绍了数据库核验，并展示了完全匹配、部分匹配和不匹配的结果。[数据库核验：完全匹配、部分匹配与不匹配 — Didit Academy](https://www.youtube.com/embed/7htTWCWsl60?start=665\&rel=0\&playsinline=1)## 全球覆盖将鼠标悬停在任何高亮显示的国家/地区上，即可查看我们在该处运行的每项数据库核验服务、数据领域（身份、金融、生物识别、地址、电信等）以及每次调用的价格。已上线的国家/地区现已可直接用于生产环境；其余国家/地区则在客户提出需求后按需接入。Live Database Validation coverageProduction-ready countries and the cheapest live service available in each.LIVEShow on-demand catalog countries ()
| 国家/地区 |
\ISO3 |
\服务 |
\描述 |
\价格（美元） |
|---|
\
## 继续阅读- [匹配方法](https://docs.didit.me/zh/core-technology/database-validation/database-validation-matching-methods.md) — 1×1 / 2×2 结果的计算方式以及如何对其进行处理。
- [结果代码](https://docs.didit.me/zh/core-technology/database-validation/database-validation-outcome-codes.md) — 完整的供应商响应代码列表（已故、未成年人、未找到证件、生物识别不匹配等）以及它们如何映射到会话决策。
- [警告](https://docs.didit.me/zh/core-technology/database-validation/database-validation-warnings.md) — 当服务因缺少数据而无法运行时，我们提示的警告信息。
- [报告](https://docs.didit.me/zh/core-technology/database-validation/database-validation-report.md) — 包含国家/地区、服务 ID、用量、单价和总费用的每月按服务计费导出报表。
- [支持的国家/地区](https://docs.didit.me/zh/core-technology/database-validation/database-validation-supported-countries.md) — 我们当前覆盖的所有国家/地区的静态表格视图。
This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.