Glossary
Payment orchestration
Payment orchestration is the software layer that connects a payment business to many providers through one integration and decides, for each payment, which provider handles it: routing by rules, cascading on declines, one vault and one checkout across providers, and one journal and ledger for all of them. It replaces the adapters and glue code a payment company would otherwise build and maintain itself.
What orchestration adds to a gateway
A gateway connects a merchant to an acquirer. Orchestration sits above gateways and providers: it holds the rules that choose a provider per payment, retries declines on the next one, stores cards as tokens that work across acquirers, normalises statuses and callbacks, and reports on everything in one place. For a business with one provider in one country it adds little; with two providers or two countries it starts paying back in approvals and fees.
What it does not do
An orchestration layer holds no money, contracts with no merchants and replaces no licence. Settlement runs between the licensed business and its providers; the layer records it. The business that runs the layer stays the regulated party.
On the platform
Tranzify is an orchestration platform licensed to payment companies: the gateway API, the hosted checkout, the vault, routing and cascading in a visual flow builder, payouts, webhooks, white-label networks, the back office and the ledger, with journals kept five years.
Updated: 2026-11-08