We are using REST API to create envelopes and the Template is set up in DocuSign, with signer roles etc. Our customer wants to be able to decide in every separate occasion whether to use InPerson signing or send the signing link via email to the recipient.
Currently/originally we implemented Embedded signing, but our customer wants the "security question" (e.g. ask for driver's license number) to be there before the signing. So that they can prove that the buyer has actually been there to sign.
Is there a way to do this? I have the DocuSign Template set up with "needs to sign" option, but when sending the request to create a new envelope, somehow change a signer to be InPerson and trigger a workflow for that?
I managed to find information about Embedded signing and clientUserId, but is there a way to deliver information for example to the Certificate of Completion, like with the InPerson case with the input showing there?
In order to switch from In-Person (embedded) to remote signing and vice-versa, you will need to use the property ClientUserId. It is well described in the DocuSign article Embedded Signing.
If you're willing to switch after the envelope is created, see my recent question here that deals with the same issue.
To implement the "security questions", DocuSign offers multiple authentication option. It seems to me that you are looking to use the "ID Check" authentication here
In C#, it would look like this when you try to implement ID Check for a given signer :
signer.RequireIdLookup = bool.TrueString;
signer.IdCheckConfigurationName = "ID Check $";
Lastly, for your question regarding the authentication method and the certificate of completion, the Embedded signing article I mentioned above explains well what happens for the authentication method in the certificate completion below :
The authenticationMethod is an enumerated value that indicates the convention used to authenticate the signer. Since, with Embedding, you are telling Docusign that you are handling authentication this is your way of telling the platform how you authenticated the recipient. This information will also be included in the Certificate of Completion, a PDF that is automatically generated for every completed envelope.
Related
I am embedding the signature request with DocuSign in my application. Is there any way that I can allow customers to change embedded signature responsibility(forward the document to someone else)?
I have already checked the setting to enable recipients to Assign to Someone Else according to this link: https://support.docusign.com/s/document-item?language=en_US&rsc_301&bundleId=yca1573855023892&topicId=uin1573855010064.html&_LANG=enus
enter image description here
Another question, if it is impossible then is there any way that customers can save all the changes that they have made so far?
Embedded Signing doesn't directly support signers changing signing responsibility. This is because out-of-the-box if a captive signer did so, the recipient they changed it to would not have a way to access the envelope.
The most straightforward way to resolve this would be to change the signer to a Remote signer so that the Signer Reassign function you've linked would work.
If it's necessary for a signer to remain embedded/captive, but still have the ability to reassign, you would need to build out functionality in your application that would (outside of DocuSign)
prompt the recipient for the new signer's info
make an UpdateRecipient call on the envelope to change the name/email/clientUserId as needed
Notify the new recipient that they have an envelope to sign
Grant the new recipient access to the envelope.
I'm trying to find out if it is possible using the DocuSign API to create a signing request that is sent to multiple parties for signature with nobody seeing the other parties signatures until they have all signed?
Once all parties have signed I would download the final PDF and review this then send to all parties, but not sure if it's possible to hide these as it goes from one recipient to another?
Well, one technique would be for each signer to have their own signature page for the document set. The signature page would actually be a separate document within the envelope. (But signers are not particularly aware of the fact that there can be multiple documents in an envelope since they all flow together.)
You'd use the document visibility feature so each signer would only see the main document(s) and their own signing page.
Try it out first via the web tool, docs within the developer sandbox. Then automate via the API.
I am trying to integrate Docusign in my Web application. The website workflow will be as follows:
Users visit my website and log in.
Users will be given the option to choose Docusign Templates.
After selection, users need to sign that document.
After a successful signing, the signed document is sent to some authority.
My problem is how can I link my users to Docusign to sign. Does every user needs to have an account for embedded signing?? I need some help in understanding the flow of authentication and signing in DocuSign REST API. I have gone through the documentation but didn't understand properly. When I try to use the auth grant GitHub code to understand the flow. After logging in, it throws a null pointer exception. Please, someone, help me.
You can find code example in different languages to do what you're asking (sign from a template). You will want to use embedded signing so that the user sign as part of the app and not remote signing (via email).
As for your authentication question, no, signers never need to be part of the account. The sender can be a single user that is "sending" envelopes that are embedded in the app. So while there's no sending technically, you can think of it this way.
Hope this makes sense, please ask additional questions if not clear
recipientID is a GUID uniquely used to identify a recipient in DocuSign. When you create an envelope, each recipient should have one.
"and If the same name+email combination comes again, will it get the same signature or generate a new one?" It will remember it if they have an account.
I have a web app which I use to collect some information from a user (not name or email) and then plan on having them electronically sign a document via DocuSign immediately online (not via email).
In order to get a signing url (aka recipient view), it appears I have to provide a definition of a recipient. Part of the definition of a "recipient" is a username and email address. Is this true?
Does the DocuSign API/SDK require me to provide an end-user's (aka signer) name and email address? It seems like the API/SDK will always return a validation error if I don't provide these things. What if I don't have that information?
You need to provide the signer's name and their client_user_id within your app. You also need to supply an email for them.
The client_user_id must be unique per signer.
If you have the signer's email, use it.
If you don't, use a unique email address that includes the client_user_id to guarantee uniqueness. Eg noreply_{client_user_id} #your_company.com
Added
Re comments:
Yes, an email address is required by DocuSign to generate an embedded signing ceremony. But it is okay to fake one (that includes your app's client_user_id for the signer) if you don't, in fact, have the signer's email.
Re: Why is this the case? Because the email and name are used by DocuSign to index the "captive signer" (someone who signs your account's envelopes but doesn't have their own account with DocuSign). That's why a fake email must be unique to this person.
This technique of using name + email to identify people enables DocuSign to, for example, not require the signer to agree to the consumer agreement to use eSignatures on second and subsequent document signings with your account. -- This provides a better UX.
Since it is very common for web apps to know their user's email, this is usually not a problem. But if you don't know the signer's email, then everything works fine with a fake email as described above.
Added more
Re:
please provide a source for DocuSign being Okay with fake email address in this case? I mean is it legal?
Currently this technique for providing a fake email address for embedded signing (when a real email address is not available), is not documented on the DocuSign web site. I will add it to the embedded signing recipe when I revise it in 2017.
Re legality: the important issue is how your app authenticates the signer. Email is one way. Depending on the use case, email authentication may or may not provide a strong enough assurance to the relying party (the person who receives the signed document).
But we digress. Even if you do have a person's email address, it is common to authenticate the person beyond using their email. DocuSign has many different types of additional authentication built-in and easy to use including 2FA via SMS, pre-shared secret, in-person signing (which can include in-person verification of government ID), e-notary, digital certificates, telephone authentication, knowledge based authentication, and more. Most of these can be included with embedded signing if you wish.
Or your app (which is using embedded signing) can itself authenticate the person. When someone signed up for your app, did they have to first prove their identity? That was the authentication step. If no one else can log in as them, then they're still authenticated when you give them the embedded signing ceremony from DocuSign.
I am using the DocuSign API in an embedded manner. I create an envelope and add signers, the first signer always being set as embedded. This allows me to retrieve a URL that is then embedded in an iframe.
However, I also wish, to trigger an email (as soon as the envelope has been created, NOT upon completion) that gets sent to the primary recipient/signer as if they were a nonembedded signer.
I tried adding the signer twice, with the same role, to the recipients, but that didn't work. No email was sent.
Is there a way to accomplish this?
I believe there is a setting to enable this but that it needs to be enabled by someone on DocuSign's side, like your account manager. If you do not have an account manager yet please respond to the auto-generated emails that were sent out to you once you created your account, you should have 3 of them.
The account settings available are only for Completion emails. However, the REST API also supports an embeddedRecipientStartURL parameter on the signer object that triggers a normal DocuSign email. The value of this parameter is the URL that should be included in the email. This means you can link back to your own application and request the recipient view as normal.
Check here for more detail: Signer embeddedRecipientStartURL. Note: if you set this to a value of "SIGN_AT_DOCUSIGN" then DocuSign will provide its own URL and take care of signing. The trade-off is that you won't be able to initiate any bespoke authentication you are doing in your own application.