AFRICA / IDEAL CHECKOUT

Make mobile-money confirmation the center of the local journey.

For many domestic contexts, M-PESA merchant collection may be essential; integrating it requires an eligible operator/aggregator product and careful reversal handling.

See the checkout experience ↓Review merchant requirements ↓

SHOPPER MARKET KenyaDISPLAY CURRENCY KESRESEARCH DATE Nov 4, 2026

REFERENCE CHECKOUT / NOT A LIVE PAYMENT FORM01 — 03

EXAMPLE MERCHANTCheckout preview

Order summaryCurrency · KES

PAYMENT OPTIONS TO EVALUATEOnly show contractually enabled methods

01M-PESA merchant collections where contractually supported

02Cards for supported merchants and buyers

03Other bank/mobile alternatives where verified

ORDER STATUSAwait verified provider confirmationBrowser redirect ≠ settled payment

Design concept only · No credentials collected · No provider compatibility implied

01 / PAYMENT METHOD HIERARCHY

What the shopper should see first.

The method order depends on local preference, device and eligibility. A popular scheme is not automatically available to your merchant.

FIRST-SCREEN EXPERIENCE

Prioritize a usable path, not a logo wall.

Show the correct merchant paybill/till or STK push instructions with buyer authorization and authoritative callback confirmation.

LOCALIZATION & TRUST

Respect the buyer's context.

Display KES and a clear pending state; provide recovery for delayed prompts and duplicate attempts.

02 / INTERACTIVE CHECKOUT PATH PLANNER

What does an ideal checkout actually do?

Select the buyer relationship. The steps change because a local one-time sale, a subscription and a cross-border purchase are different payment products and legal journeys.

LOCAL CHECKOUT FLOW / KENYA

Choose the transaction you need to support.

A shopper in Kenya needs a straightforward KES purchase without ambiguous payment status.

STEP 01

Recognize the buyer

Confirm the shopper's country, language, device and KES total before payment.

STEP 02

Offer usable local methods

Show the correct merchant paybill/till or STK push instructions with buyer authorization and authoritative callback confirmation.

STEP 03

Guide authorization

Display KES and a clear pending state; provide recovery for delayed prompts and duplicate attempts.

STEP 04

Confirm and recover

Offer safe re-request and card alternative with order state reconciliation.

DO NOT ASSUME

Customer screenshots or SMS alone must not mark a merchant order as settled.

03 / TRANSACTION LIFECYCLE

A complete checkout is more than authorization.

Use this sequence as an implementation and procurement handoff.

01 / FLOW

Identify payer context

Locale, device, KES currency and product eligibility

02 / FLOW

Present only actual methods

M-PESA merchant collections where contractually supported

03 / FLOW

Secure customer authorization

Handle redirects, wallet prompts, issuer challenges or mandates

04 / FLOW

Wait for authoritative status

Confirm pending, paid, declined, expired or cancelled states

05 / FLOW

Reconcile & fulfill

Match provider references and deliver only after approved merchant confirmation

06 / FLOW

Support reversals

Refunds, chargebacks, expiries and customer service

04 / MODEL-SPECIFIC DECISIONS

One country. Three different checkout contracts.

DOMESTIC CUSTOMER

Local method fit

Show the correct merchant paybill/till or STK push instructions with buyer authorization and authoritative callback confirmation.

REPEAT PURCHASE

Subscriptions & stored credentials

Do not assume a person-to-person wallet transfer or merchant collection API provides subscriptions.

FOREIGN MERCHANT

Cross-border acceptance

Confirm whether the foreign entity can use domestic collection products, and how FX/payouts work.

PAYMENT FAILURE DESIGN

Build a recovery path.

Offer safe re-request and card alternative with order state reconciliation.

CRITICAL RISK

What you must not assume.

Customer screenshots or SMS alone must not mark a merchant order as settled.

05 / EVIDENCE BEFORE PROCUREMENT

Five questions to ask before shipping this checkout.

These are a merchant’s validation questions, not claims that every payment provider supports the market.

01Can our legal entity and merchant category accept these methods in Kenya?02Are the methods usable for this channel, customer type and transaction amount?03What does the provider require for mandates, authentication and risk screening?04How are pending statuses, expirations, refunds and duplicate attempts reconciled?05What fees, FX charges, payout timing and reserves apply to KES transactions?

06 / FREQUENT QUESTIONS

How should checkout work in Kenya?

What payment methods belong in a Kenya checkout?

Show the correct merchant paybill/till or STK push instructions with buyer authorization and authoritative callback confirmation.

What should a mobile checkout in Kenya look like?

Display KES and a clear pending state; provide recovery for delayed prompts and duplicate attempts.

Can Kenya checkout support recurring billing?

Do not assume a person-to-person wallet transfer or merchant collection API provides subscriptions.

Can an overseas business accept local payments from Kenya buyers?

Confirm whether the foreign entity can use domestic collection products, and how FX/payouts work.

What if a Kenya payment fails or times out?

Offer safe re-request and card alternative with order state reconciliation.

07 / SOURCES AND CAVEATS

Official system documentation, then the merchant contract.

Payment networks, regulators and product pages establish different kinds of facts. None proves underwriting approval for a merchant.

PRIMARY SOURCECentral Bank of Kenya — national payments systemRead reference ↗PAYMENTSOLUTIONS.APP RESEARCHKenya payment systems guideSee country evidence ↗

Editorial checkout design framework reviewed November 4, 2026. Product eligibility, scheme adoption, fees and local regulation change. Verify every method for your contracting entity and actual use case before implementation.