Updated 18/09/2024
In force

Version from: 12/09/2023
Amendments
QA2018_4052 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 26/10/2018
Art. 4
QA2018_4053 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 08/02/2019
Art. 4
QA2018_4110 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 20/12/2019
Art. 4
QA2018_4141 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 24/05/2019
Art. 4
QA2018_4237 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 15/05/2020
Art. 4
QA2018_4238 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 21/12/2018
Art. 4
QA2019_4783 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 25/09/2020
Art. 4
QA2019_4910 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 25/09/2020
Art. 4
QA2018_4315 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 15/01/2021
Art. 4(1)
QA2018_4041 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 05/10/2018
Art. 4(3)(a)
QA2019_4875 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 25/09/2020
Art. 4(3)(a)
QA2019_4662 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 19/06/2020
Art. 4(3)(b)
QA2018_4065 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 26/10/2018
Art. 4(3)(d)
QA2018_4068 - Strong customer authentication and common and secure communication (incl. access)
Status: Final
Answered: 21/12/2018
Art. 4(3)(d)
QA2023_6949 - Strong customer authentication and common and secure communication (incl. access)
Status: Under Review
Published: 21/12/2023
Art. 4(3)(d)
Search within this legal act

Article 4 - Authentication code

Article 4

Authentication code

1.  
Where payment service providers apply strong customer authentication in accordance with Article 97(1) of Directive (EU) 2015/2366, the authentication shall be based on two or more elements which are categorised as knowledge, possession and inherence and shall result in the generation of an authentication code.

The authentication code shall be only accepted once by the payment service provider when the payer uses the authentication code to access its payment account online, to initiate an electronic payment transaction or to carry out any action through a remote channel which may imply a risk of payment fraud or other abuses.

2.  

For the purpose of paragraph 1, payment service providers shall adopt security measures ensuring that each of the following requirements is met:

(a) 

no information on any of the elements referred to in paragraph 1 can be derived from the disclosure of the authentication code;

(b) 

it is not possible to generate a new authentication code based on the knowledge of any other authentication code previously generated;

(c) 

the authentication code cannot be forged.

3.  

Payment service providers shall ensure that the authentication by means of generating an authentication code includes each of the following measures:

(a) 

where the authentication for remote access, remote electronic payments and any other actions through a remote channel which may imply a risk of payment fraud or other abuses has failed to generate an authentication code for the purposes of paragraph 1, it shall not be possible to identify which of the elements referred to in that paragraph was incorrect;

(b) 

the number of failed authentication attempts that can take place consecutively, after which the actions referred to in Article 97(1) of Directive (EU) 2015/2366 shall be temporarily or permanently blocked, shall not exceed five within a given period of time;

(c) 

the communication sessions are protected against the capture of authentication data transmitted during the authentication and against manipulation by unauthorised parties in accordance with the requirements in Chapter V;

(d) 

the maximum time without activity by the payer after being authenticated for accessing its payment account online shall not exceed 5 minutes.

4.  
Where the block referred to in paragraph 3(b) is temporary, the duration of that block and the number of retries shall be established based on the characteristics of the service provided to the payer and all the relevant risks involved, taking into account, at a minimum, the factors referred to in Article 2(2).

The payer shall be alerted before the block is made permanent.

Where the block has been made permanent, a secure procedure shall be established allowing the payer to regain use of the blocked electronic payment instruments.