Updated 18/09/2024
In force

Version from: 12/09/2023
Amendments
QA2019_5054 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 23/04/2021
Art. 33
QA2023_6752 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 22/03/2024
Art. 33
QA2018_4071 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 08/02/2019
Art. 33(1), 33(2)
QA2023_6753 - Strong customer authentication and common and secure communication (incl. access)
Status: Rejected
Repelled: 10/07/2023
Art. 33(1), 33(4), 33(6)
QA2019_4826 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 19/06/2020
Art. 33(4), 33(5)
QA2019_4638 - Other topics
Status: Final
Answered: 26/04/2019
Art. 33(6)
QA2018_4138 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 07/06/2019
Art. 33(6)
QA2018_4163 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 12/04/2019
Art. 33(6)
QA2019_4681 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 09/08/2019
Art. 33(6)
QA2022_6613 - Strong customer authentication and common and secure communication (incl. access)
Status: Rejected
Repelled: 29/03/2023
Art. 33(6)
QA2024_7103 - Other topics
Status: Under Review
Published: 04/06/2024
Art. 33(7)
QA2018_4140 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 22/03/2019
Art. 33(7)
Search within this legal act

Article 33 - Contingency measures for a dedicated interface

Article 33

Contingency measures for a dedicated interface

1.  
Account servicing payment service providers shall include, in the design of the dedicated interface, a strategy and plans for contingency measures for the event that the interface does not perform in compliance with Article 32, that there is unplanned unavailability of the interface and that there is a systems breakdown. Unplanned unavailability or a systems breakdown may be presumed to have arisen when five consecutive requests for access to information for the provision of payment initiation services or account information services are not replied to within 30 seconds.
2.  
Contingency measures shall include communication plans to inform payment service providers making use of the dedicated interface of measures to restore the system and a description of the immediately available alternative options payment service providers may have during this time.
3.  
Both the account servicing payment service provider and the payment service providers referred to in Article 30(1) shall report problems with dedicated interfaces as described in paragraph 1 to their respective competent national authorities without delay.
4.  
As part of a contingency mechanism, payment service providers referred to in Article 30(1) shall be allowed to make use of the interfaces made available to the payment service users for the authentication and communication with their account servicing payment service provider, until the dedicated interface is restored to the level of availability and performance provided for in Article 32.
5.  

For this purpose, account servicing payment service providers shall ensure that the payment service providers referred to in Article 30(1) can be identified and can rely on the authentication procedures provided by the account servicing payment service provider to the payment service user. Where the payment service providers referred to in Article 30(1) make use of the interface referred to in paragraph 4 they shall:

(a) 

take the necessary measures to ensure that they do not access, store or process data for purposes other than for the provision of the service as requested by the payment service user;

(b) 

continue to comply with the obligations following from Article 66(3) and Article 67(2) of Directive (EU) 2015/2366 respectively;

(c) 

log the data that are accessed through the interface operated by the account servicing payment service provider for its payment service users, and provide, upon request and without undue delay, the log files to their competent national authority;

(d) 

duly justify to their competent national authority, upon request and without undue delay, the use of the interface made available to the payment service users for directly accessing its payment account online;

(e) 

inform the account servicing payment service provider accordingly.

6.  

Competent authorities, after consulting EBA to ensure a consistent application of the following conditions, shall exempt the account servicing payment service providers that have opted for a dedicated interface from the obligation to set up the contingency mechanism described under paragraph 4 where the dedicated interface meets all of the following conditions:

(a) 

it complies with all the obligations for dedicated interfaces as set out in Article 32;

(b) 

it has been designed and tested in accordance with Article 30(5) to the satisfaction of the payment service providers referred to therein;

(c) 

it has been widely used for at least 3 months by payment service providers to offer account information services, payment initiation services and to provide confirmation on the availability of funds for card-based payments;

(d) 

any problem related to the dedicated interface has been resolved without undue delay.

7.  
Competent authorities shall revoke the exemption referred to in paragraph 6 where the conditions (a) and (d) are not met by the account servicing payment service providers for more than 2 consecutive calendar weeks. Competent authorities shall inform EBA of this revocation and shall ensure that the account servicing payment service provider establishes, within the shortest possible time and at the latest within 2 months, the contingency mechanism referred to in paragraph 4.