Is multi-provider routing only for large merchants?
No. Large merchants were the first buyers, but PSPs, PayFacs and ISVs now offer multi-provider routing to merchants of every size, because the operator carries the integrations once for its whole portfolio. A small merchant gets fallback and local methods without running several provider contracts itself.
In detail
No. Large merchants were the first buyers, but PSPs, PayFacs and ISVs now offer multi-provider routing to merchants of every size, because the operator carries the integrations once for its whole portfolio. A small merchant gets fallback and local methods without running several provider contracts itself.
How it started
The first buyers of orchestration and routing were large merchants with several PSP contracts and in-house payment teams. They could afford the integrations and had the volume to negotiate with each provider. For a small merchant, running several providers made no sense.
What changed
- PSPs, PayFacs and ISVs now carry the provider integrations once, for their whole portfolio.
- A merchant on such a platform gets routing, fallback and local methods as features, not as projects.
- The operator negotiates with providers on aggregated volume, which a small merchant could never do.
What a small merchant gets
A payment that fails on one provider and succeeds on another, without knowing it. Local payment methods in its market, enabled by the operator. Cards stored as portable tokens, so a change of provider by the operator does not touch its customers. The merchant runs one contract, one integration and one statement. The economics work because the operator spreads the cost of multi-provider infrastructure across hundreds or thousands of merchants, which is also why operators treat routing as a product feature rather than an enterprise service.