Glossary · payments and processing
What is payment orchestration?
Payment orchestration is a layer that sits between your checkout and several payment providers, deciding which one handles each transaction. Instead of integrating each provider separately, you integrate the orchestrator once and route from there.
Why businesses add a layer instead of another integration
Most companies do not set out to have several payment providers. They add a second one to cover a market the first refuses, a third for a currency, and a fourth when a contract expires. Each one arrives with its own API, its own webhook format and its own reconciliation quirks.
Orchestration collapses that. You build against one interface, and the routing rules decide what goes where. If a provider declines a transaction, the rule can retry it elsewhere. If a corridor is cheaper with a different provider, the rule sends it there.
The real prize is not routing though. It is that adding or removing a provider stops being an engineering project. That is what makes an orchestration layer worth its own cost.
Crypto usually enters a stack this way. A business that already has card acquiring adds a crypto provider for the customers cards keep failing, and the orchestrator decides which checkout the shopper sees.
Compare
Orchestration, gateway and processor, which get mixed up constantly
Three different jobs that vendors describe with overlapping words.
| Layer | What it decides | What it does not do |
|---|---|---|
| Orchestration | Which provider handles this transaction, and what happens if one fails | Move money. It has no licence and holds no funds |
| Gateway or processor | How this transaction is priced, confirmed and settled | Choose between itself and a competitor |
| Acquirer or CASP | Whether it is authorised to hold and move the funds at all | Decide your checkout logic |
In crypto the gateway and the authorised entity are usually the same company, which is why the words collapse into one. Ask which licence the entity holds rather than what it calls itself.
Where crypto fits in an orchestrated stack
Three things to settle before you route a single transaction through a crypto provider.
Crypto is a provider, not a fallback
Routing crypto only after a card declines wastes it. Shoppers who prefer crypto do not try a card first, so it works better as a visible option than as a safety net.
Frequently asked questions
Is payment orchestration the same as a payment gateway?
No. A gateway processes a transaction. An orchestrator decides which gateway processes it. A business can have one gateway and no orchestration, or several gateways and an orchestration layer above them.
Do I need orchestration to accept crypto?
No. If crypto is your only alternative payment method, one integration is simpler than two layers. Orchestration earns its place once you have three or more providers to keep in step.
Can CoinGate act as the orchestration layer?
No. CoinGate is a crypto payment provider, so it sits underneath an orchestrator rather than above one. If you want one vendor covering cards and crypto together, that is a card acquirer with a crypto add-on.
Does routing affect what I settle into?
Not at CoinGate. Settlement currency is an account setting, so it behaves the same however the transaction reached us. How settlement works