QTSPs and eIDAS
QTSPs are regulated (Qualified) to provide trusted digital certificates under the electronic Identification and Signature (eIDAS) regulation.
PSD2 requires specific types of eIDAS certificates to be issued.
Open Banking Europe runs an engagement group of QTSPs that offer these PSD2 compliant certificates.
This group aims to help the financial world meet the electronic security world by addressing common issues.
Other eIDAS related documents
This guide summarises the existing technology framework that is already in place in order to use certificates for website authentication and identity verification and enable secure Access to Account (XS2A) services in Europe, as required under the revised Payment Services Directive (PSD2). Download it here.
This document provides the answers to common questions about the use of Qualified certificates to support secure communications between payment services under PSD2 and their related Regulatory Technical Standards (RTS). Download it here.
List of QTSPs supplying PSD2 compliant Qualified certificates
This page contains a list of QTSPs who are offering PSD2 certificates, and further information about where to contact the QTSP. The aim of this page is to help Payment service providers who are looking for suppliers of eIDAS certificates for PSD2 to find out who is supplying them, and how to contact them.
By PSD2 qualified certificates we mean qualified certificates (QWACs or QSEALCs) that are issued in compliance with ETSI TS119495 for the purposes of identification or PSPs within PSD2 access to account, as referenced in Article 34 of the Regulatory Technical Standards on Strong Customer Authentication and Common and Secure Communications.
Click here to download the full list.
Open Banking Europe is not a supervisor or certification body in relation to QTSPs and the information is based on their own statements about capabilities and services. All QTSPs listed are found in the EU trusted list, but Open Banking Europe is not responsible for the accuracy of the information.
The PSD2 RTS on strong customer authentication and Common and secure communication require that Qualified eIDAS certificates are used for identification of TPPs and ASPSPs.
Qualified certificates are issued by Qualified Trusted Service Providers (QTSPs) as described in the eIDAS regulation, and further described within various ETSI standards.
ETSI have published specific standards to support PSD2 compliant eIDAS certificates.
Data required in PSD2 eIDAS certificates according to the RTS
ETSI eIDAS PSD2 Standard
At its plenary meeting of the 10th October 2017, the European Telecommunications Standards Institute (ETSI) agreed to create a standard for PSD2 eIDAS certificates, in accordance with the EBA RTS.
The new European Telecommunications Standards Institute (ETSI) PSD2 standards were developed by Open Banking Europe.
- Details of the background discussions we had with ETSI for the ratification of PSD2 standards request is here.
The final standard ETSI TS 119 495 is here.
For those who wish to know more, a day long event was held that describes the various aspects of PSD2 and eIDAS. Video and presentations of the event are available here.
The limits of an eIDAS certificate
The process of revocations (and its link to NCA’s) is accurately described on page 44 of the ERPB report which has a clear position.
The industry will use:
- The eIDAS certificate for Identification.
- The NCA registers for Authorisation.
Open Banking Europe provides such a directory to make this easier.
Considering that the NCA is not obliged to inform the QTSP, and the QTSP is not obliged to check the NCA register, it is clear that although we can trust the certificates for Identification, in the case that an NCA has withdrawn a license and the certificate has not yet been revoked, there is a period when the roles in the certificate will not be accurate. In the case that anybody wishes to check the up to date role of an ASPSP, then they must look at the Home NCA of that entity.
As there will be 31 NCA’s, this raises the need for a machine readable, standardised repository of TPP
details, as published by NCAs (Recommendation #7).
The directory should provide a real-time accessible, machine readable and standardised repository of the details of all authorised and revoked TPPs as published by NCAs. These details should include regulatory information such as passporting information, and could also include operational information such as contact details.