eIDAS (EU Regulation 910/2014) establishes the legal framework for electronic signatures across EU member states. When you process documents through FlexOrch, the pipeline automatically checks for the presence of eIDAS-recognized signature formats and records what it finds in the execution metadata — giving your downstream systems a structured signal without any extra configuration.
FlexOrch identifies the following eIDAS-compliant advanced electronic signature formats:
| Format | Full Name | Common Use Case |
|---|
| XAdES | XML Advanced Electronic Signature | XML documents and web service payloads |
| PAdES | PDF Advanced Electronic Signature | Signed PDF contracts and official documents |
| CAdES | CMS Advanced Electronic Signature | Detached signatures, email, and binary files |
Signature data in execution results
When FlexOrch detects an eIDAS signature format in a document, it adds a structured block to the execution metadata. You can read this from the pipeline result:
{
"eidas_detected": true,
"eidas_formats": ["PAdES"],
"eidas_note": "Document contains a PAdES electronic signature. Validity verification requires a qualified trust service provider (QTSP)."
}
eidas_detected is false and eidas_formats is an empty array.
| Field | Type | Description |
|---|
eidas_detected | boolean | Whether any eIDAS-recognized signature format was found in the document. |
eidas_formats | string[] | List of detected formats — "XAdES", "PAdES", and/or "CAdES". |
eidas_note | string | A human-readable note describing the detection result and next steps. |
FlexOrch detects the presence and format of electronic signatures but does not validate signature validity, signer identity, or certificate trust chains. For legally binding signature validation — including qualified electronic signatures (QES) — you must use a qualified trust service provider (QTSP) listed in an EU Member State’s trusted list.
