eIDAS & Trust Services

What Is Qualified Website Authentication Certificate (QWAC)?

A Qualified Website Authentication Certificate (QWAC) is a qualified certificate, issued by a qualified trust service provider under Article 45 and Annex IV of the eIDAS Regulation, that makes it possible to authenticate a website and links it to the natural or legal person to whom the certificate is issued. Technically it is a TLS server certificate with verified identity information and the QCStatements that mark it as qualified.

What is inside a QWAC

Annex IV requires the certificate to state that it is a qualified certificate for website authentication and to contain the name of the person or organisation, a registration number where one exists, at least the city and state of their address, and the domain names they operate. In X.509 terms that means QcCompliance (0.4.0.1862.1.1) together with QcType set to web (0.4.0.1862.1.6.3), the organisation in the subject, and the domain names as Subject Alternative Names.

The profile is ETSI EN 319 412-4, and the issuance policies are in ETSI EN 319 411-2. The policy long known as QCP-w is now named QEVCP-w and keeps the OID 0.4.0.194112.1.4. It builds on the CA/Browser Forum Extended Validation Guidelines. Two further policies exist: QNCP-w (0.4.0.194112.1.5), built on organisation or individual validation under the CA/Browser Forum Baseline Requirements, and QNCP-w-gen (0.4.0.194112.1.6), a general-purpose policy that is not tied to browser requirements.

QWACs and browsers

A browser decides which TLS certificates to accept from its own root store, under its own root programme. The EU Trusted List is a separate mechanism, so for years a QWAC worked in browsers only if its issuer was also in the browser root stores, and browsers showed nothing that distinguished it from any other certificate.

eIDAS 2 changed the legal position. Article 45 now says that QWACs shall be recognised by providers of web browsers, and that browsers shall display the identity data in the certificate in a user-friendly manner. Article 45a adds that browsers may not take measures contrary to this, with one exception: where there are substantiated concerns about a security breach or loss of integrity of a certificate, a browser may take precautionary measures and must then notify the Commission, the supervisory body and the issuer without undue delay. How recognition works technically is set out in implementing acts and the standards they reference.

Where QWACs are used today

The largest deployment is open banking. Under the PSD2 regulatory technical standards (Commission Delegated Regulation (EU) 2018/389), payment service providers identify themselves to banks with qualified certificates for website authentication or for electronic seals. Those certificates follow ETSI TS 119 495 and carry the PSD2 statement with the provider's roles and authorisation number. Here the QWAC is typically used as a client certificate in mutual TLS between a third-party provider and a bank's interface, not shown to an end user in a browser.

Try it yourself — free tools

  • Certificate Checker — decode the QCStatements, PSD2 roles and policy OIDs of a QWAC and check the issuer against the EU Trusted List

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