European Union: PSD2: Strong Customer Authentication - A Political Football?

Last Updated: 30 August 2017
Article by Arun Srivastava and Richard Powell

Strong Customer Authentication (SCA) has become a political football passing between the European Banking Authority and the European Commission. The EBA's Opinion issued on 29 June objects to amendments that the Commission intends to make to the EBA's final draft Regulatory Technical Standards on SCA and Common and Secure Communication (the RTS). This back and forth between the EBA and the Commission is unusual, though it is part of a trend that has seen the EBA become more assertive. While the implementation date of 13 January 2018 for the recast Payment Services Directive (PSD2) is fast approaching, in contrast the expected date for the RTS to take effect is slipping further away.

The Football Pitch

The RTS have been subject to much controversy, criticism from various industry sectors and much lobbying and representations.

There are two main areas in dispute:

  • the use of SCA to authenticate electronic payment transactions. In response to growing concerns about cyber crime and fraud, PSD2 seeks to enhance the security around the making of online payments mandating the use of SCA. Payment Service Providers (PSPs) are unhappy believing that SCA will make it more difficult for customers to authenticate payments while reducing the ability of firms to use technologies such as Risk Based Authentication to counter fraud; and
  • the interface through which the new payment initiation (PISPs) and account information services providers (AISPs) will access customer accounts. These firms have voiced concerns that if banks and other account providers can require access through a "dedicated interface" too much power may be placed in their hands, for instance, the interface may be inferior to that used by customers.

The EBA has pushed back on the Commission's amendments made this spring to the draft RTS publishing an Opinion objecting to various aspects. The outstanding issues are these: (1) the need for a statutory audit of the application of security measures when a firm applies the transaction risk analysis exemption to SCA (i.e. who polices the exemption); (2) the scope of the Commission's new exemption for corporate payments; (3) whether fraud reporting should be just to national authorities or also to the EBA - over which the EBA has some concerns as it lacks direct supervisory powers over PSPs; and (4) the requirement for banks and other account providers to make user-facing interfaces available to AISPs and PISPs where the dedicated interface is unavailable or performing inadequately.

What is SCA?

There has been tremendous growth in online payments over recent years accompanied by an increasing level of fraud and loss. According to Payments UK, 2016 saw 1.3 billion payments made via remote (online or mobile) banking and which were transmitted via the Faster Payments Service or cleared in-house. Figures published by Financial Fraud Action UK show that online fraud against UK retailers amounted to approximately GBP 189.4 million in 2016, an increase of 20% compared to 2015.

PSD2 is supposed to facilitate innovation and enhance customer convenience. This does have to be weighed against security concerns. The text of the Directive requires the application of SCA where a payer accesses its payment account online, initiates a payment transaction or carries out any action through a "remote channel" which may imply the risk of fraud. Moreover, "remote" online payment transactions (i.e., payments over the internet and smartphone) will be subject to further steps and will have to "dynamically link" the transaction to a specific amount and to a specific payee. Where a PSP fails to use SCA, the customer will not bear any financial loss unless they have acted fraudulently.

To this end, SCA must be used which is a means of authentication based on the use of two or more of the following elements:

  • Knowledge - something only the user knows (e.g., a password or PIN);
  • Possession - something only the user holds (e.g., a card or a token);
  • Inherence - something only the issuer is (e.g., a finger print or voice recognition).

How the exemptions to SCA should be interpreted (and applied) has been in the dispute between PSPs and the EBA (the latter taking a more restrictive and cautious approach) along with now the Commission. The EBA has been criticised consistently for failing to get the balance right between innovation and convenience on the one hand and security on the other. The EBA interprets PSD2 as only permitting a risk based approach as an exemption to SCA, leaving it, perhaps, as the captive of the text of a Directive that has long since been overtaken by technology. Adopted in 2015, it was the developed considerably before then.

In the face of industry pressure, the EBA accepted in February this year that firms could apply risk based authentication and that SCA would not be mandatory in all cases. It also raised the threshold for exemptions for remote payment transactions from EUR 10 to EUR 30. These steps addressed some of the major concerns raised by the industry.

The extent to which a transaction is exempted from SCA risk based authentication is based on a PSP's overall fraud rate for the specific payment instrument, which must meet predefined "reference fraud rate[s]" to provide incentives to strengthen the protection of customers. The EBA wants PSPs to monitor both their fraud rates and the performance of the transaction-risk analysis method employed. This method would be independently assessed by qualified auditors. PSPs would need to report any change related to the use of the exemption to the national supervisors. After the first 18 months there will be a review to ensure that the calibration of the exemption is sufficiently conservative. The Commission would like the audit and verification of the methodology, risk model and report risk rates to be performed by statutory auditors to ensure objectivity. It is presumably concerned that, without strict independent control, the exemption could be abused. This is likely to lead to higher compliance costs for PSPs using this exemption.

The Commission has also created an exemption to SCA for certain corporate payment processes which use dedicated processes and protocols (e.g., involving business-to-business and machine-to-machine payment transactions) and therefore enjoy high levels of security. The EBA in its Opinion has raised numerous objections and proposed subjecting it to similar conditions as the transaction risk analysis exemption.

Dedicated interfaces - Second Class Access?

The EBA must develop the requirements for common and secure open standards of communication between account providers, PISPs and AISPs that are necessary for them to operate. A mandatory "dedicated interface" could allow account providers to impede or limit "direct access" to a customer's account by these new service providers. This would run contrary to the overriding principles of PSD2 which are to open up competition and innovation. In response, the EBA insists that neither PSD2, nor its mandate to develop technical standards, specify the nature of access or whether it should be direct access - merely the principles governing access. A further related bone of contention with PISPs and AISPs is the EBA's insistence that "screen scraping" as a means of access should be prohibited once the RTS apply.

The Commission, however, has backed third party service providers in stipulating that account providers must allow access via their customer user interface, as a contingency measure, whenever a dedicated interface is unavailable or not working adequately. This represents a significant win for PISPs and AISPs who feared second class access.

In contrast to almost everything else, the EBA does agree with the Commission's deletion of the standard that communication messages are compliant with ISO 20022. The EBA accepts that to achieve technological neutrality and despite risks to harmonisation, this approach may be preferable.

The Next Round

With PSD2 coming into force on 13 January 2018, it is essential that the RTS are finalised as soon as possible (although the RTS will not apply until 18 months after their adoption, i.e. early 2019). The spat between the EBA and the Commission reassuringly demonstrates that the Commission is not a mere rubber stamp. However, the current uncertainty does not permit the sector to prepare properly for the forthcoming Big Bang in the payments industry.

What next? The EBA's work on the RTS has concluded. The Commission must now make the final decision on the text, although the European Council and European Parliament have a scrutiny right. This might lead to further delay in the process. In the UK, the Government has announced its intention to lay implementing regulations before Parliament prior to the summer recess.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on

Click to Login as an existing user or Register so you can print this article.

In association with
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
Email Address
Company Name
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.


Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.


Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.


A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.


This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.


If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.


This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at and we will use commercially reasonable efforts to determine and correct the problem promptly.