Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 6 Current »

To define the place for the Signature, signer's name, or real date of the agreement execution, provider-specific templates have to be used. This article describes the available Document signing integrations and relevant settings.

Adobe EchoSign 

https://acrobat.adobe.com/us/en/sign.html

You can put any AdobeSign tag into a document template directly. No additional development is required.

Adobe EchoSign Signer Roles

In AdobeSign, each signer is identified with a unique role ID.

The role IDs should be the following:

  • signer1 - for the borrower user

  • signer2 - for the co-applicant user

These role IDs must be used when preparing document templates for AdobeSign

Adobe EchoSign Text Tags

Service uses text tags in the following format:

  • {{Sig_es_:signer1:signature}}

  • {{Sig_es_:signer2:signature}}

NOTE: The font size determines the size of the signing field. The larger font - the larger field for signing.

If text tags are not defined in the document, signature placeholders will be placed at the bottom of the last page

SignNow 

Tags need to be defined in the System. Users can add only hard-coded tags to a document.  

https://www.signnow.com/features/add-text-tags-to-the-document

https://docs.signnow.com/sn/ref/smart-fields/postdocumentdocumentidintegrationobjectsmartfields


Using roles in code:

https://github.com/signnow/SignNow.NETSDK

Radio button example

Account Type:   
Saving {{t:r;r:y;o:"Customer";rn:"Group_name";rv:"Saving";checked:0;}}
Checking {{t:r;r:y;o:"Customer";rn:"Group_name";rv:"Checking";checked:0;}}


SignNow Signer Roles

In SignNow, each signer is identified with a unique role ID.

The role IDs should be the following:

  • Customer - for the borrower user

  • CoApplicant - for the co-applicant user

These role IDs must be used when preparing document templates for SignNow


SignNow Text Tags

Service uses text tags in the following format:

  • {{t:s;r:y;o:"Customer";w:100;h:15;}}

  • {{t:s;r:y;o:"CoApplicant";w:100;h:15;}}

  • The tag can be made as non-required:

  • {{t:s;r:n;o:"Customer";w:100;h:15;}}

ESignLive

This signature provider no longer belongs to the Silanis company. Now OneSpan owns this product. ESignLive supports TextTags as well as the mentioned above signature providers. It supports multiple signers and signature placeholders. All documentation is available on the page: https://community.onespan.com/documentation/onespan-sign/guides/feature-guides/developer/text-tag-extraction

ESignLive Signer Roles

In ESignLive, each signer is identified with a unique role ID.

The role IDs should be the following:

  • Signer1 - for the borrower user

  • Signer2 - for the co-applicant user

These role IDs must be used when preparing document templates for ESignLive

ESignLive Text Tags

The service uses text tags in the following format:

  • {{esl:Signer1:capture:offset(0,-20),size(150,40)}}

  • {{esl:Signer2:capture:offset(0,-20),size(150,40)}}

If text tags are not defined in the document, signature placeholders will be placed at the top of the first page.

If text tags are defined for the borrower, but are not defined for the co-applicant, the co-applicant will be added as a reviewer of the document - he can watch, but can't make a signature


  • No labels