Belgium

Belgium eKYC verification matches submitted individual data against Belgium's consumer credit and telco records. See the eKYC API Reference for common response semantics that apply across all sources.

Available sources

Source	API source string	Description
Belgium Credit + Telco	`BE_CREDIT_TELCO`	Verifies submitted data against Belgium's consumer credit and telco records.

Belgium Credit + Telco

Request parameters

Parameter	Required	Description
`source`	Mandatory	Must be `BE_CREDIT_TELCO`.
`country`	Mandatory	Must be `BE`.
`firstName`	Mandatory	First name of the individual. Must not contain digits.
`surName`	Mandatory	Last name of the individual. Must not contain digits.
`phone`	Mandatory	Belgium mobile phone number. See format note below.
`street`	Optional	Full street including house number (address = `street` + house number in Belgium).
`city`	Optional	City of the individual's address (for example, Brussels).
`state`	Optional	Region of the individual's address.
`postalCode`	Optional	Belgium postal code. See format note below.
`dateOfBirth`	Optional	Format: yyyy-mm-dd.

Sample request

{
    "plugins": ["kyc"], //required field
    "source": "BE_CREDIT_TELCO", //required field
    "firstName": "Jane", //required field
    "surName": "Doe", //required field
    "street": "Rue de la Loi 12",
    "city": "Brussels",
    "state": "Brussels-Capital Region",
    "postalCode": "1000",
    "country": "BE", //required field
    "dateOfBirth": "1991-08-02",
    "phone": "475123456" //required field
}

Response fields

Belgium Credit + Telco anchors verification on individual name and 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.
`fullNameMatch`	exact, fuzzy, nomatch	Composite of `firstNameMatch` and `lastNameMatch`. `exact` if both match; `nomatch` if either does not match; otherwise `fuzzy`.
`phoneMatch`	exact, fuzzy, nomatch	Matches phone submitted against the value in the source of truth.
`dobMatch`	exact, fuzzy, nomatch, nodata	Matches date of birth submitted against the value in the source of truth.
`streetMatch`	exact, fuzzy, nomatch, nodata	Matches street submitted against the value in the source of truth.
`cityMatch`	exact, fuzzy, nomatch, nodata	Matches city submitted against the value in the source of truth.
`stateMatch`	exact, fuzzy, nomatch, nodata	Matches state submitted against the value in the source of truth.
`postalCodeMatch`	exact, fuzzy, nomatch, nodata	Matches postal code submitted against the value in the source of truth.
`fullAddressMatch`	exact, fuzzy, nomatch, nodata	Composite of `streetMatch`, `cityMatch`, and `postalCodeMatch`. `stateMatch` is not factored into this calculation. See below for calculation logic.
`overallLevel`	low, medium, high	Overall risk level. See below for calculation logic.

overallLevel is calculated based on the risk associated with the submitted full name and phone number:

low when fullNameMatch and phoneMatch are both exact.
high when fullNameMatch or phoneMatch is nomatch.
medium for 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": "fullNameMatch", "status": "exact" },
        { "key": "phoneMatch", "status": "exact" },
        { "key": "dobMatch", "status": "exact" },
        { "key": "streetMatch", "status": "exact" },
        { "key": "cityMatch", "status": "exact" },
        { "key": "stateMatch", "status": "exact" },
        { "key": "postalCodeMatch", "status": "exact" },
        { "key": "fullAddressMatch", "status": "exact" },
        { "key": "overallLevel", "status": "low" }
    ]
}