QWAC Certificate: Qualified Website Authentication for eIDAS and PSD2
Updated: November 17, 2026
Netlock is a qualified trust service provider on the EU Trusted List and issues qualified website authentication certificates itself, PSD2 QWACs included. For HTTPS on your website, we recommend the standard SSL/TLS certificates we resell: DV, OV, Wildcard and EV.
For a QWAC, a PSD2 QWAC, or DV, OV, Wildcard and EV SSL/TLS certificates
A QWAC certificate (qualified website authentication certificate) is a website certificate that a qualified trust service provider issues under the EU’s eIDAS Regulation and that meets its Annex IV (Article 3(39)). It links a website to the person or organisation behind it. Payment service providers can use it to identify themselves under PSD2.
What Is a QWAC Certificate?
A QWAC certificate is the qualified version of a website authentication certificate under the EU’s eIDAS Regulation (Regulation (EU) No 910/2014, as amended by Regulation (EU) 2024/1183). eIDAS defines a certificate for website authentication as “an electronic attestation that makes it possible to authenticate a website and links the website to the natural or legal person to whom the certificate is issued” (Article 3(38)). The qualified version is “a certificate for website authentication, which is issued by a qualified trust service provider and meets the requirements laid down in Annex IV” (Article 3(39)). Our guide to the eIDAS Regulation explains the framework.
QWAC stands for qualified website authentication certificate. Issuing it is a qualified trust service, so only a provider with qualified status can issue one, and before issuing it, the provider “shall verify the identity” of the person or organisation it issues it to (Article 24(1)). A qualified certificate for website authentication issued in one member state is recognised as one “in all other Member States” (Article 24a(7)).
A QWAC identifies a website and its operator; it does not sign documents. For signing documents, you need a qualified electronic signature, and for documents that your organisation issues, an electronic seal.
What Does a QWAC Certificate Contain?
Annex IV of eIDAS lists what every QWAC must contain. For a website operated by an organisation, that is:
- (a) “an indication, at least in a form suitable for automated processing, that the certificate has been issued as a qualified certificate for website authentication”;
- (b) data that unambiguously represents the issuing qualified trust service provider, including the member state where it is established;
- (ca) “a unique set of data unambiguously representing the legal person to whom the certificate is issued, with at least the name of the legal person to whom the certificate is issued and, where applicable, the registration number as stated in the official records”;
- (d) “elements of the address, including at least city and State”, of the organisation;
- (e) “the domain name(s) operated by the natural or legal person to whom the certificate is issued”;
- (f) the beginning and end of the certificate’s validity period;
- (g) a certificate identity code that is unique for the issuing provider;
- (h)–(i) the advanced electronic signature or seal of the issuing provider, and where the certificate behind it is available free of charge;
- (j) where to check the certificate’s validity status.
If the certificate is issued to a natural person, it names that person or a pseudonym instead (point (c)). When an organisation operates the website, Netlock’s QWAC contains the organisation’s data.
Who Needs a QWAC?
You need a QWAC where a law or a business partner expects qualified, eIDAS-based identification of a website and its operator. eIDAS does not require every website to use a qualified certificate, but some sector rules expect one.
A typical case is PSD2, the EU’s Payment Services Directive: payment service providers that connect to the access interfaces of account servicing payment service providers, such as banks, identify themselves with a QWAC or a qualified seal certificate (see the next section). If you work in payments, see also our page on solutions for fintech companies.
For HTTPS on a public website, we recommend the standard SSL/TLS certificates we resell (see below).
PSD2 QWAC: The Certificate for Payment Service Providers
Under the regulatory technical standards of PSD2, payment service providers identify themselves with a qualified certificate: “For the purpose of identification, as referred to in Article 30(1)(a), payment service providers shall rely on qualified certificates for electronic seals as referred to in Article 3(30) of Regulation (EU) No 910/2014 or for website authentication as referred to in Article 3(39) of that Regulation.” (Article 34(1) of Commission Delegated Regulation (EU) 2018/389)
The identification in question is set out in Article 30(1)(a): through a bank’s access interface, account information service providers, payment initiation service providers and card-issuing payment service providers must be “able to identify themselves towards the account servicing payment service provider”.
A PSD2 certificate carries extra data. Under Article 34(3), it “shall include, in a language customary in the sphere of international finance, additional specific attributes” on:
- the role of the payment service provider, which may be one or more of: account servicing, payment initiation, account information, and issuing of card-based payment instruments;
- “the name of the competent authorities where the payment service provider is registered”.
The registration number in the certificate is the payment service provider’s authorisation number (Article 34(2)), and the PSD2 attributes “shall not affect the interoperability and recognition” of the qualified certificate (Article 34(4)).
Netlock issues PSD2 QWACs. Article 34(1) also allows a qualified certificate for electronic seals: ask the banks you connect to which certificate their interface accepts. If you also need a PSD2 seal certificate (QSealC), talk to sales. For qualified electronic seals in general, see our electronic seal page.
QWAC vs SSL/TLS Certificates: DV, OV and EV
All of these certificates authenticate a website; they differ in what the issuer checks before issuing and in what the certificate states. The strength of the encryption does not depend on the level.
For HTTPS on your website, we recommend the standard SSL/TLS certificates we resell; the QWAC is for qualified, eIDAS-based identification.
What eIDAS 2.0 Says About QWACs and Web Browsers
The 2024 amendment of eIDAS (Regulation (EU) 2024/1183) added obligations for web browser providers. Under Article 45(1a), qualified certificates for website authentication “shall be recognised by providers of web-browsers”, and browser providers “shall ensure that the identity data attested in the certificate and additional attested attributes are displayed in a user-friendly manner”. Microenterprises and small enterprises are exempt from the support and interoperability duty during their first five years as browser providers.
Browsers may depart from this only “in the event of substantiated concerns related to security breaches or the loss of integrity of an identified certificate or set of certificates”, in which case they may take precautionary measures (Article 45a(2)). They must then notify their concerns in writing, without undue delay, to the Commission, the competent supervisory body, the entity the certificate was issued to and the qualified trust service provider that issued it (Article 45a(3)).
Our guide to eIDAS 2.0 and the EUDI wallet covers the other changes of the 2024 amendment.
How to Order a QWAC From Netlock
You order a QWAC through our sales team, and we agree the details of your use there:
- Talk to sales. Tell us the domain names, whether you need the certificate for eIDAS or for PSD2 identification and, for PSD2, your role and the authority you are registered with.
- We verify the applicant and your organisation. eIDAS requires us to verify the identity of the person or organisation before we issue a qualified certificate (Article 24(1)). Under the Hungarian Digital State Act (Dáptv., Act CIII of 2023), the provider checks at least the organisation’s full name and unique identifier, for an organisation registered in Hungary against the public register (section 85(8)), and makes sure of the right of representation before issuing the certificate (section 85(9)).
- We issue your QWAC with your organisation’s data and your domain names (Annex IV). Under Netlock’s price list in force from 11 August 2026, we issue certificates within 14 working days of successful data verification, identification and contract conclusion; expedited issuance within 1 or 3 working days is available for an extra fee.
QWAC, PSD2 QWAC, and DV, OV, Wildcard and EV SSL/TLS certificates
Standard SSL/TLS Certificates for HTTPS
For HTTPS on your website, we offer standard SSL/TLS certificates from Certum, which we resell: DV, OV, Wildcard and EV. You order them through our sales team: you tell us the level and the domains, and we handle the order. Prices are given in a quote. SSL is the old name of the protocol: today’s connections use TLS, but the certificate is still widely called an SSL certificate.
Publicly trusted TLS certificates now have much shorter lifetimes. Under section 6.3.2 of the CA/Browser Forum’s Baseline Requirements, the maximum validity depends on the date of issue:
| Issued | Maximum validity |
|---|---|
| Before 15 March 2026 | 398 days |
| From 15 March 2026 | 200 days |
| From 15 March 2027 | 100 days |
| From 15 March 2029 | 47 days |
Because of these limits, you renew and reinstall certificates more often. For email, our encryption certificate page also covers S/MIME email certificates.
Why Netlock
Netlock is a qualified trust service provider. Its entry on the EU Trusted List shows qualified certificates for electronic signatures, electronic seals and website authentication, and qualified timestamping. On the Hungarian trusted list issued on 19 October 2026, the services of NETLOCK Trust Qualified EV CA, EV CA 2 and EV CA 3 have “granted” status for website authentication.
The National Media and Infocommunications Authority (NMHH) supervises trust service providers in Hungary (Digital State Act, section 95(1)), and you can find Netlock in the NMHH register of trust service providers. Our certificate of conformity for trust services under the ETSI standards, E-NL25T1_TAN-01.QTSP/2025/011, is valid until 11 April 2027.
What you get with Netlock:
- Two solutions in one place: QWACs and PSD2 QWACs that we issue ourselves as a qualified trust service provider, and standard SSL/TLS certificates for HTTPS that we resell.
- Every level: DV, OV, Wildcard and EV.
- Help from our team by phone: +36 1 255 0792.
- A quote tailored to you, for every QWAC and SSL/TLS order. See our certificates overview for Netlock’s other certificates.
FAQ
An EV certificate is a validation level for SSL/TLS certificates. A QWAC is a qualified certificate under eIDAS: a qualified trust service provider issues it after verifying the holder’s identity (Article 24(1)), and its content is set by Annex IV of eIDAS, including the organisation’s name and, where applicable, its registration number, its city and state, and its domain names.
Yes. Netlock issues qualified website authentication certificates for eIDAS and PSD2 identification, PSD2 QWACs included. A PSD2 QWAC carries the payment service provider’s role and the name of the competent authority where it is registered (Article 34(3) of Delegated Regulation (EU) 2018/389). To order one, talk to sales.
Either. Payment service providers “shall rely on qualified certificates for electronic seals … or for website authentication” for identification (Article 34(1) of Delegated Regulation (EU) 2018/389), and both carry the same PSD2 attributes (Article 34(3)). Ask the banks you connect to which one their interface accepts.
Every QWAC states the beginning and end of its validity period (eIDAS Annex IV, point (f)). Netlock bills the QWAC yearly, and your quote states its validity period.
Yes. A QWAC contains “the domain name(s) operated by” its holder (eIDAS Annex IV, point (e)).
Yes. “A qualified certificate for website authentication issued in one Member State shall be recognised as a qualified certificate for website authentication in all other Member States.” (eIDAS Article 24a(7))
No. A website authentication certificate identifies a website and its operator, not a signatory. To sign documents, you need a qualified electronic signature, which is based on a qualified certificate for electronic signatures (eIDAS Article 3(12)).
Ask for revocation by email at revocation@netlock.com or by phone through customer service (+36 1 255 0792). Our guide to certificate revocation explains what happens next.
A QWAC or PSD2 QWAC for qualified, eIDAS-based identification, and standard SSL/TLS certificates for HTTPS, from a qualified trust service provider on the EU Trusted List.
For a QWAC, a PSD2 QWAC, and DV, OV, Wildcard and EV SSL/TLS certificates