Treat MFS Concentration as Critical Infrastructure: Interoperability, Redundancy, and a Resolution Plan for bKash and Nagad

Diagnosis

Mobile financial services (MFS) in Bangladesh have become concentrated around a small number of providers, principally bKash and Nagad. The curated assessment characterizes this as MFS market concentration carrying single-point-of-failure risk. That phrasing is the heart of the problem: when a large share of everyday digital payments, wages, remittance cash-out, merchant settlement, and government disbursements routes through one or two platforms, the failure of any single provider stops being a commercial inconvenience and becomes a national-scale disruption.

The risk is not hypothetical or distant. A concentrated MFS layer means a technical outage, a cyber incident, a liquidity squeeze, or a governance failure at one dominant operator can freeze payments for a very large population at once, with no easy fallback. Concentration also dampens the competitive pressure that normally drives down fees and forces resilience investment, so users bear both fragility and cost. Because the platforms have effectively become shared public payments infrastructure, the appropriate policy frame is critical-infrastructure protection, not ordinary market regulation. The lead responsible government body recorded for this issue is the ICT Division (ICTD), supported by the Bangladesh Computer Council, the Bangladesh Hi-Tech Park Authority, and the Ministry of Science and Technology.

The current_state indicator for this issue has not yet been collected (it is null), which is itself a finding: there is no maintained, decision-grade measure of how concentrated the MFS layer is or how resilient each provider is. You cannot manage a single-point-of-failure risk you do not measure.

Recommended actions

1. Stand up a continuous MFS concentration and resilience monitor.

• Owner: ICT Division (ICTD), executed through the Bangladesh Computer Council as the technical agency.
• Mechanism: a standing data collection and dashboard that tracks provider-level shares, transaction availability, and incident reports, replacing the current null indicator with a maintained series.
• Signal it is working: a published, regularly updated concentration-and-uptime indicator exists and is cited in regulatory decisions.

1. Mandate full interoperability so no single provider is a chokepoint.

• Owner: ICT Division (ICTD), coordinating with the financial-sector regulator that licenses MFS.
• Mechanism: a binding interoperability circular requiring account-to-account and merchant transfers across providers, so a user on one platform can transact with any other without re-onboarding.
• Signal it is working: cross-provider transfers settle reliably, and users can switch or multi-home without losing access to merchants or counterparties.

1. Set critical-infrastructure resilience standards for dominant MFS operators.

• Owner: ICT Division (ICTD), with the Bangladesh Computer Council writing the technical baseline.
• Mechanism: a designation of large MFS operators as critical digital infrastructure, attached to mandatory redundancy, geographic failover, incident-reporting timelines, and periodic continuity testing.
• Signal it is working: each designated operator passes a documented failover test, and major incidents are reported within the mandated window.

1. Require a resolution and continuity plan for each dominant provider.

• Owner: ICT Division (ICTD), with the licensing financial regulator.
• Mechanism: a recovery-and-resolution framework ensuring that if one provider fails, customer balances are protected and payments can be redirected, with the Bangladesh Hi-Tech Park Authority supporting any shared technical fallback capacity.
• Signal it is working: an approved, tested continuity plan exists for each major provider and is rehearsed on a fixed schedule.

1. Lower entry barriers to broaden the provider base.

• Owner: Ministry of Science and Technology with the ICT Division (ICTD).
• Mechanism: a programme to ease technical onboarding for new and smaller MFS entrants, reducing structural concentration over time rather than only managing the incumbents.
• Signal it is working: new entrants reach the interoperable network and gain share, reducing the concentration indicator.

Sequencing (first 12 months)

Start with the monitor (action 1): without the indicator, every later step is unaccountable. In parallel, draft and issue the interoperability circular (action 2), because it delivers the fastest resilience gain and unlocks multi-homing as a user-level fallback. Once interoperability is mandated and measured, layer on the critical-infrastructure standards and the resolution plans (actions 3 and 4), which depend on knowing who the systemically important providers are. Entry-barrier reduction (action 5) runs as the slower structural track underneath.

Risks and constraints

The binding constraint is institutional: payments are licensed by the financial-sector regulator, while the responsible body recorded here is the ICT Division, so any mandate requires cross-agency coordination that can stall. Incumbents have strong commercial incentives to resist interoperability that erodes their lock-in. Mandating redundancy and continuity imposes real compliance cost, and smaller entrants must not be crushed by standards calibrated to large incumbents. Fiscal capacity to fund a shared fallback or supervisory monitor is limited.

Bottom line

A concentrated MFS layer is a single-point-of-failure risk that should be governed as critical infrastructure, not as an ordinary market. The ICT Division should first build the missing measurement, then mandate interoperability and resilience standards, so that the failure of one provider can no longer freeze the country's everyday payments.