PayShap and SADC-RTGS on native ISO 20022

The gap on this mandate

PayShap, SADC-RTGS, and IMTO operator files run on three clocks. NPS and FIU staff reconstruct last month while instant domestic and regional legs have already settled. FATF Recommendation 16 originator and beneficiary fields are not on the same screen as the hold state.

What examiners would open

• PayShap-originated and IMTO-originated payments in one live feed, with operator, corridor, UETR, and hold state
• SADC-RTGS multi-currency legs beside classic correspondent IMTO corridors
• Native ISO 20022 inspection (pacs.008 / pacs.009) without an MT translation dump
• APP-style abuse held before gross settlement
• Onboarding evidence for non-bank IMTOs in days rather than a six-month paper cycle

How Nexus maps to the mandate

Nexus does not replace PayShap or SADC-RTGS. It is the supervisory overlay: ISO 20022 telemetry and a settlement hold so examiners can open the instruction while it is still in flight. Pair with PAPSS corridor monitoring when continental clearing is in scope, and with Bank of Zambia when SADC neighbour corridors matter.

What this does not replace

PayShap, SAMOS / SADC-RTGS, or SARB licensing of banks and IMTOs. Nexus is the overlay those rails do not provide.

Data residency and how you buy

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