Orchestration is what separates merchants who scale past $1M MTD from merchants who hit ceilings. A single MID has a velocity ceiling, a CB-ratio ceiling and a single-acquirer political ceiling. Orchestration removes all three by treating acquirers as fungible execution venues behind a unified API.
ApexPay FZ-LLC is a payments consultancy — we introduce merchants to licensed acquirers, gateways and alert networks, and we do not process payments or hold funds.
What an orchestration layer actually does
Routes each authorisation to the acquirer most likely to approve it (per BIN, currency, MCC, customer history).
Cascades declined transactions to a second/third acquirer in real time — recoverable approval lift of 5–12%.
Balances volume across MIDs to keep velocity profiles inside acquirer thresholds.
Detects acquirer-side issues (decline-code clustering, settlement halts) and shifts traffic before customers notice.
Tokenises cards once — same token bills any acquirer, no re-tokenisation on MID swap.
Unifies reporting — one CB rate, one approval rate, one settlement view across every MID.
Routing rules we deploy
BIN-based: US-issued → US acquirer, EU-issued → EU acquirer, etc.
Currency-based: settle in customer's currency, avoid cross-border interchange.
Issuer-based: known low-approval issuers routed via 3DS step-up automatically.
Volume-based: even distribution to keep MIDs warm without breaching velocity.
Cost-based: route to lower-MDR acquirer when approval probability is equal.
Risk-based: high-risk segments (new customer, high ticket, suspect IP) routed via tighter MID with 3DS.
Why high-risk needs orchestration more than low-risk
Low-risk merchants survive on a single Stripe account because Stripe's underlying acquirer relationships are stable. High-risk merchants don't have that stability — any single MID is one acquirer-policy-change away from frozen. Orchestration makes that decision survivable instead of fatal.
Build vs buy
Building orchestration in-house is feasible but expensive: PCI Level 1 vault, integrations into 5+ acquirers, real-time routing engine, CB unification, settlement reconciliation, plus ongoing acquirer relationship management. Most operators get to ROI faster by buying — and using the saved engineering time to grow the product.
Frequently asked questions
Can I bring my own acquirer relationships?
Yes. Our partner gateways route to any acquirer we have an integration for, including ones you've sourced directly. We add new acquirers in 2–4 weeks if not already integrated.
How much approval lift can I expect from cascading?
5–12% net authorisation lift is typical when moving from single-acquirer to multi-acquirer cascading. Higher in geographies where issuer-acquirer affinity is strong.
Does orchestration add latency?
Marginal — sub-200ms decision time on top of acquirer round-trip. Cascading on decline adds the second acquirer's auth round-trip only when the first declines.
Can I see per-acquirer performance?
Yes — real-time approval rate, decline reason distribution, CB ratio, MDR and settlement timing per MID. Webhook export to your BI stack.
Payment Infrastructure cluster
Part of the Payment Infrastructure cluster
Multi-MID architecture, orchestration, cascading, gateways and offshore vs domestic strategy.
