UK: PSD2 And GDPR - Friends Or Foes?

In the first half of 2018, two major new pieces of regulation will "go live" as the revised Payment Services Directive (PSD2) and the General Data Protection Regulation (GDPR) come into effect from January and May respectively. Seemingly unconnected, these two regulatory initiatives do in fact share two common aims – putting customers in control of their own data and keeping that data safe.

Both GDPR and PSD2 are built on the principle that individuals own their personal data and should therefore be able to choose how it is used and with whom it is shared. However, once one moves from the high-level principles to implementation, the challenges of reconciling the details of each regulation quickly become apparent. In our view, if left unattended, these challenges have the potential to jeopardise the successful implementation of PSD2.

This article focuses on two key issues: i) determining who is responsible for obtaining consent1 from customers to allow banks to share their payment data with Third Party Providers (TPPs) under PSD2; and ii) determining what constitutes "sensitive payment data".

Customer Consent

As explained previously, under PSD2 TPPs will be able to access the customer's payment account information directly, provided they have the customer's explicit consent, and use banks' infrastructure to facilitate provision of payment initiation or account information services. In principle, this marries perfectly with the right to data portability introduced by GDPR, but in practice the key question about which party should obtain the customer's consent is currently unanswered.

Under data protection regulations, banks are the data controllers of their customers' information and are responsible for the purposes and the manner in which personal data is processed and shared. Under GDPR's guidance on portability, data controllers are responsible for implementing safeguards "to ensure that they genuinely act on the data subject's behalf". PSD2 adds additional data protection requirements by stating that TPPs are only permitted to access information for the specific purpose(s) "explicitly requested by the customer" relating to the provision of the account information or payment initiation services, and not for any other reason.

Considering these interacting requirements, we believe that while TPPs will likely initiate the process of securing customers' consent, including consent for their own activities and use of the data once obtained, banks will ultimately remain responsible for confirming, or otherwise separately obtaining, the consent directly with their customers. This will probably include confirming details such as the identity of the TPP customers wish to share data with, what data they wish to share, how frequently, and when such consent will expire. Such a two-part process, first to obtain and then to confirm consent, has the potential to provide greater protection to TPPs, banks and customers, than banks relying solely on the consent provided by the TPPs.

Our view is in line with the draft APIs specifications recently published by the UK's Open Banking Implementation Entity. While the Open Banking API standards, which will become effective from January 2018, will only be mandatory for the nine largest UK banks2 and apply to a more limited number of products than PSD2, the Financial Conduct Authority (FCA) and HM Treasury (HMT) are encouraging all banks and TPPs to adopt these standards as the basis for the safe and effective sharing of banking data. We believe banks and other players across Europe will be watching these standards with interest and we may see others outside of the UK aligning themselves voluntarily to these standards.

Sensitive Payment Data

The current draft Regulatory Technical Standard (RTS) on Strong Customer Authentication (SCA) and Common and Secure Communication (SC) under PSD2 states that banks will have to provide Account Information Service Providers (AISPs) with the same information available to the customer when directly accessing their account information, provided that this information does not include "sensitive payment data".

Unhelpfully, neither the RTS nor PSD2 primary legislation defines sensitive payment data. The RTS states only that it includes all data, including personalised security credentials, which can be used to carry out fraud, but leaves it at the banks' discretion to determine which data they consider sensitive.3

GDPR defines "personal data", and therefore protects, as any information relating to an identified or identifiable natural person, who can be identified, directly or indirectly, including by reference to an identifier such as a name, an identification number, location data, an online identifier or other factors including the economic identity of that natural person. However, it also allows EU Member States to specify their own rules "for the processing of special categories of personal data ('sensitive data')", defined as personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, and the processing of genetic data, biometric data.

This lack of clarity on what constitutes sensitive payment data creates challenges for interpretation and implementation and increases the risk of non-compliance. Without further guidance banks may need to take a very risk-averse approach and redact all data that could possibly fall into the sensitive data category in order to avoid breaching rules around data protection, both under PSD2 and GDPR. This in itself could pose challenges, as redacting such contextual data through "fuzzy logic" techniques tends to be complex, costly and less than 100% reliable.4

In the UK, the government and the regulators have recently acknowledged these challenges. HMT, the FCA and the Information Commissioner's Office are currently working together to ensure a pragmatic approach to align the requirements under GDPR and PSD2.

The Interim Period

A further complication is that the RTS on SCA and SC has not yet been finalised and it is not expected to become applicable before the first quarter of 2019 at the earliest.5 An area of contention in the RTS is whether "screen scraping" should be allowed, but in the interim period (from January 2018 to when RTS takes effect), the EBA and the EU commission agree that TPPs can continue using this practice to access customers' payment information and initiate payments transactions.6 Screen scraping poses challenges for banks, as it inherently allows TPPs to access any information available to customers on their online banking platforms, as if they had they logged in. As such, when screen scraping is used, it is very difficult, if not impossible, for banks to limit access only to data allowable in line with a customer's consent, and comply with the other data protection requirements related to sensitive data. Indeed, under such a model, it is unlikely banks will be able to know if and what consent has been provided by the customers.


Further guidance is urgently needed from both EU and national regulators on how firms can reconcile the requirements under PSD2 and GDPR, both in the interim period and thereafter. With GDPR introducing a new maximum monetary penalty of 4% of annual global turnover for breaches, the continued lack of such guidance may lead some banks to give GDPR compliance greater priority over PSD2. In all likelihood, this would lead to severe limitations on TPPs' access to data and very strict interpretations of consent. This in turn would make third party services more difficult to use, and less beneficial to consumers. It would also put a dampener on the "open banking" movement and reduce the effectiveness of regulators' efforts to increase competition and innovation in the payments market.

In the meantime, firms should avoid considering GDPR and PSD2 implementation programmes in silos, but instead ensure they are co-ordinated and take into account each other's requirements.

With regards to the issue of consent, we believe the emerging UK Open Banking APIs approach provides a useful model on which to proceed and we would suggest that firms, both in the UK and the rest of the EU, review these plans and consider whether this approach can be embedded into their own planning for PSD2 and GDPR.


This publication has been written in general terms and we recommend that you obtain professional advice before acting or refraining from action on any of the contents of this publication. Deloitte LLP accepts no liability for any loss occasioned to any person acting or refraining from action as a result of any material in this publication.


1. GDPR introduces a new, and very high, standard for the type of consent required for the processing of personal data. Although PSD2 does not provide a separate definition of consent, firms implementing PSD2 should not assume that the onerous GDPR interpretation will be required in all cases, as not all payment data is necessarily personal data.

2. As per the Competition and Markets Authority's "Retail banking market investigation – Final Report", the nine largest UK banks are: Allied Irish Bank, Bank of Ireland, Barclays, Danske, HSBC, Lloyds Banking Group, Nationwide, RBS Group, and Santander.

3. The RTS explicitly states that the name of the account owner and the account number do not constitute sensitive payment data.

4. Fuzzy logic is an approach to computing based on "degrees of truth" rather than the usual "true or false" (1 or 0) Boolean logic.

5. The RTS on SCA and SC will become applicable 18 months after its publication in the European Union Official Journal.

6. The action of using a computer program to copy data from a website built for human users, rather than via a machine-to-machine API. Normally the screen scraping software would identify itself, but as a human user rather than as a robot.

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.

Similar Articles
Relevancy Powered by MondaqAI
Lowndes, Drosdick, Doster, Kantor & Reed, P.A.
In association with
Practice Guides
by Mondaq Advice Centres
Relevancy Powered by MondaqAI
Related Topics
Similar Articles
Relevancy Powered by MondaqAI
Lowndes, Drosdick, Doster, Kantor & Reed, P.A.
Related Articles
Related Video
Up-coming Events Search
Font Size:
Mondaq on Twitter
Mondaq Free Registration
Gain access to Mondaq global archive of over 375,000 articles covering 200 countries with a personalised News Alert and automatic login on this device.
Mondaq News Alert (some suggested topics and region)
Select Topics
Registration (please scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of

To Use you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

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 or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.


The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq 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 of the Content or performance of Mondaq’s Services.


Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions