India eKYC non-doc verification leverages India'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. User data can be collected via a user input flow by using pre-selected fields where users can type in their name, date of birth, etc.

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.

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.

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.

• country: (mandatory) String. Two letter Alpha-2 country code. Must be IN. Note: countryCode takes priority over country if both are provided.
• source: (mandatory) String. Must be IN_DMV.
• firstName: (mandatory) String. First name of the individual. Must not contain digits.
• surName: (mandatory) String. Last name of the individual. Must not contain digits.
• middleName: (optional) String. Must not contain digits.
• dateOfBirth: (mandatory) String. Format: YYYY-MM-DD (e.g. 1991-08-02).
• idNumber: (mandatory) String. Driving License Number.(eg. SS-RRRR-YYYY-NNNNNNN)
• street: (optional) String. House number and street name of the address.
• city: (optional) String. City of the individual's address (e.g. Bengaluru).
• state: (optional) String. State of the individual's address (e.g. Karnataka).
• postalCode: (optional) String. Must be exactly 6 digits — PIN code (e.g. 560001).
• gender: (optional) String. Accepted values are "m" or "f".

Example Incode request:

{
    "plugins": ["kyc"],
    "source": "IN_DMV",
    "firstName": "Rahul",
    "middleName": "Kumar",
    "surName": "Sharma",
    "street": "24 MG Road",
    "city": "Bengaluru",
    "state": "Karnataka",
    "postalCode": "560001",
    "country": "IN",
    "dateOfBirth": "1991-08-02",
    "idNumber": "DL0420110123456",
    "gender": "m"
}

Direct API Response

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": "exact"
        },
        {
            "key": "lastNameMatch",
            "status": "exact"
        },
        {
            "key": "fullNameMatch",
            "status": "exact"
        },
        {
            "key": "dobMatch",
            "status": "exact"
        },
        {
            "key": "idNumMatch",
            "status": "exact"
        },
        {
            "key": "streetMatch",
            "status": "exact"
        },
        {
            "key": "cityMatch",
            "status": "exact"
        },
        {
            "key": "stateMatch",
            "status": "exact"
        },
        {
            "key": "postalCodeMatch",
            "status": "exact"
        },
        {
            "key": "fullAddressMatch",
            "status": "exact"
        },
        {
            "key": "genderMatch",
            "status": "nomatch"
        },
        {
            "key": "overallLevel",
            "status": "low"
        }
    ]
}

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 India, custom 400 error messages if required fields are missing or incorrectly formatted:

overallLevel

Overall Level is the API response key for the submitted name. The fields low, medium, and high are mapped to the result of the identity verification check.

As a default, overallLevel will return:

low: when fullNameMatch & dobMatch & idNumMatch are exact;

high: when fullNameMatch OR dobMatch OR idNumMatch are nomatch;

medium: for all otherwise combinations.

Single Session Dashboard Result

E