Migration to Wajub
Guides for migrating your existing payment integration to Wajub or moving from one API version to another.
10 min read
Migrating to Wajub is designed to be progressive and seamless. Whether you're coming from another aggregator, a direct operator integration, or moving from one API version to another, these guides walk you through step by step.
Migration paths
- Migrate from another provider — replace your existing integration (Orange, MTN, Stripe, Paystack…) with Wajub.
- API upgrade — move from one major version to another without breaking your integration.
Dedicated support
For large volumes (> 1000 transactions/day), contact migration@wajub.com. Our team supports you for free: dual write, progressive roll-out, scenario validation.
Migration principles
Progressive approach
We recommend a three-phase migration:
- Dual write: your transactions are sent simultaneously to your old provider and to Wajub (sandbox). Validate results side by side.
- Progressive roll-out: redirect an increasing percentage of traffic to Wajub (10%, 50%, 100%) while monitoring metrics.
- Cutover: once traffic is stable on Wajub, disable the old provider.
What doesn't change
- Your business flows (checkout, confirmation, fulfillment).
- Your customer data.
- Your operator compatibility: Wajub covers the same networks (MTN, Orange, Wave, Airtel…).
What improves
- One contract, one API for all operators.
- Automatic orchestration: if an operator is down, fallback takes over.
- Normalized webhooks regardless of the underlying provider.
- A built-in debugging console (Konsole).