[OR] [GCash] [E1] [C6] Analysing Key Characteristics

Chapter 6

Key Characteristics of GCash

Introduction

The purpose of this chapter is to identify the key organisational and operational characteristics of GCash that influence how its Business Continuity Management and Operational Resilience capabilities should be designed, governed and implemented.

GCash operates as a highly digital, customer-facing financial-services platform within a large and interconnected ecosystem.

Its characteristics—including extensive dependence on mobile technology, high transaction volumes, reliance on telecommunications and external financial institutions, broad merchant connectivity, third-party service dependencies, significant cybersecurity exposure and a large customer base—create a resilience profile that differs substantially from that of a conventional organisation.

GCash states that 94 million Filipinos have used the service, while its ecosystem includes approximately six million merchants and social sellers. Its mobile wallet operations are handled by G-Xchange, Inc., which is regulated by the Bangko Sentral ng Pilipinas.

This chapter enables the reader to understand how these characteristics translate into specific Operational Resilience considerations under BSP Circular No. 1203, Series of 2024 – Guidelines on Operational Resilience, as well as the broader organisational-resilience principles of ISO 22316.

BSP requires supervised financial institutions to identify Critical Operations based on their size, nature and complexity; consider the end-to-end activities required to deliver those operations; establish Tolerance for Disruption; map interconnections and interdependencies; identify Severe but Plausible Scenarios; manage operational vulnerabilities; and test resilience capabilities.

By the end of this chapter, the reader should be able to recognise the characteristics of GCash that materially affect its resilience requirements and understand how these characteristics should influence Critical Operation identification, dependency mapping, BCM, technology and cyber resilience, third-party risk management, scenario testing, customer protection and resilience investment.

Understanding Organisational Characteristics

Every organisation has characteristics that influence the type and level of resilience capability it requires.

These may include:

• products and services;
• customer profile;
• transaction volumes;
• geographic reach;
• operating model;
• technology dependence;
• third-party reliance;
• regulatory obligations;
• workforce structure;
• interconnections with other organisations;
• risk profile; and
• significance of disruption to customers and stakeholders.

Operational Resilience should therefore not be implemented using a generic framework without adapting it to the organisation.

For GCash, these characteristics are especially important because the organisation operates primarily through digital channels and participates directly in everyday financial activities involving individuals, merchants, businesses and other financial institutions.

BSP Circular No. 1203 recognises this principle by requiring the number and nature of Critical Operations identified by a supervised institution to be commensurate with its size, nature and complexity of operations. 

Characteristic 1 – Digital-First Operating Model

One of the most significant characteristics of GCash is its digital-first operating model.

Customers primarily access GCash services through smartphones and digital channels rather than physical branches.

GCash enables users to undertake activities such as:

• sending and receiving money;
• purchasing goods and services;
• paying bills;
• cashing in and cashing out;
• making merchant payments;
• transferring funds to bank accounts;
• accessing savings;
• accessing loans and credit;
• purchasing insurance; and
• accessing investment-related services.

The GCash wallet itself is a reloadable electronic money instrument regulated by the BSP.

From an Operational Resilience perspective, this digital-first model means that:

• The availability of technology is directly connected to the availability of service.

A technology disruption can therefore become a customer-service disruption almost immediately.

GCash should accordingly place particular resilience emphasis on:

• application availability;
• infrastructure resilience;
• database resilience;
• authentication services;
• transaction processing;
• APIs;
• connectivity;
• capacity management;
• monitoring;
• disaster recovery;
• cyber resilience; and
• rapid service restoration.

Characteristic 2 – Large Customer Population

GCash serves a very large customer population.

GCash currently states that 94 million Filipinos have used the platform.

This scale has important implications for Operational Resilience.

Even a relatively short service disruption may potentially affect a significant number of customers.

The effect of disruption should therefore not be evaluated only using conventional recovery-time measures.

GCash should also assess measures such as:

• number of customers affected;
• percentage of active customers affected;
• duration of service unavailability;
• value of transactions affected;
• volume of transactions delayed;
• number of failed transactions;
• customers unable to access funds;
• customer complaints; and
• impact on vulnerable customers.

This directly aligns with BSP's approach to Tolerance for Disruption.

BSP requires supervised institutions to establish a Tolerance for Disruption for each Critical Operation and allows both quantitative and qualitative metrics.

A time-based metric is required at a minimum, while other metrics may include the maximum number of customers affected and the volume or value of disrupted transactions. (Bangko Sentral ng Pilipinas)

For GCash, customer-scale metrics should therefore be an important component of resilience assessment.

Characteristic 3 – High Transaction Dependency

GCash supports frequent financial transactions throughout the day.

These may include:

• peer-to-peer transfers;
• merchant payments;
• bank transfers;
• wallet funding;
• bills payment;
• withdrawals;
• online purchases; and
• other payment activities.

Transactions are expected to be processed accurately, securely and quickly.

This creates three simultaneous resilience requirements:

Availability

Transactions must be available when customers require them.

Integrity

Transaction values and account balances must remain accurate.

Confidentiality

Customer and financial information must remain protected.

Operational disruption affecting any of these dimensions can create customer harm.

For example, a transaction-processing incident could potentially result in:

• delayed transactions;
• duplicate transactions;
• incomplete transactions;
• incorrect balances;
• reconciliation discrepancies;
• customer complaints; and
• increased operational workload.

Operational Resilience must therefore consider not only whether systems can recover, but whether financial integrity can be preserved throughout the disruption and recovery process.

Characteristic 4 – Large Merchant and Business Ecosystem

GCash is not used only by individual consumers.

Its ecosystem includes approximately six million merchants and social sellers, while the platform also provides solutions for enterprises, MSMEs and public-sector organisations. (GCash)

This characteristic increases the consequences of disruption.

A payment outage may potentially affect:

GCash

↓

Customers

↓

Merchants

↓

Businesses

↓

Suppliers

↓

Other Financial Institutions

The disruption can therefore propagate beyond the immediate customer.

From an Operational Resilience perspective, merchant-payment capabilities and related transaction flows may require particular attention when Critical Operations are identified.

GCash should understand:

• which merchant services are most critical;
• payment-processing dependencies;
• settlement dependencies;
• peak transaction periods;
• alternative payment arrangements;
• reconciliation requirements; and
• communication requirements during disruption.

Characteristic 5 – Extensive Interconnections with Financial Institutions

GCash operates within a broader financial ecosystem.

Digital-wallet operations may involve interaction with:

• banks;
• other electronic-money issuers;
• payment networks;
• fund-transfer arrangements;
• merchants;
• billers;
• financial-service partners; and
• clearing or settlement infrastructure.

This means that GCash may remain technically operational even if customers are still unable to complete certain transactions due to an external participant's failure.

Operational Resilience therefore requires an end-to-end perspective.

A simplified interconnection may be represented as:

Customer

↓

GCash

↓

Payment / Transfer Interface

↓

External Financial Institution

↓

Settlement / Recipient

↓

Confirmation

BSP explicitly requires the first line to identify all resources needed for end-to-end delivery of Critical Operations, including resources provided by third parties and, where relevant, subcontracted providers used by those third parties. 

For GCash, dependency mapping should therefore extend outside the organisation itself.

Characteristic 6 – Significant Third-Party Dependency

A modern digital financial platform depends on numerous external service providers.

Potential GCash dependencies may include:

• telecommunications providers;
• cloud providers;
• technology suppliers;
• payment processors;
• identity-verification services;
• cybersecurity providers;
• customer-notification services;
• financial institutions;
• software vendors; and
• other specialised providers.

GCash also states that certain services available through the application involve Fuse or external partners, with GCash acting as a payment or fund channel for some services. (GCash)

This creates third-party concentration and dependency risk.

Operational Resilience should therefore determine:

• which providers support Critical Operations;
• whether substitute providers are available;
• how quickly provider failure would affect customers;
• whether subcontractors create additional dependencies;
• whether contractual resilience requirements are sufficient;
• whether exit arrangements exist;
• whether providers participate in scenario tests; and
• whether recovery assumptions have been validated.

Third-party resilience should therefore be assessed from the perspective of the supported Critical Operation, rather than solely through supplier performance measures.

Characteristic 7 – Strong Dependence on Telecommunications

GCash relies substantially upon telecommunications and network connectivity because customers interact with the platform through mobile devices.

Potential dependencies include:

• mobile internet;
• broadband networks;
• SMS;
• OTP delivery;
• application connectivity;
• merchant connectivity;
• customer-support channels; and
• connectivity with external financial institutions.

A telecommunications disruption may therefore affect multiple services simultaneously.

For example:

Telecommunications Failure

↓

Customers cannot connect

↓

Authentication impaired

↓

Payments interrupted

↓

Merchant transactions affected

↓

Customer-service demand increases

↓

Operational incident escalates

This demonstrates why external infrastructure must be included in dependency mapping and scenario testing.

Characteristic 8 – High Cybersecurity Exposure

A large digital financial platform is an attractive target for cybercriminals.

Potential threats include:

• phishing;
• credential theft;
• account takeover;
• ransomware;
• malware;
• distributed denial-of-service attacks;
• API attacks;
• fraudulent transactions;
• social engineering;
• insider threats;
• data compromise; and
• attacks against third-party providers.

GCash itself maintains customer-facing security and fraud-management guidance covering unauthorised transactions, account protection, biometrics, device security and other safeguards.

Operational Resilience requires cyber risk to be considered beyond prevention.

The organisation must ask:

If preventive controls fail and a severe cyber incident occurs, can Critical Operations continue within their Tolerance for Disruption?

Cybersecurity, BCM, technology recovery and crisis management should therefore be integrated rather than tested separately.

Characteristic 9 – Data-Intensive Operations

Digital financial services depend heavily upon reliable and accurate data.

Relevant information may include:

• customer identity information;
• account information;
• wallet balances;
• transaction history;
• authentication information;
• merchant records;
• reconciliation information;
• regulatory records; and
• operational monitoring information.

The resilience requirement extends beyond simply restoring stored data.

GCash needs to ensure:

• data remains complete;
• data remains accurate;
• unauthorised changes are detected;
• recovery points are appropriate;
• transactions can be reconciled;
• customer balances remain accurate;
• duplicated transactions are identified; and
• data can be restored after disruption.

Consequently, data integrity should be considered a major Operational Resilience outcome.

Characteristic 10 – Real-Time Customer Expectations

Customers generally expect digital-wallet and payment services to be available continuously.

Unlike some conventional business processes that may tolerate extended manual processing, customers may notice digital service disruptions within minutes.

This characteristic creates particularly demanding expectations for resilience.

GCash may therefore require:

• real-time monitoring;
• automated incident detection;
• rapid escalation;
• high availability;
• resilient architecture;
• tested failover;
• alternate customer communication;
• rapid decision-making; and
• predefined incident-response arrangements.

The practical consequence is that the Tolerance for Disruption may be significantly shorter than conventional business recovery objectives for some Critical Operations.

Characteristic 11 – Limited Manual Alternatives

Digital financial services may have fewer practical manual workarounds than traditional business processes.

For example, employees may be unable to manually process millions of digital wallet transactions if the transaction engine becomes unavailable.

This distinguishes Operational Resilience from conventional continuity planning.

The organisation may need technological alternatives such as:

• redundant platforms;
• alternate processing;
• automated failover;
• alternate connectivity;
• traffic rerouting;
• capacity reserves;
• geographically separated recovery infrastructure; and
• alternative providers.

For GCash, resilience investment may therefore place greater emphasis on technology architecture and engineering resilience than manual continuity procedures.

Characteristic 12 – High Dependency on Identity and Authentication

Digital financial transactions require confidence that the person initiating the transaction is authorised.

GCash requires verification to access the full range of its services and employs various security mechanisms to protect customer identities and account access. 

Authentication resilience therefore affects both:

Security

and

Availability

Overly weak authentication creates fraud exposure.

Overly unavailable authentication prevents legitimate customers from accessing their services.

GCash must therefore balance security controls with resilience.

Potential dependencies include:

• identity verification;
• OTP;
• device authentication;
• biometrics;
• account credentials; and
• fraud-detection controls.

The failure of authentication services should consequently be included in Operational Resilience scenarios.

Characteristic 13 – Complex Product and Service Ecosystem

GCash has evolved beyond a basic stored-value wallet into a broader financial-services ecosystem.

Its current offering includes services related to:

• payments;
• transfers;
• savings;
• credit;
• loans;
• insurance;
• investments;
• merchant services;
• bills; and
• other partner-provided services.

This creates complexity because different services may depend upon different:

• legal entities;
• systems;
• partners;
• regulatory frameworks;
• processes;
• data; and
• recovery arrangements.

Operational Resilience therefore requires a clear distinction between:

Products

and

Critical Operations

Not every product is necessarily a Critical Operation.

Instead, GCash should identify the underlying operations that, if disrupted, could have material consequences for customers, the organisation, or the financial system.

Characteristic 14 – Significant Regulatory Oversight

G-Xchange, Inc. states that it is duly registered, licensed and regulated by the Bangko Sentral ng Pilipinas.

Consequently, resilience capabilities must operate within a broader regulatory environment covering areas such as:

• electronic money;
• operational resilience;
• operational risk;
• ICT risk;
• cybersecurity;
• business continuity;
• third-party arrangements;
• consumer protection;
• anti-money laundering;
• data protection; and
• incident reporting.

BSP Circular No. 1203 therefore creates important additional expectations.

These include:

Critical Operations

↓

Tolerance for Disruption

↓

Severe but Plausible Scenarios

↓

Dependency Mapping

↓

Risk Management

↓

Scenario Testing

↓

Response and Recovery

↓

Continuous Improvement

BSP states that financial institutions should integrate Operational Resilience with existing governance and risk-management structures.

Characteristic 15 – Customer Harm as a Key Resilience Consideration

A central characteristic of GCash's resilience profile is the potential for operational disruptions to directly affect customers.

Customers may experience harm where disruption results in:

• inability to access money;
• inability to make payments;
• failed transfers;
• incorrect balances;
• duplicate transactions;
• delayed payments;
• inability to purchase essential goods;
• inability to pay bills; or
• uncertainty regarding transaction completion.

This is why BSP's Critical Operation assessment considers not only institutional viability but also potential impact on customers and the institution's role in the financial system. (Bangko Sentral ng Pilipinas)

GCash should therefore design resilience around customer outcomes, not simply system uptime.

Characteristic 16 – Potential for Cascading Disruption

Because GCash is highly interconnected, an incident may propagate from one dependency into several operations.

For example:

Cloud Provider Failure

↓

GCash Application Degradation

↓

Transaction Processing Delays

↓

Payments and Transfers Affected

↓

Merchant Transactions Delayed

↓

Customer Complaints Increase

↓

Customer Support Overloaded

↓

Reconciliation Backlog Develops

↓

Recovery Capacity Becomes Constrained

This demonstrates the importance of considering cascading disruption rather than isolated failure.

Scenario testing should therefore examine simultaneous or sequential effects across several resources and operational processes.

Characteristic 17 – Significant Peak-Demand Variability

Digital financial services may experience periods of substantially increased transaction demand.

Examples could include:

• salary periods;
• holidays;
• major sales events;
• bill-payment deadlines;
• emergencies; and
• large national events.

A resilience capability that performs adequately during normal demand may fail when disruption coincides with peak activity.

Capacity resilience should therefore form part of scenario design.

GCash should consider whether:

• infrastructure capacity remains sufficient;
• failover infrastructure has equivalent capacity;
• alternate providers can manage demand;
• queues remain manageable;
• customer support can respond; and
• recovery procedures remain effective.

Characteristic 18 – Need for Rapid Incident Communication

The customer-facing nature of GCash means that communication forms part of resilience.

During a major service disruption, customers may require timely information regarding:

• affected services;
• transaction status;
• expected recovery;
• safe actions;
• alternative arrangements; and
• scam warnings.

GCash maintains public service-status and advisory mechanisms to communicate operating conditions. 

Operational Resilience should therefore integrate:

• incident management;
• customer communications;
• corporate communications;
• social-media monitoring;
• contact-centre operations;
• regulatory communication; and
• partner communication.

Poor communication can increase the consequences of an otherwise manageable operational incident.

Key Characteristics and Operational Resilience Implications

The following table summarises the principal characteristics of GCash and their implications for Operational Resilience.

BSP Compliance Implications

These organisational characteristics help determine how GCash should implement BSP Circular No. 1203.

Examples include:

BSP requires the first line to identify the complete set of resources needed to deliver Critical Operations, the second line to review end-to-end activities and their exposure to disruption, and the third line to independently assess the design and effectiveness of the resilience approach.

BCM Implications

The characteristics identified in this chapter should also influence GCash's Business Continuity Management programme.

The BIA should recognise that:

• customer impact may develop rapidly;
• technology recovery is critical;
• transaction integrity must be maintained;
• external dependencies may determine recovery;
• manual workarounds may be limited;
• peak demand may affect recovery capacity;
• critical third parties may need to participate in exercises; and
• recovery objectives should align with Operational Resilience tolerances.

Business Continuity Strategies should therefore consider:

• Prevention

• Redundancy

• Alternate Processing

• Technology Recovery

• Third-Party Contingency

• Crisis Management

• Customer Communication

• Reconciliation

Traditional workplace recovery alone would be insufficient for many GCash Critical Operations.

Relationship with ISO 22316

The characteristics identified in this chapter also support the organisational-resilience principles of ISO 22316.

For GCash, organisational resilience requires awareness of:

• its operating environment;
• important stakeholders;
• interdependencies;
• rapidly changing technology;
• emerging threats;
• organisational capabilities;
• external networks;
• leadership and governance;
• adaptive capacity; and
• organisational learning.

ISO 22316 encourages organisations to develop the capacity to anticipate and respond to change rather than simply recover from known disruption.

Applied to GCash, this means resilience should evolve continuously as:

• customer numbers change;
• transaction volumes grow;
• technology evolves;
• new products are introduced;
• partners change;
• cyber threats evolve; and
• regulatory expectations develop.

Characteristics Should Drive Resilience Priorities

The primary purpose of understanding organisational characteristics is to ensure that resilience investment is proportionate to the potential consequences of disruption.

For GCash, the combination of:

• Large Customer Base

• High Transaction Volumes

• Digital Dependency

• Cyber Exposure

• Financial-System Interconnections

• Third-Party Dependencies

creates a resilience profile in which relatively small technical or operational failures can become large customer-facing incidents.

Resilience investment should therefore prioritise capabilities that protect the continued delivery of Critical Operations rather than spreading investment evenly across all processes.

This is consistent with BSP's outcome-based approach to Operational Resilience.

The key characteristics of GCash demonstrate why Operational Resilience must be treated as an enterprise-wide business priority rather than solely as a Business Continuity or technology-recovery activity.

GCash combines a digital-first operating model, a very large customer base, millions of merchant connections, high transaction dependence, extensive financial-system interconnections, significant reliance on third parties and telecommunications, complex financial-service partnerships, and substantial cyber and data risks.

These characteristics increase both the likelihood that operational disruption can propagate rapidly and the potential scale of consequences for customers and stakeholders.

GCash therefore needs to view resilience from the perspective of end-to-end delivery of Critical Operations, rather than from the perspective of individual departments or technology components.

BSP Circular No. 1203 reflects this approach by requiring supervised financial institutions to identify Critical Operations according to their size, nature and complexity; identify the resources supporting those operations; establish Tolerance for Disruption; map interconnections and interdependencies; identify Severe but Plausible Scenarios; manage operational vulnerabilities; and test whether Critical Operations can continue through disruption.

For GCash, understanding its organisational characteristics therefore provides the basis for determining what requires the greatest resilience, where critical dependencies exist, how disruption may cause customer harm, and where resilience investment should be prioritised.

When these characteristics are integrated with BCM, ICT and cyber resilience, third-party risk management, and the organisational resilience principles of ISO 22316, GCash can progressively strengthen its capacity to anticipate, withstand, respond to, recover from, and adapt to severe operational disruption.

Understanding Your Organisation
C1	C2	C3	C4	C5
C6	C7	C8	C9	eBook Cover

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-300 Operational Resilience Implementer course and the OR-5000 Operational Resilience Expert Implementer course.

	If you have any questions, click to contact us.