ONC Certification 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 14 of 14 topics. Each verdict names what it rests on; read the wording before relying on it.
- ONC Certification Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- PSD2 Asks more on 0 topics Alone on 14 topics More detailed on 0 topics
| Topic | ONC Certification | PSD2 | Verdict |
|---|---|---|---|
| Risk management | |||
| Risk management framework | ONC Certification: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
| Risk assessment | ONC Certification: – | PSD2: 2 | Only PSD2no specific requirement on the other side in the acts covered |
| Review, audit and improvement | ONC Certification: – | PSD2: 2 | Only PSD2no specific requirement on the other side in the acts covered |
| Protection | |||
| Access control | ONC Certification: – | PSD2: 2 | Only PSD2no specific requirement on the other side in the acts covered |
| Authentication | ONC Certification: – | PSD2: 14 | Only PSD2no specific requirement on the other side in the acts covered |
| Cryptography and encryption | ONC Certification: – | PSD2: 2 | Only PSD2no specific requirement on the other side in the acts covered |
| Data security | ONC Certification: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
| Secure communications | ONC Certification: – | PSD2: 4 | Only PSD2no specific requirement on the other side in the acts covered |
| Detection and response | |||
| Monitoring and detection | ONC Certification: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
| Reporting to authorities | ONC Certification: – | PSD2: 3 | Only PSD2no specific requirement on the other side in the acts covered |
| Continuity and resilience | |||
| Business continuity and crisis management | ONC Certification: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
| Third parties and supply chain | |||
| Supplier and third-party risk | ONC Certification: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
| Supervision and enforcement | |||
| Registration with authorities | ONC Certification: – | PSD2: 7 | Only PSD2no specific requirement on the other side in the acts covered |
| Penalties and liability | ONC Certification: – | PSD2: 1 | Only PSD2no specific requirement on the other side in the acts covered |
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
- ONC Certification 45 CFR Part 170; final rule RIN 0955-AA09, FR Doc. 2026-21943, 91 FR 67916, 28 October 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
Threshold
ONC Certification: Not in the acts covered
PSD2: Member state option, at most EUR 3 million a month
Incident reports go to
ONC Certification: Not in the acts covered
PSD2: Competent authority (providers outside DORADigital Operational Resilience Act only)
First notice of an incident
ONC Certification: Not in the acts covered
PSD2: Without undue delay (providers outside DORADigital Operational Resilience Act only)
External assessment or certification
ONC Certification: Not in the acts covered
PSD2: Independent audit of the security measures; yearly where the transaction risk analysisIn EU payment requirements, a real-time assessment used to identify low-risk remote electronic payments that may qualify for an exemption from strong customer authentication, normally a check using at least two independent factors. The assessment considers spending patterns, devices, locations and fraud indicators. Use of the exemption also depends on payment-value limits and the provider's fraud rates. The methodology, model and reported fraud rates require at least annual independent audit. exemption is used (Payment service providers)
Review of the risk framework
ONC Certification: 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
ONC Certification: Not in the acts covered
PSD2: Authorisation by the home authority before providing payment services
Maximum fines
ONC Certification: Not in the acts covered
PSD2: Set by each member state
Risk management
Risk management framework
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.RM · ISO/IEC 27001:2022 Clause 6.1
Nothing in the acts covered.
Operational and security risk management
Mitigation measures and controls for operational and security risks, with a yearly risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. to the authority.
Risk assessment
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.RA · ISO/IEC 27001:2022 Clauses 6.1.2, 8.2
Nothing in the acts covered.
Risk measures and yearly assessment
Mitigation measures and controls, and a comprehensive risk assessmentA structured process for identifying risks, analysing their possible effects and judging which need attention. In information security, this means examining threats, weaknesses and existing safeguards to prioritise risks to information and business operations. The assessment informs decisions about reducing or accepting risk and should be reviewed as circumstances change. to the authority at least yearly. For banks, payment and e-moneyElectronic Money institutions and account information providers, without prejudice to DORADigital Operational Resilience Act Chapter II since 17 January 2025.
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
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 ID.IM, GV.OV · ISO/IEC 27001:2022 A.5.35, A.5.36, Clauses 9, 10
Nothing in the acts covered.
Transaction monitoring and review of security measures
Applies to: Payment service providers
Monitor transactions to detect unauthorised or fraudulent payments. Document, test and evaluate the security measures, and have them audited by operationally independent internal or external auditors; the report is available to the authority on request.
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
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.
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.
Reporting to authorities
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5
Nothing in the acts covered.
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.
Third parties and supply chain
Supplier and third-party risk
Only PSD2 no specific requirement on the other side in the acts covered
NIST CSF 2.0 GV.SC · ISO/IEC 27001:2022 A.5.19, A.5.21 to A.5.23
Nothing in the acts covered.
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
Only PSD2 no specific requirement on the other side in the acts covered
Nothing in the acts covered.
Authorisation, capital and safeguarding
A payment institutionIn the EU payment-services framework, a legal entity authorised under PSD2 to provide and execute payment services. Depending on its permission, these can include transferring money, processing card payments or providing payment-initiation services. It is one category of payment service provider, alongside other categories such as banks and electronic money institutions, which are authorised to issue electronically stored monetary value accepted for payments by someone other than the issuer. Its authorisation covers specified services rather than every financial activity. is authorised by its home authority before it starts, holds initial capital and own funds, and keeps users' funds safe.
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.
Penalties and liability
Only PSD2 no specific requirement on the other side in the acts covered
Nothing in the acts covered.
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.