The Orchestrator Decision: When to Add One, When You're Just Paying Twice
A four-variable diagnostic we run before any merchant signs an orchestration MSA.
Orchestration is the most over-pitched layer in modern payments. The deck always promises smart routing, cascading retries and a single integration. The reality, for a lot of merchants, is an 11-bps fully-loaded cost without a meaningful auth lift to match.
It's also genuinely transformative when the math fits. The decision isn't ideological — it's a four-variable model: cross-border volume, scheme mix, processor concentration risk, and your team's appetite for ongoing vendor management.
We walk every payments leader through the same diagnostic before they sign an orchestration MSA: where does your current routing actually break, what's the migration cost in engineering weeks, and what's the credible auth uplift net of orchestration fees and 3DS impact. About half the time the answer is 'add one now.' About half the time the right move is to fix your primary processor's settings first and revisit in twelve months.
Seeing this pattern in your stack?
Walk us through your environment. We’ll come back with the architecture critique that matters.