Versions Compared

Version Old Version 1 New Version Current
Changes made by

Austin Logie (Unlicensed)

Rich Walker

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. The user clicks the "Sign" button, which captures the data needed for signing.

    1. The Sign button event displays the Quik! Form's e-sign popup screen.

    2. User enters relevant signing data and clicks the SEND button.

    3. The SEND event posts the form data directly to Quik! (https://websvcs.quikforms.com/rest/ESignatureesignature/signix/sign)

  2. Quik! starts a transaction with SIGNiX

    1. Quik! uses the provided Signix credentials information stored by Quik! and then calls the Signix Api to start the transaction

  3. Signix responds with either a success or a failure. If a failure is returned, the Quik! Form (HTML window) will alert the error message from SIGNiX.

  4. If successful, Quik! responds to user's Quik! Form (HTML window) with a successful message.  

    1. The transaction's metadata, including the SIGNiX Transaction ID, is stored with the QFVUNID in the Quik! system for later retrieval by the customer via web service as a backup method for retrieving e-sign transactions.

  5. If using CallBack Url, the user's Quik! Form posts the SIGNiX response to the Customer's SignCallBackURL in JSON format along with any status message returned by the signing process

    1. The customer's server should then respond in JSON format to the user's form with a StatusCode and StatusMessage properties. 

  6. Assuming a successful transaction was started, signers will begin receiving emails from Signix inviting them to e-sign the forms.

  7. Once everyone has signed, customer can independently access and download the documents from Signix by logging into their Signix account.