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

NIS2 vs PSD2

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

NIS2Essential and important entities

PSD2Payment service providers; authorisation requirements for payment institutions

At a Glance

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

  • NIS2 Asks more on 0 topics Alone on 18 topics More detailed on 1 topic
  • PSD2 Asks more on 0 topics Alone on 1 topic More detailed on 3 topics
Requirements per topic and verdict
Topic NIS2PSD2 Verdict
Governance
Management accountability NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Roles and independence NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Security policy NIS2: 2 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Awareness and training NIS2: 2 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Risk management
Risk management framework NIS2: 3 PSD2: 1 NIS2 more detailedmore requirements on this, not necessarily stricter
Risk assessment NIS2: 2 PSD2: 2 Both cover itread the wording below
Review, audit and improvement NIS2: 3 PSD2: 2 Both cover itread the wording below
Asset management NIS2: 2 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Protection
Access control NIS2: 2 PSD2: 2 Both cover itread the wording below
Authentication NIS2: 2 PSD2: 14 PSD2 more detailedmore requirements on this, not necessarily stricter
Cryptography and encryption NIS2: 1 PSD2: 2 Both cover itread the wording below
Data security NIS2: – PSD2: 1 Only PSD2no specific requirement on the other side in the acts covered
Network security NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Secure communications NIS2: 1 PSD2: 4 PSD2 more detailedmore requirements on this, not necessarily stricter
Secure acquisition and development NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Configuration, change and patch management NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Vulnerability handling NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Human resources security NIS2: 2 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Physical and environmental security NIS2: 2 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Detection and response
Monitoring and detection NIS2: 1 PSD2: 1 Both cover itread the wording below
Incident handling NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Incident classification NIS2: 3 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Reporting to authorities NIS2: 5 PSD2: 3 Both cover itread the wording below
Informing customers and the public NIS2: 2 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Threat intelligence and information sharing NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Continuity and resilience
Business continuity and crisis management NIS2: 1 PSD2: 1 Both cover itread the wording below
Backup and recovery NIS2: 2 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Security testing NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Third parties and supply chain
Supplier and third-party risk NIS2: 2 PSD2: 1 Both cover itread the wording below
Register of third-party arrangements NIS2: 1 PSD2: – Only NIS2no specific requirement on the other side in the acts covered
Supervision and enforcement
Registration with authorities NIS2: 2 PSD2: 7 PSD2 more detailedmore requirements on this, not necessarily stricter
Penalties and liability NIS2: 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

  • NIS2 Directive (EU) 2022/2555 Articles 3, 20, 21, 23, 27, 29, 34 · 31 requirements
  • NIS2 Implementing Regulation Commission Implementing Regulation (EU) 2024/2690 Articles 3 to 14 · Annex · 17 requirements Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

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

Threshold

NIS2: Not in the acts covered

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

Incident reports go to

NIS2: CSIRTComputer Security Incident Response Team or competent authority

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

First notice of an incident

NIS2: Without undue delay and in any event within 24 hours of becoming aware

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

Incident notification

NIS2: Without undue delay and in any event within 72 hours of becoming aware (24 hours for trust serviceAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2. providers, for incidents affecting their trust servicesAn electronic service, normally provided for payment, such as issuing and validating certificates, creating and validating electronic signatures and seals, electronic registered delivery, electronic archiving, attestation of attributes or recording data in electronic ledgers. Trust service providers are regulated by eIDAS and in scope of NIS2.)

PSD2: Not in the acts covered

Intermediate report

NIS2: On request

PSD2: Not in the acts covered

Final report

NIS2: Within one month of the incident notification

PSD2: Not in the acts covered

External assessment or certification

NIS2: 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

NIS2: 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. and treatment plan at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

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

Register of third-party arrangements

NIS2: Directory of direct suppliers and service providers (DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers)

PSD2: Not in the acts covered

Registration with the authority

NIS2: Required; changes without delay and in any event within two weeks

PSD2: Authorisation by the home authority before providing payment services

Management body training

NIS2: Required

PSD2: Not in the acts covered

Management body liability

NIS2: Yes, for infringements of Article 21

PSD2: Not in the acts covered

Maximum fines

NIS2: Essential entitiesAn organisation that NIS2 places in its stricter tier, mainly large entities in the Annex I sectors of high criticality, plus some entities regardless of size such as qualified trust service providers, DNS service providers and critical entities under CER. Essential entities face proactive supervision and higher maximum fines than important entities.: maximum of at least EUR 10 million or 2% of the undertaking's total worldwide annual turnover in the preceding financial year, whichever is higher. Important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance.: maximum of at least EUR 7 million or 1.4%, whichever is higher.

PSD2: Set by each member state

Governance

Management accountability

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

NIST CSF 2.0 GV.RR, GV.OV · ISO/IEC 27001:2022 Clause 5.1, A.5.4

  • Management approves and oversees the measures

    The management body approves the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.

    NIS2, Article 20(1)

Nothing in the acts covered.

Roles and independence

Only NIS2 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

  • Roles, responsibilities and authorities

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Security roles assigned and communicated to the management bodies, at least one person reporting directly to them, conflicting duties segregated where applicable, and the assignment reviewed by the management bodies at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 1.2

Nothing in the acts covered.

Security policy

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

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

  • Risk analysis and security policies

    Policies on risk analysis and on information system security.

    NIS2, Article 21(2)(a)

  • Network and information system security policy

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A security policy approved by the management body, reviewed at least annually and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 1.1

Nothing in the acts covered.

Awareness and training

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

NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3

  • Management body training

    Members of the management body follow training to identify risks and assess cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management practices. Entities are encouraged to offer similar training to employees regularly.

    NIS2, Article 20(2)

  • Cyber hygiene and training

    Basic cyber hygiene practices and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. training.

    NIS2, Article 21(2)(g)

Nothing in the acts covered.

Risk management

Risk management framework

NIS2 more detailed more requirements on this, not necessarily stricter

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

  • Appropriate and proportionate measures

    Technical, operational and organisational measures to manage the risks to network and information systems, set by the state of the art, relevant standards, cost, the entity's exposure and size, and the likelihood and severity of incidents.

    NIS2, Article 21(1)

  • All-hazards approach

    The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.

    NIS2, Article 21(2)

  • Risk management framework

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.1

  • 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

  • Risk analysis and security policies

    Policies on risk analysis and on information system security.

    NIS2, Article 21(2)(a)

  • Risk management framework

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A framework to identify, analyse, assess and treat risks, with a risk treatment plan. Results and plan are reviewed at planned intervals, at least annually, and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.1

  • 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

Both cover it read the wording below

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

  • Assessing effectiveness

    Policies and procedures to assess whether the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures work.

    NIS2, Article 21(2)(f)

  • Corrective measures

    An entity that finds it does not comply with the measures takes the necessary corrective measures without undue delay.

    NIS2, Article 21(4)

  • Independent review

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Independent reviews of network and information securityProtecting information and the systems that handle it so that only authorised people can access it, it remains accurate and complete, and it is available when needed. These aims are called confidentiality, integrity and availability. Information security combines organisational requirements, staff practices and technical safeguards to reduce risks such as disclosure, alteration, disruption or destruction. at planned intervals and after significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. or changes.

    NIS2 Implementing Regulation, Annex, point 2.3

  • 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

Asset management

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

NIST CSF 2.0 ID.AM · ISO/IEC 27001:2022 A.5.9 to A.5.13

  • Asset management

    Asset managementAsset Management in Information Security.

    NIS2, Article 21(2)(i)

  • Asset inventory

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A complete, accurate, up-to-date and consistent inventory of assets, with changes recorded in a traceable way.

    NIS2 Implementing Regulation, Annex, point 12.4

Nothing in the acts covered.

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

  • Access control policies

    Access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements. policies.

    NIS2, Article 21(2)(i)

  • Access rights and privileged accounts

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Management of access rights, and stricter controls on privileged and system administration accounts.

    NIS2 Implementing Regulation, Annex, points 11.2 and 11.3

  • 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

PSD2 more detailed more requirements on this, not necessarily stricter

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

  • Multi-factor authentication

    Multi-factor or continuous 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. solutions, where appropriate.

    NIS2, Article 21(2)(j)

  • Multi-factor authentication

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Multi-factor or continuous 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. where appropriate, in line with the classification of the asset accessed.

    NIS2 Implementing Regulation, Annex, point 11.7

  • 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

  • Cryptography

    Policies and procedures on the use of cryptographyThe use of mathematical methods to protect information and provide evidence that it can be trusted. Cryptography can hide information, detect changes and help verify where information came from. Encryption, which makes readable information unintelligible without the means to decrypt it, is one use of cryptography. The broader discipline also supports integrity checks and digital signatures. and, where appropriate, 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..

    NIS2, Article 21(2)(h)

  • 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

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.12, A.8.10 to A.8.12

Nothing in the acts covered.

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

  • Network security and segmentation

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Network security measures, and systems segmented into networks or zones by risk and from third parties' systems.

    NIS2 Implementing Regulation, Annex, points 6.7 and 6.8

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

  • Secured communications

    Secured voice, video and text communications and secured emergency communication systems within the entity, where appropriate.

    NIS2, Article 21(2)(j)

  • 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

Secure acquisition and development

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

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.25 to A.8.31

  • Secure acquisition, development and maintenance

    Security in the acquisition, development and maintenance of network and information systems, including vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling and disclosure.

    NIS2, Article 21(2)(e)

Nothing in the acts covered.

Configuration, change and patch management

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

NIST CSF 2.0 PR.PS · ISO/IEC 27001:2022 A.8.9, A.8.19, A.8.32

  • Configuration, change and patch management

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Secure configurations, controlled changes, repairs and maintenance, and security patches applied within a reasonable time after release, unless the disadvantages outweigh the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. benefits and the reasons are documented.

    NIS2 Implementing Regulation, Annex, points 6.3, 6.4 and 6.6

Nothing in the acts covered.

Vulnerability handling

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

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.8.8

  • Secure acquisition, development and maintenance

    Security in the acquisition, development and maintenance of network and information systems, including vulnerabilityA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. handling and disclosure.

    NIS2, Article 21(2)(e)

Nothing in the acts covered.

Human resources security

Only NIS2 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

  • Human resources security

    Human resources security.

    NIS2, Article 21(2)(i)

  • Background verification

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Background checks on employees, and where applicable on direct suppliers and service providers, to the extent feasible and where the role needs it.

    NIS2 Implementing Regulation, Annex, point 10.2

Nothing in the acts covered.

Physical and environmental security

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

NIST CSF 2.0 PR.IR · ISO/IEC 27001:2022 A.7.1 to A.7.14

  • All-hazards approach

    The measures follow an all-hazards approach that aims to protect network and information systems and their physical environment from incidents.

    NIS2, Article 21(2)

  • Physical and environmental security

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Supporting utilities, protection against physical and environmental threats, and perimeter and physical access controlRequirements and safeguards that decide who or what may use information, systems or facilities, and what actions they may perform. Access control can grant or refuse access to people, software or devices. Examples include restricting a user account to permitted systems and limiting its privileges. In the plural, access controls are the measures used to enforce these requirements..

    NIS2 Implementing Regulation, Annex, points 13.1 to 13.3

Nothing in the acts covered.

Detection and response

Monitoring and detection

Both cover it read the wording below

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

  • Monitoring and logging

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Monitoring and logging of network and information systems to detect events that could be incidents.

    NIS2 Implementing Regulation, Annex, point 3.2

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

Nothing in the acts covered.

Incident classification

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

NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25

  • When an incident is significant

    An incident is significant when it has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to others.

    NIS2, Article 23(3)

  • Event assessment and classification

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Suspicious events are assessed to decide whether they are incidents and, if so, their nature and severity. Recurring incidents under Article 4 are checked quarterly.

    NIS2 Implementing Regulation, Annex, point 3.4

  • When an incident is significant

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    Criteria that make an incident significant: general criteria for all these providers (Article 3), recurring incidents (Article 4) and criteria for each kind of provider (Articles 5 to 14).

    NIS2 Implementing Regulation, Articles 3 to 14

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 significant incidents

    Notify the CSIRTComputer Security Incident Response Team or competent authority without undue delay of any significant incidentUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident., with the information needed to judge any cross-border impact.

    NIS2, Article 23(1)

  • Early warning

    An early warning, saying where applicable whether the incident is suspected to be caused by unlawful or malicious acts or could have a cross-border impact.

    NIS2, Article 23(4)(a)

  • Incident notification

    An incident notification updating the early warning with an initial assessment of severity and impact and, where available, indicators of compromise.

    NIS2, Article 23(4)(b)

  • Intermediate report

    An intermediate report on status updates, when the CSIRTComputer Security Incident Response Team or authority asks for one.

    NIS2, Article 23(4)(c)

  • Final report

    A final report with a detailed description, the likely type of threat or root cause, the applied and ongoing mitigation and any cross-border impact. For an ongoing incident, a progress report at that time and the final report within one month of handling it.

    NIS2, Article 23(4)(d) and (e)

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

NIST CSF 2.0 RS.CO, RC.CO

  • Inform affected recipients

    Where appropriate, notify recipients of the services without undue delay of significant incidentsUnder NIS2, an incident that has caused or can cause severe operational disruption or financial loss for the entity, or considerable material or non-material damage to other people or organisations. Essential and important entities must report it to their CSIRT or authority, starting with an early warning without undue delay and no later than 24 hours after becoming aware of a significant incident. likely to affect the provision of those services.

    NIS2, Article 23(1)

  • Warn of significant cyber threats

    Where applicable, tell recipients potentially affected by a significant cyber threatA cyber threat whose technical characteristics suggest it could have a severe impact on an organisation's systems or on the users of its services. NIS2 links the impact to considerable material or non-material damage; DORA links it to a possible major ICT-related incident., without undue delay, what they can do about it and, where appropriate, about the threat itself.

    NIS2, Article 23(2)

Nothing in the acts covered.

Threat intelligence and information sharing

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

NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 A.5.6, A.5.7

  • Information-sharing arrangements Optional

    Entities may exchange cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. information such as threats, vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. and indicators of compromise within information-sharing arrangements. Essential and important entitiesAn organisation in an Annex I or Annex II sector of NIS2 that falls within scope but does not qualify as an essential entity, typically a medium-sized or large company. Important entities have the same risk management and reporting duties, but supervision is mainly reactive, after evidence of non-compliance. notify the competent authority when they join or withdraw.

    NIS2, Article 29

Nothing in the acts covered.

Continuity and resilience

Business continuity and crisis management

Both cover it read the wording below

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

  • Business continuity and crisis management

    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., such as backupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. management and disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out., and crisis management.

    NIS2, Article 21(2)(c)

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

  • Business continuity and crisis management

    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., such as backupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. management and disaster recoveryThe organised work of restoring IT systems and recovering information after a serious disruption, so the organisation can resume operations. It includes deciding which systems matter most, preparing backups and recovery resources, assigning responsibilities, and testing the recovery procedures. A disaster recovery environment is the technical set-up used for this restoration. A disaster recovery plan records how the work will be carried out., and crisis management.

    NIS2, Article 21(2)(c)

  • Backup and redundancy

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    BackupA backup is a copy of files, programs or other information kept so they can be recovered when needed. If original records are lost, damaged or unavailable, a usable backup provides a source for restoring them. Backups can support recovery of business systems and health records. copies and sufficient redundancy, with regular integrity checks on the copies and regular testing of recovery of copies and redundancies.

    NIS2 Implementing Regulation, Annex, point 4.2

Nothing in the acts covered.

Security testing

Only NIS2 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

  • Security testing

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A policy and procedures for security testing of network and information systems.

    NIS2 Implementing Regulation, Annex, point 6.5

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

  • Supply chain security

    Supply chain security, including the security aspects of the relationship with each direct supplier and service provider.

    NIS2, Article 21(2)(d)

  • What to weigh for each supplier and service provider

    Entities weigh the specific vulnerabilitiesA weakness, susceptibility or flaw that a threat can exploit. NIS2 applies it to ICT products and services, the CRA to products with digital elements and DORA to any asset, system, process or control. Coordinated vulnerability disclosure and handling duties build on this definition. of each direct supplier and service provider, the quality of their products and cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. practices, including secure development, and the results of EU coordinated risk assessmentsRisk Assessment of critical supply chains.

    NIS2, Article 21(3)

  • 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

Register of third-party arrangements

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

NIST CSF 2.0 GV.SC

  • Directory of suppliers

    Applies to: DNS service providers, TLD name registries, cloud computing service providers, data centre service providers, content delivery network providers, managed service providers, managed security service providers, providers of online market places, of online search engines and of social networking services platforms, and trust service providers

    A directory of direct suppliers and service providers, kept up to date.

    NIS2 Implementing Regulation, Annex, point 5.2

Nothing in the acts covered.

Supervision and enforcement

Registration with authorities

PSD2 more detailed more requirements on this, not necessarily stricter

  • Register with the authority

    Submit to the competent authority the entity's name, address, contact details including IP ranges and, where applicable, its sector and the Member States where it provides services. Report changes without delay and within two weeks.

    NIS2, Article 3(4)

  • Registry of digital providers

    DNSDomain Name System, TLDTop-Level Domain, domain name registration, cloud, data centre, content delivery, managed (security) service providers, marketplaces, search engines and social networks submit their details to the competent authority by 17 January 2025 for the ENISAEuropean Union Agency for Cybersecurity registry, and report changes without delay and within three months. The authority is that of their main establishment or EU representative (Article 26).

    NIS2, Article 27

  • 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

Penalties and liability

Both cover it read the wording below

  • Management approves and oversees the measures

    The management body approves the cybersecurityThe activities needed to protect network and information systems, their users and other persons affected by cyber threats. NIS2 and the CRA adopt this Cybersecurity Act definition, so it frames most EU cybersecurity obligations. risk-management measures, oversees their implementation and can be held liable for infringements of Article 21 by the entity. National liability requirements for public institutions and officials are unaffected.

    NIS2, Article 20(1)

  • Administrative fines

    Infringements of Article 21 or 23 can be fined. Member States set maximums of at least the amounts below, whichever is higher.

    NIS2, Article 34(4) and (5)

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