engg_nayan | Posts: 34

Signing ceremony is required to collect signature or ‘Click to Sign’ option.

0 votes
Signing ceremony is required to collect signature or ‘Click to Sign’ option from user using eSign UI. When user chooses ‘Click to Sign’ option, he or she does not need to sign in signing text pad. Is it possible to pass ‘Click to Sign’ option through any API instead of starting signing ceremony and click to sign on the eSign screen? Our scenario Steps are explained below: 1. Create package in eSign system with ‘Click to Sign’ option. 2. We create our own UI page that contains click to sign option check box. We don’t need to show any documents to customer or text. 3. User goes to our own page (not eSIgn UI) and click the checkbox to complete signature process. 4. Once user click the checkbox, we will call some eSign API to send ‘Click to Sign’ option along with required information like IP number, date signed..etc provided by esignLive. 5. ESign system will get the ‘Click to Sign’ option and embed signature in uploaded document. Later we can download signed document from eSign system.

Duo_Liang | Posts: 3776

Reply to: Signing ceremony is required to collect signature or ‘Click to Sign’ option.

0 votes
Hi Engg, Per your workflow, it seems Bulk Sign for a Signer guide was what you are looking for. This feature allows you to generate an temporary signer session token that can be set in request header, and to call APIs on behalf of your signers. You can find the basic usage example in our guide and here's few points that may interest you: (1)you mentioned that your signers have options to skip/not signing few signatures, if I understood it correctly, you probably need to set non-required signatures as optional. (Guide here) and we need to discuss about the point two below. (2)Once you generated the signer's session token/id, there're multiple APIs allowing you to programmatically sign "Click-to-Sign" boxes. Option1 allows you to sign per document which is more straight-forward and recommended in our guide. But the defect was that all signatures on that document will all be signed.
HTTP Request
POST /api/packages/{packageId}/documents/signed_documents

HTTP Headers
Accept: application/json
Content-Type: application/json
Cookie: ESIGNLIVE_SESSION_ID={sessionToken}

Request Payload

{
  "documents": [
    {
      "id": "default-consent"
    },
    {
      "id": "6489338764d20465"
    }
  ]
}
To adjust to this scenario, it would be better that if you can first let your signer choose from which signatures to sign, then create your package with only necessary signatures and programmatically bulk sign all. Or if you still want to sign per signature, for each document, you can #1 loop through to sign signatures #2 confirm the document after all required signatures are signed. This method was a little bit complex so it's better that you give your thoughts on above options before we came here. (3)For "programmatically sign on behalf of your signer" scenario, IP address would be shown as your application's and the signing date was the moment you call the API. And please always consult your legal department before you follow this solution. Hope this could help! Duo

Duo Liang OneSpan Evangelism and Partner Integrations Developer


Hello! Looks like you're enjoying the discussion, but haven't signed up for an account.

When you create an account, we remember exactly what you've read, so you always come right back where you left off