#Aadhaar eSign Name Match

If you require the capability to match the name and year of birth of the signer with the Aadhaar data received from UIDAI, we can offer that feature during your onboarding process.

No changes will be required on your end. Raise a ticket at Setu Support to enable this feature.

This name match feature is performed by means of fuzzy matching, so you can set a percentage threshold for name matching. Any name match that falls below this threshold will be automatically rejected during the signing process.

The error reason will be displayed to the end user on the final eSign page prior to redirection.

You can refer to the error codes listed to see the specific error code and message that will be displayed.

Below are some sample accept and reject scenarios:

#Accepted scenarios:

1. If both names are in the right/same order (name1 = Rakesh Kumar Singh, name2 = Rakesh Kumar Singh)
2. If both names are in a different/jumbled order (name1 = Rakesh Kumar Singh, name2 = Singh Rakesh Kumar)
3. If the match percentage of both names is above the threshold
4. Names having honorifics such as Mr., Mrs. etc
5. If one or both names contain initials (name1 = Rakesh Kumar Singh, name2 = R K Singh [OR] name1 = Rakesh K Singh, name2 = R K Singh)

#Rejected scenarios:

1. If both names have a match percentage below the set threshold
2. If the number of words in each name do not match (i.e, first/middle/last name missing in one of the names) (name1 = Rakesh Kumar Singh, name2 = Rakesh Singh)
3. If one name contains only initials (name1 = Rakesh Kumar Singh, name2 = R K S)
4. If in the case of initials, the non-initial parts of the name do not match (name1 = Rakesh Kumar Singh, name2 = R K Sngh)

Apart from rejecting an eSign request on the basis of name match we also provide the option for you to receive the fuzzy name match scores in our API responses. This way you will be able to take the call to either accept or reject the request on the basis of scores received. This feature can also be configured during your onboarding process.

This data will be optionally available in the following ways:

1. Get signature request status
2. eSign notification

A sample name match data in API response and notification will look like this:

"signers": [
    {
        "nameMatchDetails": {
            "optimisticMatchOutput": {
                "match_percentage": 100.0,
                "match_type": "COMPLETE_MATCH"
            },
            "pessimisticMatchOutput": {
                "match_percentage": 100.0,
                "match_type": "COMPLETE_MATCH"
            }
        },
    }
]

Possible values for the match_type key:

1. COMPLETE_MATCH
2. HIGH_PARTIAL_MATCH
3. MODERATE_PARTIAL_MATCH
4. LOW_PARTIAL_MATCH
5. NO_MATCH

Please note that these features are independent, and should you not opt for it, there will be no changes to the normal eSign flow.