2018年-CEPS欧洲政策研究中心_Europes_Payments_Revolution_21页_801kb

Europe's Payments Revolution: Summary

Core Content

This document explores the transformative impact of the Payment Services Directive II (PSD2) on Europe's financial services landscape. It highlights the shift from traditional banking models to a more open and digital financial ecosystem, driven by the need for innovation while ensuring consumer privacy. The authors, Inna Oliynyk and William Echikson, analyze the implications for various stakeholders including banks, fintechs, consumers, and regulators.

Main Viewpoints

• PSD2 as a Catalyst for Innovation: The directive aims to foster fintech innovation by enabling access to payment account data through APIs, making it easier for third-party providers to offer new services.
• Privacy and Data Protection Concerns: The implementation of PSD2 overlaps with the General Data Protection Regulation (GDPR), raising concerns about data consent, usage, and security. GDPR's stricter rules may conflict with PSD2's objectives.
• Challenges for Banks: Banks face significant costs and technical challenges in updating their legacy IT systems to comply with PSD2. They also express concerns about losing competitive advantage to fintechs and tech giants.
• Fintechs' Dilemma: While PSD2 opens new opportunities, fintechs worry about the fragmentation caused by varying API standards across Europe and the high costs of adapting to new systems.
• Consumer Preferences: European consumers prioritize convenience over security, but they also expect their data to be protected. The authentication process under PSD2 may be seen as cumbersome, affecting user adoption.
• Fragmentation and Regulatory Uncertainty: Despite the directive's intent to create a unified market, the lack of a strict pan-European framework and varying national implementations may lead to market fragmentation and operational complications.

Key Information

1. Payment Services Directive II (PSD2)

• Purpose: To promote innovation in payment services by opening up access to customer financial data through APIs.
• Historical Context: PSD2 was introduced in 2015 as a revision of PSD1, which aimed to liberalize the payments market and allow non-banks to provide payment services.
• Key Provisions:
  • API Access: Third-party providers must access payment data through APIs, not screen-scraping.
  • Fall-back Mechanism: Banks must provide a fall-back option if API access fails after five consecutive attempts.
  • Payment Account Definition: Payment accounts include current accounts, e-money accounts, flexible savings, and credit cards, but exclude fixed-term deposits, loans, and mortgages.

2. Stakeholder Analysis

• Banks:

  • Face challenges in updating legacy systems and may lose a portion of their payment revenue to fintechs.
  • Concerned about data security and the potential for unfair competition with fintechs and tech giants.
  • Some advocate for access to fintech customer data to maintain fair competition.

• Fintechs:

  • Seek standardized API frameworks to reduce development costs and ensure interoperability.
  • Concerned about the cost and complexity of integrating with multiple banks' APIs.
  • Fear that PSD2 may stifle innovation due to regulatory fragmentation.

• Consumers:

  • Prefer convenience over security but are worried about privacy.
  • 68% of Europeans use digital wallets, mobile payments, or credit cards for online transactions.
  • Many are frustrated by the authentication process under PSD2, which may reduce adoption of digital services.

• Regulators:

  • Struggle to create a unified regulatory framework across EU member states.
  • Attempt to balance innovation and consumer protection by introducing contingency measures and exemption criteria.
  • Lack of clarity on consent and data usage between PSD2 and GDPR remains a challenge.

3. Implementation Challenges

• Adoption Across Europe: Only 17 of 28 EU member states have fully transposed PSD2 into national law by January 2018. Some countries are still in the process of confirming drafts.
• National Fragmentation: Divergent interpretations of PSD2 lead to inconsistencies in how data is accessed and protected, potentially limiting cross-border payment services.
• API Standards: While initiatives like the Berlin Group and STET aim to develop interoperable API standards, they remain non-binding and informal.
• GDPR Overlap: The overlap between PSD2 and GDPR creates ambiguity in data usage and consent, with GDPR's stricter rules possibly undermining PSD2's goals.

4. Global Perspective

• UK's Open Banking Initiative: The UK has implemented a more ambitious version of open banking, requiring banks to use a common API standard. It allows price comparison websites and fintechs to access customer data.
• China and the US: China leads in digital payments with services like Alipay and WeChat, while the US relies on minimal regulation to drive innovation.

Policy Recommendations

• Develop common, standardized API frameworks to ensure interoperability and reduce costs for fintechs.
• Clarify the relationship between PSD2 and GDPR to resolve conflicts and ensure consumer privacy.
• Encourage banks to modernize their IT systems to support the new regulatory requirements.
• Address the concerns of consumers regarding data security and authentication processes.
• Promote collaboration between regulators, banks, and fintechs to ensure a smooth and secure transition to open banking.

Conclusion

PSD2 represents a significant step toward a more open and innovative financial services market in Europe. However, its success depends on resolving regulatory ambiguities, ensuring technical interoperability, and addressing the concerns of all stakeholders, particularly consumers and small businesses. The global context highlights the need for Europe to stay competitive in the digital payments landscape.