Work Update: Documented, Being Prepared, and Next
A dated account of what the public record establishes, what remains at a preparatory stage and which evidence should come next.
Progress updates are most useful when they distinguish a completed public record from work that is still being prepared. This update brings together the latest material currently documented on my website and identifies the next evidence needed from each programme.
It does not turn an earlier signing into a new achievement, and it does not present a planned pilot as a completed deployment. Where a current operating result has not been documented, the project remains at its last evidenced stage.
Documented
The public record now gives readers a clearer route through the work associated with CapitalPay.
For the Viaservice trade-corridor project, reports published by KBC and The Star in March 2026 document the agreement and its intended focus. The stated direction concerns cargo visibility and the working capital connected to container-deposit requirements on the Mombasa route. The project page preserves that as an announced partnership rather than claiming an operating result that has not yet been published.
For Tanzania, the work collection separates two different programmes. One concerns the preparation of a farmer-payment pilot involving account validation before disbursement. The other concerns the TAFFA/TACAS clearing-agent programme described by CapitalPay. Keeping the programmes separate makes it easier to state what each one is intended to do and what information is still required.
The website also records CapitalPay's announced cloud, data and AI alliance with GoPomelo, Tencent Cloud and Techtanium. The partner announcement establishes the organisations involved and the broad contribution described by GoPomelo. A later update is still needed to explain implementation responsibilities and milestones.
The editorial work completed around these programmes is also now organised by project. Readers can move from a dated source to a plain-language explanation and then to the next information that would demonstrate progress. This is a communications deliverable, not evidence that the underlying service has reached a new operational stage.
Being prepared or tested
CapitalPay's public programme description places the Korosho farmer-payment work in preparation for pilot and testing ahead of full deployment. The purpose described is to validate bank-account details before farmer payments are sent.
A meaningful pilot record should identify the cooperative or user group involved, the period covered, the number of cases and the outcomes being measured. It should explain how corrections are handled and distinguish a payment prepared for submission from money confirmed in the intended account.
The public description of the clearing-agent programme identifies its intended scope but does not state a deployment date. The next useful operating information would include participation instructions, the applicable fee basis and authority, support contacts and the stage agents can actually access.
For the Viaservice and cloud partnerships, the current public material establishes the agreements and intended contributions. It does not by itself establish production use, completed integrations or measured performance. Those claims should wait for dated evidence from the organisations responsible for delivery.
Next
The next updates should be attached to the project that produced them.
For Korosho farmer payments, the next record should define the pilot scope and period, followed by results from completed attempts and the handling of cases needing correction.
For the Tanzania clearing-agent programme, the priority is a practical service guide: who participates, what the user is paying for, which record confirms completion and where an exception is resolved.
For the Viaservice corridor project, the strongest next account would combine current service terms with a documented journey. It should state the route, period and method used for any comparison of turnaround time or working-capital requirements.
For the technology alliance, the next milestone should identify the implementation scope, the operational responsibility of each organisation and a dated test or service result. General descriptions of cloud or AI capability are not a substitute for that account.
How future updates will be reported
Each completed item should name the deliverable and completion date. Each test should state its scope, period, participants and definition of success. Each next step should identify the responsible party and make clear whether the date is committed or aspirational.
That approach may produce shorter updates, but it will make them more useful. A reader will be able to see what changed, what remains open and what evidence to expect next.
Filed under Partnerships, Tanzania, Payments infrastructure, Trade and customs.
- CapitalPay International — country programmes Company description: Korosho pilot preparations and TAFFA/TACAS programme. Read 24 September 2026. Read 26 September 2026
- GoPomelo — CapitalPay, Tencent Cloud and Techtanium alliance GoPomelo’s own announcement describes its cloud, data and AI contribution. Read 24 September 2026
- KBC: Viaservice and Capital Pay agreement, 12 March 2026 Reporting on the agreement and the parties’ intended outcomes. Read 26 September 2026
- The Star, CapitalPay–Viaservice agreement Reporting and event photograph by Martin Mwita Read 26 September 2026