2015年-SWIFT环球同业银行金融电讯_Guidelines_for_the_next_generation_of_Real-Time_Retail_Payments_Systems_RT-RPS_8页_427kb

Summary of "Guidelines for the next generation of Real-Time Retail Payments Systems (RT-RPS)"

Core Content

This document outlines the guidelines for the development of the next generation of real-time retail payment systems (RT-RPS), focusing on the technical, operational, and strategic considerations necessary to meet the evolving needs of the payments industry. It emphasizes the importance of real-time payments in a digital age, where consumers expect instant and convenient transactions across multiple channels.

Main Trends Impacting Retail Payments

• Advent of mobile and Internet technology: Mobile and internet usage has surged, enabling users to access financial services anytime, anywhere.
• High customer expectations: Customers now demand fast, secure, and transparent payment experiences, similar to what they get with e-commerce and mobile services.
• Competition from new entrants: Digital payment providers are challenging traditional banks by offering better customer experiences and new business models.
• Increased regulation: Regulations on data protection, financial inclusion, and cost control are reshaping the payments landscape.
• Emergence of new technologies: Technologies like blockchain and distributed ledgers are expected to support future payment systems.
• Threat from cybercrime: The rise of real-time payments increases vulnerability to cyber threats, necessitating stronger security measures.

Key Challenges in Developing RT-RPS

• Meeting the expectations of all stakeholders (regulators, banks, end-users) with a system that is cost-effective, resilient, and fast.
• Ensuring 24/7/365 operation, low latency, and high transaction volumes.
• Managing interbank settlement risk effectively.
• Providing end-to-end security and certainty of execution.
• Enabling easy integration of overlay services like fraud detection, e-commerce, and mobile functions.
• Supporting rich data to improve reconciliation and accommodate non-Latin characters.
• Achieving cost efficiency through reusing existing infrastructure.
• Ensuring ubiquity and interoperability across different markets and systems.

Design Guidelines

• Provide the rails for real-time 24/7/365 service: Enable seamless, uninterrupted payment processing.
• Support all payment types: Including P2P, B2B, and bulked non-real-time payments.
• Ensure high resiliency and availability: With site redundancy, disaster recovery, and business continuity.
• Manage interbank settlement risk: Use either deferred net settlement or pre-funded/gross settlement models.
• Enhance user convenience and confidence: Allow payment via personal identifiers, ensure security, and provide immediate execution confirmation.
• Enable integration of overlay services: Through open and simple API frameworks.
• Use ISO 20022 standards: For long-term interoperability and rich data support.
• Be cost-efficient: Leverage lean and open architecture, and reuse existing technology.
• Cater for ubiquity: Ensure all participants can join the system, directly or indirectly.
• Leverage common industry standards: Promote interoperability and reduce integration complexity.

SWIFT's Modular Design Approach

SWIFT provides modular components that can be used in building RT-RPS systems. These include:

• Domestic Messaging Channel (DMC): A high-volume, low-latency messaging solution that operates 24/7/365 with no downtime.
• Payment Gateway (PAG): Orchestrate clearing and settlement messages, supporting integration with value-added services.
• Addressing database: Links personal identifiers (e.g., email, mobile number) to bank account numbers for efficient payment routing.
• ISO 20022 standard: Ensures long-term interoperability and supports rich data.
• Round the clock support: Ensures continuous operation and reliability for all participants.

Case Study – Australia’s New Payments Platform (NPP)

• Overview: Australia is developing a new RT-RPS, the NPP, which will enable real-time payments across multiple channels.
• SWIFT's role: SWIFT is providing infrastructure components, including DMC and PAG, to support the NPP.
• Architecture: The NPP uses a distributed clearing and centralised settlement model, managed by the Reserve Bank of Australia (RBA).
• Benefits:
  • Cost Efficiency: Reduces the need for expensive central infrastructure.
  • Reliability and Trust: Uses SWIFT's secure and resilient network.
  • Additional Resiliency: Allows for real-time posting before settlement.
  • Speed and Scalability: Supports high transaction volumes and low latency.

Conclusions

• Real-time retail payment systems share common features like instant clearing, real-time posting, and 24/7/365 operation.
• Despite these similarities, clearing and settlement models vary to meet local market needs.
• Interoperability is essential for cross-border operations and to avoid fragmentation.
• SWIFT plays a critical role in facilitating dialogue and providing modular, standardized, and secure solutions for RT-RPS development.
• The evolution of real-time retail payments is a key focus of SWIFT's 2020 strategy, with a commitment to supporting the industry in its transition to real-time capabilities.

SWIFT's Role in the Payments Ecosystem

• Standards expertise: SWIFT is a key contributor to ISO 20022 and other global standards.
• Market infrastructure experience: SWIFT has a proven track record in supporting large-scale, complex payment systems.
• Compliance with CPMI-IOSCO principles: SWIFT solutions help market infrastructures meet strict regulatory and operational requirements.
• Facilitating cross-industry dialogue: SWIFT supports the development of interoperable and sustainable payment systems globally.

Final Notes

The document highlights the importance of adopting a modular, standardized, and secure approach to developing RT-RPS. It underscores the value of reusing components from other markets to achieve cost efficiency, interoperability, and resilience. The Australian NPP case study demonstrates how such an approach can be effectively implemented to support a wide range of payment services and customer channels.