The price you see is the small number
When businesses budget for accepting payments, they ask 'what does it cost to build?' That is the wrong question to lead with, because the build is usually the small number. The large number is the fee skimmed from every transaction, every day, for as long as you accept payments.
A payment integration is not a purchase, it is a subscription to a percentage of your revenue. Understanding the full cost - one-off and ongoing, visible and hidden - is what lets you choose a setup that fits your economics instead of quietly eroding your margin for years.
One-off costs: build and setup
The upfront cost is the work to get payments flowing: registering with the provider, integrating the collection flows (STK Push, C2B) and any payouts, wiring reconciliation into your books, securing it properly, and going through the provider's go-live process.
This scales with complexity. Taking a few payments through a gateway is modest. A direct multi-channel integration with payouts, reconciliation into an ERP, and production hardening is a real project. But whatever the figure, it is paid once. It is the ongoing costs, not this, that usually determine whether your payment setup is a good deal over its life.
Ongoing costs: the fee on every transaction
This is the cost that compounds. Every payment carries a charge, and the sources stack up.
- M-Pesa collection tariffs applied by Safaricom on transactions.
- B2C payout charges, borne by your business, on every disbursement you send.
- Gateway or aggregator margin - a percentage on top of the underlying rail, if you use one.
- Card processing fees, typically higher per transaction than M-Pesa, plus chargeback costs.
- Bank API and transfer charges for payments moved through bank rails.
Who actually bears the charge
A detail that quietly decides your margin: for some transactions the customer pays the charge, for others your business does - and B2C payouts are always a cost to you. If you absorb transaction costs without pricing for them, they come straight off your profit on every sale.
So the question 'what does M-Pesa cost' is really 'which of these charges land on us, and have we priced for them?' Businesses that map this out set prices that cover their payment costs. Businesses that assume the customer always pays discover, at scale, that a slice of every sale has been leaking to transaction fees they never accounted for.
The volume calculation that changes everything
The single most useful thing you can do is turn this into arithmetic. Estimate your monthly transaction volume, apply the percentages you are paying, and annualise it. That number - the fee you hand over every year - is what you compare against the one-off cost of building a more direct, lower-fee setup.
At low volume, the recurring fee is small and a gateway's convenience wins easily. At high volume, that annual fee can exceed the cost of building direct for your biggest channel, meaning every month you delay is money given away. The crossover point is real, and reaching it is normal as a business grows. Knowing roughly where you sit turns payment cost from an invisible drain into a decision you can make on purpose.
How Upeosoft helps you control payment costs
We help you see the whole cost - build, transaction fees, payout charges, settlement, maintenance - and design a setup that fits your volume rather than defaulting to whatever is easiest to switch on. For lower volumes that often means a gateway; as you scale, it can mean bringing your highest-volume channel direct to cut the recurring fees, behind an architecture that makes switching painless.
We also eliminate the biggest hidden cost by building integrations that reconcile reliably, so you are not losing payments to leaks. If you want payments that cost less over their life, talk to Upeosoft.
