Does ENISA Data Protection Engineering cover EU Payment Services Directive (PSD2)?

16% of EU Payment Services Directive (PSD2) you already have

ENISA Data Protection Engineering already covers about 16% of EU Payment Services Directive (PSD2), leaving 16 of 19 controls as genuinely new work.

Already covered 0 Likely covered 3 New work 16

No control in ENISA Data Protection Engineering maps directly to one in EU Payment Services Directive (PSD2). Everything counted as covered is covered because both map to the same third standard, which is what a crosswalk is, but it is an inference rather than a lookup.

What is genuinely new work

Nothing in ENISA Data Protection Engineering reaches these. This is the list to scope.

PSD2-Art.10

Safeguarding requirements (PSD2 Article 10) - segregation or insurance

PSD2-Art.104_117

Delegated acts, transposition, repeal of PSD1 and entry into force (PSD2 Articles 104-117)

PSD2-Art.11_12_13

Grant, withdrawal and EBA register of authorisation (PSD2 Articles 11, 13, 14, 15)

PSD2-Art.19_20

Use of agents and outsourcing rules (PSD2 Articles 19 and 20)

PSD2-Art.1_2_3_4

Subject matter, scope and definitions (PSD2 Articles 1-4)

PSD2-Art.32_33

Exemptions for small payment institutions and AIS-only providers (PSD2 Articles 32 and 33)

PSD2-Art.38_60

Transparency of conditions and information requirements (PSD2 Articles 38-60)

PSD2-Art.5_19_22

Money-laundering / CFT and AML controls in payment institution authorisation + agents

PSD2-Art.5_8

Authorisation application, initial capital and own funds (PSD2 Articles 5, 7 and 8)

PSD2-Art.64_65

Consent and confirmation of availability of funds (PSD2 Articles 64 and 65)

PSD2-Art.66_67

Payment initiation services and account information services (PSD2 Articles 66 and 67) - the Open Banking rules

PSD2-Art.71_74_75_76_77

Unauthorised transactions, refunds and liability (PSD2 Articles 71, 74, 75, 76, 77)

PSD2-Art.96

Incident reporting to competent authority (PSD2 Article 96)

PSD2-Art.98

Article 98 RTS - SCA + common and secure communication (Commission Delegated Regulation (EU) 2018/389)

PSD2-Art.99_103

Out-of-court redress, competent authorities and penalties (PSD2 Articles 99-103)

PSD2-Status

PSD2 status - in force pending PSD3 + PSR adoption + transposition

Show the 3 you already have

PSD2-Art.94

Data protection (PSD2 Article 94) - GDPR alignment

PSD2-Art.95

Management of operational and security risks (PSD2 Article 95)

PSD2-Art.97

Strong Customer Authentication (PSD2 Article 97) - knowledge / possession / inherence + dynamic linking

How this is calculated

Already covered means a mapping runs from a control in ENISA Data Protection Engineering to that control. Likely covered means no direct mapping exists but both frameworks map to the same control in a third standard. New work means neither. We keep those separate rather than adding them into one friendlier number, because blending them would present a two-hop inference as a verified fact.

Coverage is not symmetric. Run it the other way and you will get a different number; both are correct.

From 332,959 cross-framework control mappings across 723 frameworks, 531 of them verified against their source documents. It does not tell you that you are compliant: a mapped control means the two standards ask for the same thing, not that you have done it.

Try another pair · Today's edition