Payment Security

EU PSD2 — Payment Services Directive (Directive (EU) 2015/2366)

PSD2 framework badge
Summarize with
ClaudeChatGPTPerplexityGoogle AI Mode
In this article
At a Glance
PSD2 (Directive (EU) 2015/2366)
  • Classification
    Category
    Payment Security
    Domain
    Financial Services Regulation
    Framework Family
    Other
  • Regulatory Context
    Type
    Regulation
    Legal Instrument
    Directive
    Sector
    Financial Sector
    Industry
    Payment & FinTech
  • Region / Publisher
    Region
    European Union
    Region Detail
    European Union
    Publisher
    European Parliament and Council of the European Union
  • Versioning
    Version
    Directive (EU) 2015/2366
    Effective Date
    January 13, 2018 (national measures apply)
    Issue Date
    November 25, 2015 (signed); published December 23, 2015
  • Adoption
    Adoption Model
    Regulatory Compliance
    Implementation Complexity
    High
  • Official Reference
License Information

License included / downloadable: Yes

The Directive is EU law published in the Official Journal and is included with the platform for reference.

Framework text is licensed by its publisher and is included only where stated above.

Official Resources
Payment Services Directive (PSD2) Text
Defines the legal framework and requirements for the Payment Services Directive.
PSD2 Implementation Guidelines
Provides guidelines for implementing PSD2 requirements across financial institutions.
EBA Regulatory Technical Standards for PSD2
Describes the technical standards for strong customer authentication and secure communication.
PSD2 Compliance and Risk Management Overview
Outlines compliance requirements and risk management processes for PSD2 adherence.
Key takeaways
  • PSD2 (Directive (EU) 2015/2366) regulates payment services in the European Union, with national measures applying from January 13, 2018.
  • It licenses payment institutions and gives payment initiation and account information providers regulated access to customers' payment accounts.
  • Strong customer authentication is required for online and remote payments under Article 97.
  • Providers set up an operational and security risk framework and report major incidents to their authority.
  • Articles 71 to 74 set refund and liability rules for unauthorized payments.

Overview

The revised Payment Services Directive (PSD2, Directive (EU) 2015/2366) regulates payment services in the European Union: it licenses payment institutions, gives licensed payment initiation and account information providers access to customers' payment accounts, requires strong customer authentication for online and remote payments, and sets refund and liability rules for unauthorized payments. Member States had to apply it from January 13, 2018.

The European Parliament and the Council adopted it on November 25, 2015. National competent authorities license and supervise payment service providers, and the European Banking Authority (EBA) issues technical standards and guidelines under it. It applies to banks, payment institutions, e-money institutions and the providers of payment initiation and account information services, as the categories of provider in Article 1 and the services in Annex I show.

Providers implement it by obtaining authorization and meeting capital rules, setting up an operational and security risk framework (Article 95), applying strong customer authentication (Article 97), reporting major incidents to their authority (Article 96), and handling unauthorized payment claims under Articles 71 to 74.

Why does it matter?

PSD2 changed who may touch a customer's bank data and how a customer proves who they are. It opened payment accounts to regulated third parties with the customer's consent and tightened security and liability for everyone who processes payments.

Key benefits include:

  • Regulated third-party access

Payment initiation and account information service providers can access payment accounts with the customer's explicit consent, and banks must allow it (Articles 36, 66 and 67).

  • Strong customer authentication

Providers apply strong customer authentication when the payer accesses an account online, initiates an electronic payment or acts remotely in a way that may imply fraud risk (Article 97(1)).

  • Fast refunds

The payer's provider refunds an unauthorized payment immediately and in any event by the end of the following business day (Article 73(1)).

  • Capped consumer losses

A payer may bear losses from a lost or stolen payment instrument only up to EUR 50, with exceptions such as fraud (Article 74(1)).

  • Incident reporting

Providers notify their authority without undue delay of a major operational or security incident and tell affected users if their financial interests may be affected (Article 96).

How does it work?

The Directive has six titles. Title I sets subject matter, scope and definitions. Title II covers payment service providers and their authorization, including capital (Article 7) and the rules for account information providers (Article 33). Title III covers transparency of conditions and information. Title IV covers rights and obligations, including access to accounts (Article 36), consent (Article 64), liability (Articles 73 and 74) and security (Articles 95 to 98).

Payment initiation and account information providers rely on the authentication procedures the account servicing provider offers its customer (Article 97(5)) and must identify themselves to the account provider. Account providers may deny access only for objectively justified and duly evidenced reasons relating to unauthorized or fraudulent access (Article 68(5)).

Article 98 mandates regulatory technical standards from the EBA on authentication and secure communication. Providers also keep records to prove authentication and execution of transactions (Article 72), and run complaints and dispute resolution procedures (Articles 99 to 101).

Key Elements

  • Authorization and supervision (Titles I and II)

Payment institutions are authorized and supervised by home Member State authorities, with initial capital rules and a professional indemnity requirement for some providers.

  • Access to accounts (Articles 36, 66 and 67)

Credit institutions give authorized payment initiation and account information providers access to payment accounts, on an objective, non-discriminatory and proportionate basis.

  • Consent (Article 64)

A payment transaction is authorized only if the payer has given consent, in the form agreed, and consent can be withdrawn.

  • Authentication (Article 97)

Strong customer authentication with dynamic linking to the amount and payee for remote electronic payments, and protection of personalized security credentials.

  • Liability and refunds (Articles 71 to 74 and 89)

Payers notify unauthorized or incorrect transactions, providers bear the burden of proof of authentication, refund promptly and the payer's liability is capped at EUR 50 in defined cases.

  • Operational and security risk and incidents (Articles 95 and 96)

A risk framework, an annual assessment of risks provided to the authority, and notification of major incidents without undue delay.

What does it cover?

PSD2 applies to payment service providers listed in Article 1: credit institutions, electronic money institutions, post office giro institutions, payment institutions, and the ECB, national central banks and Member State authorities when they are not acting as public authorities. It covers payment services provided in the Union, with different rules where only one provider is in the Union. It excludes activities listed in Article 3 such as some cash and commercial agent activities.

What are its objectives?

PSD2 aims for a safer and more competitive payments market with better consumer protection.

Make payments safer through strong customer authentication and security requirements.

Open payment accounts to regulated providers with the customer's consent.

Give consumers clear refund rights and capped liability for unauthorized payments.

Harmonize authorization and supervision of payment institutions.

Increase competition and innovation in payment services.

Framework in Context

PSD2 is a directive that Member States transposed into national payment services law, so the exact rules depend on the country. It works with the EBA's technical standards on authentication, with the GDPR for the data it processes (Article 94) and with the DORA and NIS2 rules on operational resilience. The Commission has proposed replacing it with a new payment services directive and a payment services regulation; those were not in force on 14 Oct 2026.

Common Framework Mappings

Payment service providers map PSD2 to the regulations and standards they already run so one control set covers authentication, access, security and reporting obligations.

Mapped frameworks include:

EU Digital Operational Resilience Act (DORA)

EU General Data Protection Regulation (GDPR)

EBA Guidelines on ICT and security risk management (EBA/GL/2019/04)

NIS2 Directive

PCI DSS v4.0.1

ISO/IEC 27001:2022

SMARTSUITE

How SmartSuite Supports EU PSD2

SmartSuite provides the system for managing controls, evidence, mappings, assessments, and reporting.

Use Compliance Management and Cyber & IT Risk to hold the Article 95 risk framework, the strong customer authentication controls, incident reports and the evidence behind authorization conditions, and Third Party Risk Management for payment initiation and account information partners.

Authorization and Capital Evidence

Record the license, capital calculations and professional indemnity cover with expiry and review dates (Articles 5 and 7).

Operational and Security Risk Framework

Maintain the risk assessments, mitigation measures and the annual assessment sent to the competent authority (Article 95).

Strong Customer Authentication Controls

Map each access and payment flow to its authentication factors, dynamic linking and exemptions (Article 97).

Major Incident Reporting

Time each major incident against the notification to the authority and the message to affected users (Article 96).

Unauthorized Payment Claims

Track claims, evidence of authentication, refund deadlines and the EUR 50 liability cases (Articles 71 to 74).

Third-Party Access Register

List payment initiation and account information providers with access, their consent evidence and any access denials with reasons (Articles 66 to 68).

Related frameworks

EU DORA

DORA (Regulation (EU) 2022/2554) requires EU financial entities to manage ICT risk, report major incidents, test resilience and control ICT third-party risk, applying from January 17, 2025.

GDPR

The GDPR (Regulation (EU) 2016/679) sets principles, lawful bases, individual rights and accountability duties for personal data, with fines up to EUR 20 million or 4 percent of turnover.

ISO 27001:2022

ISO/IEC 27001:2022 specifies requirements for an information security management system: Clauses 4 to 10, risk treatment, the Statement of Applicability and 93 Annex A controls.

NIS2 (EU 2022/2555)

The NIS2 Directive requires essential and important entities in critical sectors to manage cyber risk, report significant incidents within 24 and 72 hours and make management accountable.

NIST CSF 2.0

NIST CSF 2.0 (CSWP 29, February 26, 2024) is the voluntary cybersecurity framework with six Functions including Govern, 22 Categories, 106 Subcategories, Profiles and Tiers.

PCI DSS 4.0.1

PCI DSS v4.0.1 (June 2024) is the current Payment Card Industry Data Security Standard: twelve requirements, two validation approaches and the dates that retired v4.0.

SWIFT CSCF

The SWIFT Customer Security Controls Framework (CSCF v2026) sets 32 mandatory and advisory controls that every Swift user attests to each year under the Customer Security Programme.

FAQ

Frequently Asked Questions For EU PSD2 (Payment Services Directive 2)

Authorization and supervision, an operational and security risk framework (Article 95), strong customer authentication (Article 97), notification of major incidents (Article 96) and clear rules on consent, refunds and liability for unauthorized payments (Articles 64 and 71 to 74).

PSD2 requires it when a payer accesses a payment account online, initiates an electronic payment or acts through a remote channel that may imply fraud risk. For remote electronic payments the authentication must dynamically link the transaction to a specific amount and payee (Article 97).

Licensed payment initiation and account information service providers, with the customer's explicit consent. The bank holding the account must allow this and may deny access only for objectively justified, evidenced reasons relating to unauthorized or fraudulent access (Articles 36, 66, 67 and 68).

Immediately, and in any event no later than the end of the following business day after noting or being notified of the transaction, except where the provider has reasonable grounds to suspect fraud and informs the authority (Article 73(1)). A payer's loss from a lost or stolen instrument is capped at EUR 50 in defined cases (Article 74).

Yes, as of October 14, 2026. A proposed third payment services directive and a payment services regulation would replace it, but they were not reported in force. Member States apply PSD2 through national law.

Put this framework to work in SmartSuite

Manage controls, risks, evidence, and audits in one platform designed for modern governance, risk, and compliance.