Contact us
/// Compare / Categories

Payment gateway vs payment orchestration

The two words are used interchangeably and mean different things. A gateway takes a payment: it presents the methods, authorizes, captures, and settles. An orchestration platform sits above gateways and decides which one to use for each transaction. Whether you need the second depends almost entirely on how many providers you already have — and why you have them.

Talk to usSee Protocore Gateway
/// Category vs category

What each layer is actually for

Dimension
Payment gateway
Orchestration platform
What it does
Takes the payment end to end — presents methods, authorizes, captures, settles, and produces the receipt and the payout.
Decides where a payment goes. It routes across gateways and acquirers you already have, and normalises their reporting.
Who it's for
Anyone who needs to accept money — from a single storefront to a business processing at scale.
Businesses already running several providers, usually for geographic coverage, redundancy, or rate arbitrage.
What it settles
Money. A gateway is in the payment path and produces the payout that reaches your account.
Nothing directly. Settlement stays with whichever underlying provider took the transaction.
Where the value is
Coverage and simplicity — one integration for every method your customers want to use.
Approval rates and cost — a percentage point of authorization, or a better rate on some corridor, multiplied by volume.
What it costs you
Per transaction, proportional to what you process.
A layer fee on top of the providers you're still paying — which only makes sense if the routing gains exceed it.
Integration burden
One integration, and the provider maintains the methods behind it.
One integration to the orchestrator, plus the ongoing commercial and technical relationship with every provider underneath it.
When it's overkill
Rarely — you need something in this layer to take money at all.
When you have one provider. Orchestrating a single gateway adds a fee, a dependency, and a layer of indirection for no routing gain.
/// 01

When a gateway is all you need

If you have one provider, or you're choosing your first, the orchestration layer has nothing to orchestrate. The gains it sells — routing between acquirers, cascading a decline to a second provider, arbitraging rates by corridor — all presuppose that you already run several relationships. Adding a layer above one gateway buys you a fee and an extra hop. What actually moves the numbers at this stage is method coverage, a checkout that converts, and clean reconciliation.

  • [ 01 ]You have one provider, or are picking your first
  • [ 02 ]Your conversion problem is method coverage, not routing
  • [ 03 ]You'd rather not manage several acquirer relationships
  • [ 04 ]One reconciliation model matters more than a point of approval rate
Protocore Gateway
/// 02

When orchestration earns its fee

When the volume is large enough that a fraction of a percent is real money, and you already hold several acquiring relationships because no single one covers your markets, your risk profile, or your rates. At that scale, routing by issuer and corridor, cascading soft declines to a second acquirer, and normalising reporting across providers stop being nice ideas and start being a line in the P&L. The prerequisite is the same in every case: multiple providers you have a reason to keep.

  • [ 01 ]You already run several acquirers for coverage, redundancy, or rates
  • [ 02 ]Volume makes a point of approval rate worth more than the layer's fee
  • [ 03 ]You need one reporting model across providers that disagree
  • [ 04 ]Failover between providers is a business requirement, not a nice-to-have
Run the gateway whitelabelGlossary
/// 03

Where Protocore fits

Protocore Gateway is the first layer — it takes the payment and settles the money — with the parts of the second layer that matter to a single-provider business built in rather than sold above it: routing policy you can read, a retry on an alternative route before the customer sees a failure, and decline reasons in language an operator can act on. If you reach the point where you genuinely need to route across acquirers you own, the whitelabel platform connects yours alongside ours. The honest summary is that most businesses asking this question need a better gateway, not a layer above the one they have.

  • [ 01 ]A gateway that settles, with routing and retry policy included
  • [ 02 ]Cards, wallets, bank transfer, and USDC on one page and one reference
  • [ 03 ]Your own acquirers connected alongside ours on the whitelabel platform
  • [ 04 ]No layer fee for orchestrating a single provider
Protocore GatewayRun it whitelabel

Which layer does your problem live in?

Tell us how many providers you run and where the payments are failing. We'll tell you whether the fix is routing or the gateway itself.

Talk to us