There is no reliable universal number of months that a founder can use as a guaranteed Kenyan PSP approval timeline. The useful estimate depends on the proposed service, how much preparation is complete and which regulatory, banking and technical dependencies remain unresolved.
Treat the project as three connected periods: preparing a coherent application, obtaining CBK’s decision and completing the work needed for an authorised launch. A timetable that measures only the regulator’s review gives an incomplete picture of the funding and delivery commitment.
What do the legal timing provisions actually say?
Regulation 5 permits CBK to request additional information within 30 days of receiving an application. Following approval, the certificate is to issue within seven days of receipt of the authorisation fee. Neither period guarantees approval within that number of days from the founder’s first approach. National Payment System Regulations, regulation 5.
Sections 12 and 13 of the Act require authorisation before conducting PSP business and provide for CBK’s assessment and conditions; they do not prescribe a universal end-to-end application deadline. National Payment System Act, sections 12 and 13.
The distinction matters when reviewing a proposal that promises a licence in a fixed period. Ask what starts the clock, what stops it, what work is included and which external decisions the estimate assumes. A commercial target is useful only when its assumptions are visible.
Build a timetable around evidence
The following is a project-planning framework, not a CBK service standard:
| Workstream | Useful completion test | Dependency to resolve early |
|---|---|---|
| Product and regulatory scope | One agreed explanation of the service and transaction flow | Changes to launch features or markets |
| Ownership and funding | Ownership records and funding evidence reconcile | Missing overseas corporate records |
| People and governance | Named owners can explain their responsibilities | Recruitment and outstanding personal documents |
| Operating model | Contracts and procedures match actual processes | Banking, settlement and outsourced services |
| Technology readiness | Evidence supports the security and recovery design | Remediation of identified weaknesses |
| Application and review | Submissions and responses are complete and traceable | Questions requiring several teams to respond |
| Launch preparation | Approval scope and operational readiness are checked | Partner activation and unresolved conditions |
Avoid assigning the same deadline to every workstream. Some can proceed together; others depend on decisions that must be settled first. A policy writer cannot accurately describe settlement before the finance and banking arrangements are sufficiently clear.
What should be ready before submission?
CBK’s checklist covers corporate documents, funding evidence, business planning, fit-and-proper material, contracts, safeguarding, risk controls and technology evidence. It specifically includes funds-flow and settlement material, an IT audit, vulnerability assessment and business continuity arrangements. CBK PSP authorisation checklist.
Convert those requirements into an evidence register. Give every item an owner, status, target date and document location. Mark an item complete when the evidence is available and internally consistent, rather than when someone has begun drafting it.
For example, a settlement policy may appear finished while the proposed bank contract uses a different settlement sequence. Treat that as an unresolved operating decision. Sending both documents without reconciling them creates a question that the business will eventually need to answer.
Where should founders look for avoidable delay?
The following are practical risks to investigate during readiness planning; they are not a published ranking of reasons CBK applications take longer.
An unsettled product. Repeatedly adding stored balances, countries or customer segments changes the underlying explanation. Maintain a clear initial launch scope and a separate list of later features.
Ownership records that do not reconcile. Compare incorporation records, the group chart, shareholder information and funding documents early. Ask who is responsible for obtaining information from each overseas shareholder or parent entity.
Policies that describe an imaginary business. A template may assign duties to a committee that does not exist or promise monitoring that the selected software cannot perform. Test the documents against the people, systems and budget actually available.
Unresolved partner terms. Identify the commercial decisions that could change the application: settlement timing, reserves, refunds, termination, access to records and responsibility during an outage. Give those decisions an executive owner.
Fragmented responses. Keep a single register of regulatory questions. Link each answer to supporting evidence, obtain internal sign-off and check it against earlier submissions before sending it.
How can a business improve the timetable?
Begin with a readiness review that produces specific deliverables: the proposed scope, a gap register, a document plan and a dependency map. Use those to develop a dated project plan after the initial assessment, rather than choosing a launch date first and forcing every task to fit it.
Ask the leadership team to review progress weekly using four questions:
- What evidence became complete this week?
- Which unresolved decision is holding up another workstream?
- Which dependency sits with a bank, vendor, shareholder or regulator?
- What has changed in the intended launch scope?
Report external dependencies separately from tasks controlled by the company. This helps investors understand whether an apparent delay is a missing internal deliverable, a third-party response or an unresolved regulatory question.
Plan funding and launch commitments carefully
Build a cash-flow scenario for a longer preparation or review period. Identify commitments that can be phased, including hiring, vendor activation and marketing spend. Partner agreements should make the intended launch conditions clear rather than assume approval on a particular date.
Maintain product demonstrations and testing within an appropriately assessed framework. An application acknowledgement or an encouraging meeting should not be described to customers or investors as a licence. National Payment System Act, sections 12–13.
Before setting a public launch date, compare the final approval and its conditions with the product that will actually go live. Confirm that the contracts, customer wording and operational responsibilities reflect that scope.
Frequently asked questions
Can a Kenyan PSP licence be guaranteed within 90 days?
The provisions discussed above do not support a blanket 90-day approval promise. Any estimate should identify its source, assumptions, starting point and dependencies.
Does engaging an adviser guarantee faster approval?
An adviser can help organise the application, identify gaps and coordinate responses. The regulator controls its assessment and decision. Measure professional support through agreed deliverables and responsiveness.
What is the best first step if I have a target launch date?
Work backwards from the intended product and commission a readiness assessment. Identify the longest dependencies before making commitments that assume regulatory approval.
Build your application plan
For help assessing readiness and preparing a PSP application programme, email info@snnyagaadvocates.co.ke. Use PSP TIMELINE in the subject and include your proposed services, current preparation stage and intended launch window. Start with a non-confidential summary.
Related guides: Types of PSP Licences in Kenya, When Does a Fintech Need a PSP Licence?, and How to Apply for a PSP Licence in Kenya.
This guide provides general information and a planning framework. It does not promise an approval outcome or completion date.
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.