Migrate from another provider
A progressive, zero-downtime migration strategy to Wajub from an existing aggregator.
Migrating your payments should never interrupt revenue collection. This progressive approach lets you switch over smoothly, with the ability to roll back at any time.
Principle: route in parallel
Rather than a "big bang", let the old provider and Wajub coexist, and shift traffic gradually.
Steps
1. Integrate in test
Reproduce your current payment collection flow with Wajub test keys, without touching production.
2. Map your data
StatusesmappingoptionalReferencesmappingoptionalWebhooksmappingoptional3. Route a percentage of traffic
First route a small share (e.g. 10%) to Wajub via a simple application switch, and compare success rates in the Dashboard.
function choosePsp(order) {
// controlled ramp-up
return Math.random() < ROLLOUT_RATIO ? 'wajub' : 'legacy';
}4. Scale up
Increase the Wajub share as metrics confirm better results. Enable orchestration for automatic fallback — often Wajub alone replaces multiple direct integrations.
5. Decommission the old provider
Once 100% of traffic has been switched and is stable over several settlement cycles, remove the old integration.
Wajub often replaces several integrations
Where you maintained one connection per operator, the orchestrator manages several behind a single API. Migration is also simplification: less code, fewer dependency-caused outages.