Following the release of the Seal&Sign feature, it is now possible to sign a document and then easily apply an Electronic Seal to it.
You can now use a previously signed Document as a parameter when calling the POST /electronic_seal_documents endpoint (see API reference) to create a sealed version of the Document. (see How to create an electronic Seal for details about Sealed Document).
Simply provide the signature_request_document_id in the request payload. This operation will generate a new copy of the signed Document with the Seal applied, allowing you to preserve both the original and the sealed versions.
For more details on how to apply a Seal to a signed Document, please refer to our dedicated guide.
The Qualified Electronic Seal is now available through the Yousign API!
It allows companies (legal persons) to seal documents without requiring the actions linked to a signature process.
It prevent the risk of fraud and proves document authenticity and integrity.
In addition to simpler use cases, we advise using this seal level in particular for electronic invoicing and notary deeds.
Please reach out to your customer representative to activate this product on your account.
We've enhanced Text to Copy Consent by providing real-time error highlighting. When the Signer makes a mistake, the incorrect character will be highlighted in red.Once correct, the text will turn green, making it easier to identify and fix errors.
Additionally, input is now restricted to the exact number of characters specified in the instruction, helping Signers avoid mistakes and enter the text accurately.
For more details about this feature, please refer to our guide.
You can now manage how your Signature Requests are embedded in your applications or websites directly from the Yousign interface. A new iFraming settings page is available in your Application, under API > iFraming.
From there, you can:
Choose between three security modes (not authorized, authorized domains only, origin referer always authorized)
Add and manage authorized domains for embedding Signature Requests
💡
Any previous settings configured with our Support Team remain unchanged and continue to apply.
We have improved how identification errors are displayed to Signers during the Qualified Electronic Signature (QES) process. Error messages are now clearer, better structured, and include explicit guidance on how to resolve issues and successfully complete the next attempt.
Previously, only one first name from a Signer’s list of given names was accepted for identity validation during the Qualified Electronic Signature (QES) flow. For example, if a Signer’s ID document lists "Eve Louise Coralie", only one of these names —"Eve", "Louise", or "Coralie" — needs to be used.
Starting today, we now accept any combination of all given names as a valid first name for a Signer! This means "Eve Louise Coralie" can now be used as a valid first name for the identification phase in the QES flow.