Question

I've got a form (Been toying with both an ASP and PHP) that is going to have the info saved to a database and then be signed by docusign ink.

I'm thinking the best way would be to pump out a PDF (Thanks to http://koivi.com/fill-pdf-form-fields/tutorial.php) which would help with the database part but not help with the signing part without PDFTK (Which I barely understand so would like to avoid unless I can get someone to guide me through it).

Is there a better way or am I stuck with this?

Was it helpful?

Solution

I'm working with EchoSign on a similar project, as our CRM currently spits out FDF/PDF files for print. We are now implementing EchoSign, but in order to "sign" the documents you need to use the API, I believe, or manually key data into the DocuSign interface.

What you'll most likely need to do is create a .NET web app (or other application) that will connect to the DocuSign API here, and allow you to "sign" the documents you require.

So essentially your workflow would operate as such:

User enters data into your ASP/PHP Application -->
Stores data into your database -->
Through a link, or some type of function, transmit the data (using API) to DocuSign -->
DocuSign transmits to your client for signage -->
You get signed document back via API or other supplied method.

It's best to have DocuSign handle the signage of the document, as they are certified and take some legal liabilities out of the equation. You want to ensure that whatever you're trying to get signed can hold up in court.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top