Document Trust allows companies and compliance teams to analyse the authenticity of a document in order to detect document Fraud.

We leverage more than 600 detectors to give actionnable risk labels for your teams to take action. Risk labels range from : High, Medium, Low to Trusted and come with comprehensive indicators to help you understand the verdict.

To analyse any document's authenticity :

In addition to analyzing any document for authenticity, Document Trust enables you to run :

  • Extraction
  • Data consistency checks
  • Document type check

On a wide list of selected documents, more details on supported documents can be found here

To get extraction results, data consistency checks and document type checks :

  • Select a type among the ones we currently support
  • use the analysis_type[extraction] : 'true' parameter to run an extraction.
  • use the checksobject to match your data with the data extracted from the document.

Read our full detailed guide here.

We are reaching out to inform you of a scheduled maintenance window that will temporarily affect the Custom Experience API.

⚠️

Maintenance window: Thursday, 18 June 2026, from 18:00 to 20:00 CEST. The endpoints listed below will be unavailable during this period.

What will be affected?

The following endpoints will be unavailable during the maintenance window:

What will still work?

Applying a Custom Experience to a Signature Request will not be affected. Custom Experiences already linked to Signature Requests will continue to be applied normally.

If you have any questions, reach out to our support team.

You can now verify the existence of a company in Italy and Luxembourg and, when available, retrieve structured official company data. To initiate a verification, use the Company Verification creation endpoint POST /verifications/companies (see API reference) with the right company_number and country_code:

  • For Italy, use the Partita IVA: an 11-digit number (first 7 digits identify the company, the next 3 the province, the last is a check digit). Set country_code = IT.
  • For Luxembourg, use the RCS number: 1 letter (A to J) followed by 1 to 7 digits. Set country_code = LU.

For more details, please refer to our dedicated guide section here.


A new endpoint allows you to permanently and irreversibly delete a Document attached to an Electronic Seal. This is available to organizations with the feature config activated by a Sales representative, and requires the customer to sign a legal acknowledgement document. DELETE /electronic_seal_documents/{electronicSealDocumentId} (API reference)

Conditions and constraints:

  • All document versions are permanently deleted, Yousign will not retain any copy of the document. Deletion is irreversible. Yousign cannot restore deleted Documents.
  • Deletion is only possible when the Electronic Seal is in done or error status.
  • Qualified Electronic Seals are not supported.
  • The Audit Trail and all associated metadata are retained.
  • Standalone Electronic Seal Documents not linked to a sealing process can also be deleted.

Access:

The feature required an activation by a Sales representative (not a paid feature). Yousign assumes no liability for the deletion of these documents in the event of a dispute.

You can now personalise the Workflow Collect interface with your own customization. This configuration is currently done via the Yousign app only.

The following settings are available:

  • Branding: company logo, background color, text color, button color
  • Flow settings: show/hide the start page, show/hide the side panel, show/hide the "Powered by Yousign" badge
  • Redirect URLs: custom redirect on success or on error (optional)

Any update made to the Custom Experience in the app is reflected instantly across all Workflow Sessions using the associated template.

Learn how to set it up in the guide.

You can now retrieve an Audit Trail for Certified Identity Verification - PVID. This helps you access a verification summary and keep a record of the verification process when needed.

The audit trail is available via:

For more details, please refer to our dedicated guide section.

You can now restrict Document access per recipient within a single Signature Request. Excluded recipients cannot see the Document at all: it is not listed, not accessible, and not referenced in their signing experience. A Signer's electronic signature covers only the Documents visible to them.

By default, all recipients see all Documents; existing integrations require no changes.

New parameters on Document, Signer, and Approver endpoints:

  • excluded_signers and excluded_approvers (arrays of UUIDs) on POST /documents and PATCH /documents/{documentId}: define which Signers and Approvers cannot see a Document
  • excluded_documents (array of UUIDs) on POST /signers, PATCH /signers/{signerId}, POST /approvers, and PATCH /approvers/{approverId}: define which Documents a Signer or Approver cannot see

Available on Pro and Scale plans.

An organization admin must enable it first: Settings > Signature settings > Sender capabilities > Document visibility.

For full details, see the updated Document, Signer, and Approver guides.

To preserve signature integrity, QES (Qualified Electronic Signature) identifications are now invalidated 30 minutes after they are validated. If a Signer attempts to sign after this window, an error is triggered and the identification must be restarted. New webhook event: signer.identification_expired fired when a Signer's identification expires and the event is also tracked in the Signer's Activity feed.

  • Credits consumed for an expired identification are not refunded.
  • Wallet enrollment and previously enrolled wallets are not affected by this expiration rule.
  • This behavior is not available in Sandbox.

If you need any additional information about QES limitations, consult the dedicated guide here.

You can now analyze payslips with Document Analysis by using the initiation endpoint.
This helps you automate income and employment verification by extracting key payroll data from supported documents. Document Analysis will also automatically recognize and validate that the uploaded file is indeed a payslip. For the payslip document type, Document Analysis now extracts:

  • first_name
  • last_name
  • full_name
  • employer_name
  • pay_period_start_date
  • pay_period_end_date
  • net_pay
  • gross_pay
  • document_type

You can also send optional consistency-check parameters when creating the analysis:

  • first_name: checks that the provided first name matches the document
  • last_name: checks that the provided last name matches the document

To learn more, see the Document Analysis guide.