The verdict in three sentences
Merchants stay stuck on an overpriced aggregator because migration feels scary. The safe 2026 method: run both in parallel (dual-run) then cut over gradually, with a 5 % traffic canary and a ready rollback plan. Executed well, migration saves 0.5 to 1.5 % in fees without losing a single payment.
The real risks and their fixes
Migration fear boils down to three things: losing card tokens, breaking webhooks, and interrupting subscriptions. Each has a proven fix.
| Risk | Without a plan | 2026 fix |
|---|---|---|
| Card token loss | customer re-entry, drop-offs | portable network tokens or vault export |
| Broken webhooks | statuses not updated | reconfigure + dual-listen during dual-run |
| Interrupted subscriptions | involuntary churn | re-link mandates before cut-over |
| Hard cut-over | spike of failures | gradual canary 5 % → 25 % → 100 % |
| No rollback | prolonged incident | one-click rollback to old provider |
Token portability is the most technical point: network tokens (at the card-network level) transfer, while a proprietary vault needs an export negotiated with the old provider.
The migration checklist with go/no-go gates
A successful migration isn't a big bang: it's a sequence of gates where you verify before advancing.
| Step | Duration (2026 order) | Go/no-go gate |
|---|---|---|
| Contract audit + vault export | 3-5 days | tokens confirmed exportable |
| New aggregator integration | 5-10 days | test webhooks validated |
| Dual-run (dual-listen) | 2-4 weeks | identical reconciliation on 2 systems |
| Canary 5 % of traffic | 3-7 days | success rate ≥ old provider |
| Ramp to 25 % then 100 % | 1-2 weeks | no failure spike, rollback tested |
| Decommission old provider | 1 week | 0 residual transactions |
The 2 to 4 week dual-run window is the heart of the plan: you process in parallel long enough to prove reconciliation is identical before routing real traffic.
Need a professional website?
Kolonell builds websites that attract clients, optimized for the Sénégalese market. Free quote in 2 minutes.
Mini case study
Salimata runs a fashion marketplace in Dakar processing 40,000,000 FCFA of monthly volume at 2.4 % fees. A new aggregator offers 1.4 %. The gain: 1 % of 40,000,000 = 400,000 FCFA per month. The migration, run as dual-run then canary over 6 weeks for about 900,000 FCFA of dev, is paid back in a bit over two months. Thanks to the 5 % canary, a misconfigured webhook is caught on just 200 test transactions and fixed before full cut-over: zero lost payments.
FAQ
Can you migrate without customers re-entering cards? Yes, if tokens are portable: network tokens transfer at the network level, and a proprietary vault can be exported by agreement with the old provider. That's the first gate to validate.
How long does a zero-downtime migration take? Expect 6 to 10 weeks total in 2026, including 2 to 4 weeks of dual-run. The slowness is deliberate: each go/no-go gate protects your payments.
What is a canary deployment? You first route 5 % of traffic to the new aggregator to compare the real success rate. If all is good, you ramp to 25 % then 100 %; otherwise, you roll back instantly.
What happens to subscriptions during migration? Direct-debit mandates are re-linked to the new aggregator before cut-over, to avoid involuntary churn. You test this re-linking during the dual-run.
Does the 0.5 to 1.5 % gain justify the effort? At meaningful volume, yes: 1 % on 40,000,000 FCFA is 400,000 FCFA a month, paying back migration cost within a few months then becoming pure gain.
Let's talk about your project. We audit your current contract, quantify the gain and run the dual-run migration without losing a payment. WhatsApp +221 77 596 93 33.
Mohamed Bah
Fondateur, Kolonell
Passionate about digital and entrepreneurship in Africa, Mohamed has been helping Sénégalese businesses with their digital transformation since 2020. Founder of Kolonell, he believes every SME deserves a professional and accessible online présence.
