AI Act 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 20 of 27 topics. Each verdict names what it rests on; read the wording before relying on it.
- AI Act Asks more on 0 topics Alone on 13 topics More detailed on 1 topic
- PSD2 Asks more on 0 topics Alone on 5 topics More detailed on 1 topic
| Topic | AI Act | PSD2 | Verdict |
|---|---|---|---|
| Governance | |||
| Roles and independence | AI Act: 3 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Awareness and training | AI Act: 1 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Risk management | |||
| Risk management framework | AI Act: 1 | PSD2: 1 | Both cover itread the wording below |
| Risk assessment | AI Act: 1 | PSD2: 2 | Both cover itread the wording below |
| Review, audit and improvement | AI Act: 1 | PSD2: 2 | Both cover itread the wording below |
| Protection | |||
| Access control | AI Act: – | PSD2: 2 | Only PSD2no specific requirement on the other side in the acts covered |
| Authentication | AI Act: – | PSD2: 14 | Only PSD2no specific requirement on the other side in the acts covered |
| Cryptography and encryption | AI Act: – | PSD2: 2 | Only PSD2no specific requirement on the other side in the acts covered |
| Data security | AI Act: 1 | PSD2: 1 | Both cover itread the wording below |
| Secure communications | AI Act: – | PSD2: 4 | Only PSD2no specific requirement on the other side in the acts covered |
| Secure acquisition and development | AI Act: 1 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Detection and response | |||
| Monitoring and detection | AI Act: 2 | PSD2: 1 | Both cover itread the wording below |
| Incident handling | AI Act: 2 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Reporting to authorities | AI Act: 4 | PSD2: 3 | Both cover itread the wording below |
| Continuity and resilience | |||
| Business continuity and crisis management | AI Act: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
| Threat-led penetration testing | AI Act: 1 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Third parties and supply chain | |||
| Supplier and third-party risk | AI Act: 2 | PSD2: 1 | Both cover itread the wording below |
| Contract requirements | AI Act: 1 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Privacy and data protection | |||
| Impact assessment | AI Act: 1 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Artificial intelligence | |||
| Risk classification of AI systems | AI Act: 4 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Data and data governance | AI Act: 3 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Transparency to users | AI Act: 6 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Human oversight | AI Act: 2 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Conformity assessment and monitoring | AI Act: 5 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Registration with authorities | AI Act: 2 | PSD2: 7 | PSD2 more detailedmore requirements on this, not necessarily stricter |
| Cooperation with supervisors | AI Act: 1 | PSD2: – | Only AI Actno specific requirement on the other side in the acts covered |
| Penalties and liability | AI Act: 4 | PSD2: 1 | AI Act more detailedmore requirements on this, not necessarily stricter |
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
- AI Act
- KI-loven Draft act on artificial intelligence (KI-loven), consultation of 30 June 2025
- Decreet 16 oktober 2026 Decreet van 16 oktober 2026, Belgisch Staatsblad 19 November 2026, numac 2026008360
- No. 31/2026 Regulation of Artificial Intelligence Act 2026 (No. 31 of 2026)
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
AI Act: Immediately on identifying a serious incident (Deployers of high-risk AI systems); Without undue delay (Providers of general-purpose AI models with systemic risk); Within 2 days of becoming aware (Providers of high-risk AI systems); Within 10 days of becoming aware (Providers of high-risk AI systems)
PSD2: Not in the acts covered
Threshold
AI Act: Not in the acts covered
PSD2: Member state option, at most EUR 3 million a month
Goes to
AI Act: Market surveillance authorities and, where applicable, the notified body (ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.); Provider first, then importer or distributor and market surveillance authorities (Deployers of high-risk AI systems); Market surveillance authority (Public law bodies and private providers of public services deploying Article 6(2) systems (except Annex III, point 2), and deployers of Annex III, points 5(b) and (c) systems)
PSD2: Not in the acts covered
Evidence to keep
AI Act: Documented assessment, provided on request (Providers of Annex III AI systems they consider not high-risk); Annex IV technical documentation (Providers of high-risk AI systems); Automatically generated logs, at least six months (ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.); Documentation, 10 years after placing on the market or putting into service (ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.); Provider contact details, EU declaration, technical documentation and any notified body certificate, 10 years (Providers of high-risk AI systems established in third countries); Certificate, instructions and EU declaration, 10 years (Importers of high-risk AI systems); Logs under the deployer's control, at least six months (Deployers of high-risk AI systems); EU declaration of conformity, 10 years (Providers of high-risk AI systems); Annex XI and Annex XII documentation (Providers of general-purpose AI models); Post-market monitoring plan in the technical documentation (Providers of high-risk AI systems)
PSD2: Not in the acts covered
Incident reports go to
AI Act: AI Office and, as appropriate, national competent authorities (Providers of general-purpose AI models with systemic risk); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems); Market surveillance authorities of the Member States where the incident occurred (Providers of high-risk AI systems)
PSD2: Competent authority (providers outside DORADigital Operational Resilience Act only)
First notice of an incident
AI Act: Within 2 days of becoming aware for a widespread infringement or critical infrastructure disruption; 10 days for a death; 15 days otherwise (Providers of high-risk AI systems)
PSD2: Without undue delay (providers outside DORADigital Operational Resilience Act only)
Deadline to have the measures in place
AI Act: By 2 December 2026 (Operators of AI systems); By 2 December 2027 (Annex III) and 2 August 2028 (Annex I) (Providers of AI systems); By 2 December 2027 (Annex III) and 2 August 2028 (Annex I) (ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.); By 2 December 2026 for systems on the market before 2 August 2026 (Providers of AI systems, including general-purpose AI systems, that generate synthetic content)
PSD2: Not in the acts covered
External assessment or certification
AI Act: Internal control, or a notified body where Article 43 requires one (Providers of high-risk AI systems)
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
AI Act: Regular systematic review throughout the lifecycle (Providers of high-risk AI systems)
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
AI Act: EU database, under Article 49(2) (Providers of Annex III AI systems they consider not high-risk); EU database under Article 71, before placing on the market or putting into service (Providers of Annex III AI systems or their authorised representatives); EU database under Article 71, before putting into service or use (Deployers that are public authorities, Union bodies or persons acting on their behalf)
PSD2: Authorisation by the home authority before providing payment services
Maximum fines
AI Act: Up to EUR 35,000,000 or 7% of worldwide annual turnover, whichever is higher (Operators of AI systems); Up to EUR 15,000,000 or 3% of worldwide annual turnover, whichever is higher (Operators of AI systems and notified bodies); Up to EUR 7,500,000 or 1% of worldwide annual turnover, whichever is higher (Anyone supplying information to notified bodies or national competent authorities in reply to a request); Up to EUR 15,000,000 or 3% of worldwide annual turnover, whichever is higher (Providers of general-purpose AI models)
PSD2: Set by each member state
Governance
Roles and independence
Only AI Act 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
Provider obligations
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
Ensure the system meets the Section 2 requirements, taking account of its intended purpose and the state of the art. Show your name and contact address, run a quality management system, keep documentation and logs, complete conformity assessment, the EU declaration and CE marking, register, take corrective action, demonstrate conformity on request and meet accessibility requirements.
Appoint an authorised representative
Applies to: Providers of high-risk AI systems established in third countries
Before making a high-risk system available in the Union, appoint an EU-established authorised representative by written mandate. The representative verifies the conformity documents, keeps them for 10 years, deals with authorities and ends the mandate, informing the authority, if the provider acts against the Regulation.
When others become the provider
Applies to: Distributors, importers, deployers, other third parties and initial providers
A distributor, importer, deployer or other third party takes on provider obligations if it puts its name or trademark on a high-risk system (unless a contract allocates them otherwise), substantially modifies one, or changes the purpose of an AI system so that it becomes high-risk. The initial provider then stops being the provider of that system but cooperates and hands over information and access, unless it clearly specified that the system is not to be changed into a high-risk one.
Nothing in the acts covered.
Awareness and training
Only AI Act no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AT · ISO/IEC 27001:2022 A.6.3
Support AI literacy
Take measures to support the AI literacy of staff and others who operate or use AI systems on your behalf, taking account of their knowledge, experience and training, the context of use and the people affected. The duty does not require you to guarantee a specific level of literacy for any individual.
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
Risk management system
Applies to: Providers of high-risk AI systems
Establish, implement, document and maintain a risk management system for each high-risk AI system. Run it as a continuous, iterative process across the whole lifecycle, with regular systematic review and updating.
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
Assess, treat and test for risk
Applies to: Providers of high-risk AI systems
Identify and evaluate known and foreseeable risks to health, safety and fundamental rights, including under foreseeable misuse and from post-market data, and adopt targeted measures until residual risk is acceptable. Consider the effect on under-18s and other vulnerable groups. Test against predefined metrics and probabilistic thresholds, in any event before placing the system on the market or putting it into service.
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
Quality management system
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
Run a documented quality management system with written policies and procedures, covering regulatory strategy, design and development controls, testing, data management, risk management, post-market monitoring, incident reporting, record-keeping, resources and an accountability framework for management and staff. Scale it to the size of the organisation, without lowering the level of protection.
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
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 PR.AA · ISO/IEC 27001:2022 A.5.15, A.5.18, A.8.2, A.8.3
Nothing in the acts covered.
Access for third-party providers
Account servicing providers confirm funds and give payment initiation and account information providers access without discrimination.
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
Both cover it read the wording below
NIST CSF 2.0 PR.DS · ISO/IEC 27001:2022 A.5.12, A.8.10 to A.8.12
Protect the model and its infrastructure
Applies to: Providers of general-purpose AI models with systemic risk
Ensure an adequate level of cybersecurity protection for the model and its physical infrastructure.
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.
Secure acquisition and development
Only AI Act 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
Accuracy, robustness and cybersecurity
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
Achieve an appropriate level of accuracy, robustness and cybersecurity throughout the lifecycle and declare accuracy metrics in the instructions. Make the system resilient to errors and to attempts to alter its use or output, with measures where appropriate against data poisoning, model poisoning, adversarial examples, confidentiality attacks and model flaws.
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
Automatic logs
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
Build the system so it records events automatically over its lifetime, supporting risk identification, post-market monitoring and deployer monitoring. Keep the logs under your control for a period that suits the intended purpose and is at least six months, unless other law says otherwise.
Keep deployer logs
Applies to: Deployers of high-risk AI systems
Keep the logs generated by the system, to the extent you control them, for a period that suits the intended purpose and is at least six months, unless other law says otherwise. Financial institutions keep them with their financial services documentation.
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 AI Act 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
Corrective action and duty to inform
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
If a system may not conform, immediately correct, withdraw, disable or recall it and tell distributors and, where applicable, deployers, the authorised representative and importers. If it presents a risk under Article 79(1), immediately investigate the causes and inform the market surveillance authorities and, where applicable, the notified body.
Investigate a serious incident
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
After reporting, investigate without delay, including a risk assessment and corrective action, and cooperate with authorities. Do not alter the system in a way that could affect later evaluation of the causes without first informing the authorities.
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
Report serious incidents on models
Applies to: Providers of general-purpose AI models with systemic risk
Track, document and report relevant information about serious incidents and possible corrective measures without undue delay.
Report a serious incident
Applies to: Providers of high-risk AI systems
Report any serious incident immediately after establishing a causal link, or its reasonable likelihood, between the system and the incident, taking account of its severity. An incomplete initial report may be followed by a complete one.
Report widespread infringements and critical infrastructure disruption
Applies to: Providers of high-risk AI systems
Report immediately in the event of a widespread infringement, or a serious and irreversible disruption of the management or operation of critical infrastructure.
Report a death
Applies to: Providers of high-risk AI systems
Where a person dies, report immediately after establishing, or as soon as you suspect, a causal relationship between the system and the incident.
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.
Continuity and resilience
Business continuity and crisis management
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 RC.RP, RC.CO · ISO/IEC 27001:2022 A.5.29, A.5.30
Nothing in the acts covered.
Dedicated interface and fallback
Applies to: Payment service providers
The same availabilityThe information-security property that authorised people and systems can access and use information or services when needed, reliably and within an acceptable time. An outage or an attack that overwhelms a service can reduce availability even if no information is stolen or changed. In product security, this includes keeping essential functions accessible and usable. and performance as the customer interface, without obstacles, with indicators published quarterly; a fallback to the customer interface unless the authority grants an exemption after consulting the EBAEuropean Banking Authority.
Threat-led penetration testing
Only AI Act no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.IM
Evaluate models and mitigate systemic risk
Applies to: Providers of general-purpose AI models with systemic risk
Evaluate the model using standardised protocols and tools reflecting the state of the art, including documented adversarial testing. Assess and mitigate possible systemic risks at Union level and their sources.
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
Importer checks
Applies to: Importers of high-risk AI systems
Before placing a high-risk system on the market, verify the conformity assessment, technical documentation, CE marking, EU declaration, instructions and authorised representative. Hold back a system you have reason to think is non-conforming or falsified, and report risks. Keep the certificate, instructions and declaration for 10 years and cooperate with authorities.
Distributor checks
Applies to: Distributors of high-risk AI systems
Before making a high-risk system available, verify the CE marking, EU declaration and instructions, that the provider and importer show their name and contact address, and that the provider has a quality management system. Hold back a system you consider non-conforming. If one is already on the market, ensure it is corrected, withdrawn or recalled, inform the provider or importer and authorities of any risk, and cooperate with them.
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.
Contract requirements
Only AI Act no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.20
Written agreements with suppliers
Applies to: Providers of high-risk AI systems and their third-party suppliers
Specify by written agreement the information, capabilities, technical access and other assistance a supplier of AI systems, models, tools, services, components or processes gives so that the provider can comply. This does not apply to open-source tools, services, processes or components that are made public, other than general-purpose AI models.
Nothing in the acts covered.
Privacy and data protection
Impact assessment
Only AI Act no specific requirement on the other side in the acts covered
NIST Privacy Framework ID.RA-P
Fundamental rights impact assessment
Applies to: Public law bodies and private providers of public services deploying Article 6(2) systems (except Annex III, point 2), and deployers of Annex III, points 5(b) and (c) systems
Before first use, assess the impact on fundamental rights: the processes involved, period and frequency of use, people affected, specific risks of harm, human oversight, and measures if risks materialise, including governance and complaints. Update it when elements change and notify the market surveillance authority of the results. You may cross-refer to an existing data protection impact assessment.
Nothing in the acts covered.
Artificial intelligence
Risk classification of AI systems
Only AI Act no specific requirement on the other side in the acts covered
Prohibited AI practices
Applies to: Operators of AI systems
Do not place on the market, put into service or use AI that manipulates people or exploits their vulnerabilities causing, or likely to cause, significant harm, scores people socially leading to unjustified or out-of-context detriment, predicts crime from profiling alone, builds facial recognition databases by untargeted scraping, infers emotions at work or in education other than for medical or safety reasons, or categorises people biometrically to infer sensitive traits. Real-time remote biometric identification in public spaces for law enforcement is banned outside narrow exceptions.
Intimate imagery and child sexual abuse material
Applies to: Operators of AI systems
Do not place on the market, put into service or use AI that generates or manipulates realistic non-consensual intimate or sexually explicit material of an identifiable person, or child sexual abuse material unless a national 'without right' defence applies. For providers the ban bites where this is the intended purpose, or a foreseeable and reproducible outcome without adequate safeguards. For deployers it bites where the system is used for that purpose. Manipulation that adds no exposure and does not alter the nature of the activity is outside the ban.
Classify high-risk AI systems
Applies to: Providers of AI systems
Treat an AI system as high-risk where it is a safety component of a product, or is itself a product, under Annex I legislation that requires third-party conformity assessment, or where it falls in an Annex III use case. A third-party assessment required only for risks other than health and safety does not count. AI used only for non-safety assistance, optimisation, efficiency, convenience or quality control is not a safety component, unless its failure would endanger health and safety.
Document an Annex III opt-out
Applies to: Providers of Annex III AI systems they consider not high-risk
An Annex III system is not high-risk only if it poses no significant risk and meets one of four conditions, such as a narrow procedural or preparatory task. It is always high-risk if it profiles people. A provider relying on this documents its assessment before placing the system on the market or putting it into service, registers it and gives the assessment to authorities on request.
Nothing in the acts covered.
Data and data governance
Only AI Act no specific requirement on the other side in the acts covered
Special category data for bias correction Optional
Providers may exceptionally process special categories of personal data where strictly necessary to detect and correct bias. Other data, including synthetic or anonymised data, must not be able to do the job, and the data must be secured, not passed to others, deleted once the bias is corrected or the retention period ends, and the reasons recorded.
Data sets and data governance
Applies to: Providers of high-risk AI systems
Apply governance to training, validation and testing data covering design choices, origin, preparation, data gaps and examination for bias, with measures to detect, prevent and mitigate it. Data sets must be relevant, sufficiently representative, as error-free and complete as possible, and fit the intended setting. Where no model is trained, this applies to testing data only.
Copyright policy and training content summary
Applies to: Providers of general-purpose AI models
Put in place a policy to comply with Union copyright law, including identifying and respecting rights reservations. Publish a sufficiently detailed summary of the content used for training, using the AI Office template.
Nothing in the acts covered.
Transparency to users
Only AI Act no specific requirement on the other side in the acts covered
Transparency and instructions for use
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
Design the system so deployers can interpret its output and use it properly. Supply clear instructions covering the provider's identity, intended purpose, tested accuracy, robustness and cybersecurity, foreseeable risks, human oversight measures, maintenance needs and how to collect and interpret logs.
Tell workers and affected people
Applies to: Deployers of high-risk AI systems, including employers
Before using a high-risk system at the workplace, employers inform workers' representatives and affected workers. Deployers of Annex III systems that make or assist decisions about people tell those people that the system is used.
Disclose interaction with AI
Applies to: Providers of AI systems that interact directly with people
Design systems that interact directly with people so those people are told they are dealing with AI, unless this is obvious to a reasonably well-informed person. Give the information clearly at the latest at the first interaction, in an accessible form.
Mark synthetic content
Applies to: Providers of AI systems, including general-purpose AI systems, that generate synthetic content
Ensure outputs are marked in a machine-readable format and detectable as artificially generated or manipulated, with solutions that are effective, interoperable, robust and reliable as far as technically feasible. This does not apply to assistive standard editing or where the input is not substantially altered.
Disclose emotion recognition and deep fakes
Applies to: Deployers of emotion recognition, biometric categorisation or content-generating AI systems
Inform people exposed to emotion recognition or biometric categorisation. Disclose that deep fake content, and text published to inform the public on matters of public interest, is artificially generated or manipulated. Artistic works carry a limited disclosure, and reviewed text under editorial responsibility is exempt.
Model documentation
Applies to: Providers of general-purpose AI models
Keep up-to-date technical documentation of the model for the AI Office and national authorities (Annex XI), and information for providers integrating the model (Annex XII). Open-source models with public parameters are exempt unless they carry systemic risk.
Nothing in the acts covered.
Human oversight
Only AI Act no specific requirement on the other side in the acts covered
Design for human oversight
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
Design the system so people can effectively oversee it in use: understand its limits, watch for automation bias, interpret output, disregard or override it, and stop it safely. For remote biometric identification under Annex III, point 1(a), no action is taken on an identification unless at least two competent people verify it separately. This does not apply in law enforcement, migration, border control or asylum where Union or national law considers it disproportionate.
Use as instructed and assign oversight
Applies to: Deployers of high-risk AI systems
Use the system in line with its instructions through appropriate technical and organisational measures. Assign human oversight to people with the necessary competence, training, authority and support. Where you control input data, ensure it is relevant and sufficiently representative for the intended purpose.
Nothing in the acts covered.
Conformity assessment and monitoring
Only AI Act no specific requirement on the other side in the acts covered
Technical documentation
Applies to: Providers of high-risk AI systems
Draw up technical documentation with at least the Annex IV elements before placing the system on the market or putting it into service, and keep it up to date. SMEs and small mid-caps may use the Commission's simplified form. Products under Annex I, Section A legislation need a single set of documentation.
Monitor use and report problems
Applies to: Deployers of high-risk AI systems
Monitor operation on the basis of the instructions. If use may present a risk, inform the provider or distributor and the market surveillance authority without undue delay and suspend use. If you identify a serious incident, immediately inform the provider first, then the importer or distributor and the market surveillance authorities.
Conformity assessment
Applies to: Providers of high-risk AI systems
Annex III, point 1 systems may choose internal control or a notified body where harmonised standards or common specifications are fully applied, and otherwise use a notified body. Annex III, points 2 to 8 use internal control, and Annex I, Section A systems follow the sectoral procedure. A substantial modification needs a new assessment. For systems that continue to learn, changes pre-determined at the initial assessment and documented are not a substantial modification.
EU declaration of conformity and CE marking
Applies to: Providers of high-risk AI systems
Draw up an EU declaration for each system with the Annex V content, keep it up to date and available for 10 years, and accept responsibility for compliance by drawing it up. Affix the CE marking visibly, legibly and indelibly, or digitally for systems provided digitally, with the notified body number where applicable.
Post-market monitoring
Applies to: Providers of high-risk AI systems
Establish and document a post-market monitoring system, proportionate to the technology and risk, that actively collects and analyses performance data throughout the system's lifetime to evaluate continuing compliance. Base it on a plan held in the technical documentation.
Nothing in the acts covered.
Supervision and enforcement
Registration with authorities
PSD2 more detailed more requirements on this, not necessarily stricter
Register in the EU database
Applies to: Providers of Annex III AI systems or their authorised representatives
Before placing on the market or putting into service an Annex III high-risk system, or a system you concluded is not high-risk under Article 6(3), register yourself and the system in the EU database. Critical infrastructure systems under Annex III, point 2 are registered at national level.
Public bodies register their use
Applies to: Deployers that are public authorities, Union bodies or persons acting on their behalf
Before putting into service or using an Annex III high-risk system, other than a critical infrastructure system under point 2, register yourself, select the system and register its use in the EU database. Do not use a system that is not registered, and inform the provider or distributor.
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 AI Act no specific requirement on the other side in the acts covered
Keep documents and cooperate with authorities
Applies to: ProvidersProvider Under the AI Act of high-risk AI systemsAn AI system classified as high-risk under AI Act Article 6, either through the Annex I product-safety route or an Annex III use case. Certain Annex III systems may fall outside that classification under Article 6(3) if its conditions are met, while Annex III systems performing profiling of natural persons remain high-risk. Classification determines the applicable conformity and compliance requirements.
Keep technical and quality system documentation, notified body decisions and the EU declaration available to authorities for 10 years. On a reasoned request, give the authority the information needed to show conformity and access to logs under your control.
Nothing in the acts covered.
Penalties and liability
AI Act more detailed more requirements on this, not necessarily stricter
Fines for prohibited practices
Applies to: Operators of AI systems
Breach of the Article 5 prohibitions carries fines of up to EUR 35 million or 7% of total worldwide annual turnover, whichever is higher. For SMEs and start-ups the lower of the two applies.
Fines for operator obligations
Applies to: Operators of AI systems and notified bodies
Breach of the obligations of providers, authorised representatives, importers, distributors, deployers and notified bodies, or of Article 50 transparency, carries fines of up to EUR 15 million or 3% of total worldwide annual turnover, whichever is higher. For SMEs and small mid-caps the lower of the two applies.
Fines for misleading information
Applies to: Anyone supplying information to notified bodies or national competent authorities in reply to a request
Supplying incorrect, incomplete or misleading information to notified bodies or national authorities in reply to a request carries fines of up to EUR 7.5 million or 1% of total worldwide annual turnover, whichever is higher. For SMEs and small mid-caps the lower of the two applies.
Fines for general-purpose AI model providers Optional
Applies to: Providers of general-purpose AI models
The Commission may fine a provider that intentionally or negligently infringes the Regulation, fails to answer an information request correctly, or does not comply with a requested measure or evaluation access, up to 3% of annual total worldwide turnover or EUR 15 million, whichever is higher.
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.