Summary

  • Qatar Central Bank says it manages and oversees national high-value and retail payment systems, while its technology sector is responsible for continuity and resilience of mission-critical platforms.
  • Its December 2025 disclosure reports 66.188 million payment-system transactions worth QAR 20.089 billion. That scale makes recovery evidence a public-interest asset, but it does not itself prove availability or tested failover.

Scale is visible; recovery performance is not

The December numbers give the continuity question a practical denominator. QCB reported 66.188 million payment-system transactions in the month. Fawran alone accounted for 3.187 million transactions worth QAR 5.092 billion, with 3.614 million registered accounts and 25% of the transaction mix shown in the infographic. Those are not outage statistics. They show how quickly a technical problem could become a participant, merchant or household problem.

QCB’s own institutional description makes the control surface unusually clear. Its Technology and Digital Transformation Sector manages payment systems, data governance, digital applications and financial technology. The IT Operations and Infrastructure Department is assigned continuous availability, security and resilience of mission-critical platforms. The Payment Systems Department develops, manages and oversees high-value and retail systems, including operational risk, business continuity and participant compliance.

Named rails make a generic resilience claim less useful. QCB describes Fawran as a 24-hour instant-payment system launched in 2024, supporting credit transfers, request to pay and confirmation of payee. It describes the upgraded QA-RTGS, also launched in 2024, as the primary interbank settlement system using ISO 20022, directly integrating local banks and connecting clearing systems and the central securities depository for final settlement.

These facts establish mandate, function and published scale. They do not reveal measured uptime, incident frequency, restoration time, recovery-point performance or exercise results for either system. Nor do they show whether the named rails share identity, network, power, vendor or recovery dependencies. RIPE membership confirms the institution’s registry relationship, but does not identify a production ASN, route, facility or payment topology.

The most useful public ledger would therefore remain deliberately bounded. For each material rail, it could report availability against a stated measurement window; the number and duration of material interruptions; time to restore critical service; whether settlement queues reconciled without loss or duplication; and the date and scope of the latest continuity exercise. Dependency categories could be disclosed without publishing exploitable network diagrams.

QCB defines financial stability as the ability to withstand shocks while basic functions continue effectively. It also names early-warning systems and stress tests among its tools. Applying the same evidence discipline to payment operations would connect institutional language to observable recovery outcomes.

Sources