From c021c899d4cb840d8e159a57a0042f1851a3eb95 Mon Sep 17 00:00:00 2001 From: Piyush Das Date: Fri, 11 Apr 2025 11:15:23 +0530 Subject: [PATCH 1/3] added details of name match data in api response and esign notification response as an optional feature --- content/data/esign/name-match.mdx | 41 ++++++++++++++++++++++++++++++- 1 file changed, 40 insertions(+), 1 deletion(-) diff --git a/content/data/esign/name-match.mdx b/content/data/esign/name-match.mdx index 1d0b9dd5..6fca628f 100644 --- a/content/data/esign/name-match.mdx +++ b/content/data/esign/name-match.mdx @@ -34,6 +34,45 @@ Below are some sample accept and reject scenarios: 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) -Please note that this feature is independent, and should you not opt for it, there will be no changes to the normal eSign flow. +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: + +```json +...... +"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. From 5109057b66c072985ec2cefd3aeae96de546c976 Mon Sep 17 00:00:00 2001 From: Piyush Das Date: Tue, 15 Apr 2025 13:57:44 +0530 Subject: [PATCH 2/3] formatted code block with tag --- content/data/esign/name-match.mdx | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/content/data/esign/name-match.mdx b/content/data/esign/name-match.mdx index 6fca628f..c048f2af 100644 --- a/content/data/esign/name-match.mdx +++ b/content/data/esign/name-match.mdx @@ -44,7 +44,8 @@ This data will be optionally available in the following ways: A sample name match data in API response and notification will look like this: -```json + +{` ...... "signers": [ { @@ -63,7 +64,8 @@ A sample name match data in API response and notification will look like this: } ], ...... -``` +`} + Possible values for the `match_type` key: From dc3dc331a2b1b9ac489ae479a9e73838c7b4b715 Mon Sep 17 00:00:00 2001 From: Aditya Gannavarapu Date: Wed, 16 Apr 2025 09:39:17 +0530 Subject: [PATCH 3/3] Remove extra characters --- content/data/esign/name-match.mdx | 6 +----- 1 file changed, 1 insertion(+), 5 deletions(-) diff --git a/content/data/esign/name-match.mdx b/content/data/esign/name-match.mdx index c048f2af..a4c8f6c7 100644 --- a/content/data/esign/name-match.mdx +++ b/content/data/esign/name-match.mdx @@ -46,10 +46,8 @@ A sample name match data in API response and notification will look like this: {` -...... "signers": [ { - ...... "nameMatchDetails": { "optimisticMatchOutput": { "match_percentage": 100.0, @@ -60,10 +58,8 @@ A sample name match data in API response and notification will look like this: "match_type": "COMPLETE_MATCH" } }, - ...... } -], -...... +] `}