Qatar · QCB

High-value inflow oversight on a live RTGS overlay

Qatar’s fintech strategy and sovereign-wealth inflows need a supervisory picture that is not a month-old file. Nexus sits beside RTGS as the IMTO and high-value overlay.

The gap on this mandate

High-value and private-wealth transfers clear on RTGS and IMTO rails that the FIU reconstructs after the fact. Correspondent files arrive late. Supervisors see the licence, not the instruction, while the payment is still in flight.

What examiners would open

  • A live feed of IMTO and high-value legs with operator, corridor, amount, UETR, and hold state
  • Native ISO 20022 inspection (pacs.008 / pacs.009) without an MT translation dump
  • A hold path so APP-style or coercion patterns can be opened before settlement
  • Onboarding evidence for licensed IMTOs measured in days, not a six-month paper cycle

How Nexus maps to the mandate

Nexus is the supervisory overlay beside QCB RTGS — not a retail wallet and not a second switch. It maps FATF Recommendation 16 originator and beneficiary fields to the same screen as the hold state. When Arab Monetary Fund rails are in scope, pair this brief with BUNA clearing oversight.

What this does not replace

QCB RTGS, IMTO licensing, and Qatari AML reporting obligations. Nexus does not replace those rails or licences.

Data residency and how you buy

Production is designed on-premise or in a Qatari sovereign cloud under QCB control. Nexus SupTech Ltd remains the UK OEM; a GCC accredited integrator deploys it. See how to buy Nexus for commercial options, the on-premise roadmap, and platform screenshots for a committee pack.

Related

Related reading