Orchestration Layer

The orchestration layer is the software component within a payment architecture that sits above individual payment providers and manages the logic of how transactions are routed, optimized, and handled across the full provider ecosystem. It is the "intelligent middle layer" between a merchant's application and the payment gateways, processors, and services that ultimately process transactions.

An orchestration layer performs several functions simultaneously. It maintains the connections to all configured payment providers. It evaluates each transaction against routing rules and performance data to select the optimal provider. It handles provider failures through Failover Routing. It applies Decline Salvage logic when a transaction is declined. It manages the Payment Vault and Network Token lifecycle. It normalizes provider-specific response codes and data formats into a consistent structure that the merchant's application can process uniformly. And it provides the analytics and reporting infrastructure through which payment performance is measured and routing logic is refined.

The orchestration layer is distinct from any individual payment provider, it is provider-agnostic by design. It is also distinct from the merchant's application layer above it: the application determines what to pay and to whom, while the orchestration layer determines how that payment is executed most effectively.

Payments Orchestration Platforms like Spreedly deliver the orchestration layer as a managed, cloud-based service, the merchant accesses it through a single API integration and benefits from the platform's maintained ecosystem of provider integrations, vault infrastructure, and routing intelligence without building or managing the orchestration layer themselves.