Providers
The Mobile Money operators, card networks, and bank integrations available through Wajub's orchestration engine — coverage, SLAs, and configuration.
Wajub connects to payment providers on your behalf. The orchestration engine routes each transaction to the best available provider based on your configuration, the payment's country/channel/currency, and real-time success-rate data.
Provider categories
| Category | Providers | Channels |
|---|---|---|
| Mobile Money | MTN MoMo, Orange Money, Wave, Airtel Money, Moov Money, M-Pesa, Safaricom | cm.mtn, ci.mtn, gh.mtn, ng.mtn, ug.mtn, rw.mtn, bj.mtn, cm.orange, ci.orange, sn.orange, ml.orange, bf.orange, sn.wave, ci.wave, ke.mpesa, tz.mpesa |
| Cards | Visa, Mastercard (via acquiring partners) | card |
| Bank transfers | Local bank transfers (CM, CI, SN) | bank_transfer |
Mobile Money — provider details
MTN MoMoMobile MoneyoptionalOrange MoneyMobile MoneyoptionalWaveMobile MoneyoptionalM-Pesa (Safaricom)Mobile MoneyoptionalAirtel MoneyMobile MoneyoptionalMoov MoneyMobile MoneyoptionalProvider priority and routing
Providers are enabled and prioritized per team from the Providers page in the Dashboard. The orchestration engine uses your priority tiers to determine which provider is tried first for each transaction.
- Priority (
integer) — determines order. Higher priority = tried first, always. Multiple providers at the same priority compete by tie-break scoring. - Weight (
integer) — used for traffic splitting within the same priority tier. - Circuit breaker — automatically disables a provider after repeated failures, re-enabling it after a cooldown. Visible in Konsole → Routing Log.
Configure providers in the Dashboard
Provider connection, priority assignment, and weight configuration are managed in Dashboard → Developers → Providers. There is no API endpoint to programmatically update provider priority — use the Dashboard or contact your account manager.
SLAs and expected latency
| Provider category | Typical confirmation time | Notes |
|---|---|---|
| Mobile Money (push) | 5–30 seconds | Customer must accept the push notification |
| Mobile Money (USSD) | 30–120 seconds | Customer completes the USSD menu |
| Wave | 10–30 seconds | App-based approval |
| Cards | 2–5 seconds | 3DS2 adds 10–30 seconds |
| Bank transfer | 1–24 hours | Asynchronous — webhook confirms |
Timeouts
A payment that doesn't complete within 30 minutes expires automatically with status expired.
The customer's funds are not debited on a timeout.
Adding a new provider
To request integration with a provider not listed here, contact your account manager or reach out to providers@wajub.com with the provider name and countries you need.
Was this page helpful?