THPDFQCStatementInfo Record

Reports eIDAS qualified-certificate statements of a loaded signature's signer certificate per ETSI EN 319 412-5 and TS 119 495

Declaration

THPDFQCStatementInfo= record
  SignerCertFound: boolean;
  HasQCStatements: boolean;
  QCCompliant: boolean;
  QCSSCD: boolean;
  QCTypes: THPDFAnsiStringArray;
  HasQCLimit: boolean;
  QCLimitCurrency: AnsiString;
  QCLimitAmount: Int64;
  QCLimitExponent: Integer;
  QCPDSUrls: THPDFAnsiStringArray;
  // Deprecated since v2.755.3 and always empty: ETSI TS 119 495 defines
  // no payer / payee role lists. Read PSD2RolesOfPSP instead
  PSD2RolesPayer: THPDFAnsiStringArray;
  PSD2RolesPayee: THPDFAnsiStringArray;
  QualifiedSignatureLikely: boolean;
  // v2.755.3 ETSI TS 119 495 PSD2QcType: True only for a well-formed
  // statement; each role carries its roleOfPspOid and roleOfPspName, and
  // NCAName / NCAId name the national competent authority
  HasPSD2Statement: boolean;
  PSD2RolesOfPSP: THPDFPSD2RoleArray;
  PSD2NCAName: UnicodeString;
  PSD2NCAId: UnicodeString;
end;

Unit

HPDFDoc

Fields

Field	Purpose
`SignerCertFound`	True when the signer certificate could be extracted from the CMS data
`HasQCStatements`	True when the certificate carries at least one QC statement extension
`QCCompliant`	True when the id-etsi-qc-compliant statement is present and true
`QCSSCD`	True when the id-etsi-qc-SSCD statement marks a secure signature creation device
`QCTypes`	Declared QC type OIDs such as the eIDAS natural or legal person identifiers
`HasQCLimit`	True when a monetary transaction value limit statement is present
`QCLimitCurrency`	Three-letter currency code of the limit statement
`QCLimitAmount`	Amount digits of the limit; combine with `QCLimitExponent` for the value
`QCLimitExponent`	Exponent applied to `QCLimitAmount`
`QCPDSUrls`	URLs from the QC PDS statements pointing to the trust service provider's policy pages
`PSD2RolesPayer`	Deprecated and always empty since v2.755.3; read `PSD2RolesOfPSP` instead
`PSD2RolesPayee`	Deprecated and always empty since v2.755.3; read `PSD2RolesOfPSP` instead
`QualifiedSignatureLikely`	Computed as `QCCompliant` and `QCSSCD`, the usual eIDAS qualified-signature preconditions
`HasPSD2Statement`	True only for a well-formed PSD2QcType statement
`PSD2RolesOfPSP`	PSD2 payment-service-provider roles, each carrying its roleOfPspOid and roleOfPspName
`PSD2NCAName`	Name of the national competent authority from the PSD2 statement
`PSD2NCAId`	Identifier of the national competent authority from the PSD2 statement

Usage notes

Fill it with GetLoadedSignatureQCStatements, which returns false when the signature's CMS data or signer certificate cannot be read
Treat QualifiedSignatureLikely as a certificate-level indicator, not proof that the signature itself is qualified
Ignore PSD2RolesPayer and PSD2RolesPayee: they remain declared for compatibility but are never populated

THPDFQCStatementInfo Record

Declaration

Unit

Fields

Usage notes

Related APIs