H2H API
Connect your server directly through the H2H API integration. Your backend receives each status by postback, and you show the customer the result in your own interface.
Mobile money checkout
Payment Gateway Africa provides a payment gateway Kenya customers can use to pay your online store or platform with M-Pesa. Connect through an H2H API integration or a hosted payment page, with backend setup and status handling required.
Contact the team
Customers in Kenya pay with M-Pesa on this service, and it is the only payment method we support in that market. Plan your checkout around this single method rather than a list of local options. As market context, mobile money operators are authorized there as payment service providers.
Pay-ins and customer payouts are confirmed separately. Having M-Pesa on the coverage list does not by itself enable both, so confirm each direction with the team.
Choose the connection that fits your stack. Both options need backend setup and status handling, and payment status reaches your backend by postback.
Connect your server directly through the H2H API integration. Your backend receives each status by postback, and you show the customer the result in your own interface.
Send customers to a hosted payment page. You still complete backend setup and handle postback statuses. An Android project can open this page in a browser; it is not a native in-app checkout.
Merchant settlements are sent on the same day, known as T+0. That date describes when the settlement is sent, not when your bank shows the credit. A settlement is also separate from any customer payout.

Before live payments start, onboarding confirms your eligibility and you complete backend setup. The path differs for new merchants and for merchants already connected.
Describe your business, platform and target customers. A non-Kenyan business can contact the team too, and eligibility is confirmed during onboarding.
Build your H2H API integration or hosted payment page connection, then set up postback handling so your backend receives each payment status.
Existing merchants can add a supported method at no extra connection cost. Enabling an already supported method can be resolved within about one day.
Yes. It is the only supported method in that market, and the service offers no other local option there. Pay-ins and customer payouts are confirmed separately, so ask the team which directions apply to your account.
No. The 85% figure is the overall transaction success rate, calculated as successful transactions divided by all transactions. It is not a rate measured for one country alone, so read it as a service-wide figure.
The Central Bank of Kenya sets policy for payment, clearing and settlement systems. The National Payment System Act 2011 and the National Payment System Regulations 2014 cover payment service providers, and mobile money operators are authorized in that category.
Yes. Integration API credentials are protected, and access uses multi-factor authentication and role-based access controls. Share credentials only with the people on your team who build and maintain the integration. Raise your specific security questions with the team during onboarding. Multilingual technical support is available 24 hours a day for integration, payment processing and transaction checks. That is availability, not a promised reply time.