Payment Gateway Solutions in Kenya: Local and International Options

Safaricom’s Daraja portal provides APIs for connecting M-PESA and Safaricom services to websites and mobile apps, including a sandbox for testing. [1] That makes it a candidate when your team wants to build around a direct M-PESA relationship. A working sandbox is a development milestone; confirm the production product, merchant onboarding and commercial terms separately.

Paystack’s Kenya page offers card and M-PESA collection. Pesapal’s business FAQ describes a gateway combining mobile money, cards and mobile banking. [2][4] These are relevant candidates when the business wants several ways to pay through one provider relationship. Pesapal also advertises a shareable payments page for businesses taking online orders without a full website. [5]

The operating choice matters as much as the checkout screen. A direct route can justify separate development when it meets a specific requirement. A combined gateway may reduce the number of connections your team maintains. Running both gives you more work to own: payment references, refunds, reconciliation and incident handling must stay consistent across systems. Compare that workload before assuming another connection will save money.

A provider offering payments to Kenyan customers has not necessarily agreed to onboard your company. Name the contracting entity, owners, trading website, products, delivery times and customer countries in the first enquiry. For a foreign company selling into Kenya, request that exact entity-and-payout arrangement rather than relying on a Kenya payment-method page.

Paystack’s Kenya compliance guidance distinguishes Starter Businesses, sole proprietorships and other registered businesses. The Starter route requires identity information and a personal bank or mobile-money account with matching names. Its other-registered-business requirements include incorporation details, CR-12, corporate KRA PIN, ownership information and a matching corporate bank account. [8] Those are Paystack’s published categories, not a substitute for determining your own business obligations.

Pesapal requires a Merchant Agreement and supporting business documentation. [4] Obtain the current checklist for your legal form before integration work starts. Ask each candidate about the actual activity and funds flow: ordinary retail, advance bookings, marketplace collections and subscriptions should not be treated as interchangeable applications.

Paystack’s published Kenya transaction schedule lists 1.5% for M-PESA, 2.9% for local cards and 3.8% for international cards. [3] Use those as separate categories rather than applying the card headline to every order.

Suppose a merchant collects KES 1,000,000 in successful payments during a month. In one scenario, M-PESA supplies 80% of the value, local cards 15% and international cards 5%. Processing charges come to KES 18,250, an effective 1.825%. In another scenario, the same sales value is split 50%, 30% and 20%; charges become KES 23,800, or 2.38%.

The KES 5,550 difference comes entirely from the assumed method mix. These are illustrative calculations, not observed merchant results or an argument for steering customers away from their preferred method. Both totals exclude any additional applicable taxes, conversion, refunds, disputes, transfers and other contracted services. Negotiated pricing could change them.

Repeat this exercise with your own reports before comparing proposals. For a new shop without transaction history, keep both scenarios in the budget. A cheaper method that customers do not use cannot deliver the saving your spreadsheet expects.

Collection fees and the cost of moving money onward answer different questions. Paystack’s Kenya page has a separate Transfers tariff alongside its collection rates. It also describes automatic settlement to a bank account or M-PESA wallet in two working days. [2] Ask which charges apply to routine settlement and which belong to a separately initiated transfer; do not add every transfer fee to every sale.

For each proposal, request a sample payout report showing sales, fees, adjustments and the destination amount. Ask about minimum payouts, bank charges and any account-specific holds. Keep recoverable withheld funds separate from fees when budgeting; the existing Payment Guide reserve and settlement guide explains that distinction.

Cash needs their own test. Suppose you must pay KES 30,000 of suppliers daily and collections are temporarily unavailable for three calendar days. Covering those bills requires KES 90,000 before other obligations. This is a working-capital illustration, not a prediction of a provider’s delay. Model the actual cutoff, working-day calendar and bank-arrival terms offered to you.

A customer’s currency, the checkout currency and your payout currency may differ. Paystack documents international payments for Kenya in KES and USD; USD payout requires a USD account domiciled at a Kenyan bank. International acceptance also depends on activation and the relevant compliance requirements. [7] That route can be relevant to a Kenyan business receiving overseas card payments, but the USD label does not establish access to an overseas bank destination.

Price an overseas order from end to end. Ask what the buyer sees, which party converts the payment, what reaches your account and how a refund is handled if exchange rates change. If most expenses are in shillings, receiving dollars may simply move the conversion decision to your treasury process. If you pay suppliers in dollars, retaining USD may be useful; compare the banking and conversion costs rather than assuming it is automatically cheaper.

Paystack’s Pay with M-PESA documentation says that recurring payments are currently unavailable through that particular channel. [6] Do not extend that restriction to every M-PESA product, or assume that a gateway’s general subscription feature covers each payment method it displays.

For a monthly service, demonstrate the second payment as carefully as the first. Will the customer actively authorise another collection, receive a fresh payment request, or use a separately supported recurring route? Confirm consent, cancellation, failed-payment handling and the charges for that exact arrangement.

A business can choose customer-authorised renewals if it has a workable reminder and access policy. It should budget for the operational effort and possible missed renewals rather than treating them as automatic collections. Test a missed payment and a cancellation before giving customers a recurring-billing promise.

Pesapal’s Kenya payments-page product describes withdrawal to a local bank in two business days. Its business FAQ describes up to three working days and says bank settlement is limited to the country of registration. [5][4] The pages do not explain which account or product conditions reconcile those statements.

Ask Pesapal to identify the applicable product, withdrawal trigger, cutoff and expected bank-arrival period in your agreement. Neither statement is a measured delivery time for your account. The available pages also do not establish a comparable, current merchant-specific tariff for this guide, so Pesapal is not assigned an invented percentage in the fee table.

Use the same discipline with any candidate. Record unresolved answers next to the proposal, including refund costs, reserve conditions and support escalation. A missing answer is a reason to keep the estimate provisional, rather than quietly fill the gap with a rate from an old comparison article.

The Central Bank of Kenya’s PSP directory dated 10 August 2026 lists Safaricom PLC, Pesapal Limited and Paystack Payments Kenya Limited, with approved services beside each entry. [9] Match the legal company in your agreement to the relevant entry and service description, and check for subsequent updates. A directory entry does not approve your industry, settle contractual questions or establish bank-deposit protection.

Then test what happens after the happy path. Let a payment request time out; find its final status before trying again. Confirm that a repeated notification does not create a second order. Follow a partial refund through the customer record and payout report, and reconcile a mixed M-PESA/card batch to the bank or wallet destination. These are acceptance tests to arrange with your provider, not claims that every integration behaves identically.

Payment Guide’s integration guide provides a fuller launch checklist. Assign a named person to investigate unmatched payments before taking live orders; a checkout success message alone cannot reconcile the money.