# Guatemala

Guatemala eKYC verification matches submitted individual data against Guatemala's source of truth. See the [eKYC API Reference](https://developer.incode.com/docs/ekyc-api-reference) for common response semantics that apply across all sources.

## Available sources

| Source | API source string | Description                                                                          |
| ------ | ----------------- | ------------------------------------------------------------------------------------ |
| GT 1   | `GT_1`            | Verifies submitted data against Guatemalan records associated with the provided DPI. |

{/* TODO: Confirm with PM — the customer-facing source name for `GT_1`. */}

## GT 1

### Request parameters

| Parameter     | Required  | Description                                                                                                     |
| ------------- | --------- | --------------------------------------------------------------------------------------------------------------- |
| `source`      | Mandatory | Must be `GT_1`.                                                                                                 |
| `country`     | Mandatory | Must be `GT`.                                                                                                   |
| `idNum`       | Mandatory | Guatemalan DPI (Documento Personal de Identificación). Thirteen digits, typically written as `XXXX XXXXX XXXX`. |
| `dateOfBirth` | Mandatory | Format: `yyyy-mm-dd`.                                                                                           |
| `firstName`   | Optional  | First name (and often Segundo nombre) of the individual.                                                        |
| `surName`     | Optional  | Last name (and often Segundo apellido) of the individual.                                                       |

### Response fields

GT 1 anchors verification on the source-of-truth register. See the [eKYC API Reference](https://developer.incode.com/docs/ekyc-api-reference) for common match field definitions and status values. GT 1 uses `approximatematch` as an alternative to `fuzzy` for name fields.

| Field            | Statuses                               | Description                                                               |
| ---------------- | -------------------------------------- | ------------------------------------------------------------------------- |
| `firstNameMatch` | `exact`, `approximatematch`, `nomatch` | Matches first name submitted against the value in the source of truth.    |
| `lastNameMatch`  | `exact`, `approximatematch`, `nomatch` | Matches last name submitted against the value in the source of truth.     |
| `fullNameMatch`  | `exact`, `approximatematch`, `nomatch` | Matches full name submitted against the value in the source of truth.     |
| `dobMatch`       | `exact`, `fuzzy`, `nomatch`            | Matches date of birth submitted against the value in the source of truth. |
| `idNumMatch`     | `exact`, `fuzzy`, `nomatch`            | Matches DPI submitted against the value in the source of truth.           |
| `overallLevel`   | `low`, `medium`, `high`                | Overall risk level. See below for calculation logic.                      |

### overallLevel calculation

`overallLevel` is calculated based on the risk associated with the submitted full name and DPI:

- `low` when `fullNameMatch` and `idNumMatch` are both `exact`.
- `high` when `fullNameMatch` and `idNumMatch` are both `nomatch`.
- `medium` for all other combinations.

Contact your Incode representative to customize the `overallLevel` calculation for your use case.

### Sample response

```json
{
    "kyc": [
        { "key": "firstNameMatch", "status": "exact" },
        { "key": "lastNameMatch", "status": "approximatematch" },
        { "key": "fullNameMatch", "status": "approximatematch" },
        { "key": "dobMatch", "status": "exact" },
        { "key": "idNumMatch", "status": "exact" },
        { "key": "overallLevel", "status": "low" }
    ]
}
```

<br />