eIDAS & Trust Services
What Is the QCStatements Extension?
QCStatements (qcStatements, OID 1.3.6.1.5.5.7.1.3) is the X.509 certificate extension in which an issuer makes machine-readable declarations about a qualified certificate. The extension itself comes from RFC 3739. The individual statements used in the EU are defined in ETSI EN 319 412-5 under the OID arc 0.4.0.1862.1, and they are how a certificate claims to be qualified under eIDAS.
The statements and their OIDs
QcCompliance (0.4.0.1862.1.1) is the claim that the certificate is an EU qualified certificate. It has no content. Its presence is the statement.
QcType (0.4.0.1862.1.6) says which of the three purposes the certificate is issued for: electronic signature (0.4.0.1862.1.6.1), electronic seal (0.4.0.1862.1.6.2) or website authentication (0.4.0.1862.1.6.3). A certificate carries exactly one type.
QcSSCD (0.4.0.1862.1.4) declares that the private key resides in a qualified signature or seal creation device (QSCD). The name is a leftover from the 1999 directive, which called the device a secure signature creation device.
QcPDS (0.4.0.1862.1.5) holds one or more https URLs, each with a language code, pointing to the PKI Disclosure Statement, the short summary of the terms under which the certificate is issued.
QcLimitValue (0.4.0.1862.1.2) states a limit on the value of transactions the certificate may be used for, as currency, amount and exponent. QcRetentionPeriod (0.4.0.1862.1.3) states for how many years after expiry the issuer keeps the registration records. Both originate in the directive and are optional.
QcCClegislation (0.4.0.1862.1.7) lists country codes when the certificate is qualified under the law of a country outside the EU framework. An EU qualified certificate must not contain it, so its presence means QcCompliance refers to another legal regime.
Newer and sector statements
Recent versions of ETSI EN 319 412-5 add QcIdentMethod (0.4.0.1862.1.8), which records the Article 24 method used to verify the subject's identity, and QcQSCDlegislation (0.4.0.1862.1.9), for devices recognised as qualified under a non-EU legal framework.
Certificates for payment service providers under the Payment Services Directive (PSD2) carry an additional statement defined in ETSI TS 119 495, with OID 0.4.0.19495.2. It lists the provider's roles, each with its own OID (account servicing 0.4.0.19495.1.1, payment initiation 0.4.0.19495.1.2, account information 0.4.0.19495.1.3, issuing of card-based payment instruments 0.4.0.19495.1.4), and names the national competent authority that authorised the provider.
Qualified time stamp tokens have their own equivalent: ETSI EN 319 422 defines a statement with OID 0.4.0.19422.1.1 that a time stamping authority can place in the token to claim that it is a qualified electronic time stamp.
How to read them
The extension is never marked critical, and it plays no part in RFC 5280 path validation. Software that does not understand it will still build and accept the chain. That is by design, but it means a TLS library accepting a certificate tells you nothing about qualified status.
OpenSSL prints the extension in the certificate text. Depending on version it shows the statements by name or as the raw OIDs listed above, so it helps to know them. Remember that the statements are the issuer's own claims. QcCompliance only carries weight once the issuer is confirmed in the EU Trusted List with a granted qualified service of the matching type.
openssl x509 -in cert.pem -noout -text
Try it yourself — free tools
- Certificate Checker — decode every QCStatement in a certificate, PSD2 roles included, and check the claim against the EU Trusted List
- Timestamp Checker — see whether a time stamp token carries the qualified time stamp statement
How MI Support IT can help
PKI Tools is built by MI Support IT, a Danish IT company with deep specialization in enterprise PKI: ADCS design and health checks, Venafi certificate automation, key ceremonies and CP/CPS documentation. Read about our PKI services or get in touch.
PKI Glossary
- Qualified CertificateAn X.509 certificate issued by a qualified trust service provider that meets the eIDAS annex for signatures, seals or website authentication.
- ETSI EN 319 412The ETSI certificate profiles in five parts: common structures, natural persons, legal persons, websites and QCStatements.
- EU Trusted Lists (EUTL) and the List of Trusted Lists (LOTL)The signed, machine-readable national lists that decide whether a trust service is qualified under eIDAS, tied together by the List of Trusted Lists.
- Qualified Signature Creation Device (QSCD)The certified device that holds the private key for a qualified electronic signature or seal: a smart card, a token or a remote signing service.
- Qualified Website Authentication Certificate (QWAC)A qualified certificate under eIDAS that links a website to the verified legal or natural person operating it.
- Qualified Electronic Seal Certificate (QSealC)A qualified certificate issued to a legal person, used to seal data so its origin and integrity can be proven.
- X.509 Certificate StandardThe standard that defines what a digital certificate is — its fields, extensions and validation rules.
- Browse all terms →