Migration
Swapping the provider, or moving the version. Both run the same way.
Two very different jobs share this section. One replaces whoever is taking your payments today with Wajub. The other keeps Wajub and moves your integration from one dated version of the API to the next. Neither should ever be a big-bang deploy.
| You are | Read |
|---|---|
| Leaving Paystack, CinetPay, an operator API or your own code | Migrate a provider |
| Already on Wajub, moving to a newer API version | API upgrade |
The shape both migrations take
- 1
Mirror
Keep the old path authoritative. Send the same traffic to the new one in sandbox, and compare what comes back. Nothing customer-facing changes yet.
- 2
Shift
Move a percentage of live traffic to the new path, bucketed deterministically so a given order always lands on the same side. Raise it while the numbers hold.
- 3
Cut
Once the old path is carrying nothing, remove it. Delete the adapter, the flag and the credentials rather than leaving them to rot.
The shift step is the one people skip, and it is the one that saves you. A bucketing function on your order id gives you a dial with a hundred positions instead of a switch with two.
What does not change
Your checkout, your fulfilment and your customer records stay where they are. A migration replaces the call that takes the money and the message that confirms it, nothing else. If your payment logic is scattered across controllers, the first real task is putting it behind one interface, and that work pays for itself the moment you need to run two providers side by side.
What does change
| Habit from elsewhere | What Wajub does |
|---|---|
| Amounts in minor units | Major units, 25000 is 25,000 XAF |
| Polling for the final status | Webhooks, verified by signature |
| One integration per operator | One call, the channel chosen at processing |
| A confirmation the browser is trusted to deliver | A confirmation only your server can trust |
The last row is the one that catches teams coming from a redirect-only provider. The payer's return to your site is not proof of payment here, and never becomes proof.
Moving real volume
Above roughly a thousand transactions a day, write to migration@wajub.com before you start. Dual running, reconciliation and cutover planning are done with you.