CER vs PSD2
Where they overlap, where they differ and which asks more, topic by topic, with their deadlines and fines side by side.
At a Glance
They differ on 17 of 24 topics. Each verdict names what it rests on; read the wording before relying on it.
- CER Asks more on 0 topics Alone on 10 topics More detailed on 2 topics
- PSD2 Asks more on 0 topics Alone on 5 topics More detailed on 0 topics
| Topic | CER | PSD2 | Verdict |
|---|---|---|---|
| Governance | |||
| Roles and independence | CER: 1 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Security policy | CER: 1 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Awareness and training | CER: 1 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Risk management | |||
| Risk management framework | CER: 2 | PSD2: 1 | Both cover itread the wording below |
| Risk assessment | CER: 2 | PSD2: 2 | Both cover itread the wording below |
| Review, audit and improvement | CER: 2 | PSD2: 2 | Both cover itread the wording below |
| Protection | |||
| Access control | CER: 1 | PSD2: 2 | Both cover itread the wording below |
| Authentication | CER: – | PSD2: 14 | Only PSD2no specific requirement on the other side in the acts covered |
| Cryptography and encryption | CER: – | PSD2: 2 | Only PSD2no specific requirement on the other side in the acts covered |
| Data security | CER: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
| Secure communications | CER: – | PSD2: 4 | Only PSD2no specific requirement on the other side in the acts covered |
| Human resources security | CER: 3 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Physical and environmental security | CER: 1 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Monitoring and detection | CER: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
| Incident handling | CER: 1 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Incident classification | CER: 1 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Reporting to authorities | CER: 3 | PSD2: 3 | Both cover itread the wording below |
| Informing customers and the public | CER: 1 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Threat intelligence and information sharing | CER: 1 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Continuity and resilience | |||
| Business continuity and crisis management | CER: 3 | PSD2: 1 | CER more detailedmore requirements on this, not necessarily stricter |
| Third parties and supply chain | |||
| Supplier and third-party risk | CER: 3 | PSD2: 1 | CER more detailedmore requirements on this, not necessarily stricter |
| Supervision and enforcement | |||
| Registration with authorities | CER: 4 | PSD2: 7 | Both cover itread the wording below |
| Cooperation with supervisors | CER: 4 | PSD2: – | Only CERno specific requirement on the other side in the acts covered |
| Penalties and liability | CER: 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
- CER Directive (EU) 2022/2557 of the European Parliament and of the Council of 14 December 2022
Status
Reviewed against the official texts.
Included
- PSD2 Directive (EU) 2015/2366, OJ L 337, 23.12.2015, p. 35
- PSD2 SCA RTS Commission Delegated Regulation (EU) 2018/389, OJ L 69, 13.3.2018, p. 23 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
- 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
Status
Reviewed against the official texts.
Key Numbers
Deadline
CER: By 17 July 2026 (Member States); Member State notifies within one month of identification (Member States); Within nine months of receiving the notification; Central authorities reply within 10 working days of receiving the request (Member States); Rules notified to the Commission by 17 October 2024 (Member States)
PSD2: Not in the acts covered
How often
CER: List reviewed at least every four years (Member States); Whenever necessary, and at least every four years
PSD2: Not in the acts covered
Threshold
CER: Actual or potential significant disruption of essential servicesEssential Service; Essential services to or in six or more Member States
PSD2: Member state option, at most EUR 3 million a month
Goes to
CER: Competent authority
PSD2: Not in the acts covered
Evidence to keep
CER: Resilience planIn critical infrastructure regulation, a document explaining how an organisation will protect and maintain services that society depends on, and restore them after disruption. It connects identified risks with practical safeguards, responsibilities and arrangements for prevention, response and recovery. The required contents, approval process and use of equivalent existing documents depend on the applicable national law. or equivalent documents; Information and evidence on the Article 13 measures (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)
PSD2: Not in the acts covered
Incident reports go to
CER: Competent authority
PSD2: Competent authority (providers outside DORADigital Operational Resilience Act only)
First notice of an incident
CER: Within 24 hours of becoming aware
PSD2: Without undue delay (providers outside DORADigital Operational Resilience Act only)
Final report
CER: Within one month of the initial notification, where relevant
PSD2: Not in the acts covered
Deadline to have the measures in place
CER: 10 months after the date of the notification (Member States)
PSD2: Not in the acts covered
External assessment or certification
CER: Audit by an independent and qualified auditor, where the authority requires evidence (Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555)
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
CER: 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
CER: Not in the acts covered
PSD2: Authorisation by the home authority before providing payment services
Maximum fines
CER: Set by each Member State; effective, proportionate and dissuasive (Member States)
PSD2: Set by each member state
Governance
Roles and independence
Only CER 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
Liaison officer
Designate a liaison officer or equivalent as the point of contact with the competent authorities.
Nothing in the acts covered.
Security policy
Only CER no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.PO · ISO/IEC 27001:2022 A.5.1
Resilience plan
Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
Nothing in the acts covered.
Awareness and training
Only CER no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3
Raise staff awareness
Raise awareness of the resilience measures among relevant personnel, considering training courses, information materials and exercises.
Nothing in the acts covered.
Risk management
Risk management framework
Both cover it read the wording below
NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1
Proportionate measures and incident prevention
Take appropriate and proportionate technical, security and organisational measures to ensure resilience, based on the Member State 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 the entity's own. The measures include preventing incidents, with due regard to disaster risk reduction and climate adaptation.
Encouraging standards
Applies to: Member States
Where useful, and without imposing or favouring a particular technology, Member States encourage the use of European and international standards and technical specifications relevant to the security and resilience measures of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. The article places no duty on the entity itself to use them.
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.
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
Carry out a critical entity risk assessment
Carry out a risk assessment within nine months of being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., then whenever necessary and at least every four years. Assess all relevant risks that could disrupt the provision of the essential services, using the Member State risk assessmentsRisk Assessment and other relevant sources of information.
All-hazards scope and dependencies
Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
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.
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%).
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
Inspections, audits and remedial orders
Applies to: Competent authorities
Competent authorities can inspect critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
Provide information and audit evidence
Applies to: Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555
Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
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.
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.
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
Employee security management
Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
Access for third-party providers
Account servicing providers confirm funds and give payment initiation and account information providers access without discrimination.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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).
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.
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.
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.
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.
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.
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.
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.
Secure communications
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.14
Nothing in the acts covered.
Payment initiation services
The account servicing provider treats orders from a payment initiation provider like its own; the initiator never holds the funds, identifies itself and changes nothing in the order.
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.
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.
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.
Human resources security
Only CER 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
Employee security management
Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
Request background checks where permitted Optional
Under conditions set by the Member State and in duly reasoned cases, the entity may request background checks on people in sensitive roles, people with direct or remote access to its premises, information or control systems, and candidates for those positions.
Limits and content of background checks
Applies to: Member States
Checks are proportionate, strictly limited to what is necessary and carried out only to evaluate a potential security risk to the entity. At a minimum they confirm the person's identity and check criminal records for offences relevant to the position. Central authorities answer requests for criminal records held in other Member States within 10 working days.
Nothing in the acts covered.
Physical and environmental security
Only CER 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
Physical protection of premises and infrastructure
Ensure adequate physical protection of premises and critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk., considering for example fencing, barriers, perimeter monitoring, detection equipment and access controlsAccess Control.
Nothing in the acts covered.
Detection and response
Monitoring and detection
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 DE.CM, DE.AE · ISO/IEC 27001:2022 A.8.15, A.8.16
Nothing in the acts covered.
Fraud rates and monitoring of exemptions
Applies to: Payment service providers
Fraud rates are calculated per quarter; a provider whose rate exceeds the reference rate for two consecutive quarters stops using the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption and tells the authority. Fraud data on exemptions is recorded and monitored.
Incident handling
Only CER 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
Respond to and mitigate incidents
Respond to, resist and mitigate the consequences of incidents, considering risk and crisis management procedures, protocols and alert routines.
Nothing in the acts covered.
Incident classification
Only CER no specific requirement on the other side in the acts covered
NIST CSF 2.0 RS.MA · ISO/IEC 27001:2022 A.5.25
Judging the significance of a disruption
Determine significance by taking into account in particular the number and proportion of users affected, the duration of the disruption, and the geographical area affected, including whether it is geographically isolated.
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
Initial incident notification
Notify the competent authority without undue delay of incidents that significantly disrupt, or could significantly disrupt, the provision of essential services. Send the initial notification within 24 hours of becoming aware of the incident, unless operationally unable to do so.
Detailed incident report
Where relevant, follow the initial notification with a detailed report within one month.
Content of the notification
Include any available information that lets the competent authority understand the nature, cause and possible consequences of the incident, including any cross-border impact. Notifying does not expose the entity to increased liability.
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.
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.
Fraud statistics
Statistical data on fraud by means of payment, at least yearly, to the authority.
Informing customers and the public
Only CER no specific requirement on the other side in the acts covered
NIST CSF 2.0 RS.CO, RC.CO
Follow-up to the entity and informing the public
Applies to: Competent authorities and Member States
After a notification, the competent authority gives the entity relevant follow-up information as soon as possible, including information that could support its response. Member States inform the public where they determine that this is in the public interest.
Nothing in the acts covered.
Threat intelligence and information sharing
Only CER 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
Follow-up to the entity and informing the public
Applies to: Competent authorities and Member States
After a notification, the competent authority gives the entity relevant follow-up information as soon as possible, including information that could support its response. Member States inform the public where they determine that this is in the public interest.
Nothing in the acts covered.
Continuity and resilience
Business continuity and crisis management
CER more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30
Respond to and mitigate incidents
Respond to, resist and mitigate the consequences of incidents, considering risk and crisis management procedures, protocols and alert routines.
Recover and resume the essential service
Recover from incidents and resume the essential serviceIn the EU Critical Entities Resilience Directive, a service needed to keep society's vital functions, economic activity, public health and safety or the environment functioning. Examples include services in energy, transport, health and drinking water. The concept concerns the service people depend on. National authorities identify the critical entities that provide such services. The Directive requires reporting of incidents that significantly disrupt or could significantly disrupt essential services, with details implemented through national requirements., considering 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. measures and alternative supply chains.
Resilience plan
Have in place and apply a resilience plan or equivalent documents that describe the measures taken. Documents and measures produced under other legal acts may be reused where relevant, and the competent authority may declare them compliant in whole or in part.
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.
Third parties and supply chain
Supplier and third-party risk
CER more detailed more requirements on this, not necessarily stricter
NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23
All-hazards scope and dependencies
Cover all relevant natural and man-made risks, including cross-sectoral and cross-border risks, accidents, natural disasters, public health emergencies, hybrid threats and other antagonistic threats such as terrorist offences. Take into account how other sectors depend on the entity and how it depends on other sectors, including, where relevant, in neighbouring Member States and third countries. Relevant assessments made under other legal acts may be reused, and the competent authority may declare them compliant in whole or in part.
Recover and resume the essential service
Recover from incidents and resume the essential serviceIn the EU Critical Entities Resilience Directive, a service needed to keep society's vital functions, economic activity, public health and safety or the environment functioning. Examples include services in energy, transport, health and drinking water. The concept concerns the service people depend on. National authorities identify the critical entities that provide such services. The Directive requires reporting of incidents that significantly disrupt or could significantly disrupt essential services, with details implemented through national requirements., considering 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. measures and alternative supply chains.
Employee security management
Ensure adequate employee security management, considering categories of personnel in critical functions, access rights to premises, critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and sensitive information, background check procedures under Article 14 and the categories of people who must undergo them, and training and qualification requirements. Include the personnel of external service providers when setting the categories of personnel in critical functions.
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.
Supervision and enforcement
Registration with authorities
Both cover it read the wording below
Identification of critical entities
Applies to: Member States
Each Member State identifies the critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. in the sectors and subsectors of the Annex by 17 July 2026 and reviews the list at least every four years. An entity qualifies when it provides an essential service, operates on that territory with its critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. located there, and an incident would significantly disrupt that service or a dependent one.
Notification and start of obligations
Applies to: Member States
The Member State notifies each critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. within one month of identifying it and tells it which obligations apply and from when. The resilience obligations in Chapter III apply to the entity from 10 months after the date of that notification.
Carve-out for banking, financial market and digital infrastructure
Applies to: Member States, for critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. in banking, financial market infrastructure and digital infrastructure
Article 11 and Chapters III, IV and VI do not apply to critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. identified in banking, financial market infrastructure and digital infrastructure (points 3, 4 and 8 of the Annex). Member States may keep or adopt national requirements for a higher level of resilience if they are consistent with Union law.
Report services in six or more Member States
After being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
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.
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.
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.
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.
Small payment institutions and account information providers
Member states may register small payment institutionsPayment Institution instead of authorising them; account information providers are registered.
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.
Account information providers
Registered instead of authorised, with professional indemnity insurance; most of Titles III and IV does not apply to them.
Cooperation with supervisors
Only CER no specific requirement on the other side in the acts covered
Liaison officer
Designate a liaison officer or equivalent as the point of contact with the competent authorities.
Report services in six or more Member States
After being notified as a critical entityA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities., tell the competent authority if the entity provides essential services to or in six or more Member States, which services these are and in which Member States.
Inspections, audits and remedial orders
Applies to: Competent authorities
Competent authorities can inspect critical infrastructureAn asset, facility, equipment, network or system, or a part of one, that is necessary for the provision of an essential service. The AI Act uses this CER definition, for example to class AI used as a safety component in critical infrastructure as high-risk. and premises on site, supervise Article 13 measures off site, and conduct or order audits of critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities.. They may order an entity to remedy an infringement within a reasonable time limit and to report the measures taken.
Provide information and audit evidence
Applies to: Critical entitiesA public or private entity that a Member State has identified under the CER Directive as belonging to a category in its Annex and providing an essential service. Risk-assessment and resilience duties are subject to Article 8, which excludes banking, financial-market-infrastructure and digital-infrastructure critical entities from specified CER provisions. NIS2 treats entities identified as critical under CER as essential entities. that are also entities under Directive (EU) 2022/2555
Where the competent authority requires it, and within the reasonable time limit it sets, provide the information needed to assess the Article 13 measures and evidence that they are effectively implemented. The evidence includes the results of an audit by an independent and qualified auditor, chosen by the entity and paid for by it.
Nothing in the acts covered.
Penalties and liability
Both cover it read the wording below
Penalties
Applies to: Member States
Member States lay down the penalties for infringements of the national measures and take the steps needed to implement them. The penalties are effective, proportionate and dissuasive. Member States notify the Commission of these provisions by 17 October 2024 and of any later change without delay.
Penalties
Member states set effective, proportionate and dissuasive penalties.
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.