Israel · BOI

Zahav modernisation with native ISO 20022 ingestion

Zahav RTGS and open-finance APIs need a supervisory overlay that speaks ISO 20022 natively. Nexus is that overlay — behavioural fraud included — UK OEM, deployed in-country.

The gap on this mandate

Zahav RTGS upgrades and open-finance APIs still leave IMTO and cross-border fintech legs on delayed files. Supervisors see the API mandate, not the live remittance instruction.

What examiners would open

  • Native ISO 20022 ingestion for IMTO legs beside Zahav traffic
  • Behavioural fraud signals on the payment, not on a reconstructed file
  • A hold path before settlement when APP-style abuse is in the mandate
  • Open-finance adjacency without dropping wire-transfer transparency fields

How Nexus maps to the mandate

Nexus is the supervisory overlay that speaks ISO 20022 natively. It does not replace Zahav. Pair with APP fraud time-lock for the hold, and with ISO 20022 IMTO telemetry for message-level inspection. UK OFSI screening still runs on every sovereign engagement.

What this does not replace

Zahav, Bank of Israel licensing, or open-finance API mandates.

Data residency and how you buy

On-premise under BOI control. UK OEM; deployed in-country. See how to buy Nexus for commercial options, the on-premise roadmap, and platform screenshots for a committee pack.

Related

Related reading