You run a school, a clinic, a shop or an app, and you want customers to pay by M-Pesa from inside your system. Someone has to connect your Paybill or Till to Safaricom’s Daraja API, handle the payment prompts and callbacks, and make sure every shilling shows up in your records. Picking that someone is the decision that matters most. The code is much the same for everybody. The difference is who has done it with real money.
We have added M-Pesa to our own products and to clients’ systems, and we run our own Paybill every day. These are the questions we would ask if we were hiring someone else to do it.
Know what you are asking for
Daraja is not one thing. Before you call anyone, know which pieces you need, because the price and the skill needed change with each one.
- STK Push. The customer enters a PIN on their phone after your app or site asks for the payment. Good for checkout and fees.
- Paybill and Till payments, also called C2B. The customer pays from the M-Pesa menu and Safaricom tells your system who paid and how much.
- B2C payouts. Your system sends money to customers, workers or landlords.
- B2B. Payments between businesses, for suppliers or for moving money from your Paybill to a bank.
- Reversals, balance checks and transaction status. The housekeeping that keeps your records honest.
Most schools and rent collectors need Paybill payments and STK Push. A marketplace or a payroll system needs B2C too. Say which ones you want and you will get quotes you can compare.
Ask to see a live integration
The first question for any company is simple. Show me one Paybill you have taken live and the system behind it. Sandbox demos are easy. The Daraja sandbox accepts any phone number and never fails. Real M-Pesa fails in ways the sandbox never shows you, like a customer who cancels the prompt, a callback that arrives twice, or one that never arrives at all.
A company that has gone live can show you a real shortcode, a Go-Live date and a system that has been collecting for months. Ask how many payments it has handled. Ask what broke in the first week and what they changed.
Ask who owns the shortcode and the code
Two things should be in your name at the end of the project. The Paybill or Till, and the Daraja app with its consumer key and secret. Some developers put the shortcode under their own company so that payments pass through them first. That is a loan of your own money, and it ends badly when the relationship ends.
The same goes for the code. Ask for the repository, the deployment steps and the credentials in writing at handover. If the answer is that the integration lives on their platform and you pay monthly to keep it, that can be a fair deal, but you should know it before you sign.
Ask how they handle callbacks and reconciliation
This is where cheap integrations fall apart. Safaricom confirms a payment by calling a URL on your server. If that call fails, times out or arrives twice, your records and your M-Pesa statement drift apart. A parent has paid, the school says they have not, and someone spends Monday morning on the phone.
A good company will answer this question without being prompted. Listen for these.
- Every callback is checked and stored before anything else happens, so a crash later cannot lose it.
- Duplicate callbacks are caught by the M-Pesa receipt number, so one payment is never counted twice.
- Payments that never produced a callback are pulled in afterwards with a transaction status query.
- There is a daily match against the M-Pesa statement, and a report of anything that does not line up.
A payment that reached M-Pesa but not your records is the most expensive bug you will ever have. It costs you the money and the customer’s trust in the same minute.
We wrote about the paperwork and the hidden steps in Adding M-Pesa to your app, what they don’t tell you.
Ask about the Go-Live and the paperwork
Safaricom will not switch on a production shortcode because a developer asks. You need a registered business, your KRA PIN and the ID of the person applying, and the Daraja Go-Live has its own test checklist. A company that has done it a few times knows which documents the Safaricom team asks for and how long each step waits. Ask who fills the forms and who follows up, and get it into the quote.
Ask what the price covers
Prices published in Kenya for adding M-Pesa to an app or site you already run sit between about KSh 15,000 and KSh 60,000. The spread is real and it tells you something. The low end is usually STK Push only, on the developer’s own setup, with no reconciliation. The high end usually includes Paybill payments, callbacks that are stored and checked, a daily match, the Go-Live paperwork and a few weeks of support.
Whatever the number, make the quote say which of the pieces above are included, who pays the M-Pesa tariffs, and what happens when the code needs a change in six months. A quote without those lines is not a quote, it is an opening offer.
Ask what happens after launch
Safaricom changes things. Certificates expire, the API returns a new error code, a phone update breaks the prompt for some customers. Ask who you call when a payment goes missing on a Saturday and how fast they answer. Ask whether that support is in the price or on top of it. The answer does not have to be free, it has to be clear.
Red flags
- They cannot name one shortcode they have taken live.
- The Paybill, the Daraja app or the server will be in their name, not yours.
- The word reconciliation makes them change the subject.
- The quote is one line with one number.
- They will not put the handover of code and credentials in writing.
- They promise Go-Live in two days. Safaricom alone takes longer than that.
Seven questions to send before you hire anyone
Copy these into a WhatsApp message and send them to every company you are considering. The answers will sort them for you.
- Which Paybill or Till have you taken live on Daraja, and when?
- Which parts do I need and which are in your quote? STK Push, Paybill payments, B2C, reversals.
- Will the shortcode, the Daraja app and the code be in my name at the end?
- How do you store and check callbacks, and how do you catch a payment that never sent one?
- How do you match my records against the M-Pesa statement, and how often?
- Who handles the Go-Live paperwork with Safaricom?
- What support is included after launch, for how long, and what does it cost after that?
What we would say if you sent them to us
KEPAS Technologies is a software company in Loitokitok that works with clients anywhere in Kenya. Our Paybill 4052037 collects rent for landlords on KodiSap, and Wabi holds a customer’s M-Pesa payment until a job is done and pays the worker after. We publish daraja-js, an open source Node.js SDK for Daraja that other developers use, and every check in it is a bug we met with real money first. The shortcode, the Daraja app and the code are yours at handover, and we quote in writing after one call.
Read our page on M-Pesa integration services in Kenya for the full list of what we build, or send us the seven questions on WhatsApp at +254 741 642 093 and judge the answers for yourself.
Want to see what this looks like for your organization?
Talk to Us on WhatsApp