seal.ID product updates 16.01.2024
The seal.ID product updates will be available on sandbox: 22.01.2024
The seal.ID product updates will be available on production: 05.02.2024
Features marked in blue are only activated on request.
New Features identification service
Hybrid feature: If the AutoIdent system considers the image quality of either the front or back side of the identification document to be insufficient, the user will be prompted to take an additional picture by manually pressing a button on the screen.
Improvements identification services
Reduced restrictions for revoke API: Revoke API to revoke a identification link can be called for all identification cases which have not reached a final status. The final case status are: IDENTIFICATION_SUCCESSFUL / VERIFICATION_CONFIRMED and DOWNLOADED
Webhook VERIFICATION_CONFIRMED for one-time signing is only sent after successful evidence import: For seal.ID one-time signing the webhook notification with status VERIFICATION_CONFIRMED is only sent after the evidence import to Swisscom was successfully confirmed. In the API GET .../id-cases/{caseId} the field evidenceImportStatus indicates the current status with possible values null, SUCCESS or Failed. The webhook notification with status VERIFICATION_CONFIRMED will only be sent if evidenceImportStatus has value SUCCESS.
New Features signing service
Preview of visual signature: If a visual signature is added for a document, a preview of the visual signature placement will be displayed in the document preview.
Signing retry page: If a technical error occurs in the signing process a new page is displayed that briefly describes the problem to the end user. The end user can click on a retry button, to restart the signing process.
Signing info page: If a signing link can no longer be used because the signer status is SIGNED, FAILED or REJECTED or because the signing link has expired a new info page with a short explanation is displayed to the end user.
Allow signing again after signer rejects: If a end user clicks on the reject link in the signing process and confirms to reject the signature the end user can be allowed to start the signature again. If this feature is enabled, the signer status will be updated to REJECTED but the document-basket status will not be updated. In this case, either the signing retry page with a retry button will be displayed or the existing signing link can be provided to the end user to start signing again.
PDF files with form fields can be signed.
seal.ID repetitive singing
Start signing immediately after reset Swisscom QES password / reset Mobile ID for QES: For seal.ID repetitive signing, the end user has the option to reset the Swisscom signing password or reset the Swisscom Mobile ID in the signing process. To do this, the end user will be navigated to identification step to perform a new identification. After the identification is completed the end user can automatically be navigated back to the signing flow, even if the smart-link feature is not used.
Redirect to external application after Mobile ID error: For seal.ID repetitive signing, if the end user tries to sign with Mobile ID but an error occurs, the end user can be navigated to a specific redirect URL (resetMobileIdSignRedirect). After this the external application can provide the existing URL to the end user to perform a new identification.
Improvements signing services
Improved document preview: Improved preview for documents on the document preview page and on the signed document page which allows pinch and zoom navigation on mobile browsers and prevents display errors on specific Android devices.
Updated post messsage of signing iframe: Additional details about the current status of the signer are provided in post iFrame message of the signing iframe in the fields statusReason and statusDetails.
Reduced restrictions for revoke API: Revoke API API to revoke a signing link can be called for all document-baskets which have not reached a final status. The final document-basket status are: SIGNED / DOWNLOADED.
PDF files with form fields can be signed.
To receive updates about seal.ID please subscribe: Subscribe to receive updates per email
You can manage your subscription here: Manage your subscriptions
Last updated