Create a request with 2 signers with 2 different types of signature methods.

Hi Amine,

If I understood your requirement correctly, I can actually have two signers with different signature types in the same document, see below screenshots made at classic and new sender UI:

And the same design should work with API as well. Let me know if you can't do the same or I missed something.

Duo

thank you, you understood my question,

But we needed to have a signatory who signs with "accept only" and the other signatory who signs with click-to-initial or something else.

I noticed that the 2 signatories must absolutely use "accept only"

If this scenario does not exist yet, is it possible that it will be implemented in the future?

Hi Amine,

Just try to understand your business motivation, is this accept-only signer an internal reviewer so that this person could approve the content then continue the external signing process? I've seen a similar Enhancement Request asking for this, if you preferred, we can add your organization to the list.

Duo 

Hello Duo,

Yes, I would like you to add our organization to the Enhancement Request list.

Thank you

I want to know if there is a known delivery date for the production of this feature?

Hi Duo,

Sorry for the insistence, but we look forward to having this question (last question from amine_desjardins) answered so that we can prioritize our backlog items.

Thanks again,

Hi Duo,

Thanks for the fast answer to that.
Just to clarify our requirement (need) is to have the following:
- The internal signer (Desjardins employee) will signs the document; then
- The external signer (Desjardins’ client) will accept the document.

Thanks again,

Hi Paulo & Amine,

Sorry about the late reply, it seems I didn't receive a notification from Amine's last post. A support ticket has been created on your behalf and our support agencies will help you fill in an Enhancement Request as well as ask if there's any ETA for this feature, in short time. 

If your use case is to have an internal signer acts as reviewer role that (1)the reviewer has to sign first to proceed the signing (2)the signature shouldn't be visible, you could try below steps as a workaround:

(1)create a package with signing order turned on

(2)add one internal signer at index 1, and one external signer at index 2

(3)have a click-to-sign field with size of (0,0) assigned to the internal signer

Below is a sample JSON to create such a package:

{
  "roles": [
    {
      "id": "Role1",
      "index": "1",
      "signers": [
        {
          "email": "[email protected]",
          "firstName": "1.firstname",
          "lastName": "1.lastname",
          "company": "OneSpan Sign"
        }
      ]
    },
    {
      "id": "Role2",
      "index": "2",
      "signers": [
        {
          "email": "[email protected]",
          "firstName": "2.firstname",
          "lastName": "2.lastname",
          "company": "OneSpan Sign"
        }
      ]
    }
  ],
  "documents": [
    {
      "approvals": [
        {
          "role": "Role1",
          "fields": [
            {
              "page": 0,
              "top": 400,
              "subtype": "FULLNAME",
              "height": 0,
              "left": 100,
              "width": 0,
              "type": "SIGNATURE"
            }
          ]
        },
        {
          "role": "Role2",
          "fields": [
            {
              "page": 0,
              "top": 300,
              "subtype": "FULLNAME",
              "height": 50,
              "left": 100,
              "width": 200,
              "type": "SIGNATURE"
            }
          ]
        }
      ],
      "name": "Test Document"
    }
  ],
  "name": "Example Package",
  "type": "PACKAGE",
  "language": "en",
  "emailMessage": "",
  "description": "New Package",
  "autocomplete": true,
  "status": "SENT"
}

During the signing, although it's an invisible signature, the internal signer will still be able to sign it through both classic Signing Ceremony and new Signer Experience:

Although the experience won't be as good as a native feature offers, it's worth a quick try and see if this could fit your requirement.

Duo