
Psd3
| Official name | Payment Services Directive 3 |
|---|---|
| Full title | Directive (EU) 2024/... on payment services and electronic money services in the internal market |
| Status | Proposed legislation |
| Governing body | European Union |
| Preceded by | Payment Services Directive 2 (PSD2) |
| Legal form | Directive |
| Scope | Payment services, electronic money services, and data access in the EU |
Origin and history
The Payment Services Directive 3 (PSD3) is a proposed regulatory framework originating from the European Union. It follows the earlier PSD2, which was fully implemented across EU member states in the early 2020s. The development of PSD3 was initiated by the European Commission in the mid-2020s as part of a broader financial services digital package. This initiative stemmed from a recognized need to update the regulatory landscape in response to evolving technology and market practices post-PSD2. The proposal is part of a continuous legislative effort by EU institutions to shape a single market for payments and foster innovation. Its history is directly tied to the review process of PSD2, which identified areas requiring stronger provisions and new scope.
What it is for
PSD3 aims to further standardize and secure the European payments market, building upon the foundation laid by PSD2. A primary purpose is to enhance consumer protection and rights in electronic payments, particularly against fraud and poor service. It seeks to strengthen the security requirements for all payment service providers, including banks and third-party firms, to create a more level playing field. The regulation is designed to improve the functioning of open banking by making data sharing more reliable and efficient between banks and authorized third parties. It also intends to formally broaden the scope of the rules to include new types of payment services and providers that emerged after PSD2. Furthermore, PSD3 aims to improve cash availability by proposing rules that would allow retailers to provide cash services without a purchase.
Pros and cons
A significant pro of PSD3 is its potential to drastically reduce payment fraud through mandated, harmonized security measures across the EU. It also promises to increase competition by lowering barriers for non-bank payment service providers, potentially leading to more innovative and cheaper services for consumers. The proposed rules on cash access address a critical societal need, especially in areas facing bank branch closures. A primary con is the substantial compliance cost and operational complexity it imposes on traditional banks, which must overhaul systems and processes. The enhanced data-sharing requirements, while beneficial for open banking, raise persistent and complex concerns about data privacy and security vulnerabilities. A common mistake for payment service providers is underestimating the resource commitment required for implementation, leading to last-minute, costly scrambles that can degrade service quality. Merchants and some fintechs may regret the continued and potentially increased regulatory burden if the promised market benefits and revenue opportunities are slow to materialize.
Who it suits
This regulation primarily suits consumers and businesses that frequently engage in cross-border payments within the EU, as it promises more uniform and secure transactions. It is advantageous for fintech companies and other non-bank payment service providers seeking clearer rules and more reliable access to bank-held data under open banking. Large merchants and e-commerce platforms benefit from the potential for lower payment processing costs and a wider, more secure range of payment options for their customers. The regulation suits regulators and policymakers aiming for a more integrated, innovative, and resilient European payments ecosystem. It is less suited for very small banks or payment institutions with limited IT budgets, for whom compliance costs can be disproportionately high. Traditional banks with legacy IT systems are also a poor fit without significant investment, as the regulation demands agile, API-driven infrastructure they may lack.