You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
added details of name match data in api response and eSign notification response as an optional feature (#254)
* added details of name match data in api response and esign notification response as an optional feature
* formatted code block with <CodeBlockWithCopy> tag
* Remove extra characters
---------
Co-authored-by: Piyush Das <piyushdas@Setus-MacBook-Pro.local>
Co-authored-by: Aditya Gannavarapu <adityagannavarapu.67@gmail.com>
Copy file name to clipboardExpand all lines: content/data/esign/name-match.mdx
+38-1Lines changed: 38 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -34,6 +34,43 @@ Below are some sample accept and reject scenarios:
34
34
3. If one name contains only initials (name1 = Rakesh Kumar Singh, name2 = R K S)
35
35
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)
36
36
37
-
Please note that this feature is independent, and should you not opt for it, there will be no changes to the normal eSign flow.
37
+
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.
38
+
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.
39
+
40
+
This data will be optionally available in the following ways:
0 commit comments