Expat corridor visibility the KNAP era actually needs

The gap on this mandate

Kuwait’s worker-remittance outflows move on KNAP-era rails faster than operator returns. Capital flight is visible in the aggregate, not in the message. Examiners rebuild last month while corridors have already settled.

What examiners would open

• Expat corridor traffic as ISO 20022 envelopes, not a delayed spreadsheet
• Capital-flight signals (unusual corridors, amounts, and timing) while the payment can still be held
• Operator, beneficiary, and UETR on one FIU review screen
• APP-style abuse held before gross settlement when that is in the mandate

How Nexus maps to the mandate

Nexus puts the ISO 20022 data envelope and a capital-flight tracker in front of CBK staff while the payment is still held. It does not replace KNAP. Pair with APP fraud time-lock when push-payment abuse is in scope, and with SAMA payments supervision for GCC neighbour localisation rules.

What this does not replace

KNAP, CBK licensing of exchange houses and IMTOs, or Kuwait’s existing AML filings.

Data residency and how you buy

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