Canada Fintrac

Canada eKYC non-doc verification leverages Canada's source of truth to validate individuals. It is essential in eKYC processes for ensuring identity authenticity, regulatory compliance, and enhanced security. It helps prevent fraud, boosts user trust, and streamlines operations through automated and efficient verification methods.

Integration

User input flow

eKYC module configuration gives various options to specify different search criteria with various sources of truth for each country (eg. US has multiple via Telco, Credit Bureau, and Driver's License). User data can be collected via a user input flow by using pre-selected fields where users can type in their name or date of birth, etc. See an example below:

eKYC user input flow example

Module configuration

The module configuration can be leveraged to select the applicable fields for the input data you would like to collect from the end user.

eKYC Module configuration

Direct API Approach

All module configurations and user data can be forwarded directly in the request for performing an eKYC search. This will override existing configuration and data collected about the user.

API Authentication

All endpoints require authentication headers to be specified as stated in Incode API Documentation.

eKYC request

POST /omni/externalVerification/ekyc

This endpoint performs an eKYC check for the individual specified. Note: Endpoint can have empty body {} and in that case information will be pulled from module configuration and session details.

Example Incode request:

{
    "plugins": ["kyc"],
    "source": "CA_CREDIT_FINTRAC",
    "firstName": "John",
    "middleName": "",
    "surName": "Doe",
    "street": "97 Main St",
    "city": "Ottawa",
    "state": "ON",
    "postalCode": "K1M1N8",
    "country": "CA",
    "dateOfBirth": "1990-12-12"
}

Direct API Response

API Authentication

All endpoints require authentication headers to be specified as stated in Incode API Documentation.

Note: Endpoint can have empty body {} and in that case information will be pulled from module configuration and session details.

Example Incode response:

{
    "kyc": [
        {
            "key": "firstNameMatch",
            "status": "Exact"
        },
        {
            "key": "middleNameMatch",
            "status": "No Match"
        },
        {
            "key": "lastNameMatch",
            "status": "Exact"
        },
        {
            "key": "fullNameMatch",
            "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"
        },
        {
            "key": "creditFileNumber",
            "status": "123456789"
        },
        {
            "key": "creditFileCreationDate",
            "status": "01-14-2000"
        }
    ]
}

eKYC error responses

Please refer to error response to see conventional HTTP response codes to indicate the success or failure of an API request. For Canada, custom 400 error messages if taxId, or country is " " or null:

Incode API Key Status Definition
firstNameMatch exact, nomatch Matches first name submitted against the name associated to the value in the source of truth.
middleNameMatch exact, nomatch Matches middle name submitted against the name associated to the value in the source of truth.
lastNameMatch exact, nomatch Matches last name submitted against the name associated to the value in the source of truth.
fullNameMatch exact, nomatch Matches full name submitted against the full name associated to the value in the source of truth.
dobMatch exact, nomatch Matches date of birth submitted against the date of birth associated to the value in the source of truth
streetMatch exact, nomatch Matches street submitted against the street associated to the value in the source of truth
cityMatch exact, nomatch Matches city submitted against the city associated to the value in the source of truth
stateMatch exact, nomatch Matches state submitted against the state associated to the value in the source of truth
postalCodeMatch exact, nomatch Matches postal code submitted against the postal code associated to the value in the source of truth
fullAddressMatch exact, fuzzy, nomatch Matches full address (street, city, state, zip) submitted against the full address associated to the value in the source of truth
creditFileNumber Integer The credit file number of the individual.
Note: This is only available if the credit file was created at least 3 years ago. For cases where the credit file was created 3 years ago or later, the response will be " File created less than 3 years ago".
creditFileCreationDate Date Date when credit file was created.
Note: This is only available if the credit file was created at least 3 years ago. For cases where the credit file was created 3 years ago or later, the response will be " File created less than 3 years ago".
overallLevel low, medium, high Overall Risk Level is focused on the risk associated to the submitted full name, full address and date of birth.