Page tree
Skip to end of metadata
Go to start of metadata


The PDF Signing API and related documentation have been updated.

The documentation for Nexus GO PDF Signing has been restructured, and some more examples added. Information about eIDAS compliancy has been added.

New user guides for the PDF Signing portal have been added, see PDF Signing user guide for signers and PDF Signing user guide for administrators.

See more news...

What is Nexus GO PDF Signing?

Nexus GO PDF Signing is a cloud service that enables all your users to make secure digital signatures on PDF documents. The documents are uploaded to and signed in the Nexus GO PDF Signing Portal

You can either let your users sign documents with the built-in methods Nexus Personal Mobile or Swedish BankID, or use existing identities in your corporate directory to let users sign documents with any type of credential. To use your existing identities, you need to connect the service to an identity provider, such as Nexus Hybrid Access Gateway.

You can also have the PDF signing built into your own applications using the PDF Signing API.

Simply sign up for a subscription, and your users can start making digital signatures straight away. 

Nexus GO PDF Signing

How does Nexus GO PDF Signing work? 

A PDF document is signed in the Nexus GO PDF Signing Portal in the following way: 

  1. An administrator logs in with Nexus Personal Mobile to the Nexus GO PDF Signing Portal, uploads a pdf document, invites persons to sign, and selects the required signing method for each person. An email is sent to each person. 
  2. Each signer follows the link in the email to the Nexus GO PDF Signing Portal, and signs the document with the required method. 
    For each signer, the following steps take place in Nexus GO:
    1. A one-time RSA key pair is created.
    2. The signer is associated to the key pair with two-factor authentication.
    3. A hash of the PDF document is generated and signed with the private key of the key pair. The private key is then discarded.
    4. The identity of the signer is securely bound to the key pair in a certificate, issued by the CA of the service, through the use of an HSM.
    5. The signed document hash, the newly generated certificate, and a time stamp is built into the PDF file. 
    The PDF document is now securely signed and cannot be modified without detection. The signed PDF document can be verified for example in Adobe Acrobat Reader. For more information, see Validate signed documents from Nexus GO PDF Signing.

How do I order the service?

See Get started with Nexus GO PDF Signing