PS19/26: Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication — FCA — GB

Policy Statement
PS19/26
October 2019
Brexit – Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication

2
PS19/26 Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication This relates to Consultation Paper 18/44 which is available on our website at www.fca.org.uk/publications Payments Policy Financial Conduct Authority 12 Endeavour Square London E20 1JN Email:
cp18-44@fca.org.uk
Contents
1 Overview 3
2 Making technical standards (UK-RTS) and amending the Handbook 6 3 Cost benefit analysis 10
Annex 1
List of non-confidential respondents 11
Annex 2
Abbreviations used in this paper 12
Appendix 1
Instrument making regulatory technical standards for strong customer authentication
Appendix 2
Instrument making amendments to sub-articles 30(3) and (5) of the SCA-RTS (superseded by UK-RTS)
Appendix 3
Instrument making amendments to the Handbook

3
PS19/26
Chapter 1
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication 1 Overview Introduction
1.1 The EU Regulatory Technical Standards for strong customer authentication (SCARTS) came into force on 14 March 2018. The aim of the SCA-RTS is to make electronic
payments more safe and secure. It forms part of EU law, and supplements the Payment Services Directive 2015 (PSD2).
1.2 The SCA-RTS sets out how payment service providers (PSPs) must verify a customer’s
identity for electronic transactions. It also sets out requirements for secure communication between PSPs for open banking-type services.
1.3 From 14 March 2019, firms were required to comply with 2 provisions of the SCA-RTS.
Those were sub-articles 30(3) and (5). The rest of the SCA-RTS came into force on 14 September 2019.
1.4 On 19 December 2018, we published our consultation paper CP18/44. This consulted
on making regulatory technical standards for strong customer authentication substantially the same as the EU SCA-RTS (a ’UK-RTS’), in the event the UK left the EU without a ratified withdrawal agreement (a no-deal Exit). We also consulted on making consequential changes to the Handbook.
1.5 The Payment Services Regulations 2017 (PSRs 2017) make provisions for firms to
comply with the SCA-RTS. In the event of a no-deal Exit, Exit-related amendments to the PSRs 2017 will come into effect. These amendments will require firms in the UK to comply with the UK-RTS made by the FCA instead of the SCA-RTS. So, if we do not make the UK-RTS, the PSRs 2017 will be ineffective on Exit day.
1.6 As the SCA-RTS fully came into effect on 14 September 2019, it will become part of
UK law under the European Union (Withdrawal) Act 2018 on Exit day. However, after a no-deal Exit, the SCA-RTS will be redundant, as the amended PSRs 2017 will require firms to comply with the UK-RTS, and not the SCA-RTS. So, as well as consulting on making the UK-RTS in CP18/44, we also consulted on revoking the SCA-RTS in our Quarterly Consultation Paper (QCP) 25, published on 6 September 2019. This consultation closed on 4 October 2019.
1.7 This Policy Statement (PS) confirms that, in the event of a no-deal Exit, we will make
the UK-RTS and make changes to the Handbook on Exit day following feedback to our consultation.

4
PS19/26
Chapter 1
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication Who does this affect
1.8 The UK-RTS and other changes outlined in this PS will affect:

banks, building societies and other PSPs, including PSPs involved in open banking
card schemes
retailers
consumers and micro-enterprises
Is this of interest to consumers?
1.9 Most consumers use payment services. They will be affected by the topics in this PS,
particularly the rules on the security of online payments. Consumers who use open banking services, such as online account dashboards, will also find this PS of interest. Summary of feedback and our response
1.10 We received 4 responses to CP18/44, including submissions from trade associations
and other industry participants.
1.11 In CP18/44 we proposed to make a separate instrument making minor changes to subarticles 30(3) and (5) of the SCA-RTS which took effect on 14 March 2019. That was
before the rest of the SCA-RTS came into effect, and before the original planned date for the UK to leave the EU. Our proposals would have ensured that the sub-articles operated effectively in the UK after it left the EU. However, because the date of Exit day changed, we will no longer make a separate instrument to amend those subarticles. Instead, the amended version of those sub-articles, which we had proposed to make in CP18/44, will form part of the provisions of the UK-RTS on Exit day.
1.12 Broadly, respondents made no objections to our making technical standards
substantially the same as the SCA-RTS, making changes to sub-articles 30(3) and (5) of the SCA-RTS to reflect EU withdrawal, and making changes to the Handbook.
1.13 Some respondents raised concerns over the requirement to use eIDAS certificates,
and whether they would be available to PSPs in the UK after Exit day. The UK-RTS continues to require PSPs to use eIDAS certificates because of the need to maintain market consistency. However, in August 2019, we wrote to trade bodies to set out the terms of a 6-month adjustment period for implementing the SCA-RTS. After Exit day, firms should treat those terms as applying to the UK-RTS.
1.14 Some respondents raised concerns about the conversion of euro denominated
financial thresholds in the SCA-RTS to sterling in the UK-RTS using an exchange rate on Exit day. They were concerned about whether currency fluctuations could lead to the sterling value limits suddenly changing significantly. To avoid potential disruption, the UK-RTS includes the sterling values and conversion rate used in CP18/44.
1.15 The amended PSRs 2017 will allow firms based in Gibraltar to continue to provide
payment services in the UK after Exit day. So, we have clarified that the UK-RTS applies to firms that are authorised or registered in the UK or Gibraltar.

5
PS19/26
Chapter 1
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication Equality and diversity considerations
1.16 We are not expecting the changes referred to in this PS to have a material impact on
equality and diversity.
What do you need to do next?
1.17 PSPs must comply with the provisions of the UK-RTS in the event of a no-deal Exit.
1.18 In the event of a no-deal Exit, firms should treat our correspondence regarding the
SCA-RTS adjustment period as applying to the UK-RTS.

6
PS19/26
Chapter 2
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication 2 Making technical standards (UK-RTS) and amending the Handbook
2.1 In this chapter, we summarise and respond to the feedback we received on both the
following:

our proposed technical standards (UK-RTS)
our proposed amendments to the Handbook
2.2 For the UK-RTS, the main comments we received were about the:
availability of eIDAS certificates
conversion of euro denominated financial thresholds from euro to sterling
Making technical standards eIDAS certificates
2.3 In CP 18/44, we proposed to make the UK-RTS substantially the same as the SCA-RTS.
The UK-RTS sets out requirements for secure communication between account servicing payment service providers (ASPSPs), and new types of payment service providers, collectively referred to as third-party providers (TPPs). TPPs include account information service providers, payment initiation service providers, and card-based payment instrument issuers.
2.4 The UK-RTS explains how TPPs and ASPSPs should interact and communicate
securely. It sets out the basis on which a TPP identifies itself to any ASPSP and then accesses customers’ accounts (with customers’ consent). This is key to open banking services.
2.5 ASPSPs in open banking need to be able to verify who they are communicating with.
So far, this aspect of open banking in the UK has been supported by the Open Banking Implementation Entity’s (OBIE) systems and processes. These include a central directory of enrolled participants in open banking and allows the identification by ASPSPs of TPPs within open banking.
2.6 The UK-RTS requires that TPPs’ identification must be done using electronic
certificates, issued by a Qualified Trust Service Provider (QTSP). These are called eIDAS certificates and their provision is governed by an EU Regulation (eIDAS Regulation).
2.7 This EU Regulation will be amended after EU Exit so that eIDAS certificates issued in an
EU country will meet the requirements of the UK eIDAS framework and so continue to be legally valid in the UK.
2.8 Under the terms of the UK-RTS, firms will still have to use eIDAS certificates in the UK.

7
PS19/26
Chapter 2
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication Conversion of euro denominated financial thresholds from euro to sterling
2.9 Commission Delegated Regulation (EU) 2018/389 (SCA-RTS) includes financial
thresholds denominated in euro. For example, contactless payments up to €50 are exempt from strong customer authentication.
2.10 In CP18/44 we proposed to convert financial thresholds in the SCA-RTS from euro to
sterling in the UK-RTS. We proposed to use the Bank of England’s spot exchange rate on Exit day, and round down to the nearest £5.
2.11 In CP18/44 we asked:
Q1: Do you agree that we should make technical standards on strong customer authentication and common and secure open standards of communication? If not, please explain why. Q2: Do you agree with our proposed technical standards as set out in Appendix 1? If not, please explain why.
2.12 Most respondents mainly agreed with our approach. Some suggested changes to the
UK-RTS. Responses included:

concerns about whether TPPs operating in the UK would be able to access or use
eIDAS certificates, and risks to the continued functioning of open banking services after Exit day, and
uncertainty about currency exchange rate fluctuations on Exit day and the impact
of conversion of euro denominated financial thresholds from euro to sterling Our response eIDAS certificates The SCA-RTS fully came into effect on 14 September 2019. So, as it is important to maintain a level of consistency for the market, in the event of a no-deal Exit, the UK-RTS will require PSPs to continue to use eIDAS certificates. However, in August 2019, we wrote to trade bodies setting out the terms of a 6-month adjustment period for implementing the SCA-RTS. These terms explain how firms without an eIDAS certificate may rely on equivalent certificates enabling secure identification without risk of FCA enforcement action. In the event of a no-deal Exit, firms should treat those terms as applying to the UK-RTS. Conversion of euro denominated financial thresholds to sterling To avoid potential disruption, the UK-RTS includes the sterling values and conversion rate that we used in the CP.

8
PS19/26
Chapter 2
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication Sub-articles 30(3) and (5) of the SCA-RTS
2.13 In this chapter, we also summarise and respond to the feedback we received on our
proposed amendments to sub-articles 30(3) and (5) of the SCA-RTS).
2.14 In CP18/44, we proposed amendments to sub-articles 30(3) and (5) of the SCA-RTS
to ensure that they operated effectively if there was a no-deal Exit.
2.15 The main comment involved our proposed changes to the requirement for ASPSPs,
such as banks to make the necessary technical specification documents available to TPPs.
2.16 From 14 March 2019, the SCA-RTS required ASPSPs to make documents available to
TPPs with the technical specification for the routines, protocols and tools they needed to allow their software and applications to work with the ASPSPs’ systems.
2.17 In CP18/44 we asked:
Q3: Do you agree with our proposed amendments to sub-articles 30(3) and (5) of the SCA-RTS? If not, please explain why.
2.18 2.16 Most respondents supported our approach. One respondent suggested that
the changes to sub-article 30(3) should make clear if ASPSPs must make technical specification documentation available to Gibraltar-based TPPs. Our response In the event of a no-deal Exit, the Electronic Money, Payment Services and Payment Systems (Amendment and Transitional Provisions) (EU Exit) Regulations 2018 (Exit SI) will allow Gibraltar-based firms to continue to provide payment services in the UK after Exit day. The SCARTS requires ASPSPs to make technical specification documentation available to TPPs which have applied to their national competent authorities for authorisation. The UK-RTS applies to firms that are authorised and registered in the UK and Gibraltar. The national competent authorities that are relevant to this provision are the FCA and (in accordance with the Exit SI) the Gibraltar Financial Services Commission. We have clarified in sub-article 30(3) of the UK-RTS that ASPSPs must make documentation available to TPPs which have applied to the FCA or the Gibraltar Financial Services Commission for authorisation or registration. Due to the postponement of the original Exit day of 29 March 2019, the amended version of sub-articles 30(3) and (5) which we had proposed to make in CP18/44, as set out in Appendix 2, will form
part of the provisions of the UK-RTS.

9
PS19/26
Chapter 2
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication Making amendments to the Handbook
2.19 In CP18/44 we proposed making minor consequential amendments to the Handbook.
2.20 In CP18/44 we asked:
Q4: Do you agree with our proposed changes to the Handbook as set out in Appendix 3? If not, please explain why.
2.21 Respondents made no objections to our proposals.

10
PS19/26
Chapter 3
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication 3 Cost benefit analysis
3.1 In this chapter, we summarise and respond to feedback about the cost benefit analysis
for our proposals.
3.2 To help us assess the proportionality of our proposals, in CP18/44 we considered
whether they imposed costs on PSPs beyond those which were inherent in the SCA-RTS.
3.3 In CP18/44, we asked:
Q5: Do you agree with the costs and benefits we have identified? If not, please explain why.
3.4 No respondents disagreed.
3.5 The SCA-RTS has been in force since 14 March 2018 and fully took effect on 14
September 2019. In the event of a no-deal Exit, we will make the UK-RTS substantially in the form of the SCA-RTS. Therefore, the costs of implementation relate to the SCA-RTS and not to our proposal to make the UK-RTS. Moreover, unless we make the UK-RTS, the consumer benefits outlined in CP18/44 will not be realised.

11
PS19/26
Annex 1
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication
Annex 1
List of non-confidential respondents
Nationwide Building Society
The Electronic Money Association
The Open Banking Implementation Entity
UK Finance

12
PS19/26
Annex 2
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication
Annex 2
Abbreviations used in this paper
ASPSP Account servicing payment service provider CP Consultation paper PSD2 Revised Payment Services Directive PSP Payment service provider RTS Regulatory Technical Standards SCA-RTS Commission Delegated Regulation (EU) 2018/389 TPP Third-party provider UK-RTS RTS for strong customer authentication and common and secure open standards of communication made by the FCA We have developed the policy in this Policy Statement in the context of the existing UK and EU regulatory framework. The Government has made clear that it will continue to implement and apply EU law until the UK has left the EU. We will keep the proposals under review to assess whether any amendments may be required in the event of changes in the UK regulatory framework in the future. All our publications are available to download from www.fca.org.uk. If you would like to receive this paper in an alternative format, please call 020 7066 7948 or email: publications_graphics@fca.org.uk or write to: Editorial and Digital team, Financial Conduct Authority, 12 Endeavour Square, London E20 1JN

PS19/26
Appendix 1
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication
Appendix 1
Instrument making regulatory technical standards for strong customer authentication

FCA 2019/XX
TECHNICAL STANDARDS ON STRONG CUSTOMER AUTHENTICATION AND COMMON AND SECURE METHODS OF COMMUNICATION INSTRUMENT 2019 Powers exercised A. The Financial Conduct Authority (“the FCA”) makes this instrument in the exercise of the powers and related provisions in or under:
(1) the following Regulations of the Payment Services Regulations as amended by the Electronic Money, Payment Services and Payment Systems (Amendment and Transitional Provisions) (EU Exit) Regulations 2018 which comes into force on exit day as defined by the EU Withdrawal Act 2018:
(a) Regulation 106A (Technical Standards); and (b) Regulation 120 (Guidance); and (2) the following sections of the Financial Services and Markets Act 2000 (“the Act”) as amended by the Financial Regulators’ Powers (Technical Standards etc.) (Amendment etc.) (EU Exit) Regulations 2018:
(a) section 138P (Technical Standards);
(b) section 138Q (Standards instruments);
(c) section 138S (Application of Chapters 1 and 2); (d) section 137T (General supplementary powers); (e) section 138F (Notification of rules); and (f) section 138I (Consultation by the FCA). Pre-conditions to making B. The FCA has consulted the Prudential Regulation Authority and the Bank of England as appropriate in accordance with section 138P of the Act.
C. A draft of this instrument has been approved by the Treasury, in accordance with
section 138R of the Act.
Modifications
D.
(1) The FCA revokes the Commission Delegated Regulation (EU) 2018/389 of 27 November 2017 supplementing Directive (EU) 2015/2366 of the European Parliament and of the Council with regard to regulatory technical standards for strong customer authentication and common and secure open standards of communications in accordance with Annex A to this instrument.

FCA 2019/XX
(2) The FCA makes the Technical Standards on Strong Customer Authentication and Common and Secure Methods of Communication in accordance with
Annex B to this instrument.
Commencement
E. This instrument comes into force on 1 November 2019.
Citation
F. This instrument may be cited as the Technical Standards on Strong Customer Authentication and Common and Secure Methods of Communication Instrument 2019. By order of the Board [date]

FCA 2019/XX
Annex A
The FCA revokes the following EU Regulation:
Commission Delegated Regulation EU 2018/389 supplementing Directive (EU) 2015/2366 of the European Parliament and of the Council with regard to regulatory technical standards for strong customer authentication and common and secure open standards of communication.

FCA 2019/XX
In this Annex, the text is all new and is not underlined.
Annex B
Technical standards regarding strong customer authentication and common and secure open standards of communication.
Chapter -3
Application

These Standards are made by the Financial Conduct Authority pursuant to Regulation
106A of the Payment Services Regulations 2017 as amended by the Electronic Money, Payment Services and Payment Systems (Amendment and Transitional Provisions) (EU Exit) Regulations 2018 in order to specify:
(a) the requirements that must be met by strong customer authentication referred to in Regulation 100(1) and (2); (b) the exemption from the application of Regulation 100(1), (2) and (3); (c) the requirements with which security measures have to comply to protect the confidentiality and integrity of payment service users' personalised security credentials; (d) the requirements for common and secure open standards of communication for the purpose of identification, authentication, notification and information, as well as for the implementation of security measures, between account servicing payment service providers, account information service providers, payers, payees and other payment service providers.
These Standards apply to payment service providers authorised or registered in the
UK or Gibraltar, including account servicing payment service providers and account information service providers.
These Standards also apply to payment service providers who have temporary
permission in accordance with paragraphs 2 and 14 of Schedule 3 of the Payment Services Regulations 2017 and the Electronic Money Regulations 2011 as amended by the Electronic Money, Payment Services and Payment Systems (Amendment and Transitional Provisions) (EU Exit) Regulations 2018.
These Standards also apply to payment service providers who have continued
authorisation for a limited purpose in accordance with paragraph 12B of Part 1A and paragraph 26 of Part 3 of the Payment Services Regulations and Electronic Money

FCA 2019/XX
Regulations as amended by the Financial Services Contracts (Transitional and Saving Provision) (EU Exit) Regulations 2019.

FCA 2019/XX
Chapter -2
Definitions
In these Standards:
1. references to the Payment Services Regulations 2017 (SI 2017/752) are references to
the Payment Services Regulations as amended by the Electronic Money, Payment Services and Payment Systems (Amendment and Transitional Provisions) (EU Exit) Regulations 2018;
2. where a term is defined in the Payment Services Regulations 2017 (SI 2017/752), that
definition shall apply unless the contrary intention appears.
Chapter -1
Guidance
1. Payment services offered electronically should be carried out in a secure manner,
adopting technologies able to guarantee the safe authentication of the user and to reduce, to the maximum extent possible, the risk of fraud. The authentication procedure should include, in general, transaction monitoring mechanisms to detect attempts to use a payment service user’s personalised security credentials that were lost, stolen, or misappropriated and should also ensure that the payment service user is the legitimate user and therefore is giving consent for the transfer of funds and access to its account information through a normal use of the personalised security credentials. Furthermore, it is necessary to specify the requirements of the strong customer authentication that should be applied each time a payer accesses its payment account online, initiates an electronic payment transaction or carries out any action through a remote channel which may imply a risk of payment fraud or other abuse, by requiring the generation of an authentication code which should be resistant against the risk of being forged in its entirety or by disclosure of any of the elements upon which the code was generated.
2. As fraud methods are constantly changing, the requirements of strong customer
authentication should allow for innovation in the technical solutions addressing the emergence of new threats to the security of electronic payments. To ensure that the requirements to be laid down are effectively implemented on a continuous basis, it is also appropriate to require that the security measures for the application of strong customer authentication and its exemptions, the measures to protect confidentiality and integrity of the personalised security credentials, and the measures establishing common and secure open standards of communication are documented, periodically tested, evaluated and audited by auditors with expertise in IT security and payments, and operationally independent. In order to allow the FCA to monitor the quality of the

FCA 2019/XX review of these measures, such reviews should be made available to the FCA upon its request.
3. As electronic remote payment transactions are subject to a higher risk of fraud, it is
necessary to introduce additional requirements for the strong customer authentication of such transactions, ensuring that the elements dynamically link the transaction to an amount and a payee specified by the payer when initiating the transaction.
4. Dynamic linking is possible through the generation of authentication codes, which are
subject to a set of strict security requirements. To remain technologically neutral, a specific technology for the implementation of authentication codes should not be required. Therefore authentication codes should be based on solutions such as generating and validating one-time passwords, digital signatures or other cryptographically underpinned validity assertions using keys or cryptographic material stored in the authentication elements, as long as the security requirements are fulfilled.
5. It is necessary to lay down specific requirements for the situation where the final
amount is not known at the moment the payer initiates an electronic remote payment transaction, in order to ensure that the strong customer authentication is specific to the maximum amount that the payer has given consent for as referred to in the Payment Services Regulations 2017 (SI 2017/752).
6. In order to ensure the application of strong customer authentication, it is also
necessary to require adequate security features for the elements of strong customer authentication categorised as knowledge (something only the user knows), such as length or complexity, for the elements categorised as possession (something only the user possesses), such as algorithm specifications, key length and information entropy, and for the devices and software that read elements categorised as inherence (something the user is), such as algorithm specifications, and biometric sensor and template protection features, in particular to mitigate the risk that those elements are uncovered, disclosed to and used by unauthorised parties. It is also necessary to lay down the requirements to ensure that those elements are independent, so that the breach of one does not compromise the reliability of the others, in particular when any of these elements are used through a multi-purpose device, such as a tablet or a mobile phone which can be used both for giving the instruction to make the payment and in the authentication process.
7. The requirements of strong customer authentication apply to payments initiated by the
payer, regardless of whether the payer is a natural person or a legal entity.
8. Due to their very nature, payments made through the use of an anonymous payment
instrument are not subject to the obligation of strong customer authentication. Where the anonymity of such instruments is lifted on contractual or legislative grounds, payments are subject to the security requirements that follow from the Payment Services Regulations 2017 (SI 2017/752) and this Regulatory Technical Standard.
9. In accordance with the Payment Services Regulations 2017 (SI 2017/752),
exemptions to the principle of strong customer authentication have been defined based on the level of risk, amount, recurrence and the payment channel used for the execution of the payment transaction.

FCA 2019/XX
10. Actions which imply access to the balance and the recent transactions of a payment
account without disclosure of sensitive payment data, recurring payments to the same payees which have been previously set up or confirmed by the payer through the use of strong customer authentication, and payments to and from the same natural or legal person with accounts with the same payment service provider pose a low level of risk, thus allowing payment service providers not to apply strong customer authentication. This leaves aside that in accordance with regulations 68, 69 and 70 of the Payment Services Regulations 2017 (SI 2017/752), payment initiation service providers, payment service providers issuing card-based payment instruments and account information service providers should only seek and obtain the necessary and essential information from the account servicing payment service provider for the provision of a given payment service with the consent of the payment service user. Such consent can be given individually for each request of information or for each payment to be initiated or, for account information service providers, as a mandate for designated payment accounts and associated payment transactions as established in the contractual agreement with the payment service user.
11. Exemptions for low-value contactless payments at points of sale, which also take into
account a maximum number of consecutive transactions or a certain fixed maximum value of consecutive transactions without applying strong customer authentication, allow for the development of user-friendly and low-risk payment services and should therefore be provided for. It is also appropriate to establish an exemption for the case of electronic payment transactions initiated at unattended terminals, where the use of strong customer authentication may not always be easy to apply due to operational reasons (e.g. to avoid queues and potential accidents at toll gates or for other safety or security risks).
12. Similar to the exemption for low-value contactless payments at the point of sale, a
proper balance needs to be struck between the interest in enhanced security in remote payments and the needs of user-friendliness and accessibility of payments in the area of e-commerce. In line with those principles, thresholds below which no strong customer authentication needs to be applied should be set in a prudent manner, to cover only online purchases of low value. The thresholds for online purchases should be set more prudently, considering that the fact that the person is not physically present when making the purchase poses a slightly higher security risk.
13. The requirements of strong customer authentication apply to payments initiated by the
payer, regardless of whether the payer is a natural person or a legal entity. Many corporate payments are initiated through dedicated processes or protocols which guarantee the high levels of payment security that the Payment Services Regulations 2017 (SI 2017/752) aims to achieve through strong customer authentication. Where the FCA establishes that those payment processes and protocols that are only made available to payers who are not consumers achieve the objectives of The Payment Services Regulations 2017 (SI 2017/752) in terms of security, payment service providers may, in relation to those processes or protocols, be exempted from the strong customer authentication requirements.
14. In the case of real-time transaction risk analysis that categorises a payment transaction
as low risk, it is also appropriate to introduce an exemption for the payment service provider that intends not to apply strong customer authentication through the adoption of effective and risk-based requirements which ensure the safety of the payment

FCA 2019/XX service user’s funds and personal data. Those risk-based requirements should combine the scores of the risk analysis, confirming that no abnormal spending or behavioural pattern of the payer has been identified, taking into account other risk factors including information on the location of the payer and of the payee with monetary thresholds based on fraud rates calculated for remote payments. Where, on the basis of the real-time transaction risk analysis, a payment cannot be qualified as posing a low level of risk, the payment service provider should revert to strong customer authentication. The maximum value of such risk-based exemption should be set in a manner ensuring a very low corresponding fraud rate, also by comparison to the fraud rates of all the payment transactions of the payment service provider, including those authenticated through strong customer authentication, within a certain period of time and on a rolling basis.
15. For the purpose of ensuring an effective enforcement, payment service providers that
wish to benefit from the exemptions from strong customer authentication should regularly monitor and make available to the FCA upon its request, for each payment transaction type, the value of fraudulent or unauthorised payment transactions and the observed fraud rates for all their payment transactions, whether authenticated through strong customer authentication or executed under a relevant exemption.
16. The collection of this new historical evidence on the fraud rates of electronic payment
transactions will also contribute to an effective review by the FCA of the thresholds for an exemption to strong customer authentication based on a real-time transaction risk analysis. The FCA should review and if appropriate update these Standards, including where appropriate the thresholds and fraud rates, with the aim of enhancing the security of remote electronic payments, on a regular basis to take account of innovation and technical developments as well as other relevant matters.
17. Payment service providers that make use of any of the exemptions to be provided for
should be allowed at any time to choose to apply strong customer authentication to the actions and to the payment transactions referred to in those provisions.
18. The measures that protect the confidentiality and integrity of personalised security
credentials, as well as authentication devices and software, should limit the risks relating to fraud through unauthorised or fraudulent use of payment instruments and unauthorised access to payment accounts. To this end it is necessary to introduce requirements on the secure creation and delivery of the personalised security credentials and their association with the payment service user, and to provide conditions for the renewal and deactivation of those credentials.
19. In order to ensure effective and secure communication between the relevant actors in
the context of account information services, payment initiation services and confirmation on the availability of funds, it is necessary to specify the requirements of common and secure open standards of communication to be met by all relevant payment service providers. The Payment Services Regulations 2017 (SI 2017/752) provide for the access and use of payment account information by account information service providers. These Standards therefore do not change the rules of access to accounts other than payment accounts.
20. Each account servicing payment service provider with payment accounts that are
accessible online should offer at least one access interface enabling secure

FCA 2019/XX communication with account information service providers, payment initiation service providers and payment service providers issuing card-based payment instruments. The interface should enable the account information service providers, payment initiation service providers and payment service providers issuing card-based payment instruments to identify themselves to the account servicing payment service provider. It should also allow account information service providers and payment initiation service providers to rely on the authentication procedures provided by the account servicing payment service provider to the payment service user. To ensure technology and business model neutrality, the account servicing payment service providers should be free to decide whether to offer an interface that is dedicated to the communication with account information service providers, payment initiation service providers, and payment service providers issuing card-based payment instruments, or to allow, for that communication, the use of the interface for the identification and communication with the account servicing payment service providers’ payment service users.
21. In order to allow account information service providers, payment initiation service
providers, and payment service providers issuing card-based payment instruments to develop their technical solutions, the technical specification of the interface should be adequately documented and made publicly available. The effect of Articles 30(3) and (5) is that the account servicing payment service provider should offer a facility enabling the payment service providers to test the technical solutions at least six months, prior to the date on which the interface will be launched to the market. To ensure the interoperability of different technological communication solutions, the interface should use standards of communication which are developed by international standardisation organisations.
22. The quality of the services provided by account information service providers and
payment initiation service providers will depend on the proper functioning of the interfaces put in place or adapted by account servicing payment service providers. It is therefore important that in case of non-compliance of such interfaces with the provisions included in these Standards, measures are taken to guarantee business continuity for the benefit of the users of those services. It is the responsibility of the FCA to ensure that account information service providers and payment initiation service providers are not blocked or obstructed in the provision of their services.
23. Where access to payment accounts is offered by means of a dedicated interface, in
order to ensure the right of payment service users to make use of payment initiation service providers and of services enabling access to account information, as provided for in the Payment Services Regulations 2017 (SI 2017/752), it is necessary to require that dedicated interfaces have the same level of availability and performance as the interface available to the payment service user. Account servicing payment service providers should also define transparent key performance indicators and service level targets for the availability and performance of dedicated interfaces that are at least as stringent as those for the interface used for their payment service users. Those interfaces should be tested by the payment service providers who will use them, and should be stress-tested and monitored by the FCA.
24. To ensure that payment service providers who rely on the dedicated interface can
continue to provide their services in case of problems of availability or inadequate performance, it is necessary to provide, subject to strict conditions, a fallback

FCA 2019/XX mechanism that will allow such providers to use the interface that the account servicing payment service provider maintains for the identification of, and communication with, its own payment service users. Certain account servicing payment service providers will be exempted from having to provide such a fallback mechanism through their customer-facing interfaces where the FCA establishes that the dedicated interfaces comply with specific conditions that ensure unhampered competition. In the event that the exempted dedicated interfaces fail to comply with the required conditions, the granted exemptions shall be revoked by the FCA.
25. In order to allow the FCA to effectively supervise and monitor the implementation
and management of the communication interfaces, the account servicing payment service providers should make a summary of the relevant documentation available on their website, and provide, upon request, the FCA with documentation of the solutions in case of emergencies. The account servicing payment service providers should also make publicly available the statistics on the availability and performance of that interface.
26. In order to safeguard the confidentiality and the integrity of data, it is necessary to
ensure the security of communication sessions between account servicing payment service providers, account information service providers, payment initiation service providers and payment service providers issuing card-based payment instruments. It is in particular, necessary to require that secure encryption is applied between account information service providers, payment initiation service providers, payment service providers issuing card-based payment instruments and account servicing payment service providers when exchanging data.
27. To improve user confidence and ensure strong customer authentication, the use of
electronic identification means and trust services as set out in Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust service for electronic transactions in the internal market, as amended by the Electronic Identification and Trust Services for Electronic Transactions (Amendment etc.) (EU Exit) Regulations 2018 as came into force on exit day as defined in the EU (Withdrawal) Act 2018, should be taken into account, in particular with regard to notified electronic identification schemes.

FCA 2019/XX
Chapter 1
General provisions
Article 1
Subject matter
These Standards establish the requirements to be complied with by payment service providers for the purpose of implementing security measures which enable them to do the following:
(a) apply the procedure of strong customer authentication in accordance with Regulation 100 of the Payment Services Regulations 2017 (SI 2017/752); (b) exempt the application of the security requirements of strong customer authentication, subject to specified and limited conditions based on the level of risk, the amount and the recurrence of the payment transaction and of the payment channel used for its execution; (c) protect the confidentiality and the integrity of the payment service user’s personalised security credentials; (d) establish common and secure open standards for the communication between account servicing payment service providers, payment initiation service providers, account information service providers, payers, payees and other payment service providers in relation to the provision and use of payment services in application of Part 7 of the Payment Services Regulations 2017 (SI 2017/752).
Article 2
General authentication requirements

Payment service providers shall have transaction monitoring mechanisms in place that
enable them to detect unauthorised or fraudulent payment transactions for the purpose of the implementation of the security measures referred to in points (a) and (b) of
Article 1.
Those mechanisms shall be based on the analysis of payment transactions taking into account elements which are typical of the payment service user in the circumstances of a normal use of the personalised security credentials.
Payment service providers shall ensure that the transaction monitoring mechanisms
take into account, at a minimum, each of the following risk-based factors:

FCA 2019/XX
(a) lists of compromised or stolen authentication elements; (b) the amount of each payment transaction; (c) known fraud scenarios in the provision of payment services; (d) signs of malware infection in any sessions of the authentication procedure; (e) in case the access device or the software is provided by the payment service provider, a log of the use of the access device or the software provided to the payment service user and the abnormal use of the access device or the software.
Article 3
Review of the security measures

The implementation of the security measures referred to in Article 1 shall be
documented, periodically tested, evaluated and audited in accordance with the applicable legal framework of the payment service provider by auditors with expertise in IT security and payments and operationally independent within or from the payment service provider.
The period between the audits referred to in paragraph 1 shall be determined taking
into account the relevant accounting and statutory audit framework applicable to the payment service provider. However, payment service providers that make use of the exemption referred to in
Article 18 shall be subject to an audit of the methodology, the model and the reported
fraud rates at a minimum on a yearly basis. The auditor performing this audit shall have expertise in IT security and payments and be operationally independent within or from the payment service provider. During the first year of making use of the exemption under Article 18 and at least every three years thereafter, or more frequently at the FCA’s request, this audit shall be carried out by an independent and qualified external auditor.
This audit shall present an evaluation and report on the compliance of the payment
service provider’s security measures with the requirements set out in these Standards. The entire report shall be made available to the FCA upon its request.

FCA 2019/XX
Chapter 2
Security measures for the application of strong customer authentication
Article 4
Authentication code

Where payment service providers apply strong customer authentication in accordance
with Regulation 100 of the Payment Services Regulation 2017 (SI 2017/752), 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.
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.
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 Regulation 100(1) of the Payment Services Regulations 2017 (SI 2017/752) 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 5. (d) the maximum time without activity by the payer after being authenticated for accessing its payment account online shall not exceed five minutes.

FCA 2019/XX
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.
Article 5
Dynamic linking

Where payment service providers apply strong customer authentication in accordance
with Regulation 100(2) of the Payment Services Regulations 2017 (SI 2017/752), in addition to the requirements of Article 4 of these Standards, they shall also adopt security measures that meet each of the following requirements:
(a) the payer is made aware of the amount of the payment transaction and of the payee; (b) the authentication code generated is specific to the amount of the payment transaction and the payee agreed to by the payer when initiating the transaction; (c) the authentication code accepted by the payment service provider corresponds to the original specific amount of the payment transaction and to the identity of the payee agreed to by the payer; (d) any change to the amount or the payee results in the invalidation of the authentication code generated.
For the purpose of paragraph 1, payment service providers shall adopt security
measures which ensure the confidentiality, authenticity and integrity of each of the following:
(a) the amount of the transaction and the payee throughout all of the phases of the authentication; (b) the information displayed to the payer throughout all of the phases of the authentication including the generation, transmission and use of the authentication code.
For the purpose of paragraph 1(b) and where payment service providers apply strong
customer authentication in accordance with Regulation 100(2) of the Payment Services Regulations 2017 (SI 2017/752) the following requirements for the authentication code shall apply:

FCA 2019/XX
(a) in relation to a card-based payment transaction for which the payer has given consent to the exact amount of the funds to be blocked pursuant to Regulation 78 of the Payment Services Regulations 2017 (SI 2017/752), the authentication code shall be specific to the amount that the payer has given consent to be blocked and agreed to by the payer when initiating the transaction; (b) in relation to payment transactions for which the payer has given consent to execute a batch of remote electronic payment transactions to one or several payees, the authentication code shall be specific to the total amount of the batch of payment transactions and to the specified payees.
Article 6
Requirements of the elements categorised as knowledge
1. Payment service providers shall adopt measures to mitigate the risk that the elements
of strong customer authentication categorised as knowledge are uncovered by, or disclosed to, unauthorised parties.
2. The use by the payer of those elements shall be subject to mitigation measures in
order to prevent their disclosure to unauthorised parties.
Article 7
Requirements of the elements categorised as possession
1. Payment service providers shall adopt measures to mitigate the risk that the elements
of strong customer authentication categorised as possession are used by unauthorised parties.
2. The use by the payer of those elements shall be subject to measures designed to
prevent replication of the elements.
Article 8
Requirements of devices and software linked to elements categorised as inherence
1. Payment service providers shall adopt measures to mitigate the risk that the
authentication elements categorised as inherence and read by access devices and

FCA 2019/XX software provided to the payer are uncovered by unauthorised parties. At a minimum, the payment service providers shall ensure that those access devices and software have a very low probability of an unauthorised party being authenticated as the payer.
2. The use by the payer of those elements shall be subject to measures ensuring that
those devices and the software guarantee resistance against unauthorised use of the elements through access to the devices and the software.
Article 9
Independence of the elements
1. Payment service providers shall ensure that the use of the elements of strong customer
authentication referred to in Articles 6, 7 and 8 is subject to measures which ensure that, in terms of technology, algorithms and parameters, the breach of one of the elements does not compromise the reliability of the other elements.
2. Payment service providers shall adopt security measures, where any of the elements
of strong customer authentication or the authentication code itself is used through a multi-purpose device, to mitigate the risk which would result from that multi-purpose device being compromised.
3. For the purposes of paragraph 2, the mitigating measures shall include each of the
following:
(a) the use of separated secure execution environments through the software installed inside the multi-purpose device; (b) mechanisms to ensure that the software or device has not been altered by the payer or by a third party; (c) where alterations have taken place, mechanisms to mitigate the consequences thereof.
Chapter 3
Exemptions from strong customer authentication
Article 10
Payment account information
1. Payment service providers shall be allowed not to apply strong customer
authentication, subject to compliance with the requirements laid down in Article 2 and

FCA 2019/XX to paragraph 2 of this Article and, where a payment service user is limited to accessing either or both of the following items online without disclosure of sensitive payment data:
(a) the balance of one or more designated payment accounts; (b) the payment transactions executed in the last 90 days through one or more designated payment accounts.
2. For the purpose of paragraph 1, payment service providers shall not be exempted from
the application of strong customer authentication where either of the following conditions are met:
(a) the payment service user is accessing online the information specified in paragraph 1 for the first time; (b) more than 90 days have elapsed since the last time the payment service user accessed online the information specified in paragraph 1(b) and strong customer authentication was applied.
Article 11
Contactless payments at point of sale
Payment service providers shall be allowed not to apply strong customer authentication, subject to compliance with the requirements laid down in Article 2, where the payer initiates a contactless electronic payment transaction provided that the following conditions are met:
(a) the individual amount of the contactless electronic payment transaction does not exceed £40; and (b) the cumulative amount of previous contactless electronic payment transactions initiated by means of a payment instrument with a contactless functionality from the date of the last application of strong customer authentication does not exceed £130; or (c) the number of consecutive contactless electronic payment transactions initiated via the payment instrument offering a contactless functionality since the last application of strong customer authentication does not exceed five.

FCA 2019/XX
Article 12
Unattended terminals for transport fares and parking fees Payment service providers shall be allowed not to apply strong customer authentication, subject to compliance with the requirements laid down in Article 2, where the payer initiates an electronic payment transaction at an unattended payment terminal for the purpose of paying a transport fare or a parking fee.
Article 13
Trusted beneficiaries
1. Payment service providers shall apply strong customer authentication where a payer
creates or amends a list of trusted beneficiaries through the payer’s account servicing payment service provider.
2. Payment service providers shall be allowed not to apply strong customer
authentication, subject to compliance with the general authentication requirements, where the payer initiates a payment transaction and the payee is included in a list of trusted beneficiaries previously created by the payer.
Article 14
Recurring transactions
1. Payment service providers shall apply strong customer authentication when a payer
creates, amends, or initiates for the first time, a series of recurring transactions with the same amount and with the same payee.
2. Payment service providers shall be allowed not to apply strong customer
authentication, subject to compliance with the general authentication requirements, for the initiation of all subsequent payment transactions included in the series of payment transactions referred to in paragraph 1.

FCA 2019/XX
Article 15
Credit transfers between accounts held by the same natural or legal person Payment service providers shall be allowed not to apply strong customer authentication, subject to compliance with the requirements laid down in Article 2, where the payer initiates a credit transfer in circumstances where the payer and the payee are the same natural or legal person and both payment accounts are held by the same account servicing payment service provider.
Article 16
Low-value transactions
Payment service providers shall be allowed not to apply strong customer authentication, where the payer initiates a remote electronic payment transaction provided that the following conditions are met:
(a) the amount of the remote electronic payment transaction does not exceed £25; and (b) the cumulative amount of previous remote electronic payment transactions initiated by the payer since the last application of strong customer authentication does not exceed £85; or (c) the number of previous remote electronic payment transactions initiated by the payer since the last application of strong customer authentication does not exceed 5 consecutive individual remote electronic payment transactions.
Article 17
Secure corporate payment processes and protocols Payment service providers shall be allowed not to apply strong customer authentication, in respect of legal persons initiating electronic payment transactions through the use of dedicated payment processes or protocols that are only made available to payers who are not consumers, where the FCA is satisfied that those processes or protocols guarantee at least equivalent levels of security to those provided for by the Payment Services Regulations 2017 (SI 2017/752).

FCA 2019/XX
Article 18
Transaction risk analysis

Payment service providers shall be allowed not to apply strong customer
authentication where the payer initiates a remote electronic payment transaction identified by the payment service provider as posing a low level of risk according to the transaction monitoring mechanisms referred to in Article 2 and in paragraph 2(c) of this Article.
An electronic payment transaction referred to in paragraph 1 shall be considered as
posing a low level of risk where all the following conditions are met:
(a) the fraud rate for that type of transaction, reported by the payment service provider and calculated in accordance with Article 19, is equivalent to or below the reference fraud rates specified in the table set out in the Annex for ‘remote electronic card-based payments’ and ‘remote electronic credit transfers’ respectively; (b) the amount of the transaction does not exceed the relevant Exemption Threshold Value (‘ETV’) specified in the table set out in the Appendix; (c) payment service providers as a result of performing a real-time risk analysis have not identified any of the following:
(i) abnormal spending or behavioural pattern of the payer; (ii) unusual information about the payer’s device/software access; (iii) malware infection in any session of the authentication procedure; (iv) known fraud scenario in the provision of payment services; (v) abnormal location of the payer; (vi) high risk location of the payee.
Payment service providers that intend to exempt electronic remote payment
transactions from strong customer authentication on the ground that they pose a low risk shall take into account at a minimum, the following risk-based factors:
(a) the previous spending patterns of the individual payment service user; (b) the payment transaction history of each of the payment service provider’s payment service users; (c) the location of the payer and of the payee at the time of the payment transaction in cases where the access device or the software is provided by the payment service provider;

FCA 2019/XX
(d) the identification of abnormal payment patterns of the payment service user in relation to the user’s payment transaction history. The assessment made by a payment service provider shall combine all those risk-based factors into a risk scoring for each individual transaction to determine whether a specific payment should be allowed without strong customer authentication.
Article 19
Calculation of fraud rates
1. For each type of transaction referred to in the table set out in the Annex, the payment
service provider shall ensure that the overall fraud rates covering both payment transactions authenticated through strong customer authentication and those executed under any of the exemptions referred to in Articles 13 to 18 are equivalent to, or lower than, the reference fraud rate for the same type of payment transaction indicated in the
table set out in the Appendix.
The overall fraud rate for each type of transaction shall be calculated as the total value of unauthorised or fraudulent remote transactions, whether the funds have been recovered or not, divided by the total value of all remote transactions for the same type of transactions, whether authenticated with the application of strong customer authentication or executed under any exemption referred to in Articles 13 to 18 on a rolling quarterly basis (90 days).
2. The calculation of the fraud rates and resulting figures shall be assessed by the audit
review referred to in Article 3(2), which shall ensure that they are complete and accurate.
3. The methodology and any model, used by the payment service provider to calculate
the fraud rates, as well as the fraud rates themselves, shall be adequately documented and made fully available to the FCA, upon its request.
Article 20
Cessation of exemptions based on transaction risk analysis
1. Payment service providers that make use of the exemption referred to in Article 18
shall immediately report to the FCA where one of their monitored fraud rates, for any type of payment transactions indicated in the table set out in the Appendix exceeds the applicable reference fraud rate and shall provide to the FCA a description of the measures that they intend to adopt to restore compliance of their monitored fraud rate with the applicable reference fraud rates.

FCA 2019/XX
2. Payment service providers shall immediately cease to make use of the exemption
referred to in Article 18 for any type of payment transactions indicated in the table set out in the Annex in the specific exemption threshold range where their monitored fraud rate exceeds for two consecutive quarters the reference fraud rate applicable for that payment instrument or type of payment transaction in that exemption threshold range.
3. Following the cessation of the exemption referred to in Article 18 in accordance with
paragraph 2 of this Article, payment service providers shall not use that exemption again, until their calculated fraud rate equals to, or is below, the reference fraud rates applicable for that type of payment transaction in that exemption threshold range for one quarter.
4. Where payment service providers intend to make use again of the exemption referred
to in Article 18, they shall notify the FCA in a reasonable timeframe and shall before making use again of the exemption, provide evidence of the restoration of compliance of their monitored fraud rate with the applicable reference fraud rate for that exemption threshold range in accordance with paragraph 3 of this Article.
Article 21
Monitoring

In order to make use of the exemptions set out in Articles 10 to 18, payment service
providers shall record and monitor the following data for each type of payment transaction, with a breakdown for both remote and non-remote payment transactions, at least on a quarterly basis:
(a) the total value of unauthorised or fraudulent payment transactions in accordance with regulation 67(2) of the Payment Services Regulations 2017 (SI 2017/752), the total value of all payment transactions and the resulting fraud rate, including a breakdown of payment transactions initiated through strong customer authentication and under each of the exemptions; (b) the average transaction value, including a breakdown of payment transactions initiated through strong customer authentication and under each of the exemptions; (c) the number of payment transactions where each of the exemptions was applied and their percentage in respect of the total number of payment transactions.
Payment service providers shall make the results of the monitoring in accordance with
paragraph 1 available to the FCA upon its request.

FCA 2019/XX
Chapter 4
Confidentiality and integrity of the payment service users’ personalised security credentials
Article 22
General requirements

Payment service providers shall ensure the confidentiality and integrity of the
personalised security credentials of the payment service user, including authentication codes, during all phases of the authentication.
For the purpose of paragraph 1, payment service providers shall ensure that each of
the following requirements is met:
(a) personalised security credentials are masked when displayed and are not readable in their full extent when input by the payment service user during the authentication; (b) personalised security credentials in data format, as well as cryptographic materials related to the encryption of the personalised security credentials are not stored in plain text; (c) secret cryptographic material is protected from unauthorised disclosure.
Payment service providers shall fully document the process related to the
management of cryptographic material used to encrypt or otherwise render unreadable the personalised security credentials.
Payment service providers shall ensure that the processing and routing of personalised
security credentials and of the authentication codes generated in accordance with
Chapter 2 take place in secure environments in accordance with strong and widely
recognised industry standards.
Article 23
Creation and transmission of credentials
Payment service providers shall ensure that the creation of personalised security credentials is performed in a secure environment. They shall mitigate the risks of unauthorised use of the personalised security credentials and of the authentication devices and software following their loss, theft or copying before their delivery to the payer.

FCA 2019/XX
Article 24
Association with the payment service user
1. Payment service providers shall ensure that only the payment service user is
associated, in a secure manner, with the personalised security credentials, the authentication devices and the software.
2. For the purpose of paragraph 1, payment service providers shall ensure that each of
the following requirements is met:
(a) the association of the payment service user’s identity with personalised security credentials, authentication devices and software is carried out in secure environments under the payment service provider’s responsibility comprising at least the payment service provider’s premises, the internet environment provided by the payment service provider or other similar secure websites used by the payment service provider and its automated teller machine services, and taking into account risks associated with devices and underlying components used during the association process that are not under the responsibility of the payment service provider; (b) the association by means of a remote channel of the payment service user’s identity with the personalised security credentials and with authentication devices or software is performed using strong customer authentication.
Article 25
Delivery of credentials, authentication devices and software
1. Payment service providers shall ensure that the delivery of personalised security
credentials, authentication devices and software to the payment service user is carried out in a secure manner designed to address the risks related to their unauthorised use due to their loss, theft or copying.
2. For the purpose of paragraph 1, payment service providers shall at least apply each of
the following measures:
(a) effective and secure delivery mechanisms ensuring that the personalised security credentials, authentication devices and software are delivered to the legitimate payment service user; (b) mechanisms that allow the payment service provider to verify the authenticity of the authentication software delivered to the payment services user by means of the internet;

FCA 2019/XX
(c) arrangements ensuring that, where the delivery of personalised security credentials is executed outside the premises of the payment service provider or through a remote channel:
(i) no unauthorised party can obtain more than one feature of the personalised security credentials, the authentication devices or software when delivered through the same channel; (ii) the delivered personalised security credentials, authentication devices or software require activation before usage; (d) arrangements ensuring that, in cases where the personalised security credentials, the authentication devices or software have to be activated before their first use, the activation shall take place in a secure environment in accordance with the association procedures referred to in Article 24.
Article 26
Renewal of personalised security credentials Payment service providers shall ensure that the renewal or re-activation of personalised security credentials adhere to the procedures for the creation, association and delivery of the credentials and of the authentication devices in accordance with Articles 23, 24 and 25.
Article 27
Destruction, deactivation and revocation
Payment service providers shall ensure that they have effective processes in place to apply each of the following security measures:
(a) the secure destruction, deactivation or revocation of the personalised security credentials, authentication devices and software; (b) where the payment service provider distributes reusable authentication devices and software, the secure re-use of a device or software is established, documented and implemented before making it available to another payment services user; (c) the deactivation or revocation of information related to personalised security credentials stored in the payment service provider’s systems and databases and, where relevant, in public repositories.

FCA 2019/XX
Chapter 5
Common and secure open standards of communication
Section 1
General requirements for communication
Article 28
Requirements for identification
1. Payment service providers shall ensure secure identification when communicating
between the payer’s device and the payee’s acceptance devices for electronic payments, including but not limited to payment terminals.
2. Payment service providers shall ensure that the risks of misdirection of
communication to unauthorised parties in mobile applications and other payment services users’ interfaces offering electronic payment services are effectively mitigated.
Article 29
Traceability
1. Payment service providers shall have processes in place which ensure that all payment
transactions and other interactions with the payment services user, with other payment service providers and with other entities, including merchants, in the context of the provision of the payment service are traceable, ensuring knowledge ex-post of all events relevant to the electronic transaction in all the various stages.
2. For the purpose of paragraph 1, payment service providers shall ensure that any
communication session established with the payment services user, other payment service providers and other entities, including merchants, relies on each of the following:
(a) a unique identifier of the session;
(b) security mechanisms for the detailed logging of the transaction, including transaction number, timestamps and all relevant transaction data; (c) timestamps which shall be based on a unified time-reference system and which shall be synchronised according to an official time signal.

FCA 2019/XX
Section 2
Specific requirements for the common and secure open standards of communication
Article 30
General obligations for access interfaces

Account servicing payment service providers that offer to a payer a payment account
that is accessible online shall have in place at least one interface which meets each of the following requirements:
(a) account information service providers, payment initiation service providers and payment service providers issuing card-based payment instruments are able to identify themselves towards the account servicing payment service provider; (b) account information service providers are able to communicate securely to request and receive information on one or more designated payment accounts and associated payment transactions; (c) payment initiation service providers are able to communicate securely to initiate a payment order from the payer’s payment account and receive all information on the initiation of the payment transaction and all information accessible to the account servicing payment service providers regarding the execution of the payment transaction.
For the purposes of authentication of the payment service user, the interface referred
to in paragraph 1 shall allow account information service providers and payment initiation service providers to rely on all the authentication procedures provided by the account servicing payment service provider to the payment service user. The interface shall at least meet all of the following requirements:
(a) a payment initiation service provider or an account information service provider shall be able to instruct the account servicing payment service provider to start the authentication based on the consent of the payment service user; (b) communication sessions between the account servicing payment service provider, the account information service provider, the payment initiation service provider and any payment service user concerned shall be established and maintained throughout the authentication; (c) the integrity and confidentiality of the personalised security credentials and of authentication codes transmitted by or through the payment initiation service provider or the account information service provider shall be ensured.

FCA 2019/XX
3. Account servicing payment service providers shall ensure that their interfaces follow
standards of communication which are issued by international standardisation organisations. Account servicing payment service providers shall also ensure that the technical specification of any of the interfaces is documented specifying a set of routines, protocols, and tools needed by payment initiation service providers, account information service providers and payment service providers issuing card-based payment instruments for allowing their software and applications to interoperate with the systems of the account servicing payment service providers. Account servicing payment service providers shall at a minimum, and no less than six months before the target date for the market launch of the access interface, make the documentation available, at no charge, upon request by authorised payment initiation service providers, account information service providers and payment service providers issuing card-based payment instruments or payment service providers that have applied to the FCA or the Gibraltar Financial Services Commission for the relevant authorisation, and shall make a summary of the documentation publicly available on their website.
4. In addition to paragraph 3, account servicing payment service providers shall ensure
that, except for emergency situations, any change to the technical specification of their interface is made available to authorised payment initiation service providers, account information service providers and payment service providers issuing cardbased payment instruments, or payment service providers that have applied to the FCA or the Gibraltar Financial Services Commission for the relevant authorisation, in advance as soon as possible and not less than 3 months before the change is implemented. Payment service providers shall document emergency situations where changes were implemented and make the documentation available to the FCA on request.
5. Account servicing payment service providers shall make available a testing facility,
including support, for connection and functional testing to enable authorised payment initiation service providers, payment service providers issuing card-based payment instruments and account information service providers, or payment service providers that have applied for the relevant authorisation, to test their software and applications used for offering a payment service to users. This testing facility should be made available no later than six months before the target date for the market launch of the access interface. However, no sensitive information shall be shared through the testing facility.
6. The FCA shall ensure that account servicing payment service providers comply at all
times with the obligations included in these Standards in relation to the interface(s) that they put in place. In the event that an account servicing payment services provider fails to comply with the requirements for interfaces laid down in these Standards, the FCA shall ensure that the provision of payment initiation services and account information services is not prevented or disrupted to the extent that the respective providers of such services comply with the conditions defined under
Article 33(5).

FCA 2019/XX
Article 31
Access interface options
Account servicing payment service providers shall establish the interface(s) referred to in
Article 30 by means of a dedicated interface or by allowing the use by the payment service
providers referred to in Article 30(1) of the interfaces used for authentication and communication with the account servicing payment service provider’s payment services users.
Article 32
Obligations for a dedicated interface

Subject to compliance with Article 30 and 31, account servicing payment service
providers that have put in place a dedicated interface shall ensure that the dedicated interface offers at all times the same level of availability and performance, including support, as the interfaces made available to the payment service user for directly accessing its payment account online.
Account servicing payment service providers that have put in place a dedicated
interface shall define transparent key performance indicators and service level targets, at least as stringent as those set for the interface used by their payment service users both in terms of availability and of data provided in accordance with Article 36. Those interfaces, indicators and targets shall be monitored by the FCA and stresstested.
Account servicing payment service providers that have put in place a dedicated
interface shall ensure that this interface does not create obstacles to the provision of payment initiation and account information services. Such obstacles may include, among others, preventing the use by payment service providers referred to in Article 30(1) of the credentials issued by account servicing payment service providers to their customers, imposing redirection to the account servicing payment service provider's authentication or other functions, requiring additional authorisations and registrations in addition to those provided for in regulations 4 and 6 of the Payment Services Regulations 2017 (SI 2017/752) or Articles 11, 14 and 15 of Directive (EU) 2015/2366 as they are implemented in Gibraltar, or requiring additional checks of the consent given by payment service users to providers of payment initiation and account information services.
For the purpose of paragraphs 1 and 2, account servicing payment service providers
shall monitor the availability and performance of the dedicated interface. Account servicing payment service providers shall publish on their website quarterly statistics

FCA 2019/XX on the availability and performance of the dedicated interface and of the interface used by its payment service users.
Article 33
Contingency measures for a dedicated interface

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.
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.
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 the FCA without delay.
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.
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 Regulations 69(3) and 70(3) of the Payment Services Regulations 2017 (SI 2017/752) 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 the FCA;

FCA 2019/XX
(d) duly justify to the FCA, 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. The FCA will exempt 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 three 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. The exemption referred to in paragraph 6 will be revoked where the conditions 6(a)
and 6(d) are not met by the account servicing payment service providers for more than two consecutive calendar weeks. The FCA will ensure that the account servicing payment service provider establishes, within the shortest possible time and at the latest within two months, the contingency mechanism referred to in paragraph 4.
Article 34
Certificates

Payment service providers shall rely on qualified certificates for electronic seals as
referred to in Article 3(30) of the Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust service for electronic transactions in the internal market, as amended by the Electronic Identification and Trust Services for Electronic Transactions (Amendment etc.) (EU Exit) Regulations 2018 as came into force on exit day as defined in the European Union (Withdrawal) Act 2018, or for website authentication as referred to in Article 3(39) of the same Regulations.
For the purpose of these Standards the registration number as referred to in the official
records in accordance with Annex III(c) or Annex IV(c) to Regulation (EU) No 910/2014 of the European Parliament and of the Council of 23 July 2014 on electronic identification and trust service for electronic transactions in the internal market as amended by the Electronic Identification and Trust Services for Electronic

FCA 2019/XX
Transactions (Amendment etc.) (EU Exit) Regulations 2018 as came into force on exit day as defined in the European Union (Withdrawal) Act 2018 shall be the authorisation number of the payment service provider issuing card-based payment instruments, the account information service providers and payment initiation service providers, including account servicing payment service providers providing such services, available in the public register of the UK pursuant to regulation 4 of the Payment Services Regulations (SI 2017/752) or section 347 of the Financial Services and Markets Act 2000, or in the case of such payment service providers incorporated and registered or authorised in Gibraltar, their incorporation number available in the Regulated Entities Register of the Gibraltar Financial Services Commission.
3. For the purposes of these Standards qualified certificates for electronic seals or for
website authentication referred to in paragraph 1 shall include, in a language customary in the sphere of international finance, additional specific attributes in relation to each of the following:
(a) the role of the payment service provider, which may be one or more of the following:
(i) account servicing;
(ii) payment initiation;
(iii) account information;
(iv) issuing of card-based payment instruments; (b) the name of the competent authorities where the payment service provider is registered.
4. The attributes referred to in paragraph 3 shall not affect the interoperability and
recognition of qualified certificates for electronic seals or website authentication.
Article 35
Security of communication session

Account servicing payment service providers, payment service providers issuing cardbased payment instruments, account information service providers and payment
initiation service providers shall ensure that, when exchanging data by means of the internet, secure encryption is applied between the communicating parties throughout the respective communication session in order to safeguard the confidentiality and the integrity of the data, using strong and widely recognised encryption techniques.
Payment service providers issuing card-based payment instruments, account
information service providers and payment initiation service providers shall keep the access sessions offered by account servicing payment service providers as short as

FCA 2019/XX possible and they shall actively terminate any such session as soon as the requested action has been completed.
3. When maintaining parallel network sessions with the account servicing payment
service provider, account information service providers and payment initiation service providers shall ensure that those sessions are securely linked to relevant sessions established with the payment service user(s) in order to prevent the possibility that any message or information communicated between them could be misrouted.
4. Account information service providers, payment initiation service providers and
payment service providers issuing card-based payment instruments with the account servicing payment service provider shall contain unambiguous references to each of the following items:
(a) the payment service user or users and the corresponding communication session in order to distinguish several requests from the same payment service user or users; (b) for payment initiation services, the uniquely identified payment transaction initiated; (c) for confirmation on the availability of funds, the uniquely identified request related to the amount necessary for the execution of the card-based payment transaction.
5. Account servicing payment service providers, account information service providers,
payment initiation service providers and payment service providers issuing card-based payment instruments shall ensure that where they communicate personalised security credentials and authentication codes, these are not readable, directly or indirectly, by any staff at any time. In case of loss of confidentiality of personalised security credentials under their sphere of competence, those providers shall inform without undue delay the payment services user associated with them and the issuer of the personalised security credentials.
Article 36
Data exchanges

Account servicing payment service providers shall comply with each of the following
requirements:
(a) they shall provide account information service providers with the same information from designated payment accounts and associated payment transactions made available to the payment service user when directly requesting access to the account information, provided that this information does not include sensitive payment data;

FCA 2019/XX
(b) they shall, immediately after receipt of the payment order, provide payment initiation service providers with the same information on the initiation and execution of the payment transaction provided or made available to the payment service user when the transaction is initiated directly by the latter; (c) they shall, upon request, immediately provide payment service providers with a confirmation in a simple 'yes' or 'no' format, whether the amount necessary for the execution of a payment transaction is available on the payment account of the payer.
2. In case of an unexpected event or error occurring during the process of identification,
authentication, or the exchange of the data elements, the account servicing payment service provider shall send a notification message to the payment initiation service provider or the account information service provider and the payment service provider issuing card-based payment instruments which explains the reason for the unexpected event or error. Where the account servicing payment service provider offers a dedicated interface in accordance with Article 32, the interface shall provide for notification messages concerning unexpected events or errors to be communicated by any payment service provider that detects the event or error to the other payment service providers participating in the communication session.
3. Account information service providers shall have in place suitable and effective
mechanisms that prevent access to information other than from designated payment accounts and associated payment transactions, in accordance with the user’s explicit consent.
4. Payment initiation service providers shall provide account servicing payment service
providers with the same information as requested from the payment service user when initiating the payment transaction directly.
5. Account information service providers shall be able to access information from
designated payment accounts and associated payment transactions held by account servicing payment service providers for the purposes of performing the account information service in either of the following circumstances:
(a) whenever the payment service user is actively requesting such information; (b) where the payment service user does not actively request such information, no more than four times in a 24-hour period, unless a higher frequency is agreed between the account information service provider and the account servicing payment service provider, with the payment service user’s consent.

FCA 2019/XX
Chapter 6
Final provisions
Article 37
Review
The FCA will review by 14 March 2021 the fraud rates referred to in the Appendix to this Regulation as well as the exemptions granted under Article 33(6) in relation to dedicated interfaces.

FCA 2019/XX
Appendix
Reference Fraud Rate (%) for:
ETV Remote electronic card-based payments Remote electronic credit transfers £440 0.01 0.005 £220 0.06 0.01 £85 0.13 0.015

PS19/26
Appendix 2
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication
Appendix 2
Instrument making amendments to sub-articles 30(3) and (5) of the SCA-RTS (superseded by UK-RTS)

FCA 2019/18
TECHNICAL STANDARDS ON STRONG CUSTOMER AUTHENTICATION AND COMMON AND SECURE METHODS OF COMMUNICATION (AMENDMENT OF TESTING PROVISIONS) INSTRUMENT 2019 Powers exercised A. The Financial Conduct Authority, being the appropriate regulator within the meaning of the Financial Regulators’ Powers (Technical Standards etc.) (Amendment etc.) (EU Exit) Regulations 2018 (“The Regulations”), with the approval of the Treasury, makes this instrument in exercise of the power conferred by regulation 3 of the Regulations. Pre-conditions to making B. The FCA is the appropriate regulator for the EU Regulations specified in Part 1 of the
Schedule to the Regulations.
C. The FCA has consulted the Prudential Regulation Authority and the Bank of England
as appropriate in accordance with regulation 5 of the Regulations. D. A draft of this instrument has been approved by the Treasury, the Minister considering that it makes appropriate provision to prevent, remedy or mitigate any failure of retained EU law to operate effectively, or any other deficiency in retained EU law, arising from the withdrawal of the United Kingdom from the European Union. Modifications E. The FCA makes the modifications contained in the Annex to Article 30(3) and (5) of the Commission Delegated Regulation (EU) 2018/389 of 27 November 2017 supplementing Directive (EU) 2015/2366 of the European Parliament and of the Council with regard to regulatory technical standards for strong customer authentication and common and secure open standards of communication. Commencement F. This instrument comes into force on exit day as defined in the European Union (Withdrawal) Act 2018. Citation G. This instrument may be cited as the Technical Standards on Strong Customer Authentication and Common and Secure Methods of Communication (Amendment of Testing Provisions) Instrument 2019.

FCA 2019/18
By order of the Board
28 March 2019
[Editor’s Note: This instrument amends Article 30(3) and (5) only of the Commission Delegated Regulation (EU) 2018/389 of 27 November 2017 supplementing Directive (EU) 2015/2366 of the European Parliament and of the Council with regard to regulatory technical standards for strong customer authentication and common and secure open standards of communication. They are the only Articles in that Commission Delegated Regulation that will be in force on exit day, and therefore will become part of UK law in accordance with the European Union (Withdrawal) Act 2018.]

FCA 2019/18
Annex
Article 30(3) and (5) of the COMMISSION DELEGATED REGULATION (EU)
2018/389 of 27 November 2017 supplementing Directive (EU) 2015/2366 of the European Parliament and of the Council with regard to regulatory technical standards for strong customer authentication and common and secure open standards of communication In this Annex, underlining indicates new text and striking through indicates deleted text.
Article 30
General obligations for access interfaces
3. Account servicing payment service providers shall ensure that their interfaces follow
standards of communication which are issued by international or European standardisation organisations. Account servicing payment service providers shall also ensure that the technical specification of any of the interfaces is documented specifying a set of routines, protocols, and tools needed by payment initiation service providers, account information service providers and payment service providers issuing card-based payment instruments for allowing their software and applications to interoperate with the systems of the account servicing payment service providers. Account servicing payment service providers shall at a minimum, and no less than 6 months before the application date referred to in Article 38(2), 14 September 2019 or before the target date for the market launch of the access interface when the launch takes place after the date referred to in Article 38(2) 14 September 2019, make the documentation available, at no charge, upon request by authorised payment initiation service providers, account information service providers and payment service providers issuing card-based payment instruments or payment service providers that have applied to their competent authorities the FCA or the Gibraltar Financial Services Commission for the relevant authorisation, and shall make a summary of the documentation publicly available on their website.
5. Account servicing payment service providers shall make available a testing facility,
including support, for connection and functional testing to enable authorised payment initiation service providers, payment service providers issuing card-based payment instruments and account information service providers, or payment service providers that have applied for the relevant authorisation, to test their software and applications used for offering a payment service to users. This testing facility should be made

FCA 2019/18 available no later than 6 months before the application date referred to in Article 38(2) 14 September 2019 or before the target date for the market launch of the access interface when the launch takes place after the date referred to in Article 38(2) 14 September 2019. However, no sensitive information shall be shared through the testing facility.

PS19/26
Appendix 3
Financial Conduct Authority
Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication
Appendix 3
Instrument making amendments to the
Handbook

FCA 2019/XX
PAYMENT SERVICES (AMENDMENT No 2) INSTRUMENT 2019 Powers exercised A. The Financial Conduct Authority (“the FCA”) makes this instrument in the exercise of the powers and related provisions in or under:
(1) the following regulations of the Payment Services Regulations 2017:
(a) Regulation 98(3) (Management of operational and security risks); (b) Regulation 109 (Reporting requirements); and (c) Regulation 120 (Guidance); and (2) Regulation 3 (Delegation) of the Financial Regulators’ Powers (Technical Standards etc.) (Amendment etc.) (EU Exit) Regulations 2018 (“the Regulations”). Pre-conditions to making B. The FCA has consulted the Prudential Regulation Authority and the Bank of England as appropriate in accordance with regulation 5 of the Regulations.
C. A draft of this instrument has been approved by the Treasury, the Minister
considering that it makes appropriate provision to prevent, remedy or mitigate any failure of retained EU law to operate effectively, or any other deficiency in retained EU law, arising from the withdrawal of the United Kingdom from the European Union. Commencement D. This instrument comes into force on 1 November 2019, at exactly the same time as the Technical Standards on Strong Customer Authentication and Common and Secure Methods of Communication Instrument 2019 comes into force. Amendments to the Handbook E. The Glossary of definitions is amended in accordance with Annex A to this instrument. F. The Supervision manual (SUP) is amended in accordance with Annex B to this instrument. Notes

FCA 2019/XX
G. In this instrument, the “notes” (indicated by “Note:”) are included for the convenience of readers but do not form part of the legislative text. Citation H. This instrument may be cited as the Payment Services (Amendment No 2) Instrument 2019. By order of the Board [date]

FCA 2019/XX
Annex A
Amendments to the Glossary of definitions
In this Annex, underlining indicates new text.
Amend the following definition as shown.
SCA RTS Regulation (EU) 2018/389 (RTS) technical standards on strong customer authentication and common and secure open standards of communication made by the FCA under Regulation 106A of the Payment Services Regulations.

FCA 2019/XX
Annex B
Amendments to the Supervision manual (SUP)
In this Annex, underlining indicates new text and striking through indicates deleted text. 15C Applications under the Payment Services Regulations … 15C.2 Request for exemption from the obligation to set up a contingency mechanism (Article 33(6) of the SCA RTS) … 15C.2.3 G The EBA issued the Guidelines on 4 December 2018 on the conditions to be met to benefit from an exemption from the contingency measures mechanism under article 33(6) of the SCA RTS Regulation (EU) 2018/389 (RTS on SCA and CSC) (EBA/GL/2018/07) on the 4 December 2018. The Guidelines clarify the requirements account servicing payment service providers need to meet to obtain an exemption and the information competent authorities should consider to ensure the consistent application of these requirements across jurisdictions. The FCA provides further guidance on making an exemption request in chapter 17 of the FCA’s Approach Document. [Note: see https://eba.europa.eu/documents/10180/2250578/Final+Report+on+Guidelin es+on+the+exemption+to+the+fall+back.pdf/4e3b9449-ecf9-4756-8006- cbbe74db6d03 and https://www.fca.org.uk/publication/finalisedguidance/fca-approach-payment-services-electronic-money-2017.pdf] … 15C.2.5 G Account servicing payment service providers should note that article 16(3) of Regulation (EU) 1093/2010 also requires them to make every effort to comply with the EBA’s Guidelines on the conditions to benefit from an exemption from the contingency measures mechanism under article 33(6) of the SCA RTS. … 15C
Annex
1D
Form: Request for exemption from the obligation to set up a contingency mechanism …

FCA 2019/XX
ASPSPs completing the form should also comply with apply the Guidelines on the conditions to be met to benefit from an exemption from the contingency measures mechanism under
article 33(6) of Regulation (EU) 2018/389 (RTS on SCA & CSC) (EBA Guidelines).
[Note: see https://eba.europa.eu/documents/10180/2250578/Final+Report+on+Guidelines+on+the+exe mption+to+the+fall+back.pdf/4e3b9449-ecf9-4756-8006-cbbe74db6d03.] …

FCA 2019/XX
Form B: (EBA Guideline 6) design of the dedicated interface Column A Column B Column C
Article Requirement … Summary
of how the implemen tation of these specificati ons fulfils the requirem ents of PSD2 the Payment Services Regulatio ns, SCA RTS and FCA Guideline s … … PSD2 Article 67 Regulation 70 Payment Services Regulations SCA-RTS SCA RTS
Article 30 RTS
Enabling AISPs to access the necessary data from payment accounts accessible online PSD2 Article 65 & 66 Regulations 68 and 69 Payment Services Regulations SCA-RTS SCA RTS
Article 30
Enabling provision or availability to the PISP, immediately after receipt of the payment order, of all the information on the initiation of the payment transaction and all information accessible to the ASPSP regarding the execution of the payment transaction SCA-RTS SCA RTS
Article 30(3)
Conforming to (widely used) standard(s) of communication issued by international or European

FCA 2019/XX standardisation organisations
PSD2 Article 64(2)
Regulation 67(2) Payment
Services Regulations
SCA-RTS SCA RTS
Article 30(1)(c)
Allowing the payment service user to authorise and consent to a payment transaction via a PISP PSD2 Article 66(3)(b) and 67(2)(b) Regulations 69(3)(b) and 70(3)(b) of the Payment Services Regulations Enabling PISPs and AISPs to ensure that when they transmit the personalised security credentials issued by the ASPSP, they do so through safe and efficient channels. PSD2 Article 65(2)(c), 66(2)(d) and 67(2)(c) Regulations 68(3)(c), 69(3)(d) and 70(3)(c) Payment Services Regulations SCA-RTS SCA RTS
Article 30(1)(a) and 34
Enabling the identification of the
AISP/PISP/CBPII and support eIDAS for certificates SCA-RTS SCA RTS
Article 10(2)(b)
Allowing for no more than 90 days reauthentication for AISPs SCA-RTS SCA RTS
Article 36(5)
Enabling the ASPSPs and AISPs to count the number of access requests during a given period SCA-RTS SCA RTS
Article 30(4)
Allowing for a change control process
PSD2 Article 64(2) and
80(2) and 80(4)
Regulations 67(2), 83(2) and 83(4) Payment
Services Regulations
Allowing for the possibility for an initiated transaction to be cancelled in accordance with PSD2 the Payment Services Regulations, including recurring transactions

FCA 2019/XX
SCA-RTS SCA RTS
Article 36(2)
Allowing for error messages explaining the reason for the unexpected event or error PSD2 Article 19(6) Regulation 25(1) Payment Services Regulations Supporting access via technology service providers on behalf of authorised actors PSD2 Article 97(5) Regulation 100(4) Payment Services Regulations and SCARTS SCA RTS Article 30(2) Allowing AISPs and PISPs to rely on all authentication procedures issued by the ASPSP to its customers PSD2 Article 67(2)(d) Regulation 70(3)(d) Payment Services Regulations and 30(1)(b) and SCA-RTS SCA RTS
Article 36(1)(a) and
30(1)(b)
Enabling the AISP to access the same information as accessible to the payment servicer user in relation to their designated payment accounts and associated payment transactions SCA-RTS SCA RTS
Article 36(1)(c)
Enabling the ASPSP to send, upon request, an immediate confirmation yes/no to the PSP (PISP and CBPII) on whether there are funds available PSD2 Article 97(2) Regulation 100(2) Payment Services Regulations and SCARTS SCA RTS
Article 5
Enabling the dynamic linking to a specific amount and payee, including batch payments SCA-RTS SCA RTS Articles 30(2), 32(3), 18(2)(c)(v) and (vi) and 18(3) Enabling the ASPSP to apply the same exemptions from SCA for transactions initiated by PISPs as when the PSU interacts directly with the ASPSP

FCA 2019/XX
SCA-RTS SCA RTS
Article 4
Enabling strong customer authentication composed of two different elements SCA-RTS SCA RTS Articles 28 & 35 Enabling a secure data exchange between the ASPSP and the PISP, AISP and CBPII mitigating the risk for any misdirection of communication to other parties PSD2 Article 97(3) Regulation 100(3) Payment Services Regulations SCA-RTS SCA RTS Articles 30(2)(c) and 35 Ensuring security at transport and application level PSD2 Article 97(3) Regulation 100(3) Payment Services Regulations SCA-RTS SCA RTS Articles 22, 35 and 3 Supporting the needs to mitigate the risk for fraud, have reliable and auditable exchanges and enable providers to monitor payment transactions SCA-RTS SCA RTS
Article 29
Allowing for traceability
SCA-RTS SCA RTS
Article 32
Allowing for the
ASPSP’s dedicated interface to provide at least the same availability and performance as the user interface … … 15 Annex 12D Form NOT004 Notification that the fraud rate exceeds the reference fraud rate under SCA-RTS article 20

FCA 2019/XX
NOT004 - Notification that the fraud rate exceeds the reference fraud rate under SCA-RTS
Article 20
Name of service provider
FRN
…
Notification that the reference fraud rate is exceeded … Q4 Please provide the PSP’s fraud rate(s), where they exceed the applicable reference fraud rate Remote electronic card-based payments Remote electronic credit transfers EUR 500 GBP 440 EUR 250 GBP 220 EUR 100 GBP 85 Q5 For how many consecutive quarters has the fraud rate exceeded the applicable reference rate (if more than 1 quarter, please continue to question 6; otherwise, go to question 7)? Remote electronic card-based payments Remote electronic credit transfers EUR 500 GBP 440 EUR 250 GBP 220

FCA 2019/XX
EUR
100
GBP 85
Q6 Please provide the date on which the PSP ceased to apply the transactional risk analysis exemption for the type(s) of transaction which exceeded the applicable reference fraud rate (DD/MM/YYYY) Remote electronic card-based payments Remote electronic credit transfers EUR 500 GBP 440 EUR 250 GBP 220 EUR 100 GBP 85 … Notification that you intend to make use again of the transaction risk analysis exemption Q8 Please provide the PSP’s fraud rate(s) from the last quarter that have been restored to compliance with the applicable reference fraud rate. Remote electronic card-based payments Remote electronic credit transfers EUR 500 GBP 440 EUR 250 GBP 220 EUR 100 GBP 85 …

FCA 2019/XX
15
Annex
13D
Form NOT005 Notification that there are problems with a dedicated interface under SCA-RTS article 33(3) NOT005 - Notification that there are problems with a dedicated interface under SCA RTS
Article 33(3)
Name of service provider
FRN
…
…
Details of the problem with the dedicated interface … Q3 In what way is the dedicated interface failing to comply with
article 32? (select the
option which best describes the problem)
[ ] The uptime of the dedicated interface, as measured by the key performance indicators described in Guidelines 2.2 and 2.4 of the EBA Guidelines on the conditions to be met to benefit from an exemption from contingency measures under article 33(6) of the SCA-RTS SCA RTS, falls below the uptime of the interface used by the ASPSP’s payment service users. [ ] There isn’t the same level of support offered to AISPs and PISPs using the ASPSP’s dedicated interface, in comparison to the customer interface. [ ] The dedicated interface poses obstacles to the provision of payment initiation and account information services (see SCA-RTS SCA RTS article 32(3) and the EBA Guidelines on the conditions to benefit from an exemption from the contingency mechanism under article 33(6) of Regulation (EU) 2018/389 (RTS on SCA and CSC) published on 4 December 2018 (EBA/GL/2018/07) and Opinion on the implementation of the RTS on SCA and CSC (EBA-2018-Op-04)).

FCA 2019/XX
[ ] Other failure to comply with article 32.
…
16 Reporting requirements
…
16.13 Reporting under the Payment Services Regulations
…
16.13.8A G Payment service providers should use the The return in SUP 16 Annex 27ED to comply with reflects the EBA’s Guidelines on fraud reporting under the Payment Services Directive 2 (PSD2), published on 18 July 2018 (EBA/GL/2018/05). Payment service providers should note that
article 16(3) of Regulation (EU) 1093/2010 requires them to make every
effort to comply with the EBA’s Guidelines. The return also includes fraud reporting for registered account information service providers, as required by regulation 109 of the Payment Services Regulations. [Note: see https://eba.europa.eu/documents/10180/2281937/Guidelines+on+fraud+r eporting+under+Article+96%286%29%20PSD2+%28EBA-GL-2018- 05%29.pdf …
16.13.18 G Article 17 of the SCA RTS permits payment service providers not to
apply strong customer authentication in respect of legal persons initiating electronic payment transactions through the use of dedicated payment processes or protocols that are only made available to payers who are not consumers, where the FCA is satisfied that those processes and protocols guarantee at least equivalent levels of security to those provided for by the Payment Services Directive Payment Services Regulations.
16.13.19 D …
(2) an explanation of how the payment service provider’s processes and protocols achieve at least equivalent levels of security to those provided for by the Payment Services Directive Payment Services Regulations. …

FCA 2019/XX
16 Annex
27FG
Notes on completing REP017 Payments Fraud Report These notes contain guidance for payment service providers that are required to complete the Payments Fraud Report in accordance with Regulation 109(4) of the Payment Services Regulations 2017, and SUP 16.13.7D and. The notes also build on the EBA Guidelines on fraud reporting under the Second Payment Services Directive 2 (PSD2) (EBA/GL/2018/05) (“the EBA Guidelines”). The following completion notes should be read in conjunction with the EBA Guidelines. …
Table 1 - Payment transactions and fraudulent payment transactions for payment
services
The form provides the means for PSPs to provide the FCA with statistical data on fraud related to different means of payment. In turn, the FCA is required to aggregate this data and share it with the EBA and the ECB. …
Table 1 - What is a fraudulent transaction?
…
The payment service provider should not report data on payment transactions that, however linked to any of the circumstances referred to in the definition of fraudulent transaction (EBA Guideline 1.1), have not been executed and have not resulted in a transfer of funds in accordance with PSD2 the provisions in the Payment Services Regulations. … Data elements
Table 1 – Payment transactions and fraudulent payment transactions for payment services
Value should be reported in pounds sterling throughout (£) … 2A-2L 38A–38L 48A–48L 103A–103L 155A–155L

total domestic transaction volume (i.e. the number of
transactions) for payment type – Column A;
total domestic transaction value for payment type
Column B;
total transaction volume for payments made crossborder within the EEA – Column C;

FCA 2019/XX
167A–167L
199A–199L
200A–200L

total transaction value for payments made crossborder within the EEA – Column D;
total transaction volume for payments made crossborder outside the EEA – Column E;
total transaction value for payments made crossborder outside the EEA – Column F;
total domestic fraudulent transaction volume (i.e. the
number of transactions) for payment type – Column G;
total domestic fraudulent transaction value for
payment type Column H;
total fraudulent transaction volume for payments
made cross-border within the EEA – Column I;
total fraudulent transaction value for payments made
cross-border within the EEA – Column J;
total fraudulent transaction volume for payments
made cross-border outside the EEA – Column K; and
total fraudulent transaction value for payments made
cross-border outside the EEA – Column L.
PSPs should continue to report fraud data broken down into domestic, cross border within the EEA, and cross border outside the EEA as set out in Columns A-F, notwithstanding the UK’s withdrawal from the EU. … Payment initiation channel – initiated non-electronically 4A–4L (credit transfers) 49A–49L (card payments) 104A-104L (card payments acquired) Of the total transaction and total fraudulent transaction volumes and values for credit transfers and card payments only, PSPs should report the volume and value of those initiated non-electronically. Transactions initiated non-electronically include payment transactions initiated and executed with modalities other than the use of electronic platforms or devices. This includes paper-based payment transactions, mail orders or telephone orders (Recital 95 of the revised Payment Services Directive). … Remote transactions 6A-6L (credit transfers) Of the total transaction and total fraudulent transaction volumes and values for credit transfers, card payments and

FCA 2019/XX
51A–51L (card payments)
106A–106L (card payments acquired)
168A–168L (e-money payment transactions)
E-money payment transactions only PSPs should report the volume and value of those that are remote transactions. A ‘remote transaction’ means a payment transaction initiated via the internet or through a device that can be used for distance communication (revised Payment Services Directive
article 4(1)(6)) (Regulation 2 of the Payment Services
Regulations).
…
Losses due to fraud per liability bearer
35A, 36A, 37A, 45A, 46A, 47A,
100A, 101A,102A, 152A, 153A,
154A
PSPs are required to report the general value of losses borne by them and by the relevant payment service user, not net fraud figures. The figure that should be reported as ‘losses borne’ is understood as the residual loss that is finally registered in the PSP’s books after any recovery of funds has taken place. The final fraud losses should be reported in the period when they are recorded in the payment service provider’s books. We expect one single figure for any given period, unrelated to the payment transactions reported during that period. Since refunds by insurance agencies are not related to fraud prevention for the purposes of PSD2 the Payment Services Regulations, the final fraud loss figures should not take into account such refunds. 16 Annex 46BG Notes on completing REP020 Statistics on the availability and performance of a dedicated interface These notes contain guidance for quarterly reporting by Account Servicing Payment Service Providers (ASPSPs) with payment accounts accessible online that are required to publish on their website quarterly statistics on the availability and performance of the dedicated interface and of the interface used by its payment service users under article 32(4) EBA Regulator Technical Standards on Strong Customer Authentication and Common and Secure Communication (“the SCA-RTS”) SCA RTS. … Performance

FCA 2019/XX
Performance should be reported for each interface based on the daily average time in milliseconds. At column F, ASPSPs should report daily statistics for each payment service user interface on the daily average time (in milliseconds) taken, per request, for the ASPSP to respond to payment service user requests in that interface. At column G, ASPSPs should report daily statistics for each dedicated interface on the daily average time (in milliseconds) taken, per request, for the ASPSP to provide to the account information service provider (AISP) all the information requested in accordance with article 66(4)(b) of PSD2 regulation 69(2)(b) of the Payment Services Regulations and Article article 36(1)(b) of the SCA-RTS SCA RTS. At column H, ASPSPs should report daily statistics for each dedicated interface on the daily average time (in milliseconds) taken, per request, for the ASPSP to provide to the payment initiation service provider (PISP) all the information requested in accordance with article 36(1)(a) of the SCA-RTS SCA RTS. At column I, ASPSPs should report daily statistics for each dedicated interface on the daily average time (in milliseconds) taken, per request, for the ASPSP to provide to the card based payment instrument issuer (CBPII) or to the PISP a ‘yes/no’ confirmation in accordance with
article 65(3) of PSD2 regulation 68(4), (7) and (8) of the Payment Services Regulations and
article 36(1)(c) of the SCA-RTS SCA RTS.
At column J, ASPSPs should report daily statistics for each dedicated interface on the daily error response rate as a percentage – calculated as the number of error messages concerning errors attributable to the ASPSP sent by the ASPSP to the PISPs, AISPs and CBPIIs in accordance with article 36(2) of the SCA-RTS SCA RTS per day, divided by the number of requests received by the ASPSP from AISPs, PISPs and CBPIIs in the same day and multiplied by 100. Data elements Quarterly statistics on availability and performance of dedicated interfaces … Dedicated interface 2G – AISP response (millisecs) Only to be completed if “Dedicated interface” has been selected at 2B. ASPSPs should provide the daily average time (in milliseconds expressed as a whole number, e.g. 1.5 seconds is represented as 1500 milliseconds) taken, per request, for the ASPSP to provide to the account information service provider (AISP) all the information requested in accordance with article 66(4)(b) of PSD2 Regulation

FCA 2019/XX
69(2)(b) of the Payment Services Regulations and article 36(1)(b) of the SCA RTS. 2H – PISP response (millisecs) Only to be completed if “Dedicated interface” has been selected at 2B. ASPSPs should provide the daily average time (in milliseconds expressed as a whole number, e.g. 1.5 seconds is represented as 1500 milliseconds) taken, per request, for the ASPSP to provide to the payment initiation service provider (PISP) all the information requested in accordance with article 36(1)(a) of the SCA RTS. 2I – CBPII response (millisecs) Only to be completed if “Dedicated interface” has been selected at 2B. ASPSPs should provide the daily average time (in milliseconds expressed as a whole number, e.g. 1.5 seconds is represented as 1500 milliseconds) taken, per request, for the ASPSP to provide to the card based payment instrument issuer (CBPII) or to the PISP a ‘yes/no’ confirmation in accordance with article 65(3) of PSD2 regulation 68(4), (7) and (8) of the Payment Services Regulations and article 36(1)(c) of the RTS SCA RTS. 2J – Error response rate Only to be completed if “Dedicated interface” has been selected at 2B. ASPSPs should provide the daily error response rate – calculated as the number of error messages concerning errors attributable to the ASPSP sent by the ASPSP to the PISPs, AISPs and CBPIIs in accordance with article 36(2) of the RTS SCA RTS per day, divided by the number of requests received by the ASPSP from AISPs, PISPs and CBPIIs in the same day. Percentage figure should be provided to two decimal places.

PS19/26: Brexit - Regulatory Technical Standards for Strong Customer Authentication and Common and Secure Open Standards of Communication

Lineage: No known changes

Timeline

Similar documents from other regulators