App that involves document upload and signature

Question

I am creating a web app that has the following requirements:

There will be multiple administrators working for a tenant. The administrators will upload a document that needs to be signed and select the recipients and click send. The recipients will receive a link by email, click it, log in, view the document and sign it.

I was looking into third party developer API's to help with this such as DocuSign but a few questions/concerns came to mind.

I am going to assume that uploading and setting the areas to sign would need to be done through the docusign site. So would each administrator have to login in to the single tenant docusign account and upload their documents? Seems like it wouldn't be possible.

As an alternative I was thinking about staying away from the third parties entirely and just using an HTML signature pad under the document. However, with this technique the actual document would never be signed so for printing purposes it would look bad.

If anyone can shine some light on this topic that would be great. I am trying to figure out what my options are.

Answer 1

I work for HelloSign. The HelloSign API fits your use case very well and you can try it out for free. https://app.hellosign.com/api/reference

Do you want to have the document uploading take place on your website? If so, that is fine with the HelloSign API. We have a workflow called Embedded Requesting where the administrators could place the signature fields using an editor. We have other ways of placing signature fields as well.

Building it yourself is a lot of effort if you want the signature to be legally valid. You can reach out to HelloSign API Support at apisupport@hellosign.com

Answer 2

(I work for DocuSign.) Using DocuSign or another 3rd party product to handle the signing ceremony and related legal issues is usually a business decision that you'll want to discuss with your colleagues.

Legal issues to be considered include the signer's authorization to use eSignatures for the transaction, authentication, non-reputability, and more.

If you choose to use DocuSign, we have many code examples to help you implement your application.

It is common to "embed" the signing ceremony within your application. Your application can programmatically create the document, or use pre-canned documents.

Signature fields can be placed via anchor text as suggested by @EmmanuelRosa or specific coordinates on the page can be used.

If you have questions about how DocuSign works, contact DocuSign for more information. You can also sign up for a free trial account. When you're ready to develop your software, sign up for a developer sandbox account. More info is available on the DevCenter.

Added: Multiple tenant application

If you're writing an ISV application that you'll sell to multiple customers (tenants) then each customer will usually have their own DocuSign Account. In some cases you'll find that customers will have a pre-existing DocuSign account that they will want to use with your application.

In other cases, your customer's first need for a DocuSign account will be to use it with your application.

If you want, and depending on your volumes, you can resell DocuSign accounts to your customers who need them.

Each DocuSign account can handle any number of users. Users are usually people who send transactions for signing.

Signers do not need a DocuSign account and are not charged for.

You will not want your customers to share a DocuSign account since an account administrator can see all of the account's transactions.

Generally speaking, DocuSign does not charge per account. Instead it charges either per sender or per sent transaction (envelope).

Also note one ISV application written by you will have one Integration Key (same as a client_id) and that application can be used by any number of users, in any number of different DocuSign accounts.

Answer 3

I am going to assume that uploading and setting the areas to sign would need to be done through the docusign site.

Actually, you can do that programmatically :)

I don't recall the details, but I do remember creating a template (*.docx file) of the document that would be uploaded. The template had placeholders for where the signature goes. I believe I used something like {{signature}} as the placeholder. Then, in your code you use the DocuSign API to upload the document and template; There's a way to tell the API what placeholders you used for the various fields.

The signing happens on the DocuSign website, but you can set up the document through the API.

Answer 4

In fact, it is possible to upload to multiple recipients with DocuSign. As the DocuSign documentation is suggesting, here are the steps to follow in order to send to multiple different recipients from the same account (administrators account).

1. Upload your document

From your DocuSign Account, click NEW, then click Send an Envelope.

Click UPLOAD A FILE to upload a document from your computer, or click GET FROM CLOUD to upload a document from an online location. Locate the document you want to upload and click Open.

2. Add the recipient

In the RECIPIENTS field, enter the recipient's name and email address.

3. Add the email subject and message

a. DocuSign automatically adds an email subject when you upload a document. You can edit this subject and add a message to the recipient by filling in the MESSAGE fields.

b. When finished, click NEXT.

4. Add signing fields

The Fields Palette and your document appear. The recipient name is displayed in the Recipients List.

To assign a signature or other field for the recipient, click and drag a field from the Fields Palette and place it on the document.

5. Preview and send your document

Review your document, then click SEND.