Step 3

​This step explains how to sign the document, provides details on the UI options available to display the document and suggests some further steps.

Topics found on this page:

Sign the document

After retrieving the sign URL, it can be presented to the signer and it will display the E-Signing service user interface (UI) with the document. The E-Signing service UI can be presented in two modes: Embedded or Standalone. E-Signing service can be requested to display the UI in either of these modes.

 

Embedded user interface

Embedded option allows customers to present E-Signing service UI within their own web UI. To access the embedded UI, the following URL can be used (for customer test):

https://www.sign-preprod1.nets.eu/sign/index.html?ref=<sign-reference>

The sign reference is retrieved from sign URL. Refer Step 2 for details on retrieving sign URL. Note that the sign reference is sent through the ref parameter for embedded mode.

The page that is returned by the above sign URL can be styled with customer's own look-and-feel to fit their web UI. One example is to display the response from embedded UI sign URL into an iframe in the customer’s web UI.

A simple iframe can be setup with similar HTML code as below:  

 <iframe name="E-Signing" src="https://www.sign-preprod1.nets.eu/sign/index.html?ref=E63652CDEF590BAB30F5B225E1AA8A09977F890E"></iframe>

The E-Signing demo app uses embedded mode to display the E-Signing service UI for the signer to sign. The PDF document that was sent along with sign order is displayed inside the requested eID client (BankID (NO), for the purpose of this document) as shown in the screenshot below:

 ​E-Signing step 3.PNG

Standalone user interface

In the standalone UI, the E-Signing service renders the user interface using the Nets E-Signing visual interface. To access the standalone UI, the following URL can be used (for customer test):

https://www.sign-preprod1.nets.eu/sign/index.html?sref=<sign-reference>

The sign reference is retrieved from sign URL. Refer Step 2 for details on retrieving sign URL. Note that the sign reference is sent through the sref parameter for standalone mode.

The resulting page from the above sign URL does not require any further styling from the customer i.e. the signer can be directly taken to the standalone user interface sign URL.

Check sign order status

To check the status of the inserted sign order in Nets E-Signing service (to find whether the document has been signed or whether the sign order has expired, etc.), the GetOrderStatus XML message should be used.  The E-Signing client API can be used to send this message as well.  A basic GetOrderStaus XML message should contain the following:

  1. MerchantID (as provided by Nets)
  2. OrderID (the unique ID that was sent in the InsertOrder XML message)

Sample code for checking the sign order status is given below.


 ESigningFacade facade = ESigningFactory.INSTANCE.getESigningFacade("Demo Merchant");
 
 GetOrderStatusRequest req = new GetOrderStatusRequest();
 req.setMessageID("esigndemoapp-msgid-3");
 req.setTime(new Date());
 req.setMerchantID(1587);
 req.setOrderID("1587-demo-742819356");

 GetOrderStatusResponse response = facade.getOrderStatus(req);
 String orderStatus = response.getOrderStatus();

Read more about the GetOrderStatus XML message.

Test users

Test user details for the different eIDs can be found at the Test users page.   

The signed document

After signing, an SDO (Signed Data Object) is generated by the Nets E-Signing service. The SDO contains the original document, all signatures on the document and a verification seal. The SDO is contains proof of who and when the document was signed. The signed document should either be sent to the Nets E-Archive service for long term archival or retrieved from Nets E-Signing service.

Nets E-Signing service can also provided the signed document in PAdES (PDF Advanced Electronic Signature) format. PAdES displays all signatures from an SDO in a human-readable format.

  • E-Archive – must be specified while sending InsertOrder XML message. Read more.
  • GetSDO – is the XML message for fetching SDO. Read more.
  • GetPAdES – is the XML message for fetching PAdES. Read more.

​Suggested further steps​​

In the Overview section you can find information about more functionality.  Topics to consider are:

  1. Notifications (XML, e-mail and SMS)
  2. Other possible parameter settings in the sign order, such as:
    1. Archival
    2. Multiple documents
    3. Multiple signers
    4. Identification before signing

Own test and production setup Own test and production setup​

This get started guide and the Nets E-Signing demo app is based on an open test setup. To get your own test and production setup, use the Contact us form.