← Back to the directory

Payment channel profile

M-PESA (Safaricom Ethiopia)

Wallet / user payment entry · Ethiopia

EthiopiaPrimary marketMain service market
Wallet / user payment entryRole / typeMobile money, Digital wallet
Usually requires a local entityEntity requirementOnboarding conditions
Real-time / T+0SettlementPayout timing

Overview

M-PESA (Safaricom Ethiopia) is listed as mobile money, digital wallet in the LocalPayMap public directory. Use this page to prepare due-diligence questions; product availability and terms must be verified directly.

This is a market-specific M-Pesa record, not a duplicate of the brand overview and not the only official onboarding or pricing route. The brand page aggregates related countries and PSP contact leads; this page keeps the local payment scenario visible.

Role in the payment stack

Wallet / user payment entry

This is usually a wallet or consumer payment entry. Foreign merchant access often depends on a PSP, aggregator, platform partnership, or local entity setup.

Merchant usage and connection route

M-Pesa in the payment stack

M-Pesa is critical for merchants selling in markets where mobile-money wallets are a primary customer payment behavior, especially Kenya and selected East African routes. Assess it for wallet collection, till or paybill-style flows, ecommerce checkout, reversals, settlement reporting, reconciliation, and how it complements cards and bank transfer.

Connection route

Connection may be direct through a local M-Pesa operator product or indirect through a mobile-money aggregator, PSP, gateway, bank, platform, or marketplace. Merchants should confirm the country operator, product type, contract owner, settlement flow, reversal process, and customer support handoff.

Verification questions

  • Which country, M-Pesa operator, and merchant payment product are required?
  • Is the route operator-direct, aggregator-led, PSP-led, bank-led, platform-led, or marketplace-led?
  • Which collection, STK push, QR, till, paybill, refund, reversal, payout, callback, and reconciliation flows are available?
  • What entity, documentation, wallet-limit, category, and compliance checks must be completed for the merchant?
  • Who resolves failed wallet prompts, duplicate debits, reversals, disputes, and customer escalations?

Merchant caveats

  • M-Pesa merchant access is country-specific and product-specific.
  • Operator-direct and aggregator routes can differ in checkout UX, support, and reconciliation.
  • Wallet limits, reversals, and disputes should be checked against the merchant's transaction profile.
  • Provider examples are discovery examples only, not recommendations or support evidence.

Provider examples to verify

Safaricom M-Pesa for BusinessM-PESA Safaricom EthiopiaDPO Pay KenyaiPay AfricaKopo KopoPay Hero Kenya

Related markets

EthiopiaKenyaTanzania

Keep researching

This explanation separates payment methods, PSPs/aggregators, acquirers/banks, wallets, and networks/schemes. It does not publish coverage, eligibility, pricing, settlement timing, or onboarding guarantees.

Sources

What merchants should confirm

  • Whether the product is available to merchants incorporated outside the target country.
  • Whether a local entity, local bank account, licence, or local tax registration is required.
  • Supported checkout flows, currencies, refunds, disputes, reconciliation fields, and payout options.
  • Industry restrictions, reserve policies, onboarding documents, and implementation support.

Merchant eligibility

A local entity, local account, or additional licensing may be required.

Pricing and settlement

Published pricing is suitable for initial screening only. Actual pricing can vary by country, industry, volume, settlement currency, integration model, and contract terms. Confirm the official pricing page or a provider quote before going live.

Settlement timing, payout currency, foreign exchange, reserves, and withdrawal rules must be confirmed with the provider.

Capability verification checklist

Use this public checklist before you ask for a quote or implementation access. Treat unknown fields as questions to verify, not as unsupported features.

  • Confirm who owns onboarding, KYB review, pricing, settlement, refunds, disputes, reconciliation, reserves, and support for the route you will use.
  • Open the official pricing, developer, support, or website links where available, then verify the exact production terms with the provider or PSP.
  • Do not treat public notes as final approval, final pricing, settlement timing, or a guarantee that your merchant entity can go live.

Official links to open

Commercial terms to confirm

Pricing modelwallet acceptance or psp priced
Pricing basisofficial public pricing or terms
Fields still to confirm
  • Fee range: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • FX markup: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Chargeback fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Payout fee: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Reserve policy: confirm with the provider, acquirer, PSP, or official documentation before launch.

Integration route to confirm

API / checkout routepsp wallet enablement
Fields still to confirm
  • SDK languages: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Sandbox: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Webhooks: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Idempotency: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • PCI scope: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • 3-D Secure: confirm with the provider, acquirer, PSP, or official documentation before launch.

Operational features to confirm

No public field in this group is complete enough to treat as confirmed. Use it as a due-diligence prompt.

Fields still to confirm
  • Recurring billing: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Marketplace split: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Partial refund: confirm with the provider, acquirer, PSP, or official documentation before launch.
  • Preauth / capture: confirm with the provider, acquirer, PSP, or official documentation before launch.

Public pricing signals are for initial screening only. Actual quotes can vary by country, industry, transaction volume, settlement currency, integration route, and contract terms.

Visit the official website