QES capabilities and limitations

Signature Requests with QES level have intrinsic security and compliance constraints. They must hence follow these rules:

Rules

• There can be only 1 field of type signature per Signer and Document to sign.
• Signers must be ordered (use ordered_signers : trueon Initiate Signature Request). Note that this holds true even when there is only one Signer in the Signature Request. Learn more about signers ordering.
• Authentication is not managed by OTP.
• There is an identity document and a video authentication.
• All Signers must use the same signature level qualified_electronic_signature(you can omit the field signature_authentication_mode or set it as null). Refer to Set the signature level for an API call example.
• Available in Sandbox once activated by our support. Consult our Qualified eSignature guide for more info.

Allowed authentication modes

• null

Allowed types of signature interface

• ✅ Signature link delivered via email by Yousign

• ✅ Signature link delivered by you

• ❌ Signature interface embedded in iFrame

  • The signing flow cannot be iFramed. This limitation is linked to security constraints around identity verification. You should instead use redirect URLs to set up your signature user journey. Learn more about redirecting signers.

• ❌ Custom-made signature interface

Download the Verified Identity Proof for a succeeded identification

You can download a Verified Identity Proof in PDF format for a signer identified as part of a Qualified Electronic Signature (QES) flow. The PDF contains the identity verification report and supporting identity documents collected during the Video Verification session. If the User has used the Saved Identity to perform the QES, the Verified Identity Proof won’t be available.

To use it, listen to the signer.identification_succeeded webhook (see reference). Once received, you can call the endpoint to download the PDF (see reference). In most cases the proof is generated within a few seconds; if it’s not available immediately, retry after a short delay.

The Verified Identity Proof is available only if:

• Have at least the API PRO plan;
• The Signer’s identification succeeded;
• The Signature level is QES;
• The identification method used by the User is Video Verification (not a Saved Identity);
• The identification data has not been anonymized (availability is limited to the provider retention window, currently up to ~3 months);
• The related Signature Request has not been permanently deleted.

🚨 This PDF contains highly personal data. Download it only when necessary and store it securely if you need to keep it beyond the provider’s retention window.