> ## 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.

# Brazil - CPF + face match (Datavalid)

> SERPRO Datavalid v4 pf-facial — validates CPF (mandatory) against Receita Federal and matches the live selfie (mandatory) against the CNH portrait stored at Senatran. Optionally screens name and date of birth. Authoritative real-time identity lookup for Brazil. Real-time lookup, pay-per-call.

<div hidden data-didit-db-validation-defaults="{&#x22;issuing_state&#x22;:&#x22;BRA&#x22;,&#x22;services&#x22;:&#x22;bra_cpf_facial&#x22;,&#x22;consent&#x22;:&#x22;true&#x22;,&#x22;tax_number&#x22;:&#x22;11111111111&#x22;,&#x22;first_name&#x22;:&#x22;John&#x22;,&#x22;last_name&#x22;:&#x22;Doe&#x22;,&#x22;date_of_birth&#x22;:&#x22;1990-01-01&#x22;,&#x22;vendor_data&#x22;:&#x22;user-1234&#x22;}" />

SERPRO Datavalid v4 pf-facial — validates CPF (mandatory) against Receita Federal and matches the live selfie (mandatory) against the CNH portrait stored at Senatran. Optionally screens name and date of birth. Didit exposes this service through `POST /v3/database-validation/` so you can verify the submitted data against the authoritative source and receive normalized match results.

## Coverage

* **Coverage:** —
* **Country:** Brazil
* **Service ID:** `bra_cpf_facial`
* **Data domain:** Biometric
* **Category:** NationalIDRegistry

## Inputs

| Field           | Required | Example         |
| --------------- | -------: | --------------- |
| `tax_number`    |      Yes | `11111111111`   |
| `selfie`        |      Yes | `@./selfie.jpg` |
| `first_name`    |       No | `John`          |
| `last_name`     |       No | `Doe`           |
| `date_of_birth` |       No | `1990-01-01`    |
| `vendor_data`   |       No | `user-1234`     |

* **Required inputs:** `tax_number`, `selfie`
* **Optional inputs:** `first_name`, `last_name`, `date_of_birth`, `vendor_data`
* **Consent:** Required
* **Workflow availability:** Available in workflow
* **Coverage:** —
* **Price:** \$0.45 per successful query

## Body parameters

<ParamField body="issuing_state" type="string" required default="BRA" placeholder="BRA">
  ISO 3166-1 alpha-3 country code for this database service.

  Example: `BRA`
</ParamField>

<ParamField body="services" type="string" required default="bra_cpf_facial" placeholder="bra_cpf_facial">
  Array containing this service ID. Pinning the service keeps the request scoped to this exact database.

  Example: `bra_cpf_facial`
</ParamField>

<ParamField body="consent" type="boolean" required default="true" placeholder="true">
  Explicit end-user consent for this service.

  Example: `true`
</ParamField>

<ParamField body="tax_number" type="string" required default="11111111111" placeholder="11111111111">
  Tax or fiscal identification number.

  Example: `11111111111`
</ParamField>

<ParamField body="selfie" type="file" required placeholder="@./selfie.jpg">
  Selfie image file to upload for biometric database validation. Accepted formats: JPEG, PNG, or WebP.

  Example: `@./selfie.jpg`
</ParamField>

<ParamField body="first_name" type="string" default="John" placeholder="John">
  Given name to validate.

  Example: `John`
</ParamField>

<ParamField body="last_name" type="string" default="Doe" placeholder="Doe">
  Family name to validate.

  Example: `Doe`
</ParamField>

<ParamField body="date_of_birth" type="string" default="1990-01-01" placeholder="1990-01-01">
  Date of birth in `YYYY-MM-DD` format.

  Example: `1990-01-01`
</ParamField>

<ParamField body="vendor_data" type="string" default="user-1234" placeholder="user-1234">
  Your stable user reference for this person, such as your internal user ID. Didit uses it to link standalone checks to the same end user and reduce duplicate-detection noise.

  Example: `user-1234`
</ParamField>

## Input rules & validation notes

* Brazilian CPF (exactly 11 digits)
* `tax_number` must contain digits only; remove spaces, hyphens, and punctuation before sending the request.
* `tax_number` must be exactly 11 characters long.

## How to call it

<RequestExample>
  ```bash cURL theme={null}
  curl -X POST "https://verification.didit.me/v3/database-validation/" \
    -H "x-api-key: YOUR_API_KEY" \
    -F "issuing_state=BRA" \
    -F "services=bra_cpf_facial" \
    -F "vendor_data=user-1234" \
    -F "consent=true" \
    -F "tax_number=11111111111" \
    -F "selfie=@./selfie.jpg"
  ```
</RequestExample>

<ResponseExample>
  Every successful call returns HTTP `200`. The **`outcome_code`** field tells you what actually happened — distinguishing, for example, a real biometric mismatch (`BIOMETRIC_NO_MATCH`) from a selfie that could not be read (`BIOMETRIC_IMAGE_UNUSABLE`). The `status` shown is the default feature status; your configured [Partial Match / No Match actions](/core-technology/database-validation/database-validation-warnings) can override it.

  **`MATCH`** — The registry confirmed the identity and every checked field matched.

  ```json 200 OK — MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Approved",
    "issuing_state": "BRA",
    "match_type": "full_match",
    "validations": [
      {
        "outcome_code": "MATCH",
        "service_id": "bra_cpf_facial",
        "service_name": "Brazil - CPF + face match (Datavalid)",
        "source_data": {
          "date_of_birth": "1990-01-01",
          "face_match_probability": "Altíssima probabilidade",
          "face_match_score": "0.990",
          "first_name": "John",
          "identification_number": "SAMPLE-ID-12345",
          "last_name": "Doe",
          "name_match_score": "1.000",
          "verifications": {
            "identification_number": true
          }
        },
        "validation": {
          "identification_number": "full_match"
        }
      }
    ]
  }
  ```

  **`NO_MATCH`** — The registry returned no match for the submitted data.

  ```json 200 OK — NO_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "BRA",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "NO_MATCH",
        "service_id": "bra_cpf_facial",
        "service_name": "Brazil - CPF + face match (Datavalid)",
        "source_data": {
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```

  **`BIOMETRIC_NO_MATCH`** — The face-match score was below the acceptance threshold - the selfie is not the same person as the registry photo.

  ```json 200 OK — BIOMETRIC_NO_MATCH theme={null}
  {
    "request_id": "req_01H…",
    "status": "Declined",
    "issuing_state": "BRA",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "BIOMETRIC_NO_MATCH",
        "service_id": "bra_cpf_facial",
        "service_name": "Brazil - CPF + face match (Datavalid)",
        "source_data": {
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```

  **`BIOMETRIC_IMAGE_UNUSABLE`** — The selfie could not be processed (empty, no face, low quality, or the registry could not read it). Prompt the user to retake the selfie.

  ```json 200 OK — BIOMETRIC_IMAGE_UNUSABLE theme={null}
  {
    "request_id": "req_01H…",
    "status": "In Review",
    "issuing_state": "BRA",
    "match_type": "no_match",
    "validations": [
      {
        "outcome_code": "BIOMETRIC_IMAGE_UNUSABLE",
        "service_id": "bra_cpf_facial",
        "service_name": "Brazil - CPF + face match (Datavalid)",
        "source_data": {
          "identification_number": "NO_MATCH"
        },
        "validation": {
          "identification_number": "no_match"
        }
      }
    ]
  }
  ```
</ResponseExample>

## Returned data

The exact fields surfaced in `source_data` depend on what the registry returns. The generated example for `bra_cpf_facial` currently documents this normalized shape:

* `date_of_birth`
* `face_match_probability`
* `face_match_score`
* `first_name`
* `identification_number`
* `last_name`
* `name_match_score`

## Pricing & SLAs

Brazil - CPF + face match (Datavalid) queries are billed only when Didit receives a conclusive result from the validation source.

* **Per-call price:** \$0.45 USD.
* **Billing:** per successful query. You are not charged when the registry is unreachable, when required fields are missing, or when the request is rejected before reaching the source.
* **Latency:** typical p95 \< 2 s.
* **Availability:** 99.9% per quarter on Didit's side; downstream source availability varies by country and dataset.

## Continue reading

* [Brazil Database Validation overview](/api-reference/database-validation/brazil)
* [Database Validation overview](/core-technology/database-validation/overview)
* [Outcome Codes](/core-technology/database-validation/database-validation-outcome-codes)