Skip to content

Electronic Signatures

Provider Support

Out of the box Luna has support for the following electronic signature providers:

  • Adobe Sign
  • Dropbox Sign (formerly HelloSign)

Info

Support for other providers can be requested; Luna's modular design enables quick integration development.

The only requirement is that the prospective electronic signature provider must have a suitable API.

The following features must at a minimum be supported:

  • Create signature request
  • Cancle signature request
  • Check signature status
  • Expire/revoke signature requests

Desirable features:

  • Callback event support; use to provide real-time electronic signature status updates and trigger actions accordingly. i.e. the prospective provider posts a callback event back to a integration when something changes on the signature request.
  • Without this signature requests would have to be polled for changes.

Providers Configuration

Each provider provides a set of options the system administrator to setup the integration:

  • API Region Code
    • Examples: eu1, us1 or custom-domain.eu1 to validate see the url once logged in to Adobe Sign Dashboard.
  • API token
  • Client ID
  • Client secret
  • Redirect URI
  • API token
  • API URL
  • Client ID
  • Client secret
  • Redirect URI
  • Test Mode

Template Document Interaction

All electronic signature provide a common set of template tags. When used in a template document and dispatched to the client the tags are converted to the providers tag format.

Electronic signature related template tags include:

  • {{client_[signer_count]_signature}}
  • {{client_[signer_count]_signature_optional}}
  • {{client_[signer_count]_sign_date}}
  • {{client_[signer_count]_freetext_[signer_freetext_count]}}

Note

[signer_count] represents the number of clients on a enquiry/case.