Ecuador eKYC verification matches submitted individual data against Ecuador's phone register as the source of truth. See the eKYC API Reference for common response semantics that apply across all sources.
Available sources
| Source | API source string | Description |
|---|---|---|
| Ecuador Phone Register | EC_PHONE_REGISTER |
Verifies submitted data against Ecuador's phone register. |
Ecuador Phone Register
Request parameters
| Parameter | Required | Description |
|---|---|---|
source |
Mandatory | Must be EC_PHONE_REGISTER. |
country |
Mandatory | Must be EC. |
firstName |
Mandatory | First name of the individual. Must not contain digits. |
surName |
Mandatory | Last name of the individual. Must not contain digits. |
middleName |
Optional | Middle name of the individual. Not included in fullNameMatch. |
gender |
Optional | Accepted values are m or f. |
street |
Optional | Street name and house number in one field (for example, Av. 10 de Agosto N34-183). |
city |
Optional | City of the individual's address (for example, Quito). |
zipCode |
Optional | Ecuadorian postal code. Format: exactly 6 numeric digits, no spaces or special characters (for example, 170150). |
phone |
Optional | Ecuadorian phone number. Format: exactly 9 numeric digits, no spaces or special characters (for example, 998888888). Do not include the country code. Other formats return a 400 error. |
Sample request
{
"plugins": ["kyc"],
"source": "EC_PHONE_REGISTER",
"firstName": "John",
"middleName": "Example",
"surName": "Doe",
"country": "EC",
"gender": "m",
"street": "Av. Example N34-183",
"city": "Quito",
"zipCode": "170150",
"phone": "998888888"
}
Response fields
Ecuador Phone Register anchors verification on full name and address or phone number. See the eKYC API Reference for common match field definitions and status values.
| Field | Statuses | Description |
|---|---|---|
firstNameMatch |
exact, fuzzy, nomatch |
Matches first name submitted against the value in the source of truth. |
lastNameMatch |
exact, fuzzy, nomatch |
Matches last name submitted against the value in the source of truth. |
middleNameMatch |
exact, fuzzy, nomatch, nodata |
Matches middle name submitted against the value in the source of truth. Shown as a standalone field and not included in fullNameMatch. nodata when not submitted. |
fullNameMatch |
exact, fuzzy, nomatch |
Composite match derived from firstNameMatch and lastNameMatch. See below for calculation logic. |
genderMatch |
exact, fuzzy, nomatch, nodata |
Matches gender submitted against the value in the source of truth. nodata when not submitted. |
streetMatch |
exact, fuzzy, nomatch, nodata |
Matches street address submitted against the value in the source of truth. nodata when not submitted. |
cityMatch |
exact, fuzzy, nomatch, nodata |
Matches city submitted against the value in the source of truth. nodata when not submitted. |
postalCodeMatch |
exact, fuzzy, nomatch, nodata |
Matches postal code submitted against the value in the source of truth. nodata when not submitted. |
fullAddressMatch |
exact, fuzzy, nomatch, nodata |
Composite match derived from streetMatch, cityMatch, and postalCodeMatch. See below for calculation logic. |
phoneMatch |
exact, fuzzy, nomatch, nodata |
Matches phone number submitted against the value in the source of truth. nodata when not submitted. |
overallLevel |
low, medium, high |
Overall risk level. See below for calculation logic. |
Info
Any field that was not submitted counts as nodata in all composite logic, regardless of what the source of truth returns for it.
overallLevel calculation
overallLevel is calculated based on the risk associated with the submitted full name and at least one verified attribute:
lowwhenfullNameMatchisexactAND (fullAddressMatchisexactorfuzzyORphoneMatchisexact).highwhenfullNameMatchisnomatch.mediumfor all other combinations.
Contact your Incode representative to customize the overallLevel calculation for your use case.
Sample response
{
"kyc": [
{ "key": "firstNameMatch", "status": "exact" },
{ "key": "lastNameMatch", "status": "exact" },
{ "key": "middleNameMatch", "status": "exact" },
{ "key": "fullNameMatch", "status": "exact" },
{ "key": "genderMatch", "status": "exact" },
{ "key": "streetMatch", "status": "exact" },
{ "key": "cityMatch", "status": "exact" },
{ "key": "postalCodeMatch", "status": "exact" },
{ "key": "fullAddressMatch", "status": "exact" },
{ "key": "phoneMatch", "status": "exact" },
{ "key": "overallLevel", "status": "low" }
]
}