> ## Documentation Index
> Fetch the complete documentation index at: https://docs.jelou.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Government validation

> Cross biometric data against official sources according to availability by country.

Government validation queries official civil registry sources in real time to reinforce confidence in the biometric result. It is an additional value on top of the base biometrics cost, not a replacement for document and facial verification.

## Validation types

There are two types of government validation, each with different country coverage:

| Type | What it does | Coverage |
| - | - | - |
| **Data only** | Contrasts the data extracted by OCR from the document against the government source. Returns a boolean response (true/false). | Available in **Ecuador, Colombia, and Peru**. In integration: **Chile and Mexico**. |
| **Data + photo** | In addition to contrasting the data, compares the photo extracted from the document against the photo stored at the government source (selfie vs. official photo). | Available only in **Ecuador and Peru**. |

> [!WARNING]
>
> Do not communicate Colombia as coverage for government facial comparison — only **data-only** (OCR) validation is available in that country.

## Coverage by country

Government validation is currently available in **Ecuador, Peru, and Colombia**. The fields returned by each official source vary by country.

> [accordion] Ecuador
>
> Direct connection with the Civil Registry.
>
> | Variable | Description | Response type |
> | - | - | - |
> | `nombres` / `primerNombre` | User's first name as officially registered. | Data (text) |
> | `primerApellido` | User's first last name. | Data (text) |
> | `segundoApellido` | User's second last name. | Data (text) |
> | `fechaNacimiento` | Officially registered date of birth. | Data (date) |
> | `sexo` | Sex registered on the official document. | Data (text) |
> | `estadoCivil` | Registered marital status (extra field). | Data (text) |
> | `profesion` | Registered profession (extra field). | Data (text) |
> | `lugarNacimiento` | Registered place of birth (extra field). | Data (text) |
> | `domicilio` | Registered home address (extra field). | Data (text) |
> | `provincia` | Registered province of residence (extra field). | Data (text) |
> | `ciudad` | Registered city of residence (extra field). | Data (text) |
> | `codigoError` | Query status code. `000` indicates the data is valid. | Data / code (success gate) |
> | `fotografia` | Official user photo, used for facial comparison. | Data (URL) |

> [accordion] Peru
>
> Data and photo validation against RENIEC.
>
> | Variable | Description | Response type |
> | - | - | - |
> | `firstName` | User's first name. | Data (text) |
> | `paternalLastName` | User's paternal last name. | Data (text) |
> | `maternalLastName` | User's maternal last name. | Data (text) |
> | `lastName` | User's combined last names. | Data (text) |
> | `fullName` | User's full name. | Data (text) |
> | `dateOfBirth` | Officially registered date of birth. | Data (date) |
> | `civilStatus` | Registered marital status. | Data (text) |
> | `address` | Registered home address. | Data (text) |
> | `documentType` | Type of document validated (defaults to national ID). | Data (text) |
> | `expeditionDate` | Document issue date. | Data (date) |
> | `expirationDate` | Document expiration date. | Data (date) |
> | `ubigeoReniec` | Official geographic location code. | Data (code) |
> | `verificationDigit` | Document verification digit. | Data (text) |
> | `photo` | Official user photo, used for facial comparison. | Data (URL) |

> [accordion] Colombia
>
> Data validation with ANI.
>
> | Variable | Description | Response type |
> | - | - | - |
> | `firstName` | User's first name. | Data (text) or boolean (`false` if it doesn't match the official source) |
> | `secondName` | User's second name. | Data (text) or boolean (`false` if it doesn't match) |
> | `firstLastName` | User's first last name. | Data (text) or boolean (`false` if it doesn't match) |
> | `secondLastName` | User's second last name. | Data (text) or boolean (`false` if it doesn't match) |
> | `fullName` | User's full name. | Data (text) |
> | `fullLastName` | User's full last names. | Data (text) |
> | `issueDate` | Document issue date. | Data (date) |
> | `documentStatus` | Document status (current, expired, etc.). | Data (text) |
>
> > [!WARNING]
> >
> > Colombia is the only country where a name field can return a boolean value (`false`) instead of data: if any of these fields doesn't match the official source, the entire government result is invalidated.

## Key considerations

* Availability depends on the country and the active provider; confirm current coverage before promising it in a proposal.
* The fields returned may vary between jurisdictions.
* You must define business rules for partial match and non-match.
* A failed government query (for example, RENIEC) — including a deceased indicator — results in a **definitive rejection**, with no derivation to manual review (HIL).
* A technical error from the government source (`serviceError`) is a different case from an identity rejection: it requires its own retry flow instead of blocking the user.

> [!WARNING]
>
> Do not use a single signal for critical decisions. Combine this validation with biometrics and operational review.

> [!TIP]
>
> Record the result and the reason for rejection in Datum to improve traceability and auditing.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.