To set up a payment gateway, open Settings → Payment Gateways and enable a provider, then enter the credentials it requires. Only the gateways you enable appear to customers in the captive portal, the customer portal, and payment links.
Supported providers
Mobile money and MNO collection
Airtel Money, MTN Money, Orange Money, Wave, ModemPay, PalmPesa, Campay, ClickPesa, ZenoPay, PawaPay, Snippe, IoTec Pay, JulyPay, OPay, Yo! Payments.
Kenya / M-Pesa
Mpesa with API Keys, KopoKopo M-Pesa, Paybill / Till / Bank and Pochi la Biashara, Stk Pusher Pay.
Cards and global processors
Stripe, PayPal, Paystack, Flutterwave, DPO Group, Pesapal, PayEx, PayFast, Netcash.
Other aggregators
Payguard MNO, UMS Pay, Waychit.
Configuring a gateway
Each gateway asks for its own set of values - typically keys, secrets, a shortcode or merchant number, an environment selector (sandbox or live), a currency, and the callback URL the provider should call. The available tenant gateway list depends on the providers exposed in your workspace; Cryptomus is not a tenant payment option. Follow the fields and provider instructions shown for the gateway you select. Some providers also require an IP allowlist for callback verification.
How payments confirm
There are two confirmation styles, and it matters when a payment looks stuck:
- Queryable - the platform can ask the provider for the current state of a transaction. This is what Recheck payment uses from Payments.
- Callback-only - the provider only reports the result by calling your callback URL, so the platform records what arrives rather than polling. If a callback never arrives, there is nothing to query; check the provider's dashboard and the platform's payment row together.