Learn
What is the difference between payment orchestration and a payment gateway?
A payment gateway carries a transaction to an acquirer, while payment orchestration decides which acquirer should receive it and moves it to another one when the first is unavailable. This guide compares the two for in-person payments.
The short answer
The difference is that a payment gateway transports a transaction to an acquirer, while payment orchestration decides which acquirer or processor should receive it, according to a set of pre-set rules, and moves it to another one when the first is unavailable. A gateway is a connection. Orchestration is a decision layer across several connections.
Both terms are most often used for e-commerce, where a gateway takes card data from a checkout and an orchestration platform sits above several gateways and acquirers. In person, the gateway is the host that terminals send their authorisations to. An in-person payment orchestration platform takes that role for several acquirers at once and adds the rules that choose between them.
Switchio supports both. Its Payment Gateway carries each transaction to an acquirer, and the same platform orchestrates when there is more than one, so a merchant can start with one route and add others as configuration.
What a payment gateway does
A gateway receives the payment request from the point of sale, protects the card data and forwards the request to the acquirer or processor in the format that host accepts. It returns the approval or decline and keeps a record for the merchant's reports. Online, the request comes from a checkout page or an app. In person, it comes from the payment application on the terminal. Because card data passes through it, a gateway has to meet PCI DSS.
A gateway on its own usually serves one acquiring relationship per merchant account. Many acquirers and PSPs bundle their gateway with the acquiring contract and the terminals, which gives the merchant one party for pricing, devices and support. In person, the terminal software is often certified against that acquirer's host, so gateway, application and acquirer come as one package.
The limit is the single route. If that acquirer's host stops answering, the gateway has nowhere else to send the transaction. Moving to another acquirer can mean a new integration, new terminal software or new devices.
What payment orchestration adds
Orchestration gives the merchant independence from any single acquirer. The acquiring contracts stay in place, but none of them is wired into the devices. A merchant can run a different acquirer in each market without touching the terminals, and a retail chain can add an acquirer in a new country without changing the terminals in its shops.
It works by keeping connections to several acquirers and processors open at the same time and putting rules on top of them.
- Routing by card type, amount, merchant, terminal or country, so each transaction takes the route you set.
- Failover to a backup acquirer when the first one does not answer.
- Protocol translation, so each acquirer receives the message format it expects while the devices keep one integration.
- One place to add acquirers, domestic schemes, fleet cards and wallets as configuration.
- In person, terminal management and reporting across all acquirers and devices.
Payment orchestration vs payment gateway compared
The table compares the two on seven criteria, from what each one connects to who usually runs it. Two rows matter most in practice. Failover decides whether sales continue during an acquirer outage, and the effort of changing acquirer decides how much room the merchant has when a contract comes up for renewal.
| Criterion | Payment gateway | Payment orchestration |
|---|---|---|
| What it connects | A checkout or terminal to one acquirer or processor | Checkouts or devices to several acquirers, processors and payment methods |
| Number of acquirers | Usually one per merchant account | Several, chosen per transaction |
| Failover | Depends on that one acquirer being available | Automatic rerouting to a backup acquirer |
| Routing logic | A fixed route set up for the merchant | Rules by card type, amount, merchant, terminal or country |
| Device management | Separate from the gateway, often run by the acquirer | In-person platforms can include it for the whole fleet |
| Changing acquirer | Often a new integration or new terminal software | A configuration change on the platform |
| Typical owner | The acquirer or PSP, bundled with acquiring | The merchant or operator, or a bank or PSP serving many merchants |
| Best for | A merchant with one acquirer in one market and staffed counters. | Fleets with several acquirers, markets or device types, or sales that cannot stop when one acquirer is down. |
When a gateway alone is enough
For many merchants the gateway that comes with the acquiring contract is the right choice. Orchestration brings work of its own, because each acquirer behind the platform still needs its own merchant agreement, pricing and reconciliation, and the platform becomes one more party in every incident.
On Switchio this is the same platform with one acquirer behind it, so moving to orchestration later is a configuration step rather than a new project.
A gateway alone fits when these conditions hold together.
- One acquirer covers every country you sell in and the cards your customers carry.
- That acquirer processes every method you accept, including domestic schemes and any fleet or meal voucher cards.
- Payments happen at staffed counters, where a cashier can offer another way to pay while the acquirer is down.
- An occasional outage costs less than a second acquirer and an extra layer.
When orchestration pays off
Orchestration pays off when one of these conditions breaks. That happens with several acquirers across countries, unattended devices with no cashier to fall back on, methods outside the acquirer's scope, or a bank or PSP running a fleet for many merchants. The guide to what payment orchestration is covers these criteria in more detail.
Why the terms overlap in practice
Vendor names do not follow the definitions above. Some gateways on the market route to several acquirers and fail over between them, which makes them orchestration by function. On Switchio, the Payment Gateway is the switch at the core of the orchestration platform. It aggregates transactions from every terminal in the network, applies the routing rules and sends each one to the right acquirer or processing centre.
When you compare vendors, ask about behaviour rather than names. How many acquirers are live today, and in which countries? Can a routing rule change without a software release? What happens to a transaction when an acquirer stops answering? Who holds the terminal software and the keys? The answers show whether a system is a single route or a payment switch with routing on top.
How Switchio does it
Switchio connects terminals, SoftPOS phones and unattended devices to 40+ acquirers through its Payment Gateway, with routing rules, automatic backup routing and protocol translation. The rules look at the card type, the amount, the merchant or the terminal, and they are configuration rather than development. The terminal management system and the merchant portals run on the same core, and banks and acquirers can run the platform under their own brand.
ComGate, a Czech online payment gateway, built its own network of payment terminals on Switchio's payment application running on NEXGO devices.
Tell us how many acquirers and devices you run and we will tell you whether a gateway is enough.
Talk to an expertQuestions people ask
Is a payment gateway the same as a payment processor?
No. A gateway carries and protects the transaction between the point of sale and the processing side. A processor handles the authorisation and clearing messages for the acquirer, which holds the merchant agreement. One company can offer all three roles, which is why the terms get mixed up.
Can a payment gateway route to more than one acquirer?
Some can. A system that applies rules per transaction and moves traffic to a backup acquirer when one fails does the job of orchestration, whatever its name. On Switchio, the Payment Gateway works this way. It is the switch at the core of the orchestration platform.
Do we need orchestration if our acquirer offers high availability?
An acquirer's own redundancy protects against failures inside its systems. It does not help when the connection to that acquirer fails, and it gives no choice of route for cost or coverage. A second acquirer behind an orchestration layer covers both.
Does moving to orchestration mean changing acquirers?
No. Existing acquiring agreements usually stay in place, and the platform connects to those acquirers host to host. New acquirers can be added later as configuration. What changes is that the devices connect to the platform instead of to one acquirer's host.
- What is payment orchestration?Payment orchestration is a software layer that sits between the places where payments are accepted and the acquirers that process them, and decides for each transaction where it goes. This guide explains it for terminals, SoftPOS phones, kiosks and transit validators.
- What is a payment switch and how does it work?A payment switch is the system that receives authorisation requests from terminals and other devices, decides where each one should go and forwards it to the acquirer in the protocol that side expects. This guide covers what it does, its architecture and how to choose one.
- How do you manage a large fleet of payment terminals?You manage a large fleet of payment terminals with a terminal management system that keeps every device in one hierarchy, shows its live status and changes parameters, software and keys remotely. This guide covers Linux and Android fleets and how to roll out a new model.
Talk to Us
Connect with our team.
Share your current setup with us, and we’ll map out how it looks on one streamlined platform.
Other ways to reach us
Email
info@switchio.comPhone
+420 577 110 411
