Frequently Asked Questions

Payment Gateway Africa is a payment gateway focused on local payment methods in Kenya, Egypt, Ethiopia, Senegal, Tunisia, Mali and Guinea. It accepts pay-ins, processes them, sends merchant settlements, and supports payouts where available for the method and project. The African payment gateway overview gives the wider picture.

A local gateway connects your checkout to the methods customers in each market already use, such as M-Pesa in Kenya or Wave in Senegal. Customers pay in the local currency and confirm the payment in the way that method requires. You do not need to build a separate connection for each provider.

No, they are three distinct flows. A pay-in is money a customer sends to you. A payout is money you send to a customer, where available for the method and project. Settlement is Payment Gateway Africa sending your collected funds to you.

The offer in the seven markets is built around the local methods listed on each country page. Card acceptance is not part of the standard proposal. If cards matter to your project, raise it during onboarding and we will tell you what applies to your case.

No. Postbacks and webhooks deliver operation statuses to you, the merchant. Payment Gateway Africa does not run a separate notification service for customers. Your own system decides what to tell the customer and when.

There are two. With the Hosted Payment Page, Payment Gateway Africa renders the payment step and your system handles orders and statuses. With the H2H API, your backend talks to the gateway directly. The guide to choosing an integration path compares the two.

No. H2H means your server connects to the gateway over the API. It describes how the connection works. It does not mean we supply a rebranded platform.

Yes. Your server creates payment requests, receives postbacks and confirms final statuses. Only the customer-facing payment step is hosted. See the Payment Gateway Africa API documentation for how requests and confirmations are structured.

No. Mobile flows run through a payment page in the browser. Your app can open that page and then rely on your backend for the final status.

Payment Gateway Africa sends postbacks to an endpoint you configure. Your handler should check that each notification is genuine, reply correctly, and cope with repeated deliveries. The webhooks and postbacks guide covers each of these steps.

Yes. Test traffic runs in a separate test project, with its own keys and project ID. On request, support sets the callback statuses you need, so you can check how your system handles each outcome. Use the integration testing guide to plan your scenarios, then switch to live credentials once onboarding is complete.

Detailed API materials and credentials are shared during onboarding, starting with a separate test project. The public developer documentation hub explains concepts, flows and terminology so your team can prepare in advance.

Seven markets: Kenya, Egypt, Ethiopia, Senegal, Tunisia, Mali and Guinea. Other countries are not part of the current offer. If you need a market that is not listed, use the contact form to tell us.

In Kenya, Payment Gateway Africa supports M-Pesa, with payments in KES. In Egypt, Payment Gateway Africa supports mobile wallet payments by phone number, with payments in EGP. Each country page gives the details for that market.

Ethiopian payments run in ETB through three methods: CBE Birr, M-Pesa (Ethiopia) and local transfers. Methods not shown on the Ethiopia payment page should not be treated as available.

Both markets use XOF. Senegal supports Wave and Orange Money. Mali supports Wave, Orange Money and Moov Money. See the Senegal page and the Mali page for how each flow works.

Guinea supports Orange Money, with payments in Guinean francs (GNF). Tunisia supports D17 and Flouci, with payments in TND. The Guinea page and the Tunisia page describe each route.

It depends on the method. With M-Pesa in Kenya, the customer confirms a prompt on their phone with their PIN. For other methods, the provider sets the confirmation step. The guide to mobile money payments explains how mobile money payments work through Payment Gateway Africa.

Payouts are offered where available for the method and project. Availability is confirmed for your specific setup during onboarding, so do not assume every method in every market supports payouts.

Payment Gateway Africa dispatches settlement funds on a same-day basis (T+0). T+0 marks the moment Payment Gateway Africa releases the money. The time it posts to your account varies by receiving bank.

Yes. Existing merchants can activate additional supported payment methods without any connection surcharge, and the count of active methods has no impact on the connection price. For an existing merchant, switching on a method Payment Gateway Africa already supports can often be completed within one day.

No. The no-fee rule covers only the connection of additional supported methods. Processing terms are set in your quote. Onboarding for new merchants follows its own process and is not covered by this rule.

Pricing is quoted for each merchant. The quote depends on factors such as your target markets, the methods you need and the operations you plan to run. Pay-ins, payouts and settlement are treated as separate operations. The Payment Gateway Africa pricing overview explains how to request a quote.

Our overall transaction success rate is 85%, measured as successful transactions divided by all transactions. This is a single figure for the whole product. It is not a figure for any individual country or method.

There are four stages: you submit an application, we carry out a KYB review, you build and test in a test project, and then you go live. The onboarding steps page lists what to prepare for each stage.

KYB checks confirm who we are working with and how the business operates before live payments start. Requirements are described in general terms in the merchant AML and KYC policy. Local rules in each market can add further checks.

The Payment Gateway Africa security overview covers four areas: how integration keys are protected, internal roles and multi-factor authentication, continuity and recovery planning, and incident handling. It also sets out which tasks belong to Payment Gateway Africa and which belong to the merchant.

Store keys only on your server, never in front-end code or in a mobile app. Limit who on your team can access them. Rotate them if you suspect exposure. The security practices for merchants list the full set of expectations.

Send us the transaction ID, the project ID, the country, the method, the approximate time and the status you saw. Do not include API keys, passwords or other secrets in your message. Use the support contact form and choose the request type that matches your issue.

First, confirm that your postback endpoint is reachable and replied correctly. Next, query the operation status from your server. Finally, see the Payment Gateway Africa status page for how incidents are communicated. If the gap remains, report it with the transaction ID.

The service status page explains how we communicate incidents and which components they can affect. During an incident, keep recording transaction IDs so the affected operations can be traced afterwards.

Check that your target markets and methods are listed, then submit an application through the Payment Gateway Africa application page. If you have questions before applying, contact the team.