Incident to report to a regulator?Incident to report? Intake Line

GDPR vs PSD2

Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.

GDPRControllers and processors

PSD2Payment service providers; authorisation requirements for payment institutions

At a Glance

They differ on 23 of 30 topics. Each verdict names what it rests on; read the wording before relying on it.

  • GDPR Asks more on 0 topics Alone on 16 topics More detailed on 0 topics
  • PSD2 Asks more on 0 topics Alone on 7 topics More detailed on 0 topics
Requirements per topic and verdict
Topic GDPRPSD2 Verdict
Governance
Roles and independence GDPR: 2 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Risk management
Risk management framework GDPR: 1 PSD2: 1 Both cover itread the wording below
Risk assessment GDPR: 1 PSD2: 2 Both cover itread the wording below
Review, audit and improvement GDPR: – PSD2: 2 Only PSD2no specific requirement on the other side in the acts covered
Protection
Access control GDPR: – PSD2: 2 Only PSD2no specific requirement on the other side in the acts covered
Authentication GDPR: – PSD2: 14 Only PSD2no specific requirement on the other side in the acts covered
Cryptography and encryption GDPR: 1 PSD2: 2 Both cover itread the wording below
Data security GDPR: 2 PSD2: 1 Both cover itread the wording below
Secure communications GDPR: – PSD2: 4 Only PSD2no specific requirement on the other side in the acts covered
Human resources security GDPR: 1 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection GDPR: – PSD2: 1 Only PSD2no specific requirement on the other side in the acts covered
Incident handling GDPR: 1 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Reporting to authorities GDPR: 3 PSD2: 3 Both cover itread the wording below
Informing customers and the public GDPR: 1 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Continuity and resilience
Business continuity and crisis management GDPR: – PSD2: 1 Only PSD2no specific requirement on the other side in the acts covered
Backup and recovery GDPR: 1 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Security testing GDPR: 1 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk GDPR: 2 PSD2: 1 Both cover itread the wording below
Contract requirements GDPR: 1 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Privacy and data protection
Lawful processing GDPR: 7 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Transparency GDPR: 2 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Rights of individuals GDPR: 7 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Privacy by design and by default GDPR: 2 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Impact assessment GDPR: 3 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Records of processing GDPR: 2 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Data protection officer GDPR: 2 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
International transfers GDPR: 4 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Supervision and enforcement
Registration with authorities GDPR: – PSD2: 7 Only PSD2no specific requirement on the other side in the acts covered
Cooperation with supervisors GDPR: 1 PSD2: – Only GDPRno specific requirement on the other side in the acts covered
Penalties and liability GDPR: 2 PSD2: 1 Both cover itread the wording below

What This Covers

The obligations below are summarised from the acts listed here, grouped by topic. Where a side shows nothing on a topic, the acts covered have no specific requirement on it; an act not yet included, national guidance or a supervisor's expectations may still say more. Use it to see where the regimes differ, not as a compliance checklist.

Included

  • GDPR Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

Status

Reviewed against the official texts.

Included

  • PSD2 Directive (EU) 2015/2366, OJ L 337, 23.12.2015, p. 35 Articles 5, 11, 12, 14, 15, 19, 28, 32, 33, 36, 65 to 68, 70, 95 to 98, 103 · 22 requirements
  • PSD2 SCA RTS Commission Delegated Regulation (EU) 2018/389, OJ L 69, 13.3.2018, p. 23 Articles 1, 3 to 6, 9 to 12, 15 to 19, 21, 22, 27, 28, 30 to 36 · Annex · 20 requirements Applies to: Payment service providers
  • EBA/GL/2018/05 EBA/GL/2018/05 of 18 July 2018, Guidelines on fraud reporting under the Payment Services Directive 2 (PSD2), as amended by EBA/GL/2020/01 of 22 January 2020 6 requirements
  • EBA ICT Guidelines EBA/GL/2019/04 (November 2019), as amended by EBA/GL/2025/02 of 11 February 2025; consolidated version of 19 May 2026 5 requirements

Status

Reviewed against the official texts.

Key Numbers

Deadline

GDPR: At the time the data are obtained (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

PSD2: Not in the acts covered

Threshold

GDPR: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

PSD2: Member state option, at most EUR 3 million a month

Goes to

GDPR: Controller (Processors); Data subjects (Controllers)

PSD2: Not in the acts covered

Evidence to keep

GDPR: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

PSD2: Not in the acts covered

Incident reports go to

GDPR: Competent supervisory authority (Controllers)

PSD2: Competent authority (providers outside DORADigital Operational Resilience Act only)

First notice of an incident

GDPR: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

PSD2: Without undue delay (providers outside DORADigital Operational Resilience Act only)

Intermediate report

GDPR: In phases, without undue further delay (Controllers)

PSD2: Not in the acts covered

External assessment or certification

GDPR: Approved code of conduct or certification may help show compliance (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

PSD2: Independent audit of the security measures; yearly where the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption is used (Payment service providers)

Review of the risk framework

GDPR: Where necessary (ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.)

PSD2: Risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. to the authority at least once a year

Testing of critical systems

GDPR: Regularly

PSD2: Not in the acts covered

Registration with the authority

GDPR: Not in the acts covered

PSD2: Authorisation by the home authority before providing payment services

Maximum fines

GDPR: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher

PSD2: Set by each member state

Governance

Roles and independence

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.5.2, A.5.3

  • Joint controllers

    Applies to: Joint controllers

    Joint controllers set out their respective responsibilities in an arrangement, unless EU or Member State law determines them, including who handles rights requests and information duties, and make its essence available to people. A person may exercise their rights against any of them regardless of the arrangement.

    GDPR, Article 26

  • EU representative

    Applies to: Controllers and processors not established in the EU, under Article 3(2)

    A controller or processor outside the EU that falls under Article 3(2) designates a representative in writing, established in a Member State where the affected people are. Occasional low-risk processing without large-scale special category or criminal data, and public bodies, are exempt.

    GDPR, Article 27

Nothing in the acts covered.

Risk management

Risk management framework

Both cover it read the wording below

NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1

  • Measures to ensure and show compliance

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.

    GDPR, Article 24

  • Operational and security risk management

    Mitigation measures and controls for operational and security risks, with a yearly risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. to the authority.

    PSD2, Article 95

Risk assessment

Both cover it read the wording below

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2

  • Assess security risk

    When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.

    GDPR, Article 32(2)

  • Risk measures and yearly assessment

    Mitigation measures and controls, and a comprehensive risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. to the authority at least yearly. For banks, payment and e-moneyElectronic Money institutions and account information providers, without prejudice to DORADigital Operational Resilience Act Chapter II since 17 January 2025.

    PSD2, Article 95(1)-(2)

  • Transaction risk analysis

    Applies to: Payment service providers

    Remote payments assessed as low risk in real time, up to EUR 100, 250 or 500 where the provider's fraud rate stays under the reference rate for that band (for cards 0.13%, 0.06% and 0.01%; for credit transfers 0.015%, 0.01% and 0.005%).

    PSD2 SCA RTS, Article 18 and Annex

Review, audit and improvement

Only PSD2 no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10

Nothing in the acts covered.

  • Transaction monitoring and review of security measures

    Applies to: Payment service providers

    Monitor transactions to detect unauthorised or fraudulent payments. Document, test and evaluate the security measures, and have them audited by operationally independent internal or external auditors; the report is available to the authority on request.

    PSD2 SCA RTS, Articles 1-3

  • Audit of security measures

    Applies to: Payment service providers

    The audit follows the provider's statutory audit cycle; where the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption is used, its methodology, model and fraud rates are audited at least once a year.

    PSD2 SCA RTS, Article 3

Protection

Access control

Only PSD2 no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3

Nothing in the acts covered.

  • Access for third-party providers

    Account servicing providers confirm funds and give payment initiation and account information providers access without discrimination.

    PSD2, Articles 65-67

  • Confirmation of funds

    With the payer's explicit consent, the account servicing provider answers a card issuer's request with a yes or no only.

    PSD2, Article 65

Authentication

Only PSD2 no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.17, A.8.5

Nothing in the acts covered.

  • Instruments and credentials

    Users keep their credentials safe and report loss or theft without undue delay; providers offer a free way to report and block use after it.

    PSD2, Articles 68-70

  • Strong customer authentication

    Strong customer authenticationAuthentication based on two or more independent elements from knowledge, possession and inherence. PSD2 requires payment service providers to apply it, for example when a payer accesses an account online or starts an electronic payment, subject to the applicable exemptions. when the payer goes online, pays electronically or acts remotely with a risk of fraud, with dynamic linkingA payment-authentication safeguard that binds approval to a specific payment amount and recipient. The payer is shown those details, and the authentication code must correspond to what the payer agreed. Changing the amount or recipient invalidates that code. Under the PSD2 technical requirements, this protects remote electronic payments against approval being redirected to a different transaction; it does not prescribe one particular technology. for remote payments.

    PSD2, Articles 97-98

  • When strong customer authentication applies

    When the payer accesses an account online, initiates an electronic payment, or acts remotely in a way that may imply a risk of fraud; with dynamic linkingA payment-authentication safeguard that binds approval to a specific payment amount and recipient. The payer is shown those details, and the authentication code must correspond to what the payer agreed. Changing the amount or recipient invalidates that code. Under the PSD2 technical requirements, this protects remote electronic payments against approval being redirected to a different transaction; it does not prescribe one particular technology. to amount and payee for remote payments, and protection of credentials.

    PSD2, Article 97

  • Technical standards

    The details, exemptions and the communication standards are in Delegated Regulation (EU) 2018/389, reviewed by the EBAEuropean Banking Authority with regard to DORADigital Operational Resilience Act.

    PSD2, Article 98

  • Strong customer authentication

    Applies to: Payment service providers

    AuthenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. codes built from two or more independent elements (knowledge, possession, inherence) that cannot be forged or derived, with dynamic linkingA payment-authentication safeguard that binds approval to a specific payment amount and recipient. The payer is shown those details, and the authentication code must correspond to what the payer agreed. Changing the amount or recipient invalidates that code. Under the PSD2 technical requirements, this protects remote electronic payments against approval being redirected to a different transaction; it does not prescribe one particular technology. to amount and payee for remote payments.

    PSD2 SCA RTS, Articles 4-9

  • Authentication code

    Applies to: Payment service providers

    No more than five failed attempts in a row before the instrument is blocked, protected sessions and at most five minutes of inactivity for online account access.

    PSD2 SCA RTS, Article 4

  • Dynamic linking

    Applies to: Payment service providers

    The payer sees the amount and the payee, and the code works only for them; any change invalidates it.

    PSD2 SCA RTS, Article 5

  • The elements and their independence

    Applies to: Payment service providers

    Measures against disclosure of knowledge elements, replication of possession elements and abuse of inherence elements; the breach of one element does not compromise the others, including on multi-purpose devices.

    PSD2 SCA RTS, Articles 6-9

  • Exemptions from strong customer authentication

    Applies to: Payment service providers

    Providers may skip strong customer authenticationAuthentication based on two or more independent elements from knowledge, possession and inherence. PSD2 requires payment service providers to apply it, for example when a payer accesses an account online or starts an electronic payment, subject to the applicable exemptions. in defined cases; the aggregator exemption for account information is mandatory.

    PSD2 SCA RTS, Articles 10-18

  • Account information

    Applies to: Payment service providers

    Limited access to balance and the last 90 days of transactions without SCAStrong Customer Authentication, renewed at least every 180 days; mandatory for access through an account information provider since 25 July 2023 (Delegated Regulation 2022/2360).

    PSD2 SCA RTS, Articles 10 and 10a

  • Contactless payments

    Applies to: Payment service providers

    Up to EUR 50 per payment, while the cumulative amount since the last SCAStrong Customer Authentication stays under EUR 150 or there have been no more than five payments.

    PSD2 SCA RTS, Article 11

  • Unattended terminals, trusted beneficiaries, recurring payments and own accounts

    Applies to: Payment service providers

    Transport fares and parking fees at unattended terminals, payees on the payer's trusted list, a series of payments of the same amount to the same payee after the first, and transfers between the payer's own accounts at the same provider.

    PSD2 SCA RTS, Articles 12-15

  • Low-value remote payments

    Applies to: Payment service providers

    Up to EUR 30 per payment, while the cumulative amount since the last SCAStrong Customer Authentication stays under EUR 100 or there have been no more than five payments.

    PSD2 SCA RTS, Article 16

  • Secure corporate payments

    Applies to: Payment service providers

    Dedicated payment processes and protocols for payers that are not consumers, where the authority is satisfied they give equivalent security.

    PSD2 SCA RTS, Article 17

Cryptography and encryption

Both cover it read the wording below

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.8.24

  • Pseudonymisation and encryption

    Apply pseudonymisation and encryption of personal data, as appropriate to the risk.

    GDPR, Article 32(1)(a)

  • Protection of personalised security credentials

    Applies to: Payment service providers

    ConfidentialityThe information-security property of keeping information from being disclosed to people, organisations or systems that are not authorised to receive it. Access restrictions and encryption help preserve confidentiality when information is stored, sent or processed. It concerns who can see information; it does not by itself ensure that the information is accurate or that a service remains available. and integrity of credentials and authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence. devices through their life cycle: creation, association with the user, delivery, renewal, destruction and revocation.

    PSD2 SCA RTS, Articles 22-27

  • Certificates and session security

    Applies to: Payment service providers

    Qualified eIDASRegulation (EU) No 910/2014 on Electronic Identification and Trust Services for Electronic Transactions in the Internal Market certificates for electronic seals or website authenticationThe process of checking that a user, device or software process is who or what it claims to be before allowing access to a system. A system may check evidence such as a password or a security credential. Authentication establishes identity; access requirements then determine what that identity may do. Multi-factor authentication is one approach to authentication, using more than one kind of evidence., and secure encryptionEncryption changes readable information into an unreadable form using a mathematical method and a key, a value that controls the transformation. Decryption recovers the original information with the appropriate key. Encryption helps keep stored or transmitted data confidential, so people without the necessary key cannot readily read it. of the communication session.

    PSD2 SCA RTS, Articles 34-35

Data security

Both cover it read the wording below

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12

  • Integrity and confidentiality

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.

    GDPR, Article 5(1)(f)

  • Security of systems and services

    Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.

    GDPR, Article 32(1)(b)

  • Data exchange

    Applies to: Payment service providers

    Without the user actively requesting it, account information providers access the data no more than four times in 24 hours, unless agreed otherwise.

    PSD2 SCA RTS, Article 36

Secure communications

Only PSD2 no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14

Nothing in the acts covered.

  • Payment initiation services

    The account servicing provider treats orders from a payment initiation provider like its own; the initiator never holds the funds, identifies itself and changes nothing in the order.

    PSD2, Article 66

  • Account information services

    Only with the user's explicit consent, only for the designated accounts, with secure communication and no use of data beyond the service.

    PSD2, Article 67

  • Common and secure communication

    Applies to: Payment service providers

    Identification and traceability of communication between providers. Account servicing providers offer an access interface for third-party providers, either a dedicated interface or an adapted customer interface, identify them with eIDASRegulation (EU) No 910/2014 on Electronic Identification and Trust Services for Electronic Transactions in the Internal Market certificates and protect the session.

    PSD2 SCA RTS, Articles 28-36

  • Access interface

    Applies to: Payment service providers

    Technical documentation and a testing facility (published from 14 March 2019), and a choice between a dedicated interface and the customer interface.

    PSD2 SCA RTS, Articles 30-31

Human resources security

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.RR · ISO/IEC 27001:2022 A.6.1 to A.6.6

  • Staff act only on instructions

    Processors, and anyone with access to personal data under the authority of a controller or processor, process it only on the controller's instructions unless EU or Member State law requires otherwise. Controllers and processors take steps to ensure this.

    GDPR, Articles 29 and 32(4)

Nothing in the acts covered.

Detection and response

Monitoring and detection

Only PSD2 no specific requirement on the other side in the acts covered

NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16

Nothing in the acts covered.

  • Fraud rates and monitoring of exemptions

    Applies to: Payment service providers

    Fraud rates are calculated per quarter; a provider whose rate exceeds the reference rate for two consecutive quarters stops using the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption and tells the authority. Fraud data on exemptions is recorded and monitored.

    PSD2 SCA RTS, Articles 19-21

Incident handling

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.MA, RS.AN, RS.MI · ISO/IEC 27001:2022 A.5.24 to A.5.28

  • Document every breach

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Record each personal data breach, whether notified or not, with its facts, effects and remedial action, so the authority can check compliance.

    GDPR, Article 33(5)

Nothing in the acts covered.

Reporting to authorities

Both cover it read the wording below

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

  • Notify a personal data breach

    Applies to: Controllers

    Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.

    GDPR, Article 33(1)

  • Processor tells the controller

    Applies to: Processors

    Tell the controller of a personal data breach without undue delay after becoming aware of it.

    GDPR, Article 33(2)

  • What the breach notice contains

    Applies to: Controllers

    Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.

    GDPR, Article 33(3) and (4)

  • Incident reporting and fraud statistics

    Major incidents are reported (under DORADigital Operational Resilience Act for most providers since 2025) and fraud data is sent at least yearly.

    PSD2, Article 96

  • Major incident reporting

    Report major operational or security incidents to the home authority without undue delay and inform affected users. Since 17 January 2025 it no longer applies to providers in DORADigital Operational Resilience Act's scope, which report under DORADigital Operational Resilience Act.

    PSD2, Article 96(1)-(5)

  • Fraud statistics

    Statistical data on fraud by means of payment, at least yearly, to the authority.

    PSD2, Article 96(6)

Informing customers and the public

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

  • Tell the people affected

    Applies to: Controllers

    Where a breach is likely to cause high risk to people, tell them in plain language without undue delay, with the contact point, likely consequences and measures. This is not needed where the data was unintelligible, for example encrypted, where later measures remove the high risk, or where a public notice replaces disproportionate effort. The authority may require notice.

    GDPR, Article 34(1) to (4)

Nothing in the acts covered.

Continuity and resilience

Business continuity and crisis management

Only PSD2 no specific requirement on the other side in the acts covered

NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30

Nothing in the acts covered.

  • Dedicated interface and fallback

    Applies to: Payment service providers

    The same availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable. and performance as the customer interface, without obstacles, with indicators published quarterly; a fallback to the customer interface unless the authority grants an exemption after consulting the EBAEuropean Banking Authority.

    PSD2 SCA RTS, Articles 32-33

Backup and recovery

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 PR.DS, RC.RP · ISO/IEC 27001:2022 A.8.13, A.8.14

  • Restoring access after an incident

    Be able to restore availability of and access to personal data in a timely way after a physical or technical incident, as appropriate to the risk.

    GDPR, Article 32(1)(c)

Nothing in the acts covered.

Security testing

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 ID.IM · ISO/IEC 27001:2022 A.5.35, A.8.29, A.8.34

  • Testing the measures

    Have a process to test and evaluate regularly whether the technical and organisational security measures work, as appropriate to the risk.

    GDPR, Article 32(1)(d)

Nothing in the acts covered.

Third parties and supply chain

Supplier and third-party risk

Both cover it read the wording below

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23

  • Use only processors with sufficient guarantees

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.

    GDPR, Article 28(1)

  • Sub-processors

    Applies to: Processors

    Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.

    GDPR, Article 28(2) and (4)

  • Agents and outsourcing

    Agents are notified and registered before they start. Outsourcing of important operational functions, including ICTInformation and Communication Technology systems, must not impair internal control or supervision.

    PSD2, Article 19

Contract requirements

Only GDPR no specific requirement on the other side in the acts covered

NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20

  • Processing contract

    Govern processing by a written contract or other legal act covering subject matter, duration, nature and purpose, data types, the people concerned and the controller's obligations and rights. It requires the processor to act on documented instructions, keep staff bound to confidentiality, secure the data, follow the sub-processor requirements, help with rights and Articles 32 to 36, delete or return data at the end at the controller's choice, provide compliance information and allow audits. The processor warns the controller at once if an instruction appears to breach data protection law.

    GDPR, Article 28(3) and (9)

Nothing in the acts covered.

Privacy and data protection

Lawful processing

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.PO-P

  • Purpose limitation and data minimisation

    Applies to: Controllers

    Collect personal data for specified, explicit and legitimate purposes and do not use it later in a way that conflicts with them. Keep the data adequate, relevant and limited to what those purposes need.

    GDPR, Article 5(1)(b) and (c)

  • Accuracy and storage limitation

    Applies to: Controllers

    Keep personal data accurate and, where needed, up to date, and take every reasonable step to erase or correct inaccurate data without delay. Keep data in a form that identifies people only for as long as the purpose needs, or longer solely for archiving, research or statistics under Article 89(1) with safeguards.

    GDPR, Article 5(1)(d) and (e)

  • Accountability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    The controller is responsible for meeting the data protection principles and must be able to demonstrate that it does.

    GDPR, Article 5(2)

  • Lawful basis

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Process personal data lawfully, fairly and transparently, and only where at least one basis applies: consent, contract, legal obligation, vital interests, a public-interest task or official authority, or legitimate interests. Legitimate interests do not apply where the person's interests or rights override them, and are not open to public authorities performing their tasks.

    GDPR, Articles 5(1)(a) and 6(1)

  • Conditions for consent

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Be able to prove consent, and keep a written consent request separate from other matters and in plain language. Let people withdraw at any time, as easily as they gave consent, and tell them so beforehand. Consent tied to a contract for data the contract does not need may not count as freely given.

    GDPR, Article 7

  • Children's consent to online services

    Applies to: Controllers offering information society services directly to children

    Where consent is the basis for processing in relation to offering an information society service directly to a child under the age limit, make sure consent is given or authorised by the holder of parental responsibility. Make reasonable efforts, given the available technology, to verify it.

    GDPR, Article 8(1) and (2)

  • Special category and criminal offence data

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not process special category data, such as health, biometric identification or genetic data, unless a condition in Article 9(2) applies. Process criminal conviction and offence data only under official authority or where EU or Member State law authorises it with safeguards.

    GDPR, Articles 9 and 10

Nothing in the acts covered.

Transparency

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CM.AW-P

  • Information when collecting from the person

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Tell people, concisely and in plain language, who the controller and any DPO are, the purposes and legal basis, any legitimate interests relied on, recipients, transfers, retention, their rights, whether they must provide the data, and any automated decision-making. Before using the data for a new purpose, give information on that purpose and any relevant further details. This is not needed where the person already has the information.

    GDPR, Articles 12(1) and 13

  • Information when data comes from elsewhere

    Applies to: Controllers

    Give the same information, plus the categories of data and their source, when the data was not obtained from the person. Exceptions include where the person already has it, where this proves impossible or takes disproportionate effort, in which case take appropriate measures to protect the person, including making the information public, or where law requires the obtaining or disclosure or professional secrecy applies.

    GDPR, Article 14

Nothing in the acts covered.

Rights of individuals

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DM-P

  • Answer rights requests in time

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Act on a request under Articles 15 to 22 and tell the person the outcome free of charge. If more time is needed for complex or numerous requests, say so and why within the first month. If no action will be taken, say why without delay and within the first month, and explain the right to complain to an authority and seek a judicial remedy. Manifestly unfounded or excessive requests may be charged for or refused, and the controller must show why.

    GDPR, Article 12(3) to (5)

  • Right of access

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Confirm whether personal data about the person is processed and give access to it, with a copy and information on purposes, data categories, recipients, retention, rights, source and automated decision-making. A reasonable fee may be charged for further copies. The right to a copy must not adversely affect the rights and freedoms of others.

    GDPR, Article 15

  • Rectification, restriction and telling recipients

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Correct inaccurate data without undue delay and, taking account of the purposes, complete incomplete data. On request, restrict processing while accuracy is contested or an Article 21(1) objection is being checked, where processing is unlawful and the person prefers restriction to erasure, or where the controller no longer needs the data but the person needs it for legal claims. Tell each recipient of any rectification, erasure or restriction unless this proves impossible or takes disproportionate effort, and tell the person who the recipients are if asked.

    GDPR, Articles 16, 18 and 19

  • Right to erasure

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Erase personal data without undue delay where it is no longer needed, consent is withdrawn with no other basis, the person objects under Article 21(1) without overriding grounds or objects to direct marketing, processing was unlawful, law requires it, or it was collected for an information society service under Article 8(1). If the data was made public, take reasonable steps to tell other controllers of the request. The right does not apply where processing is needed for freedom of expression, a legal obligation or public task, public health, archiving, research or statistics where erasure would seriously impair them, or legal claims.

    GDPR, Article 17

  • Right to data portability

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Where processing is automated and rests on consent or contract, give people, on request, the data they provided in a structured, commonly used, machine-readable format. On request, send it directly to another controller where technically feasible. The right does not apply to public-task processing and must not adversely affect the rights of others.

    GDPR, Article 20

  • Right to object

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Stop processing based on a public task or legitimate interests when the person objects on grounds of their particular situation, unless the controller demonstrates compelling legitimate grounds that override the person's interests, or legal claims. Stop direct marketing, and related profiling, on objection without exception. Present this right clearly and separately, at the latest at first communication.

    GDPR, Article 21

  • Solely automated decisions

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Do not subject people to decisions based solely on automated processing, including profiling, with legal or similarly significant effects, unless a contract need, law or explicit consent allows it. In the contract and consent cases, provide human intervention, a chance to give a view and a way to contest the decision. Special category data needs further conditions and safeguards.

    GDPR, Article 22

Nothing in the acts covered.

Privacy by design and by default

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework CT.DP-P

  • Data protection by design

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    When deciding how to process and during processing, apply measures such as pseudonymisation that put the data protection principles into effect and build safeguards into the processing. Take account of the state of the art, cost and risk.

    GDPR, Article 25(1)

  • Data protection by default

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    By default, process only the data needed for each purpose, in amount, extent, storage period and accessibility. Do not make personal data available to an indefinite number of people without the person's intervention.

    GDPR, Article 25(2)

Nothing in the acts covered.

Impact assessment

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.RA-P

  • When an impact assessment is needed

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Assess the impact on personal data before processing that is likely to cause high risk, especially with new technologies. It is required for systematic and extensive automated evaluation with legal or similarly significant effects, large-scale special category or criminal data, and large-scale systematic monitoring of a publicly accessible area.

    GDPR, Article 35(1) and (3)

  • What the assessment contains

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Describe the processing and its purposes, assess necessity and proportionality, assess the risks to people, and set out the measures to address them. Seek the advice of the DPO where one is designated, and where appropriate the views of those affected. Where necessary, review whether processing follows the assessment, at least when the risk changes.

    GDPR, Article 35(2), (7), (9) and (11)

  • Prior consultation

    Applies to: ControllersThe person, public authority, agency or other body that, alone or jointly with others, decides the purposes and means of processing personal data. The controller carries primary responsibility for GDPR compliance and must be able to demonstrate it.

    Consult the supervisory authority before processing if the assessment shows the processing would result in a high risk in the absence of measures taken by the controller to mitigate it. Provide responsibilities, purposes and means, safeguards, DPO contact details, the assessment and anything else the authority asks for.

    GDPR, Article 36(1) to (3)

Nothing in the acts covered.

Records of processing

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework ID.IM-P

  • Controller's record of processing

    Applies to: Controllers

    Keep a written or electronic record of the name and contact details of the controller and any joint controller, representative and DPO, purposes, categories of people, data and recipients, transfers, erasure time limits and security measures where possible, and show it to the authority on request. The duty does not apply to organisations under 250 persons, unless the processing is likely to risk people's rights, is not occasional, or includes special category or criminal data.

    GDPR, Article 30(1), (3), (4) and (5)

  • Processor's record of processing

    Applies to: Processors

    Keep a written or electronic record of the name and contact details of the processor, each controller served and any representative and DPO, the categories of processing for each controller, transfers and, where possible, security measures. Show it to the authority on request. The same 250-person exemption applies.

    GDPR, Article 30(2) to (5)

Nothing in the acts covered.

Data protection officer

Only GDPR no specific requirement on the other side in the acts covered

NIST Privacy Framework GV.PO-P

  • Designate a data protection officer

    Designate a DPO if the organisation is a public body, except courts acting in their judicial capacity, if its core activities need regular and systematic large-scale monitoring of people, or if they involve large-scale special category or criminal data. Choose the DPO for expertise in data protection law and practice. Publish the DPO's contact details and give them to the authority.

    GDPR, Article 37(1), (5) and (7)

  • Position and tasks of the DPO

    Involve the DPO promptly in all data protection issues and give the resources and access needed. The DPO takes no instructions on these tasks, cannot be dismissed or penalised for doing them, and reports to the highest management level, and other duties must not create a conflict of interests. The DPO advises, monitors compliance including staff training and audits, advises on impact assessments and acts as contact point for the authority.

    GDPR, Articles 38 and 39

Nothing in the acts covered.

International transfers

Only GDPR no specific requirement on the other side in the acts covered

  • Transfers need a Chapter V ground

    Transfer personal data to a third country or international organisation, including onward transfers, only under the conditions of Chapter V. A Commission adequacy decision allows a transfer without specific authorisation.

    GDPR, Articles 44 and 45

  • Appropriate safeguards

    Without an adequacy decision, transfer only with appropriate safeguards and enforceable rights and remedies for people. Options without specific authority approval include binding corporate rules approved under Article 47, standard data protection clauses, and approved codes or certification with binding commitments. Bespoke contractual clauses need the authority's authorisation.

    GDPR, Articles 46 and 47

  • Third-country orders

    Treat a third-country court or authority order to transfer or disclose personal data as recognised or enforceable only where it rests on an international agreement, such as a mutual legal assistance treaty, without prejudice to other Chapter V grounds.

    GDPR, Article 48

  • Derogations for specific situations

    Without adequacy or safeguards, transfer only on a listed ground such as explicit informed consent, contract need, important public interest, legal claims or vital interests. As a last resort, a non-repetitive transfer about few people may rest on compelling legitimate interests not overridden by the person's interests or rights, if the controller assesses it, applies safeguards, informs the authority and the people concerned, and records it. Public authorities exercising public powers cannot use the consent, contract or last-resort grounds.

    GDPR, Article 49

Nothing in the acts covered.

Supervision and enforcement

Registration with authorities

Only PSD2 no specific requirement on the other side in the acts covered

Nothing in the acts covered.

  • Authorisation, capital and safeguarding

    A payment institutionIn the EU payment-services framework, a legal entity authorised under PSD2 to provide and execute payment services. Depending on its permission, these can include transferring money, processing card payments or providing payment-initiation services. It is one category of payment service provider, alongside other categories such as banks and electronic money institutions, which are authorised to issue electronically stored monetary value accepted for payments by someone other than the issuer. Its authorisation covers specified services rather than every financial activity. is authorised by its home authority before it starts, holds initial capital and own funds, and keeps users' funds safe.

    PSD2, Articles 5-12

  • Application for authorisation

    The application covers the programme of operations, a three-year business plan, capital, safeguarding, governance, incident and complaint procedures, sensitive payment data, business continuityAn organisation's ability to keep delivering its products and services at an acceptable, previously agreed level during a disruption. The focus is on sustaining the activities customers and others depend on, even when normal operations are interrupted. A business continuity management system helps an organisation develop and maintain that capability; a business continuity plan records the arrangements for putting it into practice., a security policy and risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change., AMLAnti-Money Laundering controls, owners and directors. The authority decides within three months; the authorisation is valid across the EU.

    PSD2, Articles 5, 11, 12

  • Registers, agents, passporting and bank account access

    Authorised and registered providers are listed in public registers; agents and outsourcing are notified; a passport opens the EU; banks give payment institutionsPayment Institution fair access to accounts.

    PSD2, Articles 14-15, 19, 28, 36

  • Public registers

    Each member state keeps a public register of payment institutionsPayment Institution, their agents and branches, exempt institutions and account information providers; the EBAEuropean Banking Authority keeps a central register.

    PSD2, Articles 14-15

  • Small payment institutions and account information providers

    Member states may register small payment institutionsPayment Institution instead of authorising them; account information providers are registered.

    PSD2, Articles 32-33

  • Small payment institutions

    A member state may exempt institutions whose monthly average of payment transactions over 12 months stays under a national limit of at most EUR 3 million; they are registered and cannot passport.

    PSD2, Article 32

  • Account information providers

    Registered instead of authorised, with professional indemnity insurance; most of Titles III and IV does not apply to them.

    PSD2, Article 33

Cooperation with supervisors

Only GDPR no specific requirement on the other side in the acts covered

  • Cooperate with supervisory authority powers

    Cooperate with the supervisory authority on request. The authority can order information, audit, access data and premises, and issue warnings, reprimands and orders, including a processing ban, suspension of data flows or a fine.

    GDPR, Articles 31 and 58

Nothing in the acts covered.

Penalties and liability

Both cover it read the wording below

  • Fines for operational obligations

    Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.

    GDPR, Article 83(1) to (4)

  • Fines for principles, rights and transfers

    Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.

    GDPR, Article 83(5) and (6)

  • Penalties

    Member states set effective, proportionate and dissuasive penalties.

    PSD2, Article 103

Requirements are summarised in plain words; the official text prevails. Verdicts compare what the acts covered state, not how a supervisor applies them. Most topics are cross-referenced to NIST CSF 2.0 and ISO/IEC 27001:2022.

More Comparisons

Subject to more than one?

We run one control set for both, without doing the work twice. Ask what that saves you.

Loading the form…