A founder building a checkout product, a wallet and a merchant payout platform may describe all three as payment businesses. Their regulatory questions can be very different. Before choosing a “PSP licence type” in Kenya, establish what the business actually does with payment instructions, customer balances and settlement.
The practical objective is a clear match between the product, the legal entity providing it and the services that the Central Bank of Kenya (CBK) authorises. Choosing a familiar industry label is only the beginning.
What does a PSP licence authorise?
Kenya’s National Payment System Act uses authorisation for payment service providers. Section 12 requires authorisation to conduct PSP business in Kenya; section 13 allows CBK to attach conditions. The statutory definition reaches beyond custody of funds to certain payment processing and data activities. A business therefore needs a functional assessment even where it describes itself as a technology company. National Payment System Act, sections 2, 12 and 13.
For founders, this means asking two questions together: which regulatory route fits the proposed activity, and what exact service scope will the approval cover?
The principal routes to distinguish
| Route or legal concept | What it concerns |
|---|---|
| Electronic retail payment service provider | Electronic retail transfers. |
| E-money issuer | Issuing electronically stored monetary value accepted by others. |
| Small e-money issuer | A registration route with specific eligibility restrictions; it is not a general startup exemption. |
| Designated payment instrument | Designation of an instrument, distinct from ordinary PSP authorisation. |
| Designated payment system | Designation of a system, also distinct from authorisation of a provider. |
These distinctions appear in the Regulations, including their application form. National Payment System Regulations, regulations 2, 46–53 and First Schedule.
The table is a starting map. It does not mean every applicant must obtain five approvals or that every product neatly occupies one row. A combined product needs a combined analysis.
Where do gateways, aggregators and mobile money fit?
Terms such as payment gateway, merchant aggregator, processor and wallet describe commercial functionality. Do not assume that each corresponds to a separate statutory licence bearing that name.
CBK’s directory identifies institutions alongside their approved services. Its August 2026 edition distinguishes, among other activities, issuing mobile money from processing or facilitating payments and providing merchant payment platforms. The wording of the approved services matters when assessing a potential partner. CBK directory of authorised PSPs, 10 August 2026.
Suppose a founder plans to aggregate several payment methods through one merchant dashboard. The analysis should address who contracts with merchants, who receives payment instructions, whose account receives collections and who owes settlement. Adding a stored balance or customer-to-customer transfers changes the questions. The interface may look almost identical while the underlying responsibilities change substantially.
For a wallet, distinguish a screen that displays balances held by another provider from a product through which the business itself issues value. For a gateway, distinguish the software connection from any additional role in routing transactions, receiving collections or controlling settlement. These are examples of issues to investigate, not automatic classifications.
Start with a funds-and-responsibilities map
Before commissioning the application pack, write a short product description and map one normal transaction, one failed transaction and one refund. For each, identify:
- The customer, merchant and entity entering each contract.
- Where money sits at each stage and who can move it.
- Which business sends or processes the payment instruction.
- Whether a balance remains available for later use.
- Which party bears a settlement shortfall or disputed payment.
- What changes when a transaction crosses a border.
Add the product’s intended customers, currencies, countries and distribution channels. A regulator or banking partner should be able to follow the explanation without needing to infer responsibilities from a software architecture diagram.
CBK’s authorisation checklist expressly starts with classification and preliminary engagement. It also calls for a business model, ownership and governance information, capital evidence and operating arrangements. CBK PSP authorisation checklist.
A useful internal test is to ask whether legal, finance and engineering would draw the same transaction. Any material disagreement should be resolved before the application is submitted.
Capital is one part of the route decision
The published Regulations assign different capital amounts to different categories. Confirm the applicable requirement and any later CBK directions for the actual model before budgeting. National Payment System Regulations, regulation 11 and First Schedule.
Prepare separate budget lines for regulatory capital, application costs, implementation and operating runway. Include the people and systems needed to run the proposed service, together with professional support and partner onboarding costs. This gives investors a more useful picture than treating the licensing fee as the cost of market entry.
A narrower initial product may be easier to explain and implement. That is a commercial sequencing decision to evaluate; it should not be presented as a way to avoid obligations that the actual activity triggers.
What about operating through a licensed partner?
Assess the precise arrangement before relying on a partner’s status. Obtain evidence of its approved scope, then compare that scope with the services contemplated by the proposed agreement. Record who owns the customer relationship, handles complaints, performs onboarding, controls funds and makes regulatory reports.
A partner listed in the directory is a starting point for due diligence. It does not, by itself, answer whether your own entity’s activities need authorisation. Your contracts, customer disclosures and operational access should tell the same story.
For the wider regulatory picture, read Fintech Regulations in Kenya: A Practical Guide. For application preparation, see How to Apply for a PSP Licence in Kenya.
Frequently asked questions
Is there one universal fintech licence in Kenya?
Do not plan on that basis. Identify each regulated activity in the proposed product, then establish the relevant approvals and ongoing obligations. A payment approval should be checked against the exact service you intend to offer.
Does using a bank or licensed PSP remove the need for my own assessment?
No. Assess your role separately, including contractual responsibility, payment processing and control over settlement. Have the proposed structure reviewed before launch.
Which route should I choose first?
Start with the product’s actual functions and the initial launch scope. Use that analysis to frame preliminary engagement and establish the appropriate application route.
Discuss your proposed payment model
S.N. Nyaga & Company Advocates can assist with a PSP regulatory assessment, application preparation and payment contracts. Send a non-confidential summary of your product, target customers and intended launch scope to info@snnyagaadvocates.co.ke. Use PSP ROUTE in the subject line so we can direct the enquiry appropriately.
This guide provides general information. The appropriate route depends on the business model and applicable requirements at the time of application.
Continue your preparation
Explore all six Kenya business guides, our related legal service, and the Legal Toolkit. For continuing updates, read the Commercial and Regulatory Briefing.