Supported gateways
Cartflox does not collect payments on your behalf: you connect your own aggregator accounts in Gateways, and each payment lands directly with them. This page lists what is supported and how your customer pays depending on the gateway.
Connect a gateway
Section titled “Connect a gateway”- In Gateways, pick the aggregator’s card, then Connect.
- Paste the keys of your aggregator account. The Verify button queries the aggregator immediately: a rejected key is never saved.
- Then enable its payment methods in Payment methods.
Some aggregators open one merchant account per country: Hub2 and Djamo Business are therefore connected country by country, with that country’s credentials on each card (“Hub2 Côte d’Ivoire”, “Hub2 Senegal”…).
Where the payment happens
Section titled “Where the payment happens”Unless stated otherwise, your customer stays on the Cartflox payment page (or on your own page with SoftPay): the request is pushed to their phone, they confirm it with their PIN, and the page updates on its own. Three other cases exist:
- Confirmation code: some operators require a code (Orange Money, Magma OnePay, Paystack Ghana and Kenya). It is entered on the page.
- App link (Wave Business, Djamo): these providers have no push request, the customer confirms in their app. The page shows an “Open Wave” or “Open Djamo” button (on mobile, it opens the app) and a QR code on desktop, then monitors the payment.
- Hosted page: a few aggregators and most card payments go through the provider’s page, then come back.
| Gateway | Countries | Where the payment happens | Outgoing transfers |
|---|---|---|---|
| PayDunya | Senegal, Côte d’Ivoire, Benin, Togo, Mali, Burkina Faso | On the page (request pushed to the phone) | Yes |
| PawaPay | Benin, Burkina Faso, Cameroon, Côte d’Ivoire, DR Congo, Ethiopia, Gabon, Ghana, Kenya, Lesotho, Malawi, Mozambique, Nigeria, Congo, Rwanda, Senegal, Sierra Leone, Tanzania, Uganda, Zambia | On the page (request pushed to the phone) | Yes |
| Hub2 (one gateway per country) | Côte d’Ivoire, Senegal, Benin, Mali, Burkina Faso, Togo, Cameroon | On the page (push request, code if needed); Wave: app link | Yes |
| Wave Business | Côte d’Ivoire, Senegal, Mali, Burkina Faso | App link: “Open Wave” button and QR code on the page, confirmation in the app | No |
| Djamo Business (one gateway per country) | Côte d’Ivoire, Senegal | App link: “Open Djamo” button and QR code on the page, confirmation in the app | No |
| PayTech | Senegal, Côte d’Ivoire, Mali, Benin | PayTech page prefilled with the number entered on the page, submitted automatically | No |
| Magma OnePay | Côte d’Ivoire, Senegal, Benin, Togo, Mali, Burkina Faso, Cameroon | Mobile Money on the page (confirmation code if the operator requires it); Wave and cards: hosted page | No |
| iPay Money | Niger, Benin | Mobile Money on the page (request pushed to the phone); cards: hosted page | No |
| FeexPay | Benin, Togo, Côte d’Ivoire, Senegal, Burkina Faso, Congo | Mobile Money on the page (request pushed to the phone); cards: hosted page | Yes |
| MonetBill | Cameroon, Senegal, DR Congo, Congo, Uganda | Mobile Money on the page (request pushed to the phone); cards: hosted page | Yes |
| FedaPay | Benin, Togo, Côte d’Ivoire, Senegal, Guinea, Mali, Burkina Faso, Niger | On the page (request pushed to the phone) | Yes |
| NotchPay | Cameroon, Côte d’Ivoire, Senegal, Benin, Togo, Burkina Faso, Mali, Guinea, Nigeria | On the page (request pushed to the phone) | Yes |
| Qosic | Benin, Togo, Côte d’Ivoire | On the page (request pushed to the phone) | No |
| Paystack | Nigeria, Ghana, South Africa, Kenya, Côte d’Ivoire, Egypt, Rwanda | Mobile Money Ghana and Kenya on the page (code by SMS); cards: hosted page | Yes |
| Flutterwave | Nigeria, Ghana, Kenya, Uganda, Tanzania, Rwanda, South Africa, Zambia, Côte d’Ivoire, Senegal, Cameroon, Burkina Faso, Malawi, Egypt | Provider’s hosted page | Yes |
| CinetPay | Côte d’Ivoire, Senegal, Mali, Togo, Benin, Burkina Faso, Cameroon, DR Congo, Guinea, Niger | Provider’s hosted page | No |
| Kkiapay | Benin, Togo, Côte d’Ivoire, Senegal | Provider’s hosted page | No |
| PayPlus | Benin, Togo, Burkina Faso, Côte d’Ivoire | Provider’s hosted page | No |
| LengoPay | Guinea, Morocco, Senegal, Côte d’Ivoire | Provider’s hosted page | No |
| Stripe | Cards, worldwide | Card entered on the page (embedded form) | No |
| Coinbase Commerce | Crypto, worldwide | Provider’s hosted page | No |
| Cryptomus | Crypto, worldwide | Provider’s hosted page | No |
Outgoing transfers (sending money to a Mobile Money account) use the same gateways: see Send money.
Webhooks to declare with the aggregator
Section titled “Webhooks to declare with the aggregator”Most aggregators receive the callback address with each payment. Three of them require it to be declared in their portal: the gateway’s configuration drawer shows it to you, in the form https://cartflox.com/api/webhooks/<gateway>.
| Gateway | Where to declare it | Secret to copy into Cartflox |
|---|---|---|
| Wave Business | Wave Business portal, Developers, Webhooks (checkout.session.completed and checkout.session.payment_failed events) |
The wave_xx_WHS_... signing secret provided at creation (optional: without it, each success is reconfirmed with Wave) |
| Djamo Business | charge/events topic with Djamo Business |
The signing secret, if you set one |
| iPay Money | Developers menu, Webhooks | The Secret-Hash you set there |
In all cases, a payment is never credited on the sole basis of an unsigned webhook: Cartflox reconfirms the success with the aggregator before notifying you.