Smart-Link

If the smart-link feature is activated (mandatory for seal.ID one-time signing) the same url is used for identification and for signing. When using the smart-link the following points should be considered:

1) Split identification and signing process

Option 1 is recommended if the identification and signature are not to take place directly after each other. A common use scenario for this option is to generate contracts including data from the identification process.

Step 1) Create an identification case

An identification case is created with the call:

POST /id-cases/schedule

When creating an identification case the returned "url" in the response can be provided to the end user to do the identification. As long as no document-basket has been created, the end user will not be redirected to the signing but either stay on the identification successful page or be redirected to the external redirect url (depending on the profile configuration).

Step 2) Create a document-basket

It is important, that the document-basket is not created while any end user is in the identification process. So for option 1, the document-basket should be created after the identification case of the according signer was completed.

A document-basket is created by passing the id(s) of the before created identification case(s) in signers.signersFromExistingCases.idCaseId with the call:

POST /document-baskets

As soon as the document-basket is created, the existing identification case url can be used again, to do the signing.

• After the webhook notification with case status "VERIFICATION_CONFIRMED" is received, the external application can create the document-basket and upload all documents into the document-basket.

• Once the document-basket was created, the same url that was used for the identification process, can be used for the end user to complete the signing.

2) Combined identification and signing process

Option 2 is recommended if all documents have been generated before the identification and the signature is to take place directly after the identification.

A document-basket and the identification case(s) are created ncluding the signer(s) information in signers.signersEvidence with the call:

POST /document-baskets

• If the identification case and the document-basket are created a the same time, the end user will be forwarded to the signing process immediately after the identification was completed.

• This means, that all documents have to be generated and uploaded to the document-basket before the end user has started the identification process.

• As a shortcut, it is possible to create the identification case and the document-basket in one API call, by creating a document-basket and providing data for the signer(s) in "signersEvidence".