Kenya · CBK

Bank and telco switches in one IMTO operating picture

Kenya’s payments strategy and M-Pesa cross-border termination need an omni-channel overlay. Nexus sits on bank and telco APIs so CBK staff see the payment, not a reconstructed wallet file.

The gap on this mandate

Telco-originated remittances and bank IMTO licences are supervised on different clocks. M-Pesa cross-border termination and classic IMTO files do not share a screen. APP-style abuse on wallets can clear before the FIU opens the case.

What examiners would open

  • Bank-switch and telco-wallet legs in one IMTO operating picture
  • Cross-border M-Pesa termination with UETR, amount, and hold state
  • A hold path before settlement for wallet-originated APP-style abuse
  • PAPSS-adjacent corridors when continental clearing is in scope

How Nexus maps to the mandate

Nexus is the omni-channel overlay on bank and telco APIs so CBK staff see the payment, not a reconstructed wallet file. It does not replace M-Pesa or the National Payments Strategy rails. Pair with Tanzania TIPS / EAC and PAPSS corridor monitoring.

What this does not replace

M-Pesa, CBK licensing, or Kenya’s national payments switch.

Data residency and how you buy

On-premise or Kenyan designated cloud under CBK control. UK OEM; East Africa integrator deploys. See how to buy Nexus for commercial options, the on-premise roadmap, and platform screenshots for a committee pack.

Related

Related reading