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

ePrivacy vs PSD2

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

ePrivacyProviders of publicly available electronic communications services; Article 5(3) and Article 13 also reach other organisations

PSD2Payment service providers; authorisation requirements for payment institutions

At a Glance

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

  • ePrivacy Asks more on 0 topics Alone on 7 topics More detailed on 0 topics
  • PSD2 Asks more on 0 topics Alone on 8 topics More detailed on 1 topic
Requirements per topic and verdict
Topic ePrivacyPSD2 Verdict
Governance
Security policy ePrivacy: 1 PSD2: – Only ePrivacyno specific requirement on the other side in the acts covered
Risk management
Risk management framework ePrivacy: – PSD2: 1 Only PSD2no specific requirement on the other side in the acts covered
Risk assessment ePrivacy: – PSD2: 2 Only PSD2no specific requirement on the other side in the acts covered
Review, audit and improvement ePrivacy: – PSD2: 2 Only PSD2no specific requirement on the other side in the acts covered
Protection
Access control ePrivacy: 1 PSD2: 2 Both cover itread the wording below
Authentication ePrivacy: – PSD2: 14 Only PSD2no specific requirement on the other side in the acts covered
Cryptography and encryption ePrivacy: – PSD2: 2 Only PSD2no specific requirement on the other side in the acts covered
Data security ePrivacy: 1 PSD2: 1 Both cover itread the wording below
Network security ePrivacy: 1 PSD2: – Only ePrivacyno specific requirement on the other side in the acts covered
Secure communications ePrivacy: 1 PSD2: 4 PSD2 more detailedmore requirements on this, not necessarily stricter
Detection and response
Monitoring and detection ePrivacy: – PSD2: 1 Only PSD2no specific requirement on the other side in the acts covered
Incident handling ePrivacy: 1 PSD2: – Only ePrivacyno specific requirement on the other side in the acts covered
Reporting to authorities ePrivacy: 4 PSD2: 3 Both cover itread the wording below
Informing customers and the public ePrivacy: 2 PSD2: – Only ePrivacyno specific requirement on the other side in the acts covered
Continuity and resilience
Business continuity and crisis management ePrivacy: – PSD2: 1 Only PSD2no specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk ePrivacy: 1 PSD2: 1 Both cover itread the wording below
Privacy and data protection
Lawful processing ePrivacy: 4 PSD2: – Only ePrivacyno specific requirement on the other side in the acts covered
Transparency ePrivacy: 3 PSD2: – Only ePrivacyno specific requirement on the other side in the acts covered
Supervision and enforcement
Registration with authorities ePrivacy: – PSD2: 7 Only PSD2no specific requirement on the other side in the acts covered
Cooperation with supervisors ePrivacy: 1 PSD2: – Only ePrivacyno specific requirement on the other side in the acts covered
Penalties and liability ePrivacy: 1 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

  • ePrivacy Directive 2002/58/EC of the European Parliament and of the Council of 12 July 2002, as amended by Directive 2009/136/EC; Commission Regulation (EU) No 611/2013 Articles 2, 4 to 6, 9, 13, 15 · 18 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

ePrivacy: Without undue delay after detection (Providers of publicly available electronic communications services); Immediately (Providers contracted by a provider of publicly available electronic communications services)

PSD2: Not in the acts covered

Threshold

ePrivacy: Not in the acts covered

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

Goes to

ePrivacy: Subscribers (Providers of publicly available electronic communications services); Subscribers and individuals affected (Providers of publicly available electronic communications services); Contracting provider (Providers contracted by a provider of publicly available electronic communications services)

PSD2: Not in the acts covered

Evidence to keep

ePrivacy: Inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive (Providers of publicly available electronic communications services)

PSD2: Not in the acts covered

Incident reports go to

ePrivacy: Competent national authority (Providers of publicly available electronic communications services)

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

First notice of an incident

ePrivacy: Within 24 hours of detection, where feasible (Providers of publicly available electronic communications services)

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

Incident notification

ePrivacy: Within three days of the initial notification (Providers of publicly available electronic communications services)

PSD2: Not in the acts covered

External assessment or certification

ePrivacy: Not in the acts covered

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

ePrivacy: Not in the acts covered

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

Registration with the authority

ePrivacy: Not in the acts covered

PSD2: Authorisation by the home authority before providing payment services

Maximum fines

ePrivacy: Set by each Member State; no EU maximum (Member States and competent national authorities)

PSD2: Set by each member state

Governance

Security policy

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

NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1

  • Secure the service

    Applies to: Providers of publicly available electronic communications services

    Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.

    ePrivacy, Article 4(1) and (1a)

Nothing in the acts covered.

Risk management

Risk management framework

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

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

Nothing in the acts covered.

  • 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

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

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

Nothing in the acts covered.

  • 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

Both cover it read the wording below

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

  • Secure the service

    Applies to: Providers of publicly available electronic communications services

    Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.

    ePrivacy, Article 4(1) and (1a)

  • 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

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

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

Nothing in the acts covered.

  • 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

  • Secure the service

    Applies to: Providers of publicly available electronic communications services

    Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.

    ePrivacy, Article 4(1) and (1a)

  • 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

Network security

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

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.8.20 to A.8.22

  • Secure the service

    Applies to: Providers of publicly available electronic communications services

    Take technical and organisational measures suited to the risk to secure the service, with the network provider where needed. At least limit access to personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. to authorised staff for lawful purposes, protect stored or transmitted data against destruction, loss, alteration and unauthorised processing, and apply a security policy. National authorities may audit the measures.

    ePrivacy, Article 4(1) and (1a)

Nothing in the acts covered.

Secure communications

PSD2 more detailed more requirements on this, not necessarily stricter

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

  • Confidentiality of communications

    Applies to: Anyone other than the users of the communication

    Do not listen to, tap, store or otherwise intercept communications and related traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. without the users' consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard., unless legally authorised under Article 15(1). Technical storage needed for transmission remains allowed. Regulation (EU) 2026/1881 gives a temporary exception, until 3 April 2028, for number-independent interpersonal communications services detecting online child sexual abuse under its conditions.

    ePrivacy, Article 5(1)

  • 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

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 ePrivacy 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

  • Keep a breach inventory

    Applies to: Providers of publicly available electronic communications services

    Keep an inventory of personal data breachesPersonal Data Breach Under the ePrivacy Directive recording the facts, effects and remedial action, with only the information authorities need to check compliance. Authorities may issue guidelines and instructions, can audit compliance and must impose appropriate sanctions for failures.

    ePrivacy, Article 4(4)

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 the authority of a personal data breach

    Applies to: Providers of publicly available electronic communications services

    For providers of publicly available electronic communications services only: report every personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms. to the competent national authority without undue delay, within 24 hours of detection where feasible. Detection means enough awareness to make a meaningful notification, not a mere suspicion. Describe the breach, contact points, recommended mitigation, the consequences and the measures taken.

    ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Article 2(1) and (2)

  • Second notification to the authority

    Applies to: Providers of publicly available electronic communications services

    For providers of publicly available electronic communications services only: where full information is not yet available and further investigation is needed, send an initial notification within 24 hours of detection. Send a second notification as soon as possible and at the latest within three days of the initial one. If information is still missing then, send what is held with a reasoned justification for the delay and the rest as soon as possible.

    ePrivacy, Regulation (EU) No 611/2013, Article 2(3)

  • Tell subscribers and individuals

    Applies to: Providers of publicly available electronic communications services

    For providers of publicly available electronic communications services only: where a breach is likely to harm a person's data or privacy, tell them without undue delay after detection, in clear language and without promoting services. This is not needed if the provider satisfies the authority that the data was unintelligible, for example securely encrypted with the key uncompromised. Delay is allowed only in exceptional cases where telling them could put the investigation at risk, and only with the authority's agreement.

    ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Articles 3 and 4

  • Subcontracted provider informs the contracting provider

    Applies to: Providers contracted by a provider of publicly available electronic communications services

    A provider contracted to deliver part of an electronic communications service, with no direct contract with subscribers, immediately tells the contracting provider of a personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms..

    ePrivacy, Regulation (EU) No 611/2013, Article 5

  • 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 ePrivacy no specific requirement on the other side in the acts covered

NIST CSF 2.0 RS.CO, RC.CO

  • Warn of a network security risk

    Applies to: Providers of publicly available electronic communications services

    Where there is a particular risk of a breach of network security, tell subscribers about the risk. Where the risk lies outside the provider's own measures, also tell them of any possible remedies and their likely cost.

    ePrivacy, Article 4(2)

  • Tell subscribers and individuals

    Applies to: Providers of publicly available electronic communications services

    For providers of publicly available electronic communications services only: where a breach is likely to harm a person's data or privacy, tell them without undue delay after detection, in clear language and without promoting services. This is not needed if the provider satisfies the authority that the data was unintelligible, for example securely encrypted with the key uncompromised. Delay is allowed only in exceptional cases where telling them could put the investigation at risk, and only with the authority's agreement.

    ePrivacy, Article 4(3); Regulation (EU) No 611/2013, Articles 3 and 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

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

  • Subcontracted provider informs the contracting provider

    Applies to: Providers contracted by a provider of publicly available electronic communications services

    A provider contracted to deliver part of an electronic communications service, with no direct contract with subscribers, immediately tells the contracting provider of a personal data breachA breach of security leading to accidental or unlawful destruction, loss, alteration or unauthorised disclosure of or access to personal data. A controller must notify the supervisory authority without undue delay and, where feasible, within 72 hours after becoming aware of the breach, unless it is unlikely to result in a risk to people's rights and freedoms..

    ePrivacy, Regulation (EU) No 611/2013, Article 5

  • 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

Privacy and data protection

Lawful processing

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

NIST Privacy Framework CT.PO-P

  • Storing or reading data on a device

    Applies to: Any organisation storing or reading information on a user's device

    Before storing or reading information on a user's device, give clear and comprehensive information and obtain consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.

    ePrivacy, Article 5(3)

  • Traffic data

    Applies to: Providers of public communications networks and publicly available electronic communications services

    Erase or anonymise traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. once it is no longer needed for transmission, apart from billing until the challenge period ends and marketing or value added services with prior, withdrawable consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. Tell subscribers what is processed and for how long, and limit handling to authorised staff.

    ePrivacy, Article 6(1) to (5)

  • Location data other than traffic data

    Applies to: Providers of public communications networks and publicly available electronic communications services, and third parties providing value added services that process location data

    Process location data only anonymised, or with consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. for a value added service for as long as that service needs. Tell users first about the data, purpose, duration and any third-party transfer. Let them withdraw consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. at any time and refuse temporarily, simply and free of charge.

    ePrivacy, Article 9

  • Unsolicited direct marketing

    Applies to: Any organisation sending electronic direct marketing

    Use automated calling, fax or email for direct marketing only with prior consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. A customer's email details may be used for the seller's own similar products if the customer can object easily and free of charge at collection and in each message. Other marketing follows the national choice of opt-in or opt-out. Marketing emails must not hide the sender's identity or lack a valid address for opt-out requests. The consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. and opt-outAn opt-out is a way for a person to refuse an activity or stop further participation. In direct marketing, it means taking a step such as unsubscribing from messages. In a default-on arrangement, the activity proceeds unless the person refuses. Having an opt-out does not establish valid consent where the applicable law requires a positive agreement beforehand. requirements protect subscribers who are natural persons; Member States protect the interests of other subscribers.

    ePrivacy, Article 13(1) to (5)

Nothing in the acts covered.

Transparency

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

NIST Privacy Framework CM.AW-P

  • Storing or reading data on a device

    Applies to: Any organisation storing or reading information on a user's device

    Before storing or reading information on a user's device, give clear and comprehensive information and obtain consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. This does not apply to storage or access solely to carry a communication, or strictly necessary for a service the user explicitly asked for.

    ePrivacy, Article 5(3)

  • Traffic data

    Applies to: Providers of public communications networks and publicly available electronic communications services

    Erase or anonymise traffic dataAny data processed to convey a communication over an electronic communications network or to bill for it. Providers must erase or anonymise traffic data when it is no longer needed for transmission, subject to permitted further processing and lawful statutory derogations under Article 15 of the ePrivacy Directive. once it is no longer needed for transmission, apart from billing until the challenge period ends and marketing or value added services with prior, withdrawable consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard.. Tell subscribers what is processed and for how long, and limit handling to authorised staff.

    ePrivacy, Article 6(1) to (5)

  • Location data other than traffic data

    Applies to: Providers of public communications networks and publicly available electronic communications services, and third parties providing value added services that process location data

    Process location data only anonymised, or with consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. for a value added service for as long as that service needs. Tell users first about the data, purpose, duration and any third-party transfer. Let them withdraw consentA freely given, specific, informed and unambiguous indication of a person's wishes, by a statement or clear affirmative action, agreeing to the processing of their personal data. The ePrivacy Directive, the DMA and the DGA rely on the same GDPR standard. at any time and refuse temporarily, simply and free of charge.

    ePrivacy, Article 9

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 ePrivacy no specific requirement on the other side in the acts covered

  • Procedures for access requests

    Applies to: Providers of publicly available electronic communications services

    Set internal procedures for answering requests for access to users' personal dataAny information relating to an identified or identifiable natural person, the data subject. A person is identifiable if they can be identified directly or indirectly, for example by a name, an identification number, location data, an online identifier or factors specific to their identity. made under national law adopted under Article 15(1). On demand, give the competent national authority information on those procedures, the number of requests received, the legal justification invoked and the response given.

    ePrivacy, Article 15(1b)

Nothing in the acts covered.

Penalties and liability

Both cover it read the wording below

  • Penalties set nationally

    Applies to: Member States and competent national authorities

    Member States set penalties for infringements, including criminal sanctions where appropriate, which are effective, proportionate and dissuasive. Competent authorities can order infringements to stop and have investigative powers and resources, including to obtain information.

    ePrivacy, Article 15a(1) to (3)

  • 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…