> For the complete documentation index, see [llms.txt](https://updates.digitaltrustplatform.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://updates.digitaltrustplatform.io/digital-trust-platform-product-updates/digital-trust-platform-update-29.04.2026.-action-required.md).

# Digital Trust Platform update 29.04.2026. Action Required !

## Improved seal.ID One-Time Signing Process

Swisscom has released a new version of its signing interface, called MAB, and will decommission the interface currently used in the seal.ID one-time signing solution. We are migrating to the new MAB service with the goal of minimizing the impact on existing integrations while improving the user experience where possible. 

## Improvements

{% hint style="success" %}

* **The signature can be confirmed without requiring an SMS OTP.**
* **The end user can complete the signature process at any time, 24/7.**
  {% endhint %}

## Preview <a href="#timeline" id="timeline"></a>

You can check a preview of the new signature confirmation by opening the following link:

{% embed url="<https://jolt-cozy-13155713.figma.site/>" %}
Preview of new seal.ID One-Time Signing (OTS) process
{% endembed %}

## Timeline <a href="#timeline" id="timeline"></a>

* First version on Sandbox: 30.04.2026
* First Go-Live on Production: ~~02.07.2026~~ 06.07.2026
* Decommission of Legacy One-Time-Signing: 01.09.2026

{% hint style="warning" %}
In case you need more time to migrate to the new solution, we can temporary activate repetitive signing until the migration has been completed. The change to repetitive signing can be configured on our side and does not include any breaking change to the current API integration of one-time signing.
{% endhint %}

## Integration <a href="#new-requirement-define-number-of-documents-to-be-signed-before-identification" id="new-requirement-define-number-of-documents-to-be-signed-before-identification"></a>

{% hint style="info" %}
For the integration of the new seal.ID one-time signing process and for testing, additional profiles will be provided. Please open a ticket to order the profiles for the integration and in case you have questions.
{% endhint %}

### New Requirement: Define number of documents to be signed before identification <a href="#new-requirement-define-number-of-documents-to-be-signed-before-identification" id="new-requirement-define-number-of-documents-to-be-signed-before-identification"></a>

For one-time identification and signing, the total number of documents to be signed with a QES must be specified before the identification process starts.

**How to comply:**

* **Via API:** Provide the number of documents to be signed with a QES in the field `numOfDocuments` when creating the identification case (`POST /schedule`) or when creating a document-basket (`POST /document-basket)`
* **Via profile configuration:** Set a fixed number of documents to be signed with a QES per identification/signing profile (via support ticket)

{% hint style="warning" %}
The signing process can only be started if the number of uploaded documents match the defined number of documents.&#x20;
{% endhint %}

### New Requirement: Signature must be confirmed within 30 Minutes <a href="#new-requirement-signature-must-be-confirmed-within-30-minutes" id="new-requirement-signature-must-be-confirmed-within-30-minutes"></a>

Due to a new regulatory requirement for one-time signing, the signature must be confirmed within 30 minutes after the identification review is completed.&#x20;

{% hint style="success" %}
**End users can already confirm the signature before the review was finished.**

**The end user can complete the signature process at any time, 24/7.**
{% endhint %}

**What you need to do:**

* **Option 1:** Immediately redirect users to the signing flow immediately after identification.
* **Option 2:** If you use a split flow today and send the end user after the identification back to your flow, ensure users are sent to signing and all documents are ready within max. 20 minutes after the manual review was completed (Status: VERIFICATION\_CONFIRMED)

{% hint style="warning" %}
If the 30-minute window is missed, the user must repeat the identification process.
{% endhint %}

### New Requirement: Asynchronous Signing (Background Completion) <a href="#new-requirement-asynchronous-signing-background-completion" id="new-requirement-asynchronous-signing-background-completion"></a>

Signing can now technically be completed after the user has left the end user session.

In the new flow, users can confirm the signature before the identification review is completed (e.g. on Sunday). Once the review is successfully completed, the signing is finalised automatically in the background.

**What you need to do:**

* Handle the **webhook with signer status `SIGNED`**, even if the user is no longer in the session.
* As a **regulatory requirement**, **signed documents must be downloadable** by the end user. If they are not present during signing, access must be provided via smart-link or other means (e.g. your application or email).
* If the users confirms the signature outside service hours, reviews are completed once the service center reopens. If the review was canceled for quality reasons, we highly recommend **notifying end users to repeat the identification** and navigate them back to the[ smart-link](https://dev.digitaltrustplatform.io/integration-guide/seal.id-features-description/seal.id-smart-link).

{% hint style="warning" %}
Signing may be completed without the user being present, so your application must handle this scenario accordingly.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://updates.digitaltrustplatform.io/digital-trust-platform-product-updates/digital-trust-platform-update-29.04.2026.-action-required.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.