Skip to main content

​
Choose a payment gateway

Open Settings → Payments. Which gateways you are offered depends on your country, on account enablement, and on commercial onboarding with the provider. The catalog contains 25 gateway codes; 23 of them have a credential form in the current interface. Every gateway below has a setup guide of its own: what to collect before you start, the exact fields, the callback URLs, how a payment completes, and what each error means.

​
Current gateway catalog

​
Know before you choose

Four things decide whether a gateway will work for you, and none of them is visible from the marketplace card.
Three gateways cannot be set up through the interface today. MTN MoMo and Vodacom M-Pesa appear in the country catalog but render no credential fields. Airtel Money is the opposite — it has a working form, but no country offers it, so it never appears in the marketplace.Do not plan a migration onto any of these without talking to support first.

​
Where the payer authorizes

On their handset — Safaricom, Paybill, Till, Bank, Kopo Kopo, Centipid, Iotec, Relworx, Airtel Money, PawaPay, PalmPesa, ZenoPay, AzamPay, Hubtel, MTN MoMo, Vodacom M-Pesa. Nothing extra is needed in the captive walled garden. In a hosted checkout page — ClickPesa, Paystack, OPay, Monnify, PesaPal, PayPal, DPO, PayFast, Orange Money. The payer’s own browser must reach the provider, so a Hotspot subscriber who is not yet online cannot pay unless that provider is reachable pre-authentication. Allow it in the walled garden and test from a device that is genuinely not logged in.

​
Whether you need provider API keys

Paybill, Till, and Bank collect M-Pesa without any Daraja keys of your own — the prompt is raised with the platform’s Daraja credentials. They are real STK pushes, not printed instructions. Centipid Collections goes further and needs no provider account at all, with the balance paid out through Withdrawals. Every other gateway needs credentials from an account the ISP owns.

​
What completes a payment

A payment is only complete when the money is confirmed back to Centipid Billing. Gateways differ in how that happens — a signed webhook, a status poll, a capture call — and the failure mode is the same in every case: the payer is charged and never provisioned. Each guide names what to check first for that gateway.

​
Whether a linked router is required

Paybill, Till, Bank, and Centipid Collections refuse to send a prompt unless a MikroTik router is linked and online.

​
Configure a gateway

1

Complete provider onboarding

Obtain credentials from an account owned by the ISP. Confirm live versus sandbox status, settlement currency, supported country, and callback requirements with the provider.
2

Open Settings → Payments

Select the intended method and read its guide before filling the form.
3

Enter credentials safely

Paste each value into its matching field. Never reuse credentials from another ISP’s account, and never mix test and live values.
4

Save and complete verification

Switching may require an OTP or a confirmation dialog. Saving validates the form; it does not prove the provider accepts your credentials.
5

Test end to end

Use a controlled amount. Verify initiation, provider authorization, confirmation, the payment ledger, the subscriber’s package, the receipt, and finally settlement into your own account.

​
Switch an existing account

  1. Resolve or record pending transactions on the old gateway.
  2. Confirm the new credentials and callback configuration.
  3. Check captive walled-garden reachability for the new provider.
  4. Update payment instructions and subscriber communications.
  5. Switch during a monitored window.
  6. Run a controlled payment from both the captive portal and the customer portal.
  7. Retain the old reconciliation data according to policy.
See the credential reference for every gateway’s fields in one place, and Payment troubleshooting for symptoms that are not specific to one gateway.