[OR] [MB] [E4] [CBS] [4] [MD] Map Dependency

Map Dependency

CBS-4: Payment and Settlement Systems

Introduction

In today’s increasingly interconnected financial ecosystem, Payment and Settlement Systems serve as the backbone of a bank’s operational integrity and customer trust.

For Maybank, one of Southeast Asia’s leading financial institutions,  CBS-4: Payment and Settlement Systems plays a pivotal role in ensuring the secure, timely, and accurate movement of funds across a diverse array of channels, including retail, corporate, domestic, and cross-border environments.

This chapter provides a comprehensive dependency mapping analysis of CBS-4, identifying the critical components required to support its end-to-end functionality.

The mapping focuses on four key dependency types—People, Process, Technology, and Third Party—highlighting how each contributes to the resilience, compliance, and service continuity of Maybank’s payment systems.

It also outlines how these dependencies interact with various sub-processes such as Real-Time Gross Settlement (RENTAS), e-Wallet integration, JomPAY, ATM settlement, fraud monitoring, and reconciliation.

This structured view serves not only as an operational reference but also as a vital resource for business continuity planning, regulatory compliance (such as BNM’s RMiT), and service resilience assessments.

Purpose of "Dependency Detail (What/Who is Involved)"

The “Dependency Detail” column identifies and describes the specific internal or external components that are crucial to each process within CBS-4. This includes:

• People: Functional roles or teams responsible for oversight, execution, or decision-making (e.g., Treasury Operations, Fraud Analysts).
• Processes: Key activities or workflows that form part of the payment and settlement lifecycle (e.g., Bulk File Processing, Dispute Intake).
• Technology: Core systems, interfaces, or digital tools used to execute, monitor, or support transactions (e.g., Core Banking System, SWIFT Gateway).
• Third Parties: External service providers, regulatory bodies, and partner institutions that play an operational or regulatory role (e.g., Bank Negara Malaysia, SWIFT, PayNet).

By detailing “what” is being relied upon or “who” is involved, this column helps stakeholders understand the precise nature of each dependency, which is critical for assessing potential vulnerabilities, resource allocation, and prioritisation in resilience planning.

Purpose of "Connectivity (Interaction with CBS or Other Components)"

The “Connectivity” column explains how each dependency interacts with CBS-2 or other components within Maybank’s operational ecosystem.

It articulates the operational relationship and integration points, such as:

• How a system supports a process or links to another system (e.g., middleware connecting mobile apps to the core banking engine).
• How people or teams coordinate across departments or with third parties.
• How external platforms are integrated to facilitate transaction flow, compliance, or settlement.

This information is crucial because understanding the interdependencies and data or operational flow helps to:

• Map single points of failure or cascading impacts in case of disruptions.
• Design more effective contingency plans and recovery strategies.
• Ensure alignment between internal capabilities and external obligations.
• Strengthen real-time monitoring and reduce blind spots in operational risk.

Together, the “Dependency Detail” and “Connectivity” columns form the foundation of a meaningful dependency map.

While “Dependency Detail” clarifies the parties and processes involved in delivering each sub-process, “Connectivity” reveals the operational dynamics and systemic links that underpin Maybank’s payment and settlement ecosystem.

This combination enables a deep understanding of the service architecture, facilitating targeted risk mitigation, business continuity planning, and operational resilience enhancement for CBS-4.

Summing Up ...

The dependency mapping exercise for CBS-4: Payment and Settlement Systems reveals the complexity and critical interdependence of people, processes, technology platforms, and external partners in delivering seamless payment services for Maybank’s customers.

Each element, from internal operational teams and real-time processing engines to third-party platforms such as RENTAS, SWIFT, and PayNet, is essential to maintaining trust, ensuring compliance, and sustaining operational uptime.

As digital transformation accelerates and customer expectations evolve, a clear understanding of these dependencies becomes essential.

It enables proactive risk management, enhances service design, and supports regulatory adherence, particularly in areas such as operational resilience, cyber risk mitigation, and financial system stability.

Moving forward, maintaining an up-to-date dependency map will be crucial to anticipating disruptions, designing recovery strategies, and strengthening the bank’s overall service resilience framework.

 

Operational Resilience in Action: Case Studies and Best Practices for MayBank
eBook 4: Starting Your OR Implementation
CBS-4 Payment and Settlement Systems
CBS-4 DP	CBS-4 MD	CBS-4 MPR	CBS-4 ITo	CBS-4 SuPS	CBS-4 ST

---

Gain Competency: For organisations looking to accelerate their journey, BCM Institute’s training and certification programs, including the OR-5000 Operational Resilience Expert Implementer course, provide in-depth insights and practical toolkits for effectively embedding this model.

 

More Information About OR-5000 [OR-5] or OR-300 [OR-3]

To learn more about the course and schedule, click the buttons below for the [OR-3] OR-300 Operational Resilience Implementer course and the [OR-5] OR-5000 Operational Resilience Expert Implementer course.

	If you have any questions, click to contact us.