Payments glossary
Payment orchestration
Payment orchestration is a single layer between a merchant and many payment services - gateways, acquirers, methods and fraud tools - managed through one integration. It handles routing, failover, tokenisation and reconciliation across all of them from one place.
What an orchestration layer actually does
Concretely, orchestration means one API in front of many providers. It routes each transaction to the best processing path (smart routing), retries a failed payment on an alternative acquirer instead of losing the sale, holds card tokens in one vault so the merchant is not locked into any single provider, and pulls reporting and reconciliation from every connection into one consolidated view. Without it, each of those jobs is a separate integration and a separate operational headache.
Who actually needs orchestration
Merchants processing in multiple markets, where each market demands local acquiring and local payment methods; enterprises negotiating with several acquirers and wanting leverage between them; and any business for which one gateway outage means zero revenue. A single-market merchant with moderate volume usually does not need a dedicated orchestration platform - a capable payment service provider already bundles multiple methods, routing and reporting behind one integration.
Orchestration versus a gateway
A gateway connects a merchant to a processing path; orchestration coordinates many paths. The line blurs in practice, because modern providers absorb orchestration features. LekkaPay, for example, presents cards, Instant EFT, voucher payments and digital wallets through a single integration - one connection where a merchant would otherwise maintain several.
Last updated:
Payments without the jargon.
One integration, every way Africa pays - we'll handle the acronyms.