---
title: Reprocessing and Biometric Base Import
description: Guide for reprocessing biometric records or importing a biometric base into the Unico platform.
canonical: https://developer.unico.io/dual-api/resources/reprocessing
locale: en
generated_by: markdown-export
---

- [/](/)
- Resources
- Reprocessing and Biometric Base Import

**On this page# Reprocessing and Biometric Base Import

This guide covers how to perform **reprocessing** or **biometric base import** on the Unico platform. It details the technical and operational requirements for an effective, secure integration following platform best practices.
### Scope​

This material covers two types of processes:

**Reprocessing**: reprocessing biometric records of users who have already been through the client's and Unico's base for re-evaluation or migration between systems.
**Biometric Base Import**: initial upload or update of a base containing selfies for identity verification and/or risk classification purposes.
**Document Base Import**: upload of a document base alongside selfies for Facematch or CPF Match verification purposes (Brazil only).

### Prerequisites​

The client **must have an active contract or NDA** signed with Unico and be in the integration phase (exception if approved by the governance team).
The project will follow formal **TPS (transactions per second) agreements**. See [TPS agreement](#tps-agreement) below.
Before obtaining production credentials, **full integration homologation is mandatory** to ensure data quality, payload compliance and stable performance.
A **dedicated service account** must be created for the reprocessing or import (e.g., "Reprocessing" or "Legacy_Import").
A **dedicated API Key** will be created specifically for the reprocessing/import.
**(Optional)** A dedicated subsidiary can be created for the reprocessing/import. This parameter is identified in the payload as `subsidiaryId`. See [Payload parameters](#payload-parameters) below.
The API Key and service account **will be deactivated** after the agreed period or processing completion.

### Available capabilities​

CapabilityDescription**Identity Verification**Verifies whether the submitted selfie belongs to the actual holder of the identifier.**Fraud Risk Classification**Checks for a history of fraudulent behavior associated with that face.**Facematch**Verifies whether the document photo matches the submitted selfie.**CPF Match** Brazil onlyVerifies whether the provided CPF matches the CPF number printed on the document. Note: not all RGs have the CPF printed.
infoThe capabilities listed above are the most commonly used in reprocessing flows. Other capabilities may be enabled depending on the client's needs and the API Key configuration — contact your Unico project manager to discuss the right setup for your use case.
### Selfie requirements​

Must be submitted in **base64** format.
The image must follow the **ICAO standard** (light background, centered face, no accessories that obstruct identification, proper lighting).
Recommended dimensions: **1080x1920** (portrait) or **1920x1080** (landscape).
Maximum size: **800 KB** (compress with JPEG 92 if needed).
Orientation: **portrait**.

### Document requirements​

**Supported document types**: see [Document Capture & Reuse — Supported documents](/capabilities/document-reuse-and-capture#supported-documents).
Images must include both the **front and back** of the document, fully visible with no cropping.
The document must be **legible** — clear, well-lit, and free of obstructions.

### TPS agreement​

The maximum agreed TPS for this project is **10 TPS**.
Distribute requests evenly over time rather than sending them in large bursts.
This limit **must not be exceeded** without formal approval from the Unico team.
Requests above the limit may be automatically dropped or blocked.
If a temporary increase is needed, a **formal prior agreement** is required.

### Integration​

#### Endpoints​

EnvironmentBase URLAccessNotesStaging`https://api.id.uat.unico.app`OpenMandatory for testingProduction`https://api.id.unico.app`Only after approved homologationRequires strict TPS control
#### Required headers​

```
Authorization: Bearer {access_token}APIKEY: {your_api_key}Content-Type: application/json
```

#### Payload parameters​

```
{  "subject": {    "duiType": 1,    "code": "11032395702",    "name": "User Name",    "email": "username@gmail.io",    "phone": "21998571922",    "birthDate": "30/07/1989",    "gender": "M"  },  "useCase": "Reprocessamento/Importação",  "subsidiaryId": "35d734c4-7fbb-4b2f-a1dc-7e1575514819",  "imageBase64": "/9j/4AAQSkZJR...",  "document": {    "purpose": "Reprocessamento",    "documentId": "doc-001",    "files": [      {        "data": "doc_base64_frente",        "faceDocumentMatch": true      },      {        "data": "doc_base64_verso"      }    ]  }}
```

FieldTypeRequiredDescription`subject`objectYesUser identification data.`subject.duiType`integerYesDocument type identifier. See [`duiType` values](#duitype-values) below.`subject.code`stringYesCPF or other user identifier.`subject.name`stringYesUser's full name.`subject.email`stringNoUser's email.`subject.phone`stringNoUser's phone number.`subject.birthDate`stringNoUser's date of birth (`DD/MM/YYYY`).`subject.gender`stringNoUser's gender (`M` or `F`).`useCase`stringYesUse case name ("Reprocessamento" or "Importação de base").`subsidiaryId`stringNoSubsidiary UUID (provided by Unico).`imageBase64`base64YesUser's selfie image converted to base64.`document`objectNoDocument data associated with the process.`document.purpose`stringNoDocument purpose (e.g., `"Reprocessamento"`).`document.documentId`stringNoDocument identifier.`document.files`arrayNoList of document image files.`document.files[].data`base64NoDocument image converted to base64.`document.files[].faceDocumentMatch`booleanNoIndicates whether the face in the document matches the submitted selfie.
**`duiType` values**CountryCodeDescriptionAR6Argentine PassportAR7Argentine DNIAR49Argentine Driving Licence (Licencia Nacional de Conducir)AT34Austrian Tax Number (STNR)BE36Belgian National Number (NN)BR1Brazilian CPFBR5Brazilian PassportBR14Brazilian CNPJCA28Canadian SINCH33Swiss AHV/AVS NumberCL9Chilean RUNCL52Chilean PassportCL57Chilean Driving Licence (Licencia de Conducir)CO26Colombian NITCO53Colombian PassportCO55Colombian Driving Licence (Licencia de Conducción)CO56Colombian Citizenship Card (Cédula de Ciudadanía)DE41German Tax Identification Number (IdNr)DK29Danish CPREC10Ecuadorian NIES50Spanish Foreigner Identity Number (NIE)ES51Spanish National Identity Document (DNI)FI35Finnish Personal Identity Code (HETU)FR46French Tax Reference Number (SPI)GB30British National Insurance Number (NINO)GT12Guatemalan CUIID16Indonesian NIKIE47Irish Personal Public Service Number (PPSN)IT37Italian Codice Fiscale (CF)LU48Luxembourg National Identification Number (Matricule)MX2Mexican CURPMX25Mexican RFC (Persona Física)MX58Mexican Driving Licence (Licencia de Conducir)NG8Nigerian NINNG20Nigerian Bank Verification Number (BVN)NG43Nigerian BVN Token (hashed)NG44Nigerian NIN Token (hashed)NL42Dutch Citizen Service Number (BSN)NO39Norwegian National Identity Number (Fødselsnummer)PE27Peruvian RUCPE40Peruvian DNIPE54Peruvian PassportPL31Polish PESELPT45Portuguese Tax Identification Number (NIF)SE32Swedish Personal Number (PNR)SE38Swedish Coordination Number (Samordningsnummer)TR24Turkish Identification Number (TCKN)US4United States SSNUS11United States PassportUS18United States Driver's LicenseUS21United States Passport CardUS22United States Polycarbonate PassportUS23United States ID CardUY13Uruguayan CIZZ15Email addressZZ17Phone number—0Unspecified—3Internal Unico identifier
#### Important notes​

The selfie **must comply with the ICAO standard** with proper quality and lighting.
The selfie must be in **base64 format**.
Avoid bulk submissions without TPS control — this can trigger rate limiting (see [Error handling](#error-handling) below).
Always test data and integration in the staging environment first.

#### Responses​

**Success — 200 OK**
Without documentWith document (Facematch)```
{  "id": "80371b2a-3ac7-432e-866d-57fe37896ac6",  "status": 3,  "unicoId": {    "result": "inconclusive"  },  "riskLevel": {    "result": "inconclusive"  }}
```

FieldTypeDescription`id`stringProcess identifier. Store it for future queries or if you implement 1:1 Validation later.`status`integerTransaction status.`unicoId.result`stringIdentity Verification capability response.`riskLevel.result`stringFraud Risk Classification result. Possible values: `reproved`, `risk-critical`, `risk-high`, `inconclusive`.```
{  "id": "80371b2a-3ac7-432e-866d-57fe37896ac6",  "score": 0,  "status": 3,  "unicoId": {    "result": "yes"  },  "faceDocumentMatch": {    "faceMatch": true  },  "riskLevel": {    "result": "inconclusive"  }}
```

FieldTypeDescription`id`stringProcess identifier. Store it for future queries or if you implement 1:1 Validation later.`status`integerTransaction status.`score`numberFacematch score.`unicoId.result`stringIdentity Verification capability response.`faceDocumentMatch.faceMatch`booleanWhether the document photo matches the submitted selfie.`riskLevel.result`stringFraud Risk Classification result. Possible values: `reproved`, `risk-critical`, `risk-high`, `inconclusive`.
**Image processing error**
```
{  "id": "80371b2a-3ac7-432e-866d-57fe37896ac6",  "status": 5}
```

**Common errors**
Codes in the `4xx` range indicate validation errors with the provided data. Codes in the `5xx` range indicate server-side failures.
HTTP CodeError TypeLikely CauseRecommended Action`400`Bad RequestInvalid payloadValidate structure and content.`401`UnauthorizedExpired or invalid tokenRegenerate token.`403`ForbiddenIncorrect API Key or insufficient permissionsVerify credentials.`429`Too Many RequestsRequest rate exceededWait and respect TPS limit.`500+`Internal Server ErrorInternal failureRetry after a few seconds; open a ticket if persistent.
### Error handling​

**Rate Limit (HTTP 429)** must be carefully monitored. Request overload can block the pipeline.
Always respect the TPS agreed with Unico (see [TPS agreement](#tps-agreement)).
For persistent failures (5xx), reprocess with retry/backoff control.
Last updated on Oct 8, 2026**