How a Foreign Company Can Accept M-PESA Payments in Kenya

A foreign company can accept M-PESA in Kenya in three main ways: through a licensed payment aggregator or gateway that supports M-PESA, through a local partner or entity that holds the merchant relationship, or through a direct Daraja API integration once you have the required Safaricom credentials. For most international companies, starting with an aggregator is fastest, and a direct integration only makes sense at scale or when reconciliation and control become critical.

If you are expanding a product into Kenya or East Africa, this is usually the first hard technical question, and getting it wrong creates reconciliation and compliance headaches later. Here is how to approach it properly. This is exactly the kind of work Infosencia does as e-commerce and payment integrations, and it pairs with the wider technical guide to expanding into Kenya.

Why M-PESA is non-negotiable

In Kenya, mobile money is not a niche payment method, it is the default. A checkout that only takes cards will lose a large share of customers. Any product serious about the market has to accept M-PESA cleanly, not as an afterthought.

Your three options

• Payment aggregator / gateway. Providers that already support M-PESA let you accept it without holding the direct Safaricom relationship. Fastest to launch, some fee overhead, less control.
• Local partner or entity. A Kenyan partner or your own local entity holds the merchant relationship. More setup, but cleaner for larger operations and often required for direct arrangements.
• Direct Daraja API integration. Safaricom's Daraja API (STK Push, C2B, B2C) gives you the most control and best economics at scale, but requires credentials, a paybill or till, and careful engineering.

What foreigners consistently underestimate

• Reconciliation is the real work. Taking the payment is easy; matching it reliably to an order, handling delays, duplicates, and failures, and giving finance clean visibility is where projects fail. The M-PESA integration guide covers why you must design for every path, not just success.
• Callbacks and timeouts. M-PESA confirmations are asynchronous. Your system must handle a customer who paid but whose callback is delayed, and never double-charge or double-fulfil.
• Compliance. Collecting Kenyan customer data brings you under the Kenya Data Protection Act. This applies to foreign companies serving Kenyan users.
• Settlement and currency. Understand how and when funds settle, and in what currency, before you build.

How to choose

1. Testing the market? Start with an aggregator. Speed beats optimisation.
2. Committed and scaling? Move toward a direct Daraja integration for control and economics.
3. Regulated or high-volume? Get a local partner and proper entity structure early.

The one thing to get right first

Design the reconciliation and failure handling before you obsess over the integration path. A store that accepts M-PESA but forces manual matching every evening is not solved, it is postponed. This is the difference between a payment button and a payment system.

Frequently asked questions

Can a company outside Kenya accept M-PESA?

Yes. The common routes are a payment aggregator that supports M-PESA, a local partner or entity holding the merchant relationship, or a direct Safaricom Daraja API integration. Aggregators are fastest to start; direct integration gives the most control at scale.

Do foreign companies have to comply with Kenyan data law?

If you collect or process the data of Kenyan users, the Kenya Data Protection Act generally applies to you regardless of where your company is based. Treat compliance as part of entering the market, not an afterthought.

What is the hardest part of M-PESA integration?

Not the payment itself, the reconciliation. Handling asynchronous confirmations, delays, duplicates, and failures, and giving finance a clean, matched view, is where most integrations fall short. Design for every path from the start.

Should we build direct or use an aggregator?

Use an aggregator to launch fast and test the market. Move to a direct Daraja integration when volume, economics, or the need for control justify the extra engineering. Many successful products start with one and graduate to the other.

Expanding into Kenya or East Africa and need M-PESA done right? Tell us your product and target market. We understand the local rails, the compliance, and the reconciliation that foreign teams miss.