> GDPR Spain vs PSD2 side by side, topic by topic: where they overlap, where they differ and which asks more, with incident deadlines, testing, third parties and fines.

# GDPR Spain vs PSD2

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

[GDPR Spain](https://grc.plus/regulation/general-data-protection-regulation-gdpr/spain/)Controllers and processors

[PSD2](https://grc.plus/regulation/revised-payment-services-directive-psd2/)Payment service providers; authorisation requirements for payment institutions

## At a Glance

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

- **GDPR Spain** Asks more on 0 topics Alone on 0 topics More detailed on 0 topics
- **PSD2** Asks more on 0 topics Alone on 7 topics More detailed on 0 topics

| Topic | GDPR Spain | PSD2 | Verdict |
| --- | --- | --- | --- |
| Risk management |  |  |  |
| Risk management framework | GDPR Spain: 1 | PSD2: 1 | **Both cover it**read the wording below |
| Risk assessment | GDPR Spain: 1 | PSD2: 2 | **Both cover it**read the wording below |
| Review, audit and improvement | GDPR Spain: – | PSD2: 2 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Protection |  |  |  |
| Access control | GDPR Spain: – | PSD2: 2 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Authentication | GDPR Spain: – | PSD2: 14 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Cryptography and encryption | GDPR Spain: 1 | PSD2: 2 | **Both cover it**read the wording below |
| Data security | GDPR Spain: 2 | PSD2: 1 | **Both cover it**read the wording below |
| Secure communications | GDPR Spain: – | PSD2: 4 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Detection and response |  |  |  |
| Monitoring and detection | GDPR Spain: – | PSD2: 1 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Reporting to authorities | GDPR Spain: 3 | PSD2: 3 | **Both cover it**read the wording below |
| Continuity and resilience |  |  |  |
| Business continuity and crisis management | GDPR Spain: – | PSD2: 1 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Third parties and supply chain |  |  |  |
| Supplier and third-party risk | GDPR Spain: 2 | PSD2: 1 | **Both cover it**read the wording below |
| Supervision and enforcement |  |  |  |
| Registration with authorities | GDPR Spain: – | PSD2: 7 | **Only PSD2**no specific requirement on the other side in the acts covered |
| Penalties and liability | GDPR Spain: 2 | PSD2: 1 | **Both cover it**read 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

- [GDPR](https://grc.plus/regulation/general-data-protection-regulation-gdpr/) Regulation (EU) 2016/679 Articles 5 to 10, 12 to 22, 24 to 39, 44 to 49, 58, 83 · 50 requirements

National requirements

None recorded yet, so the Directive is shown as it is. The national law may go further.

Status

Reviewed against the official texts.

Included

- [PSD2](https://grc.plus/regulation/revised-payment-services-directive-psd2/) Directive (EU) 2015/2366, OJ L 337, 23.12.2015, p. 35 Articles 5, 11, 12, 14, 15, 19, 28, 32, 33, 36, 65 to 68, 70, 95 to 98, 103 · 22 requirements
- [PSD2 SCA RTS](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/) Commission Delegated Regulation (EU) 2018/389, OJ L 69, 13.3.2018, p. 23 Articles 1, 3 to 6, 9 to 12, 15 to 19, 21, 22, 27, 28, 30 to 36 · Annex · 20 requirements Applies to: Payment service providers
- [EBA/GL/2018/05](https://grc.plus/regulation/psd2-guidelines-fraud-reporting/) EBA/GL/2018/05 of 18 July 2018, Guidelines on fraud reporting under the Payment Services Directive 2 (PSD2), as amended by EBA/GL/2020/01 of 22 January 2020 6 requirements
- [EBA ICT Guidelines](https://grc.plus/regulation/eba-guidelines-ict-and-security-risk-management/) EBA/GL/2019/04 (November 2019), as amended by EBA/GL/2025/02 of 11 February 2025; consolidated version of 19 May 2026 5 requirements

Status

Reviewed against the official texts.

## Key Numbers

### Deadline

GDPR Spain: At the time the data are obtained (Controllers); Within a reasonable period and at the latest one month after obtaining the data; if used to contact the person, at the latest at first communication; if disclosure is envisaged, at the latest at first disclosure (Controllers); Without undue delay and in any event within one month of receipt of the request; extendable by two further months where necessary (Controllers); Without undue delay and in any event within one month of receipt of the request (Article 12(3)); extendable by two further months where necessary (Controllers); Without undue delay after becoming aware (Processors); Without undue delay (Controllers); Before the processing starts (Controllers); Before the processing starts; where the authority considers the processing would infringe, it gives written advice within up to eight weeks of receipt of the request, extendable by six weeks (Controllers)

PSD2: Not in the acts covered

### Threshold

GDPR Spain: Under 16; Member States may lower the age, not below 13 (Controllers offering information society services directly to children); Exemption only below 250 persons, and only if none of the listed conditions applies (Controllers)

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

### Goes to

GDPR Spain: Controller (Processors); Data subjects (Controllers)

PSD2: Not in the acts covered

### Evidence to keep

GDPR Spain: Written record of processing activities (Controllers); Written record of processing activities (Processors); Internal record of each breach: facts, effects and remedial action (Controllers)

PSD2: Not in the acts covered

### Incident reports go to

GDPR Spain: Competent supervisory authority (Controllers)

PSD2: Competent authority (providers outside DORA only)

### First notice of an incident

GDPR Spain: Without undue delay and, where feasible, within 72 hours of becoming aware (Controllers)

PSD2: Without undue delay (providers outside DORA only)

### Intermediate report

GDPR Spain: In phases, without undue further delay (Controllers)

PSD2: Not in the acts covered

### External assessment or certification

GDPR Spain: Approved code of conduct or certification may help show compliance (Controllers)

PSD2: Independent audit of the security measures; yearly where the transaction risk analysis exemption is used (Payment service providers)

### Review of the risk framework

GDPR Spain: Where necessary (Controllers)

PSD2: Risk assessment to the authority at least once a year

### Testing of critical systems

GDPR Spain: Regularly

PSD2: Not in the acts covered

### Registration with the authority

GDPR Spain: Not in the acts covered

PSD2: Authorisation by the home authority before providing payment services

### Maximum fines

GDPR Spain: Up to EUR 10 million or, for an undertaking, 2% of total worldwide annual turnover of the preceding financial year, whichever is higher; Up to EUR 20 million or, for an undertaking, 4% of total worldwide annual turnover of the preceding financial year, whichever is higher

PSD2: Set by each member state

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

- Measures to ensure and show compliance
  Applies to: Controllers
  Put in place technical and organisational measures suited to the risks of the processing, so that it complies and the controller can show it does. Review and update them where needed. Where proportionate, these include data protection policies.
  [GDPR, Article 24](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Operational and security risk management
  Mitigation measures and controls for operational and security risks, with a yearly risk assessment to the authority.
  [PSD2, Article 95](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

### 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 security risk
  When judging the right level of security, weigh the risks of processing, in particular accidental or unlawful destruction, loss, alteration, and unauthorised disclosure of or access to personal data.
  [GDPR, Article 32(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Risk measures and yearly assessment
  Mitigation measures and controls, and a comprehensive risk assessment to the authority at least yearly. For banks, payment and e-money institutions and account information providers, without prejudice to DORA Chapter II since 17 January 2025.
  [PSD2, Article 95(1)-(2)](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Transaction risk analysis
  Applies to: Payment service providers
  Remote payments assessed as low risk in real time, up to EUR 100, 250 or 500 where the provider's fraud rate stays under the reference rate for that band (for cards 0.13%, 0.06% and 0.01%; for credit transfers 0.015%, 0.01% and 0.005%).
  [PSD2 SCA RTS, Article 18 and Annex](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### Review, audit and improvement

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

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

Nothing in the acts covered.

- Transaction monitoring and review of security measures
  Applies to: Payment service providers
  Monitor transactions to detect unauthorised or fraudulent payments. Document, test and evaluate the security measures, and have them audited by operationally independent internal or external auditors; the report is available to the authority on request.
  [PSD2 SCA RTS, Articles 1-3](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Audit of security measures
  Applies to: Payment service providers
  The audit follows the provider's statutory audit cycle; where the transaction risk analysis exemption is used, its methodology, model and fraud rates are audited at least once a year.
  [PSD2 SCA RTS, Article 3](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

## 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.
  [PSD2, Articles 65-67](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Confirmation of funds
  With the payer's explicit consent, the account servicing provider answers a card issuer's request with a yes or no only.
  [PSD2, Article 65](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

### Authentication

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

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

Nothing in the acts covered.

- Instruments and credentials
  Users keep their credentials safe and report loss or theft without undue delay; providers offer a free way to report and block use after it.
  [PSD2, Articles 68-70](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Strong customer authentication
  Strong customer authentication when the payer goes online, pays electronically or acts remotely with a risk of fraud, with dynamic linking for remote payments.
  [PSD2, Articles 97-98](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 linking to amount and payee for remote payments, and protection of credentials.
  [PSD2, Article 97](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Technical standards
  The details, exemptions and the communication standards are in Delegated Regulation (EU) 2018/389, reviewed by the EBA with regard to DORA.
  [PSD2, Article 98](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Strong customer authentication
  Applies to: Payment service providers
  Authentication codes built from two or more independent elements (knowledge, possession, inherence) that cannot be forged or derived, with dynamic linking to amount and payee for remote payments.
  [PSD2 SCA RTS, Articles 4-9](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Authentication code
  Applies to: Payment service providers
  No more than five failed attempts in a row before the instrument is blocked, protected sessions and at most five minutes of inactivity for online account access.
  [PSD2 SCA RTS, Article 4](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Dynamic linking
  Applies to: Payment service providers
  The payer sees the amount and the payee, and the code works only for them; any change invalidates it.
  [PSD2 SCA RTS, Article 5](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- The elements and their independence
  Applies to: Payment service providers
  Measures against disclosure of knowledge elements, replication of possession elements and abuse of inherence elements; the breach of one element does not compromise the others, including on multi-purpose devices.
  [PSD2 SCA RTS, Articles 6-9](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Exemptions from strong customer authentication
  Applies to: Payment service providers
  Providers may skip strong customer authentication in defined cases; the aggregator exemption for account information is mandatory.
  [PSD2 SCA RTS, Articles 10-18](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Account information
  Applies to: Payment service providers
  Limited access to balance and the last 90 days of transactions without SCA, renewed at least every 180 days; mandatory for access through an account information provider since 25 July 2023 (Delegated Regulation 2022/2360).
  [PSD2 SCA RTS, Articles 10 and 10a](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Contactless payments
  Applies to: Payment service providers
  Up to EUR 50 per payment, while the cumulative amount since the last SCA stays under EUR 150 or there have been no more than five payments.
  [PSD2 SCA RTS, Article 11](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Unattended terminals, trusted beneficiaries, recurring payments and own accounts
  Applies to: Payment service providers
  Transport fares and parking fees at unattended terminals, payees on the payer's trusted list, a series of payments of the same amount to the same payee after the first, and transfers between the payer's own accounts at the same provider.
  [PSD2 SCA RTS, Articles 12-15](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Low-value remote payments
  Applies to: Payment service providers
  Up to EUR 30 per payment, while the cumulative amount since the last SCA stays under EUR 100 or there have been no more than five payments.
  [PSD2 SCA RTS, Article 16](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Secure corporate payments
  Applies to: Payment service providers
  Dedicated payment processes and protocols for payers that are not consumers, where the authority is satisfied they give equivalent security.
  [PSD2 SCA RTS, Article 17](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### Cryptography and encryption

**Both cover it** read the wording below

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

- Pseudonymisation and encryption
  Apply pseudonymisation and encryption of personal data, as appropriate to the risk.
  [GDPR, Article 32(1)(a)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Protection of personalised security credentials
  Applies to: Payment service providers
  Confidentiality and integrity of credentials and authentication devices through their life cycle: creation, association with the user, delivery, renewal, destruction and revocation.
  [PSD2 SCA RTS, Articles 22-27](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Certificates and session security
  Applies to: Payment service providers
  Qualified eIDAS certificates for electronic seals or website authentication, and secure encryption of the communication session.
  [PSD2 SCA RTS, Articles 34-35](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

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

- Integrity and confidentiality
  Applies to: Controllers
  Process personal data with appropriate security, using appropriate technical or organisational measures, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage.
  [GDPR, Article 5(1)(f)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Security of systems and services
  Be able to keep processing systems and services confidential, intact, available and resilient on an ongoing basis, as appropriate to the risk.
  [GDPR, Article 32(1)(b)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Data exchange
  Applies to: Payment service providers
  Without the user actively requesting it, account information providers access the data no more than four times in 24 hours, unless agreed otherwise.
  [PSD2 SCA RTS, Article 36](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### 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.
  [PSD2, Article 66](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Account information services
  Only with the user's explicit consent, only for the designated accounts, with secure communication and no use of data beyond the service.
  [PSD2, Article 67](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 eIDAS certificates and protect the session.
  [PSD2 SCA RTS, Articles 28-36](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)
- Access interface
  Applies to: Payment service providers
  Technical documentation and a testing facility (published from 14 March 2019), and a choice between a dedicated interface and the customer interface.
  [PSD2 SCA RTS, Articles 30-31](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

## 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 analysis exemption and tells the authority. Fraud data on exemptions is recorded and monitored.
  [PSD2 SCA RTS, Articles 19-21](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

### Reporting to authorities

**Both cover it** read the wording below

NIST CSF 2.0 RS.CO · ISO/IEC 27001:2022 A.5.5

- Notify a personal data breach
  Applies to: Controllers
  Notify the competent supervisory authority without undue delay and, where feasible, within 72 hours of becoming aware, unless the breach is unlikely to risk people's rights and freedoms. Give reasons if the notice is late.
  [GDPR, Article 33(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Processor tells the controller
  Applies to: Processors
  Tell the controller of a personal data breach without undue delay after becoming aware of it.
  [GDPR, Article 33(2)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- What the breach notice contains
  Applies to: Controllers
  Describe the breach, including the categories and approximate numbers of people and records where possible, the DPO or other contact point, the likely consequences, and the measures taken or proposed. Information not yet available may follow in phases.
  [GDPR, Article 33(3) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Incident reporting and fraud statistics
  Major incidents are reported (under DORA for most providers since 2025) and fraud data is sent at least yearly.
  [PSD2, Article 96](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 DORA's scope, which report under DORA.
  [PSD2, Article 96(1)-(5)](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Fraud statistics
  Statistical data on fraud by means of payment, at least yearly, to the authority.
  [PSD2, Article 96(6)](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

## 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 availability 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 EBA.
  [PSD2 SCA RTS, Articles 32-33](https://grc.plus/regulation/psd2-rts-strong-customer-authentication-2018-389/#requirements)

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

- Use only processors with sufficient guarantees
  Applies to: Controllers
  Use only processors that give adequate assurances of technical and organisational measures that meet the Regulation and protect people's rights.
  [GDPR, Article 28(1)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Sub-processors
  Applies to: Processors
  Do not engage another processor without the controller's prior written authorisation, specific or general, and under general authorisation give notice of changes so the controller can object. Bind the sub-processor by contract to the same data protection obligations. The initial processor stays fully liable for the sub-processor's failures.
  [GDPR, Article 28(2) and (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Agents and outsourcing
  Agents are notified and registered before they start. Outsourcing of important operational functions, including ICT systems, must not impair internal control or supervision.
  [PSD2, Article 19](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

## 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 institution is authorised by its home authority before it starts, holds initial capital and own funds, and keeps users' funds safe.
  [PSD2, Articles 5-12](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 continuity, a security policy and risk assessment, AML controls, owners and directors. The authority decides within three months; the authorisation is valid across the EU.
  [PSD2, Articles 5, 11, 12](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- 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 institutions fair access to accounts.
  [PSD2, Articles 14-15, 19, 28, 36](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Public registers
  Each member state keeps a public register of payment institutions, their agents and branches, exempt institutions and account information providers; the EBA keeps a central register.
  [PSD2, Articles 14-15](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Small payment institutions and account information providers
  Member states may register small payment institutions instead of authorising them; account information providers are registered.
  [PSD2, Articles 32-33](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Small payment institutions
  A member state may exempt institutions whose monthly average of payment transactions over 12 months stays under a national limit of at most EUR 3 million; they are registered and cannot passport.
  [PSD2, Article 32](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)
- Account information providers
  Registered instead of authorised, with professional indemnity insurance; most of Titles III and IV does not apply to them.
  [PSD2, Article 33](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

### Penalties and liability

**Both cover it** read the wording below

- Fines for operational obligations
  Infringing the duties of controllers and processors in Articles 8, 11, 25 to 39, 42 and 43, or of certification and monitoring bodies, can be fined, and fines are set case by case to be effective, proportionate and dissuasive. Several infringements in the same or linked processing operations are capped at the amount for the gravest one.
  [GDPR, Article 83(1) to (4)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive
- Fines for principles, rights and transfers
  Infringing the principles and consent requirements in Articles 5, 6, 7 and 9, rights in Articles 12 to 22, transfer requirements in Articles 44 to 49, Member State law adopted under Chapter IX, or ignoring an authority's order or denying it access can be fined at the higher level.
  [GDPR, Article 83(5) and (6)](https://grc.plus/regulation/general-data-protection-regulation-gdpr/#requirements) · applies as in the Directive

- Penalties
  Member states set effective, proportionate and dissuasive penalties.
  [PSD2, Article 103](https://grc.plus/regulation/revised-payment-services-directive-psd2/#requirements)

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. 16 topics where all apply the Directive as it is are not shown.

## More Comparisons

- [Compare GDPR Spain](https://grc.plus/compare/gdpr-spain/)
- [Compare PSD2](https://grc.plus/compare/psd2/)

Source: https://grc.plus/compare/gdpr-spain-vs-psd2/
