Local methods, four countries

Accept local payments.
Across four markets.

Payment Gateway Africa lets you accept local methods from customers in Kenya, Ethiopia, Senegal and Egypt. Methods differ by country, so each market has its own supported options, and you connect through an H2H API or a hosted payment page.

Contact the team
  • Local methods differ by country
  • Choose H2H API or hosted page
  • Merchant settlements sent the same day
Local merchant illustration for payment gateway africa
Local methods. Connected to your business.
Built around local ways to payM-PesaCBE BirrWaveOrange

What Customers Can Use in Each Country

Supported payment methods differ by country, so customers in each market pay only with the local options supported there. A method available in one country is not automatically available in another. Pay-ins and customer payouts are also confirmed separately for each method and each project, so check both directions before you plan your checkout.

Kenya

Customers pay with M-Pesa, the only supported method here. As market context, mobile money operators in this country are authorized as payment service providers, and the Central Bank dates these services to 2007. Pay-ins and payouts are confirmed separately per project.

M-Pesa

Ethiopia

Customers can pay through birr P2P transfers, CBE Birr or M-Pesa. Birr P2P is a person-to-person transfer in birr, so present it to customers as a transfer option. As market context, Safaricom Ethiopia's M-PESA is licensed for mobile money services under a license dated 10 May 2023.

Birr P2P · CBE Birr · M-Pesa

Senegal

Customers can pay with Wave or Orange, the two supported methods in this market. As context, the Central Bank of West African States, the common issuing institution of the West African Monetary Union, is based in Dakar.

Wave · Orange

Egypt

Customers can use payment by phone number or fast payment by phone number. Both are phone-number payment methods, not mobile-money wallets, so describe them to customers by these names. Availability for pay-ins and payouts is confirmed separately for each project.

Phone-number payments

Two Ways to Connect Your Platform

You can connect through an H2H API or a hosted payment page. Either way, your team completes backend setup and handles payment statuses, so plan developer time before launch.

H2H API

Your backend connects directly to the API to send payment requests and receive results. It suits teams that want a server-to-server connection. You still need backend setup, status handling and record updates on your side.

Hosted page

Customers complete payment on a hosted payment page. A customer returning from the page is not proof of payment, so confirm the result from the status your backend receives. Android projects can open this browser-hosted page; it is not a native in-app checkout.

With either option, payment status is sent to your backend by postback. Your system then updates its own records, and that status, not a page return, should drive your order logic.

When Merchant Settlements Are Sent

Merchant settlements are sent on the same day, which is what T+0 means on this page. T+0 describes when the settlement is sent; it does not describe when funds are credited to your bank account. Settlement is also separate from the payouts you send to your customers. Account statistics and CSV reports help you check what was sent.

Illustration of a merchant settlement receipt and dispatch envelope
  • T+0 sending: the settlement leaves on the same day. Bank crediting is a separate step, so plan your cash flow around the send date, not an assumed credit time.
  • Not a customer payout: settlement sends funds to you. Customer payouts are a different flow, confirmed separately per method and project, so T+0 does not describe their timing.
  • Reporting: review statistics in your account and download CSV reports. Use them to reconcile settlements against the records your own backend updates from postbacks.

How Access and Incidents Are Handled

These controls cover how integration access is protected and how disruptions and incidents are planned for and handled on our side. Your team still manages its own systems.

  • API credentials: integration API credentials are protected. Store them only on your backend and limit who on your team can see them.
  • Multi-factor authentication and role-based access controls: both are used to limit who can reach systems. They are internal controls, not dashboard settings you configure.
  • Business continuity: continuity and recovery planning is in place, covering how operations are restored after a disruption that affects the service.
  • Incident response: a defined process covers detection, containment and resolution of incidents that affect the service, from first signal to closing the issue.

Common Merchant Questions

Discuss your integration
Does one payment method work in every country?

No. Methods differ by country, and M-Pesa is the only method supported in more than one market. Every other method is available in a single country, and pay-ins and payouts are confirmed separately for each method and project. Check the list before building checkout.

What does the 85 percent success rate measure?

It measures the overall transaction success rate: successful transactions divided by all transactions. It is not a rate for any single country or method, and it is not a service level agreement. Your own postback data and CSV reports show results for your project.

Can a business registered outside these countries apply?

Yes, a business registered outside the country can contact the team. Eligibility is not decided on this page; it is confirmed during onboarding. Share your company details, target countries and planned methods when you get in touch so the team can review your case. Multilingual technical support is available 24 hours a day for integration, payment processing and transaction checks. That is availability, not a promised reply time.

Who sets payment policy in Kenya and supervises payments in Egypt?

The Central Bank of Kenya sets policy for payment, clearing and settlement systems, and the Central Bank of Egypt supervises the national payment system under Law No. 194 of 2020. These are market context, not service features, so review local rules for each market you serve.