# CBK Open Banking & ISO 20022 Interbank Settlement: A 2026 Guide for Kenyan Banks and SACCOs
The Central Bank of Kenya (CBK) Open Banking Standard and the global transition to **ISO 20022 messaging formats** represent the most significant structural shift in East Africa’s financial ecosystem since the launch of mobile money. For Kenyan Deposit-Taking SACCOs (DT-SACCOs), microfinance banks, and tier-1 commercial lenders, migrating from legacy proprietary messaging formats to ISO 20022 XML/JSON specifications is no longer optional—it is mandatory for clearing, settlement, and API interoperability.
This comprehensive guide breaks down the technical architecture, ISO 20022 message schemas (`pacs.008`, `camt.053`, `camt.054`), FAPI OAuth 2.0 security controls, and PesaLink 2.0 integration requirements.
---
## 🏛️ The CBK Open Banking Mandate
The CBK Open Banking Standard establishes a unified API framework designed to enable secure, consented data sharing and payment initiation across licensed financial institutions and Payment Service Providers (PSPs).
### Core Architectural Pillars
1. **Financial-grade API Security (FAPI 1.0 / 2.0)**: Mandatory mutual TLS (mTLS) transport and PKCE-enforced OAuth 2.0 authorization flows.
2. **ISO 20022 Message Standardisation**: All credit transfers, direct debits, and account reporting must conform to UNIFI ISO 20022 XML schemas.
3. **Consent Management Lifecycle**: Explicit 90-day renewable member consent registries with real-time revocation webhooks.
4. **Real-Time Settlement Finality**: Sub-second interbank clearing via KEPSS (Kenya Electronic Payment and Settlement System) and PesaLink interbank gateways.
---
## 💳 Key ISO 20022 Message Schemas for Kenyan Financial Institutions
ISO 20022 replaces legacy MT103 and MT940 flat files with structured, XML-based financial messages.
### 1. Payment Clearing & Settlement (`pacs.008.001.10`)
The Financial Customer Credit Transfer message (`pacs.008`) is used to instruct the transfer of funds between ordering customer accounts and beneficiary accounts across banks and SACCOs.
```xml
KEPSS20260919001298
2026-09-19T09:30:00.000Z
1
CLRG
SACCO-KEPSS-2026-8812
c45f25f1-5a5b-4223-8e9c-c95e5f74ed75
2500000.00
Stima DT SACCO Member Account
KMRC Refinancing Liquidity Pool
```
### 2. Bank-to-Customer Statement (`camt.053.001.08`)
The end-of-day bank statement message (`camt.053`) provides itemized transaction accounting records, enabling automated AI ledger reconciliation between core banking systems and CBK reserve accounts.
---
## 🛡️ Implementation Checklist for SACCO CTOs
- [x] Deploy FAPI-compliant OAuth 2.0 API Gateways on Cloudflare Workers Edge.
- [x] Configure ISO 20022 XML-to-JSON translation layers in core banking connectors.
- [x] Implement real-time idempotency tracking using Worker KV namespaces.
- [x] Validate sub-second transaction finality against CBK KEPSS specifications.
For hands-on API integration testing, access the live [Open Banking Settlement Cockpit](https://ramongitau.uk/tools/open-banking) on [ramongitau.uk](https://ramongitau.uk).