The People Building This With Me
Payment infrastructure is built by people who accept clear responsibilities—from strategy and compliance to operations and delivery.
A payment platform may appear to the user as a screen, a reference number and a result. Behind that simple experience is a group of people making decisions about the service, the rules, the technology and the response when something does not go as planned.
That is why I do not think of CapitalPay's work as a story about one founder or one executive. It is a story about responsibilities. The work becomes credible when partners and users can see who is accountable for a decision, who runs the process and who can resolve a problem.
Leadership must make the work clear
CapitalPay International's published leadership directory lists Jeremy Momanyi Gisemba and Ariec Wol Mayar alongside me as directors. It identifies Eva A.S. Nyamori as Global Chief Strategy Officer and Alvin Okari as Managing Director. It also lists Emily N. Mukami as Head of Compliance and Roselyn Nyagah as Head of Operations.
Those titles describe different parts of the organisation. They should not be treated as interchangeable, and they do not by themselves explain who owns every task in a particular project. A project needs its own operating record: the decision-maker, the delivery lead, the compliance responsibility, the support route and the next milestone.
My responsibility is to help keep those pieces connected to the problem we are trying to solve. A partnership announcement is useful as a starting point. The harder work is turning it into a service with instructions, responsibilities and an outcome that can be documented.
Strategy has to become a sequence of decisions
Strategy is practical when it helps a team decide what to do first, what not to do yet and what evidence is needed before moving forward. In a farmer-payment programme, that may mean defining how account details are checked and how a correction reaches the cooperative. In freight administration, it may mean identifying the record an agent receives and the organisation responsible for an exception.
The strategic role is not to make the work sound larger than it is. It is to keep the scope understandable and connect each stage to a decision. A pilot, a technical integration and an operating service are different things. The team and the public should be able to tell which one has actually been reached.
Compliance is part of the service
Compliance is sometimes described as a final check. In payment infrastructure, it belongs much earlier. The team needs to understand what information is being requested, why it is needed, who may use it and how a disputed or incorrect record will be handled.
That work affects the user's experience. A clear correction process, an appropriate approval step and a retained history can prevent confusion later. The compliance function should help the delivery team build those controls into the process instead of adding them after the workflow has already been designed.
Operations is where the promise is tested
Operations turns the design into repeatable work. It is where instructions meet actual cases, where exceptions appear and where a partner learns whether the support route is clear.
A strong operations record should answer ordinary questions. What arrived? What was completed? What is waiting? Who owns the next action? If an item is corrected, what changed? These questions matter because users experience a service one case at a time.
The same discipline should shape project updates. Rather than saying that work is progressing, we should identify the deliverable, the date and the evidence that supports the stated stage.
Partners are part of the delivery team
CapitalPay's published work includes programmes and alliances involving cooperatives, freight organisations and technology companies. Each party contributes something different. The work is strongest when those contributions are written down and when a user is not expected to understand the organisations' internal structure just to obtain help.
Partners also help test our assumptions. A process that looks complete in a meeting may still be difficult for the person using it. Listening to that experience is not separate from delivery; it is how the service improves.
The next version of this story
This article begins with the public leadership directory because those are the roles that can be sourced today. The more valuable follow-up will focus on the people doing specific work: one task, one decision, what a test revealed and what they are responsible for next.
Those accounts should be given in each person's own words and published with consent. That is how a list of titles becomes a real record of a team building something together.
Filed under Partnerships.
- CapitalPay International leadership page Kenya leadership team and company description Read 26 September 2026