Which payment gateway should a Kenyan startup use?

By Bonaventure Ogeto, Founder and CEO, Mctaba Labs
Published

The short answer

Default to an authorised gateway that takes M-Pesa and cards and settles to your account. Compare fees at your payment size and settlement times. Go direct to Daraja only when M-Pesa is all you need and your developer has done it before. Build your own payment layer only when you run several providers or payments are the product.

"Which gateway should we use?" is usually the second question asked in the wrong order. The first is whether you need a gateway at all. A founder who sells only to Kenyans, only by M-Pesa, and already holds a Paybill may not. A founder who has customers in three countries certainly does. And a few founders are, without realising it, describing a business that would be a payment company itself.

Sort out which of those you are, and the choice of provider becomes a short job.

The short version: default to an authorised gateway that takes M-Pesa and cards and settles to your own account, and pick between gateways on the fee at your payment size and on how fast they settle. Go direct to Daraja only when M-Pesa is all you need and your developer has connected to it before. Build your own payment layer only when you run several providers or payments are the product itself.

What is the actual decision?

There are three ways to take money inside a product, and they stack on top of each other.

  1. Go direct. Your product connects to Safaricom's Daraja platform using your own Till or Paybill. M-Pesa only.
  2. Use a gateway. Your product connects to one company that already connects to M-Pesa, the card networks and the banks. It collects for you and pays you out.
  3. Build your own payment layer. Your product has its own internal system that sits above several providers, decides which one handles each payment, and keeps its own record of every shilling.

Each step up adds capability and adds work. The mistake is skipping to step 3 because it sounds serious, or staying on step 1 after you have started losing customers who wanted to pay by card.

What does going direct to Daraja give me, and what does it cost me?

It gives you the lowest cost per payment and money in your own account.

Daraja is Safaricom's developer platform. Its catalogue covers what an M-Pesa business needs: the PIN prompt at checkout (M-Pesa Express), notifications of payments to your Paybill or Till, payouts to customers, transaction status checks and reversals. Payments land in your Till or Paybill, and you pay Safaricom's tariff for that account with nobody in between.

The costs are of a different kind:

  • Paperwork and waiting. You need a live Till or Paybill in the business name, and a person with an administrator role on Safaricom's M-Pesa portal, before your developer can go live.
  • More to build. It is a job for a developer who has done it before. Yours handles confirmations, failures, retries and reconciliation that a gateway would otherwise give you ready made.
  • M-Pesa only. No cards, no customers abroad, no other mobile money networks.
  • You are the support desk. When a payment goes missing, you work it out from your own records and Safaricom's statement.

What does a gateway add?

Speed, more ways to pay, and somebody else maintaining the connections.

With a gateway you open one account, upload your documents and connect once. Your customers can then pay by M-Pesa or by card. Paystack, for example, lists cards, M-Pesa and Apple Pay for Kenya, and says international cards can be charged and settled in KES or USD. You also get a dashboard, refunds handled through the provider, and features such as card subscriptions. M-Pesa has its own standing order product, M-Pesa Ratiba, which Safaricom describes as a way for customers to set up recurring payments from M-Pesa to a Lipa na M-Pesa short code. Ask your developer whether it fits before assuming subscriptions need a card.

You pay for this in two ways. The first is a percentage of every payment. The second is time: the money sits with the gateway before it reaches you. As of 19 November 2026, Paystack says it settles to your bank account or M-Pesa wallet two working days after a payment, and Flutterwave says you receive local payments the next day.

For a first version, that trade is usually worth it. A week of developer time saved is worth more than the difference in fees at low volume.

Once you know a gateway is the right layer, you still have to pick one. Two detailed pieces already do that work: a side by side look at the main gateway options in Kenya, and a technical comparison of Paystack and Flutterwave to hand to your developer.

When does it make sense to build my own payment layer?

Later than you think, and for one of three reasons.

  • You use more than one provider and want the product to choose between them, for instance Daraja for M-Pesa and a gateway for cards.
  • You need to survive an outage. If one provider is down, payments move to another without customers noticing.
  • Money moves between your users, as in a marketplace, a wallet or an escrow service, and you need your own ledger of who is owed what.

The third reason needs care. The Central Bank of Kenya defines a payment service provider broadly, as a person or company "sending, receiving, storing or processing" payments through an electronic system, and it authorises such providers under the National Payment System Act and its regulations. If your product holds customers' money or passes it from one user to another, get legal advice before you build, and look at whether an authorised provider can hold the funds for you instead.

If none of the three applies, you do not need your own layer. You need one provider and tidy code.

Which option fits my situation?

Find the row that sounds most like you.

Your situation Use Why
Testing demand, fewer than a few dozen payments a month A Till number and manual confirmation Nothing to build. Learn first
First version of a product, Kenyan customers, no Paybill yet One gateway Fewest documents, M-Pesa and cards from one connection
Customers or donors outside Kenya A gateway with international cards Daraja cannot take a card
You want card subscriptions that renew by themselves A gateway Card billing lives there. For M-Pesa, look at the Ratiba standing order
You already have a Paybill that customers know and pay Direct Daraja Keep the number. Add automatic confirmation
M-Pesa only, high volume, thin margins Direct Daraja The per-payment saving is now real money
You need the cash in your own account the same day Direct Daraja No settlement wait
M-Pesa volume is high and you also need cards Direct Daraja plus a gateway, behind your own thin layer Each provider does what it is best at
A marketplace or wallet that moves money between users A provider authorised to hold funds, plus your own ledger, after legal advice Holding other people's money is regulated

How do I check that a provider is allowed to operate?

Look it up. The Central Bank of Kenya publishes a directory of authorised payment service providers, with each company's approved services and the date it was first licensed.

The directory dated 10 August 2026, the current one linked from the Central Bank's site when this was written, listed Paystack Payments Kenya and Pesapal among others. The typical approved service for a gateway reads "to provide a platform that facilitates processing of payments on behalf of merchants".

Do the check yourself for any provider on your shortlist, because the list is updated. Search for the company's legal name, which may differ from its brand. If you cannot find it, ask the provider which authorised institution processes and holds your money, and get the answer in writing. Some providers operate through an authorised partner. You want to know who that is before your revenue passes through them.

What do the fees look like on real numbers?

Run the sum on your own payment size. Here is the method, with made up sales and published fees as of 19 November 2026.

Say your product takes 250 M-Pesa payments of KES 2,000 in a month, which is KES 500,000.

Route Published fee Cost per payment Cost for the month
Your own Business Till, direct Up to 0.55%, capped at KES 200 KES 11 KES 2,750
A gateway at 1.5% for M-Pesa (Paystack's listed rate) 1.5% KES 30 KES 7,500
A gateway at 2.9% for mobile money (Flutterwave's listed rate, before VAT) 2.9% KES 58 KES 14,500

At this size the difference between direct and a gateway is a few thousand shillings a month. That is far less than the cost of the extra development and administration the direct route needs. Multiply the volume by twenty and the picture changes, which is the point at which adding a direct connection is worth costing.

Two cautions. Some gateways let you pass the fee to the customer, and Flutterwave says that is its default, so check who is actually paying. And a Paybill is priced differently from a Till, with fixed charges by band, so redo the sum if that is your account.

What should I ask a gateway before I sign up?

Send these questions to the two providers on your shortlist and compare the answers. Their pricing pages will answer some of them.

  1. What do you charge for M-Pesa, for local cards and for international cards, and is VAT included?
  2. When is money settled to me, and can I choose my bank account or M-Pesa?
  3. Is there a minimum payout, a payout fee or a rolling reserve?
  4. What documents do you need from a business like mine, and how long does approval take?
  5. Under which name do you appear in the Central Bank's directory of authorised providers?
  6. What is the largest single M-Pesa payment you can process?
  7. How do refunds work, and how long do they take to reach the customer?
  8. What does my customer see on their phone and on their statement when they pay?
  9. How do I reach support when a payment is stuck, and during which hours?
  10. Can I export every transaction, with the M-Pesa receipt number, for my accountant?

Can I switch providers later?

Yes, if the product is built for it.

Ask your developer for one thing at the beginning: all payment code lives in a single part of the system, and the rest of the product only ever asks it "collect this amount for this order" and "did it succeed?". Then moving from a gateway to Daraja, or adding a second provider, means changing that one part.

Keep your own record of every payment as well: amount, customer, order, provider reference and status. If you ever leave a provider, your history comes with you.

Choose the simplest option that fits the row you found in the table, launch, and revisit the decision when your monthly volume or your customers change.

Key takeaways

  • Decide first whether you need a gateway at all. The choice is between going direct, using a gateway and building your own layer.
  • A gateway buys you speed, cards and one dashboard, and charges a percentage of every payment for it.
  • Going direct to Daraja keeps the money in your own Till or Paybill and costs less per payment, but covers M-Pesa only.
  • Check any provider against the Central Bank of Kenya's directory of authorised payment service providers before you sign up.
  • Compare fees on your own payment size and volume, using the providers' pricing pages on the day you decide.
  • Ask your developer to keep payment code in one place, so that changing provider later is a small job.

Frequently asked questions

What is the difference between a payment gateway and an aggregator?
In everyday use in Kenya the words overlap. Both describe a company that connects to M-Pesa, card networks and banks on your behalf, collects payments in its own name and settles the money to you. What matters is which payment methods it offers, when it pays you and whether it is authorised.
Do I need a registered company to use a payment gateway?
Not always. Paystack, for example, publishes requirements for unregistered "Starter" businesses in Kenya, which need a government ID and a personal bank account or mobile money number. Registered businesses provide registration documents, a KRA PIN and a bank account in the business name. Check each provider's own requirements page.
Can I use more than one payment gateway?
Yes, and larger products sometimes do, for example one provider for M-Pesa and another for international cards. It doubles the reconciliation work and the things that can break, so add a second provider only when the first one cannot do something you need.
Should I pass the gateway fee on to my customer?
Only if your customers will not notice or mind. Adding a fee at the last step makes some people abandon the payment. Flutterwave says customers bear the charge by default and that you can change this on your dashboard, so check the setting on whichever provider you use and decide on purpose.
How much does a payment gateway cost in Kenya?
Gateways usually charge a percentage of each payment and no setup fee. As of 19 November 2026, Paystack lists 1.5% for M-Pesa and 2.9% for local cards in Kenya, and Flutterwave lists 2.9% for mobile money and 3.2% for local cards before VAT. Read the pricing pages yourself, since these change.

Sources

  1. Directory of Authorized Payment Service Providers (PSPs) as at August 10, 2026, Central Bank of Kenya. Checked on 19 November 2026.
  2. National Payments System, Central Bank of Kenya. Checked on 19 November 2026.
  3. Discover APIs (Daraja API catalogue), Safaricom Daraja developer portal. Checked on 19 November 2026.
  4. M-PESA Ratiba, Safaricom. Checked on 19 November 2026.
  5. M-Pesa Express Simulate (Lipa na M-Pesa Online API documentation), Safaricom Daraja developer portal. Checked on 19 November 2026.
  6. M-PESA Business Till, Safaricom. Checked on 19 November 2026.
  7. Pricing for Kenya, Paystack. Checked on 19 November 2026.
  8. Compliance requirements for Kenya, Paystack. Checked on 19 November 2026.
  9. Paystack is live for all merchants in Kenya, Paystack. Checked on 19 November 2026.
  10. Pricing for Kenya, Flutterwave. Checked on 19 November 2026.