Safaricom rarely announces a pricing tweak or an API upgrade as a headline event. Most changes to Daraja, the developer portal that connects outside businesses to M-Pesa, land as a press release, a forum post, or a line in a changelog.
Yet those quiet updates ripple through hundreds of startups that were built assuming the rails underneath them would stay still. Understanding how M-Pesa’s API changes move through the ecosystem is becoming essential reading for anyone building on top of it in East Africa.
Daraja Is Bigger Than Most People Realize
M-Pesa processes over 100 million transactions a day, and roughly a quarter of those now move through APIs rather than the consumer app.
More than 66,000 integrations and over 105,000 developers rely on Daraja to power everything from e-commerce checkouts to logistics platforms and micro lending apps.
That scale is exactly why small changes carry outsized weight. A pricing adjustment or a new access tier does not just affect Safaricom’s balance sheet, it reshapes the unit economics of every business plugged into the platform.
From Daraja 1.0 to Fintech 2.0
Daraja began in 2017 as a simple gateway that cut the time it took businesses to connect to M-Pesa from more than sixty days down to a self service process.
Daraja 2.0 followed in 2019 with expanded capabilities. The most recent overhaul, Daraja 3.0, launched in late 2025 and represents a much bigger shift.
Safaricom has rebuilt the platform on cloud native infrastructure, pushed throughput toward 12,000 transactions per second, and added security APIs for fraud detection and identity verification.
The company is framing this as a move into what it calls Fintech 2.0, positioning M-Pesa as a full digital ecosystem rather than a payments utility.
For years, developers complained about inconsistent documentation, limited sandbox environments, and slow support during peak periods.
READ ALSO :How to Apply for a PayBill Number in Kenya: Step-by-Step Guide
Those complaints shaped much of what Daraja 3.0 tries to fix, with AI powered support, redesigned onboarding, and a more capable testing environment.
The upgrade matters because onboarding friction had a real cost. Early stage startups without dedicated engineering resources sometimes lost weeks just getting production credentials approved, time that mattered enormously for teams trying to reach their first paying customers.
Pricing Changes Hit Smaller Players Hardest
Beyond the API architecture itself, Safaricom periodically revises transaction tariffs, and those revisions ripple unevenly across the ecosystem.
Recent changes to Lipa na M-Pesa Buy Goods and Pochi la Biashara charges lowered collection costs for small transactions, with collections up to a set threshold becoming free and percentage fees dropping on mid sized transfers.
For a large fintech processing millions of transactions, a few percentage points of fee movement is a rounding error absorbed into a broader cost model.
For a two person startup running a till number through a thin margin business, the same change can meaningfully alter whether a product is profitable at a given price point.
This asymmetry is the core reason API and pricing changes deserve close tracking rather than a one time read.
A platform level decision made for macro reasons, like encouraging small transaction volume or supporting SME digitization, can quietly reset the economics of dozens of startups that were not part of the conversation when the decision was made.
The Access Tier Question
Access tiers add another layer of complexity. Rate limits, sandbox capabilities, and support channels are often distributed unevenly between large integrators with direct relationships to Safaricom and smaller developers working through public documentation alone.
As Daraja opens up features like IoT payment APIs and Mini App capabilities inside the M-Pesa Super App, the businesses positioned to move first tend to be the ones with existing partnerships or dedicated account management, while smaller teams wait for wider rollout or figure out workarounds through third party aggregators.
That gap has helped sustain a whole layer of API aggregators and middleware providers who package Daraja access with easier onboarding, in exchange for a per transaction fee.
Their existence is itself a signal about how much friction still sits between Safaricom’s public API and the average small business trying to use it.
What Builders Should Watch
For founders building on M-Pesa, the practical lesson is to treat Daraja like infrastructure that evolves on Safaricom’s timeline, not a fixed foundation.
Tracking changelog updates, tariff announcements, and developer forum threads is not optional busywork, it is closer to monitoring a dependency that can shift your margins overnight.
Teams that build in some buffer around fee assumptions, diversify their payment integrations where possible, and stay close to Safaricom’s developer communications tend to adapt faster when the next change lands.
M-Pesa’s dominance in East African payments means these changes will keep arriving quietly, a tariff adjustment here, an access tier update there.
The startups that plan around that rhythm, rather than being surprised by it, are the ones best positioned to keep building on top of it.
Leave a Reply