Kenya licenses 29 additional digital credit providers

Sourced news briefing

Central Bank of Kenya press release, 30 September 2026 announced the development on 30 September 2026. The Central Bank of Kenya said it licensed 29 additional digital credit providers under section 59(2) of the Central Bank of Kenya Act. The announcement said the total number of licensed providers reached 281. It reported more than 900 applications received since March 2022 and said other applications remained under review. The central bank described its review focus as including business models, consumer protection, and the fitness and propriety of proposed shareholders, directors and management. It reported that licensed providers had granted 9,596,509 loans valued at KSh165.1 billion as of August 2026. The release also referred the public to a published directory and invited reports concerning unregulated providers.

This opening briefing is limited to the published announcement. The release concerns licensing and supervision of digital lenders; it is not an approval of every product, marketing statement, collection practice or payment arrangement used by a listed company. The sections that follow are independent FixPays analysis for merchants and do not attribute conclusions to the Central Bank of Kenya.

Independent analysis: counterparty verification

A larger official register makes name matching possible, but similar trading names, group companies and outsourced collection agents can still create ambiguity. For a merchant, the immediate question is not whether the announcement sounds ambitious, but where it changes an actual payment, settlement, compliance or customer-service workflow. Record the exact licensed legal entity rather than relying on a brand name. Compare the entity named in customer terms, checkout descriptors and settlement instructions with the official directory. Escalate mismatches before processing begins.

Evidence can include the dated directory entry, incorporation records, contracting entity and an ownership diagram. A useful review should name the responsible team, the system of record, the exception path and the date on which the control was last tested. That converts a broad industry development into work that can be compared with existing provider contracts and operating procedures.

Independent analysis: payment-purpose controls

Digital-credit flows can combine loan disbursement, repayment, fees, collections and refunds, yet those purposes should not be collapsed into one unexplained transaction stream. For a merchant, the immediate question is not whether the announcement sounds ambitious, but where it changes an actual payment, settlement, compliance or customer-service workflow. Map each incoming and outgoing payment type to a ledger event. Separate customer repayment from unrelated marketplace or wallet activity. Define how reversals, overpayments and disputed collections are handled.

A redacted lifecycle example should connect consent, loan account, payment reference, customer receipt and reconciliation result. A useful review should name the responsible team, the system of record, the exception path and the date on which the control was last tested. That converts a broad industry development into work that can be compared with existing provider contracts and operating procedures.

Independent analysis: consumer treatment and disputes

Licensing raises the importance of showing how billing, collection and data-use practices operate after onboarding. For a merchant, the immediate question is not whether the announcement sounds ambitious, but where it changes an actual payment, settlement, compliance or customer-service workflow. Make amounts and due dates visible before payment. Keep collection communications aligned with approved policies. Route vulnerability, fraud and identity complaints to trained reviewers.

Merchants should retain consent records, notices, complaint outcomes and evidence supporting any challenged debit. A useful review should name the responsible team, the system of record, the exception path and the date on which the control was last tested. That converts a broad industry development into work that can be compared with existing provider contracts and operating procedures.

Independent analysis: merchant implementation checklist

Verify the legal entity against the central bank directory on a scheduled basis. Merchants should connect this point to the loan ledger, retain evidence in a controlled compliance register, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Inventory every domain, application and payment descriptor used to collect repayments. Merchants should connect this point to the acquiring agreement, retain evidence in a reconciliation archive, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Test whether customer support can trace a payment without asking for unnecessary personal data. Merchants should connect this point to customer-facing terms, retain evidence in a case-management record, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Reconcile processor settlements to individual loan-ledger events. Merchants should connect this point to the settlement account, retain evidence in a dated vendor file, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Review vendors that perform identity checks, communications or collections. Merchants should connect this point to the loan ledger, retain evidence in a controlled compliance register, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Define how a licence, ownership or product change reaches the payments team. Merchants should connect this point to the acquiring agreement, retain evidence in a reconciliation archive, and define who decides whether an exception can proceed. The same record should show what was expected, what occurred, how any difference was resolved and whether a provider or customer communication was required.

Before changing production, the merchant should run a controlled sample through the loan ledger, compare the result with the acquiring agreement, and archive the outcome in a controlled compliance register. Failed tests should remain visible until an accountable owner records the cause, corrective action and decision to retest or stop. This protects customers from a launch based only on a successful demonstration.

Commercial review should cover more than the advertised feature. The merchant should compare contractual scope, service levels, settlement terms, data responsibilities, incident duties and exit arrangements with the operating assumptions documented in a reconciliation archive. Any unresolved dependency should be recorded before volume moves, because an announcement cannot amend the merchant’s existing agreement by implication.

After launch, performance should be reviewed by corridor, method, product or customer journey as relevant. Approval rates alone are insufficient: finance and operations should monitor unmatched items, reversals, refunds, complaints, support time and settlement differences. Material deterioration should trigger investigation through a case-management record and a decision on whether the affected flow should continue.

Keep all relevant operational merchant payment compliance control testing exception resolution approval reconciliation settlement records complete and current.