Oman · CBO

RTGS modernisation with AFAQ and remittance in one picture

Oman’s RTGS upgrade and GCC-AFAQ participation need IMTO telemetry that is not a separate spreadsheet. Nexus is the overlay: dashboard, ISO 20022, and settlement locks.

The gap on this mandate

RTGS modernisation, GCC-AFAQ participation, and expat remittance are supervised on different clocks. Capital-flight patterns clear before CBO can hold them. IMTO files arrive after the corridor has moved.

What examiners would open

  • RTGS, AFAQ, and IMTO legs in one operating picture
  • Settlement locks so a payment can be opened before gross settlement
  • ISO 20022 telemetry without MT translation loss
  • Expat corridor amounts and counterparties while the instruction is still in flight

How Nexus maps to the mandate

Nexus is the overlay: dashboard, ISO 20022, and settlement locks. It does not replace CBO RTGS or AFAQ. Pair with BUNA when regional instant rails are in scope, and with APP fraud time-lock for the hold path.

What this does not replace

CBO RTGS, AFAQ, or Omani IMTO licensing.

Data residency and how you buy

On-premise or in-sultanate cloud under CBO control. UK OEM; GCC integrator deploys. See how to buy Nexus for commercial options, the on-premise roadmap, and platform screenshots for a committee pack.

Related

Related reading