Enable Mobile Signing

 Signature mobileSignature = SignatureBuilder.mobileCaptureFor("mail32@example.com")   .onPage(0)   .atPosition(100, 100)   .build(); 

To download the full code sample see our Code Share site. You can also see this feature in our Interactive Demo. If you're unable to use Mobile Capture Signatures, contact our Support Team to have it enabled for your account.

The OneSpan Sign electronic signature mobile app provides a convenient way to send and e-sign documents from your mobile device. Users that already have a OneSpan Sign account can access their account from the mobile app.

Adding a Mobile Capture Signature

To add a mobile capture signature you need to build a Signature object. The following code will do this:

 Signature mobileSignature = SignatureBuilder.MobileCaptureFor("mail32@example.com")   .OnPage(0)   .AtPosition(100, 100)   .Build(); 

Results

Once your signers are ready to sign, they will have the option to either sign using their mobile device or sign directly through your application.

To download the full code sample see our Code Share site. You can also see this feature in our Interactive Demo. If you're unable to use Mobile Capture Signatures, contact our Support Team to have it enabled for your account.

The OneSpan Sign electronic signature mobile app provides a convenient way to send and e-sign documents from your mobile device. Users that already have a OneSpan Sign account can access their account from the mobile app.

Adding a Mobile Capture Signature

The sample JSON payload below shows you how to create a package with a mobile capture signature on a document.

HTTP Request

POST /api/packages

HTTP Headers

Accept: application/json   
Content-Type: multipart/form-data   
Authorization: Basic api_key 

Request Payload

-- -- --WebKitFormBoundary1bNO60n7FqP5WO4t Content - Disposition: form - data;
name = "file";
filename = "testDocumentExtraction.pdf"
Content - Type: application / pdf % PDF - 1.5 % µµµµ 1 0 obj < >>> endobj....-- -- --WebKitFormBoundary1bNO60n7FqP5WO4t Content - Disposition: form - data;
name = "payload" {
   "documents": [{
      "approvals": [{
         "id": "ExampleSignatureId",
         "role": "Signer1",
         "fields": [{
            "page": 0,
            "top": 100,
            "subtype": "MOBILE_CAPTURE",
            "height": 50,
            "left": 100,
            "width": 200,
            "type": "SIGNATURE",
            "name": "ExampleSignatureId"
         }],
         "name": ""
      }],
      "id": "sample-contract",
      "name": "Example document"
   }],
   "status": "SENT",
   "type": "PACKAGE",
   "roles": [{
      "id": "Signer1",
      "type": "SIGNER",
      "signers": [{
         "email": "[email protected]",
         "firstName": "John",
         "lastName": "Smith",
         "id": "Signer1"
      }],
      "name": "Signer1"
   }],
   "name": "Mobile Capture Example Package"
}-- -- --WebKitFormBoundary1bNO60n7FqP5WO4t--

For a complete description of each field, see the Request Payload table below.

Response Payload

 {   "id": "9sKhW-h-qS9m6Ho3zRv3n2a-rkI="   } 

Results

Once your signers are ready to sign, they will have the option to either sign using their mobile device or sign directly through your application.

Request Payload Table

Property	Type	Editable	Required	Default	Sample Values
status	string	Yes	No	DRAFT	DRAFT / SENT / COMPLETED / ARCHIVED / DECLINED / OPTED_OUT / EXPIRED
type	string	Yes	No	PACKAGE	PACKAGE / TEMPLATE / LAYOUT
name	string	Yes	Yes	n/a	Mobile Capture Example Package
documents
name	string	Yes	No	n/a	Example document
id	string	Yes	No	n/a	sample-contract
approvals
fields
subtype	string	Yes	No	n/a	FULLNAME / INITIALS / CAPTURE / MOBILE_CAPTURE / LABEL / TEXTFIELD / TEXTAREA / CHECKBOX / DATE / RADIO / LIST
type	string	Yes	No	n/a	SIGNATURE / INPUT
extract	boolean	Yes	No	false	true / false
height	integer	Yes	No	50	50 / 100 / 150 ...
left	integer	Yes	No	0	50 / 100 / 150 ...
page	integer	Yes	No	0	0 / 1 / 2 ...
top	integer	Yes	No	0	50 / 100 / 150 ...
width	integer	Yes	No	200	50 / 100 / 150 ...
role	string	Yes	No	n/a	Signer1
id	string	Yes	No	n/a	ExampleSignatureId
roles
id	string	Yes	No	n/a	Signer1
name	string	Yes	No	n/a	Signer1
type	string	Yes	No	SIGNER	SIGNER / SENDER
signers
email	string	Yes	Yes	n/a	[email protected]
firstName	string	Yes	Yes	n/a	John
lastName	string	Yes	Yes	n/a	Smith
phone	string	Yes	No	n/a	514-555-8888
id	string	Yes	No	n/a	Signer1
company	string	Yes	No	n/a	Acme Inc.
title	string	Yes	No	n/a	Managing Director

To download the full code sample see our Code Share site. You can also see this feature in our Interactive Demo. If you're unable to use Mobile Capture Signatures, contact our Support Team to have it enabled for your account.

The OneSpan Sign electronic signature mobile app provides a convenient way to send and e-sign documents from your mobile device. Users that already have a OneSpan Sign account can access their account from the mobile app.

Adding a Mobile Capture Signature

To add a mobile capture signature you need to build a Signature object. The following code will do this:

  String roleId = 'b9bb2f89-4a27-4c9a-80fc-aaad70f8cac8';
ESignLiveAPIObjects.Field field_mobile_capture = new ESignLiveAPIObjects.Field();
field_mobile_capture.id = 'field_mobile_capture';
field_mobile_capture.type = 'SIGNATURE';
field_mobile_capture.subtype = 'MOBILE_CAPTURE';
field_mobile_capture.page = 0;
field_mobile_capture.top = 100.0;
field_mobile_capture.left = 50.0;
field_mobile_capture.width = 150.0;
field_mobile_capture.height = 50.0;
ESignLiveAPIObjects.Approval approval_mobile_capture = new ESignLiveAPIObjects.Approval();
approval_mobile_capture.fields = new List < ESignLiveAPIObjects.Field > {
   field_mobile_capture
};
approval_mobile_capture.id = 'approval_mobile_capture';
approval_mobile_capture.role = roleId;

Results

Once your signers are ready to sign, they will have the option to either sign using their mobile device or sign directly through your application.