Smartstaff
2,460
edits
Changes
m
Client The client will need to create their '''Identity Verification Workflows''' on their own '''DocuSign''' account under “Admin – Signing and Sending – Identity Verification”. DocuSign has a list of verifying ID options for different regions, e.g. method (such as passport, driver license, bank idID, etc). When creating a new ID Verification Workflow, there are different DocuSign settings to be configured. Accepted IDs depend on different regions. You can review them by going to the '''Advanced settings''' of each of the ID verification workflow configuration pages. When viewing each ID verification workflow, there is a '''Configuration ID for API integrations''' at the bottom of the screen. The client will need to provide this in their Web Page View field for each recipient. You can use different identification workflows for different recipients (Example: one using eID, one using phone, and one without the need to verify). ===Phone Authentication===The client will need to create their '''Identity Verification Workflows''' on their own '''DocuSign''' account under “Admin – Signing and Sending – Identity Verification”. The phone number of recipient is required to be added in the WPV inside the verification syntax. DocuSign will use this number to send SMS or call the recipient for verification purpose. Syntax to be applied to Web Page View There is a new syntax for this identity verification starting with “Verification” where the syntax is delimited by a semicolon ( ; ). ====ID Verification (IDV)==== # Email# Configuration ID for API integrations (workflow ID in the DocuSign Identify Verification) <pre><!--Verification fake2@gmail.com;4ggg7cce-6c25-82e8-4444-8888d18947ef --></pre> ====Phone Authentication==== # Email# Configuration ID for API integrations (workflow ID in the DocuSign Identify Verification)# phone=[country code]-[phone number without symbols] for each recipient <pre><!--Verification fake1@gmail.com;9bbb5cce-6c25-42d6-8934-2799d18947ef;phone=1-6475558888--></pre> Since phone authentication also needs a workflow ID, the only way for us to differentiate is if you tell us this is for phone authentication with “phone=”. DocuSign requires separate values for country code and phone number. ====Knowledge-Based Authentication (US residents only)==== From DocuSign: Knowledge-based authentication requires recipients to answer detailed questions about themselves based on data available in public records (such as their current and former addresses). The DocuSign eSignature KBA feature uses an identity verification service from LexisNexis Risk Solutions that validates user identities in real time. # Email# ID Check (Enter the string exactly as ID Check. This is the syntax from DocuSign to differentiate this type of authentication) <pre><!--Verification fake2@gmail.com;ID Check--></pre> ====Access Code Authentication==== # Email# accesscode (please enter the string exactly as '''accesscode''')# value=BQ908C (The text the user must enter when they are asked for the Access Code by DocuSign. For example, if a custom field value is used as the access code for recipients, include the value in the syntax.)
When creating a new ID <pre><!--Verification workflow, there are different options to be configured, note: these are DocuSign settingsfake3@gmail.com;accesscode;value=BQ908C --></pre>
Accepted IDs depend on different regions, you can review them by going to the '''Advanced settingsNote:''' of each If the workflow ID of the DocuSign Identification Verification Workflow configuration settings pageis not found in client’s DocuSign account during submission of a signature request, DocuSign will return an error.
When viewing each Reference for DocuSign ID verification workflow, at the bottom of the screen there is a '''Configuration ID for API integrations''', client will need to provide this in their WPV for each recipient, you can use different identification workflow for different recipient, egVerification: https://www. One using eID, one using phone, one no need to verifyyoutube.com/watch?v=bJw4kzvhXK0
→Identity Verification
==Identity Verification==
Some recipient/signer authentication methods are supported: ID Verificationverification, Phone Authenticationphone authentication, Access Code Authenticationaccess code authentication, Knowledgeknowledge-based authentication (US residents only). To use this feature, clients will need to have the Identification Verification feature enabled in their DocuSign account.Log in to '''DocuSign''' account, under “Admin – Signing and Sending – Identity Verification”.
For '''ID Verification''' verification and '''Phone Authentication'''phone authentication, a DocuSign workflow has to be created. For instructions: https://support.docusign.com/s/document-item?language=en_US&bundleId=yff1696971835267&topicId=uhm1697826856678.html&_LANG=enusNOTE'''Note: the ''' The actual verification is on DocuSign’s side, recipient will be presented with different options to verify their identity based on which verification or authentication method is configured for the recipient in the Web page view Page View custom field.
===ID Verification===
==Generating Fillable PDF Forms for E-Signatures==