Skip to main content

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.

Didit’s Database Validation API verifies identity data against authoritative civil registries — RENAPER (Argentina, $0.20/check), Receita Federal (Brazil, $0.20), Tribunal Electoral (Panama, $0.75 with biometric face-match), Junta Central Electoral (Dominican Republic, $0.05) and 14 more — billed per successful query with no monthly minimums. When a service can’t run — because required fields are missing, the issuing state isn’t enabled, or the registry returned a non-conclusive answer — we surface a warning on the session. This page documents every warning code, what triggers it, and how to react.

​
Configurable verification settings

Your workflow can be configured to handle different validation outcomes by setting specific actions for each risk category:
  1. Partial Match Action
    • REVIEW: Sessions with a partial match are set to “In Review” for manual assessment.
    • DECLINE: Sessions with a partial match are automatically declined.
  2. No Match Action
    • REVIEW: Sessions with no match are set to “In Review.”
    • DECLINE: Sessions with no match are automatically declined.
See Matching Methods for the full decision logic that drives 1×1 / 2×2 outcomes.

​
Database Validation warnings

Tag
Description
COULD_NOT_PERFORM_DATABASE_VALIDATION
The system couldn’t perform the database validation. Please fill in the required fields for this country to automatically proceed with the validation. You are not charged when this warning fires.
DATABASE_VALIDATION_PARTIAL_MATCH
The system identified a partial match in the database validation, requiring further investigation.
DATABASE_VALIDATION_NO_MATCH
The system identified no match in the database validation, requiring further investigation.
When a COULD_NOT_PERFORM_DATABASE_VALIDATION warning is received, the check will be automatically re-triggered once the missing KYC data is provided and saved in the console.There’s no need for manual intervention — the system will initiate a new validation as soon as the required fields are properly populated. When this warning occurs, the session status is automatically set to In Review until the required information is provided and the validation can be completed. No charge is applied for skipped services; you only pay when the registry returns a conclusive answer.

​
Warning types

Each risk is assigned a warning type based on your application’s configuration settings. Warnings fall into three severity categories:

​
See also

  • Database Validation overview — how the API works end-to-end, supported registries, pricing from $0.05/check.
  • Matching Methods — how 1×1 / 2×2 outcomes are derived from per-service matches against RENAPER, Receita Federal, etc.
  • Outcome Codes — full per-result taxonomy with country-specific detail codes for Argentina, Brazil, Panama and the standard outcome_code values across every supported country.
  • Supported Countries & Services — every live registry, required fields and per-call price.
  • Reports — monthly per-service billing exports.