Document Escrow or Signature Escrow is a service where we won't release any documents until all signatures are complete, and approved by the other party. Note that iSignature is not a legal escrow service; this is provided as a convienience. While we will uphold the rules of the escrow unless brought before court, be advised that our service is intended for everyday signature use and not a replacement for another legal escrow service. That said, we will not break the rules of an escrow for any reason whatsoever unless ordered by a court, and in such legal proceedings, will provide a complete and thorough transaction record of the associated file.

Document / Signature Escrow is suitable for transactions or business below a threshold at which legal proceedings are unlikely due to cost.

Each and every signature generated is stamped with an "Audit Code". This code, when typed into our Audit system, will provide all the details of the signature. Signatures are obfuscated and watermarked to prevent mishandling. We are refining this system to maintain privacy while providing additional data regarding authentication to such parties accepting the signature, i.e. a funding bank in the case of a mortgage, or a Real Estate board in the case of real estate transaction.

To obtain a key in order to audit signatures, we require faxed proof of your position with the company or entity for whom you work. If we have any doubts to the nature of the request, we will contact the signature requestor for permission.

Practically, no. If you have military-grade cryptography experience AND about 1200 computers, and access to a signor's account, knowledge of their personal friends enough to identify them, and if defined in the security settings, access to their credit card and/or telephone, well, then yes. You could. If you had all that.

That said, we maintain intrusion detection code and robust security so we can determine if someone were to attempt to hack in to alter data. No server, not even top-tier servers are immune from a Denial Of Service attack, however, in such extremely unlikely event, the server will self destruct and later be backed up from DVD physical storage.

It's far more difficult than forging an ink signature, as we provide auditing data. We also have IP tracking and IP Geolocation, and challenge questions created by the requestor. We use cel phone key notification, so for someone to gain access to the document needing to be signed would require that the thief or forging party would (a.) know the answer to the challenge question, (b.) have extensive software hacking skills beyond 99.999% of all internet users sufficient to forge the bios of a file (virtually impossible), an IP address, browser statistics, (c. ) would need to be in posession of the cel phone of the signor and (d.) would need to do all of the above at a time/date capable of fooling the auditing party and (e.) the forger would need to know how the signor typically signs their name, as there is a direct correlation between one's ink signature and the signatures generated by hand using a mouse.

While signatures generated using a mouse are clearly different, the sequence and style one uses offline shows up in the way one uses a mouse. Compare it and see!

So far we have zero cases of attempted forgery, and should any auditing party have doubts as to the legitimacy of a signature, please contact us and we'll be happy to cooperate fully with a thorough investigation. Our reputation depends on our ability to deliver a dependable service, and so we are constantly refining our systems to provide the utmost in security and privacy.

We believe and can demonstrate that it is more difficult to forge an iSignature than it is to forge a regular ink signature.

Our Application Programming Interface is the world's simplest API - even a designer can master this. You just format a URL. This makes it very easy to integrate into your own website, CRM, or application.

Method #1: For dynamically produced PDFs, or for a simple, easy installation of any PDF.

Here's an example link: http://iSignature.com/RP/144DG/http://www.SomeOtherServer.com&doc=123456.pdf

Let's split that into parts, by color:
http://iSignature.com/: base URL to our server
RP/: this just tells our server to call "Remote Page" and must be present.
144DG: This is your account number, followed by a two-letter code for a template of signature locations. If no template is called, i.e. (if it said just /144/) then no pre-set signature locations would be defined and it would be up to the consumer (signor) to correctly identify where the signatures belong, which means if they miss any, you'll need to go back. To create a template, just load a document and drag in the "sign here" stickers as usual, but then hit the button for "Save as Template" within the signature-placement application.
http....c=123456.pdf: this is the complete URL to the PDF on your server.

As soon as someone clicks this URL, we'll retrieve the PDF from your server, convert it, load the corresponding template for them to sign, and store it to your account. Obviously the user must create an account or log in, and the document will be auditable as usual.

Note that any complete URL must not exceed 256 characters total. If needed, you can use a service such as TinyURL.com to crunch down long URLs into something manageable and emailable (i.e. if emailing to someone, we recommend this to avoid "line wrapping" which can "break" the URL).

Signed documents are stored to your account as usual. We are working on an API for FTP retrieval of signed documents where we'll push the document to your server via secure FTP. Til then, you must login and pick up the document.

Method #2: If you have a contract you often need signed, and only a few things change within it. Example: contract is the same but the name, address, price, change per client.

Think of a "Variable" as a tiny bookshelf. It will contain whatever you say belongs in it. Within iSignature, you must first create the bookshelf, then define the data that lives in each "record". This also allows for server interaction, for those that know what that means.

Here's an example link: http://iSignature.com/SD/5/144DG/name=John%Doe&price=13000&address=123%Main%Street&city=Anytown&state=NY&zip=90210

Let's split that into parts, by color:
http://iSignature.com/: base URL to our server
RP/: this just tells our server to call "Stored Document" and must be present. At time of upload, you must also
5/: this is the number assigned to your stored document. It typically refers to a blank contract, not containing any names, prices, addresses
144DG: This is your account number, followed by a two-letter code for a template of text (variable) and/or signature and/or initial locations. If no template is called, i.e. (if it said just /144/) then no pre-set signature locations would be defined and it would be up to the consumer (signor) to correctly identify where the signatures belong, which means if they miss any, you'll need to go back. To create a template, just load a document and drag in the "sign here" stickers as usual, but then hit the button for "Save as Template" within the signature-placement application.
name=John%Doe&price=13000&address=123%Main%Street&city=Anytown&state=NY&zip=90210: these are the variables you have set up in advance.

As soon as someone clicks this URL, we'll retrieve the PDF from your server, convert it, load the corresponding template for them to sign, and store it to your account. Obviously the user must create an account or log in, and the document will be auditable as usual.

Note that any complete URL must not exceed 256 characters total. If needed, you can use a service such as TinyURL.com to crunch down long URLs into something manageable and emailable (i.e. if emailing to someone, we recommend this to avoid "line wrapping" which can "break" the URL).

Signed documents are stored to your account as usual, along with the corresponding variables.