PesaLink vs M-Pesa vs Card: Choosing Payment Rails for a Kenyan Business

Why this question keeps coming up

Every business owner in Nairobi eventually has this conversation with a developer, an accountant, or a bank relationship manager: "Which payment method should we accept?" The honest answer is that most Kenyan businesses of any size end up accepting more than one, because your customers are not homogeneous. A parent paying school fees, a SACCO member repaying a loan, a clinic patient settling a bill, and a corporate client paying an agency invoice all behave differently, bank differently, and have different tolerances for friction. The real work is not picking one rail and discarding the rest — it is understanding what each rail is good at, what it costs you operationally (not just in transaction fees), and how it fits into your reconciliation and tax reporting workflow, including eTIMS compliance with KRA. This article walks through M-Pesa, PesaLink, and card payments from a practical, plumbing-level view, not a marketing one.

M-Pesa: the default, and why it earned that position

For most Kenyan SMEs, M-Pesa is not a "channel" — it is the assumed way of doing business. Customers already have it on their phones, they trust it, and they do not need to be taught how to use it. For a business, the practical entry points are a Paybill number (good for structured payments like invoices, fees, or memberships, because the customer enters an account reference) or a Till number (better suited to retail, point-of-sale style transactions where you don't need a reference number). Send Money to a personal or business number is common for very small operations but tends to break down as soon as you need proper reconciliation, because personal M-Pesa statements are not designed for business accounting.

The operational strength of M-Pesa is reach and familiarity — it works on basic phones, doesn't require the customer to have a bank account, and settlement is near-instant from the customer's point of view. The operational weakness, especially for growing businesses, is reconciliation at scale. If you are manually checking M-Pesa SMS notifications or the Safaricom portal against invoices, that process falls apart once you're processing more than a handful of transactions a day. This is where most SMEs eventually integrate the Daraja API, either themselves or through a payment aggregator, to get transaction data flowing automatically into their accounting or ERP system. Building or buying that integration is a real cost — in developer time if you build it, or in monthly/per-transaction fees if you buy it — and it's a cost businesses frequently underestimate when they're still doing everything by hand in a spreadsheet.

A second consideration is transaction limits and float. M-Pesa has limits on transaction size and daily volume that matter for larger B2B payments — confirm current limits directly with Safaricom rather than assuming last year's figures still apply, because these have changed over time. For a business receiving large one-off payments (say, a school collecting a term's fees from a corporate sponsor, or a SACCO receiving a bulk loan disbursement), M-Pesa may simply not be the right rail, and this is exactly where PesaLink or bank transfer becomes relevant.

PesaLink: the underused bank-to-bank rail

PesaLink, run through the Kenya Bankers Association's infrastructure, lets customers move money directly between bank accounts at participating banks, often through their mobile banking app, USSD, or agent, without needing a middle step of cash or mobile money. For businesses, PesaLink solves a specific problem: moving larger amounts of money quickly between formal bank accounts, without the delays associated with older interbank transfer methods (like traditional EFT or RTGS batch processing) and often at a lower cost than RTGS for smaller amounts. A SACCO disbursing loans to members' bank accounts, a school receiving a large fee payment from a parent's business account, or an agency paying a supplier — these are natural PesaLink use cases. It sits in an interesting middle ground: faster and cheaper than RTGS for many use cases, but requiring both parties to have bank accounts, which immediately excludes a segment of the population that relies entirely on mobile money.

The practical limitation for many Kenyan businesses is that PesaLink is bank-account-to-bank-account, and adoption among ordinary retail customers is lower than M-Pesa. Your typical walk-in customer at a shop or a clinic is far more likely to have M-Pesa open on their phone than to know their bank's PesaLink process off the top of their head. Where PesaLink shines is in B2B and institutional payments — supplier payments, payroll-adjacent transfers, SACCO-to-member disbursements, and larger one-off settlements where the sender is a business or a financially literate individual with an active bank account. If your customer base is mostly retail and mobile-first, PesaLink is a secondary rail, not a primary one. If your business does a lot of bank-to-bank movement — paying vendors, moving money between your own business accounts, or receiving payment from other companies — it deserves a proper place in your payment stack rather than being an afterthought.

Card payments: necessary for some, overhead for others

Card payments — Visa, Mastercard, and increasingly local debit cards — matter most for businesses that deal with online sales, international clients, corporate travel and hospitality, or e-commerce. If you run a hotel, an online store shipping internationally, a professional services firm invoicing foreign clients, or any business where the customer is not necessarily in Kenya or not necessarily using a Kenyan phone number, card acceptance stops being optional.

The technical and cost reality of cards is different from mobile money. You need a payment gateway (a local aggregator or an international one that supports Kenyan settlement), and that gateway takes a percentage-based fee per transaction rather than the flatter, often lower fees typical of mobile money. Card transactions also come with chargeback risk — a customer can dispute a charge with their bank, and depending on the gateway and card scheme rules, the business can lose the funds even after delivering the goods or service. This is a real operational risk that doesn't really exist in the same form with M-Pesa or PesaLink, where transactions are largely final once completed. For a small business owner, this means card acceptance requires a bit more diligence: keeping proof of delivery, understanding your gateway's dispute process, and budgeting for the percentage fee as a genuine cost of doing business, not a rounding error.

There is also a forex dimension. If your gateway settles in US dollars, or if your business tools and subscriptions (the gateway itself, invoicing software, e-commerce platform) are dollar-priced, you are carrying currency risk on top of transaction fees. A weakening shilling quietly increases your effective cost of doing business every time you're paying for dollar-denominated services out of shilling revenue. This is worth modelling explicitly rather than discovering at the end of the month when the bill lands differently than expected.

Putting it together: a decision framework, not a winner

Rather than asking "which is best," a more useful question is: who is paying you, how much, how often, and what do you need to happen after the money arrives? A clinic taking walk-in patient payments will lean heavily on M-Pesa Till or Paybill because it matches how patients already pay for everyday things, with card as a secondary option for insurance-linked or corporate clients. A SACCO handling member contributions and loan disbursements will likely run M-Pesa for day-to-day member interactions and PesaLink or direct bank transfer for larger disbursements and institutional transactions. An agency invoicing corporate clients monthly will often prefer bank transfer or PesaLink for the bulk of its revenue, with M-Pesa reserved for smaller or urgent payments, and card only if it has foreign clients. A school collecting fees typically needs Paybill as the backbone, because it allows structured, reference-based collection from a large number of parents, with bank transfer as an alternative for larger one-off payments from sponsors or employers.

The second layer of the decision is reconciliation and compliance, and this is where many small businesses get caught out. Whatever rails you accept, you need a reliable way to match incoming payments to invoices or records, and you need your records to be consistent with what you report through eTIMS to KRA. A payment that lands in your account but is not properly logged against a customer and an invoice is not just an accounting inconvenience — it is a compliance exposure. Businesses that grow past a certain size usually find that manually reconciling M-Pesa SMS alerts, bank statements, and card settlement reports separately becomes unsustainable, and this is usually the point where it makes sense to invest in either a proper accounting system with API integrations, or a payment aggregator that consolidates multiple rails into one dashboard and one settlement account. That investment has a real cost, but it should be weighed against the staff time currently spent doing the same reconciliation by hand, plus the cost of the errors that manual reconciliation inevitably produces.

Practical steps before you commit

Before locking in a payment stack, talk to your bank about current PesaLink transaction limits and fees for your account type, and confirm current M-Pesa Paybill/Till transaction and daily limits directly with Safaricom — both change over time and this article will not guess at current figures. If you plan to accept cards, get a clear, written breakdown from your prospective gateway of the percentage fee, settlement currency, settlement timeline into your Kenyan bank account, and their dispute/chargeback process, before you sign anything. If you handle any customer personal data as part of these integrations — names, ID numbers, phone numbers, payment history — remember that this falls under the Data Protection Act, and you should be able to explain how that data is stored, who can access it, and how long you keep it; the Office of the Data Protection Commissioner is the right place to check current registration and compliance obligations if you're unsure whether they apply to your setup. Finally, whatever combination of rails you choose, build your reconciliation process before you scale your marketing — it is far cheaper to fix a payment workflow when you're processing tens of transactions a day than when you're processing hundreds, and the businesses that struggle most with payments are rarely the ones that picked the "wrong" rail, but the ones that never built a proper system to track the right one.