A payment gateway sends a payment from checkout to one processor, while payment orchestration connects several gateways, PSPs and acquirers through one integration and decides which one handles each payment. The gateway encrypts card data, passes the authorization request toward the acquirer and returns the approval or decline. It neither chooses providers nor settles funds. Orchestration adds routing rules, failover and unified reconciliation on top.
The 2 are layers of the same card stack, not rival products. Almost every business starts with a gateway, usually bundled into a PSP contract, and adds orchestration once it runs more than one provider. Below, each layer is defined, then compared side by side, with a guide to when you need which. The last section covers a third layer that is often confused with both: cross-border payment orchestration, which moves the money itself rather than the card authorization.
What is a payment gateway?
A payment gateway is the part of the stack that lets a business accept card payments online. It sits between the checkout and the processor. Its job is to collect the card data safely, pass the authorization request along and bring the answer back.
The hosted vs integrated gateway choice comes down to 2 shapes. A hosted gateway sends the customer to a payment page the provider runs. An integrated gateway embeds the payment fields in the business’s own checkout, usually through the provider’s API or hosted fields, so the customer never leaves the site.
A card-not-present payment through a gateway runs like this:
- The customer enters card details at checkout.
- The gateway protects the card data with encryption in transit and, through tokenization, usually swaps the card number for a token.
- It sends the authorization request to the processor, which passes it over the card network, such as Visa or Mastercard, to the issuing bank.
- The issuer checks the card, the available funds and its own fraud models, then approves or declines.
- The response travels back along the same chain, and the checkout shows the result.
- Later, the business captures the authorized amount, often when the order ships, and the acquirer settles the funds into the merchant account, net of interchange, scheme fees and its own markup.
Not every decline is final. A soft decline, such as insufficient funds, a temporary issuer error or a request for authentication, can succeed on a later attempt. A hard decline, such as a closed account or a card reported stolen, should not be retried at all.
Most gateways do more than carry the request. They run fraud detection, from AVS and CVV checks to velocity rules and risk scores, and they trigger 3-D Secure (3DS) where the issuer asks for it or where regulation requires it, as under PSD2 strong customer authentication in Europe. They also tokenize the card number, so the business stores a token instead of the raw card data. That keeps most of its systems out of PCI DSS scope, the card industry’s data security standard. The catch is that the token normally works only with the provider that issued it.
A gateway on its own does not move money. That is the processor’s and the acquirer’s job, which is why the 3 are so often sold together and so often confused.
The life of a card payment
- Merchant
- Gateway
- Processor
- Acquirer
- Card network
- Issuer
The gateway carries the request, the processor sends it over the card network, and the issuer approves or declines. An approval puts a hold on the funds. No money moves yet.
What is payment orchestration?
Payment orchestration is a software layer above the gateways, PSPs and acquirers. The business integrates with the orchestration platform once, through one API, and the platform holds the connection to every provider behind it. A setup with several providers live at once is what the industry calls multi-PSP or multi-acquirer. Vendors also call the layer a payment orchestration platform (POP) or a payment orchestration layer (POL).
For each payment, the platform applies the business’s routing rules. Typical inputs are the card’s BIN (the first digits, which identify the issuer, the card type and the country), the currency, the amount, the payment method, each provider’s price and its recent authorization rate. Rules combined with live performance data are what vendors call smart routing.
When something goes wrong, the platform has somewhere else to go:
- Failover. If a provider times out or is down, the platform sends the payment to a backup provider instead of failing it.
- Cascading. If the issuer returns a soft decline, the platform can retry through a second acquirer, which may get a different answer, for example a local acquirer in a country where the business qualifies for local acquiring. Hard declines stay declined.
The other half is the card data. An orchestration platform keeps cards in its own vault, independent of any one processor, and many also store network tokens issued by Visa and Mastercard, which the networks can update when a card is reissued or expires. Because the token belongs to the platform rather than to a PSP, the same card can go to whichever provider the rule picks. That vault is what makes multi-PSP routing workable, and it is what lets a business leave a provider without asking customers to enter their cards again.
Fraud tools, 3DS servers and alternative payment methods plug into the same layer. Results from every provider come back in one format, which feeds reporting and analytics as well as reconciliation.
The full definition, with how it works step by step, is in our guide to what payment orchestration is.
Payment orchestration vs payment gateway: key differences
| Payment gateway | Payment orchestration | |
|---|---|---|
| What it is | The connection from a checkout to one processor | A layer above several gateways, PSPs and acquirers |
| Providers it works with | One processing setup | Several at once (multi-PSP) |
| Who decides the route | The provider | The business, through its own routing rules |
| When a provider fails | A single point of failure: the payment fails or waits | Failover to a backup provider |
| Soft declines | Retried, if at all, on the same provider | Can cascade to another acquirer |
| Fraud detection and 3DS | Built into one provider | Connected from one or several tools |
| Card data | Tokens held by the provider and tied to it | Tokens in a vault the platform holds, usable with any connected provider |
| PCI DSS scope | Reduced by the provider’s hosted fields and tokens | Reduced by the platform’s vault, which takes on the card data |
| Adding a provider or method | Usually a new integration | Usually configuration on the platform |
| Reporting and reconciliation | One provider’s data | All providers’ data in one format |
| Cost and setup | Processing fees only, lower setup effort | A platform fee and more setup, then fewer integrations to maintain |
| Typical user | A business selling in one market | A business with high volume, many markets or many payment methods |
Put simply, a gateway connects you to one processor, while orchestration works like a traffic controller that picks one of several for each payment.
The biggest difference is control. With a gateway, many processing decisions stay with the provider: which acquirer sees the payment, whether a decline is retried, how the data is stored. With orchestration, the business sets the routing rules, the retry behavior and the order in which providers are tried. That control is also the answer to vendor lock-in. A business whose cards sit in a provider-agnostic vault can move volume between PSPs as prices and performance change, instead of rebuilding its checkout to switch.
Payment gateway vs payment processor: where do PSPs fit?
The difference between a payment gateway and a payment processor is that the gateway carries the payment data and the processor moves the money. The rest of the cast fills in around those 2:
- A payment processor runs the transaction itself. It sends the authorization message over the card networks, handles clearing and drives settlement on behalf of the acquirer.
- An acquirer, or acquiring bank, holds the merchant account, takes on the merchant’s risk and pays out the settled funds. When a cardholder disputes a payment, the issuer raises a chargeback through the card network, and the acquirer debits the merchant until the dispute is decided. The processor and acquirer run that chargeback and representment flow, not the gateway.
- The issuing bank is the cardholder’s bank. It approves or declines each authorization and funds the payment.
- A payment service provider (PSP) bundles a gateway, processing and often a shared or aggregated merchant account into one contract, so a business can start taking payments without opening a merchant account of its own.
- A payment aggregator is a PSP that onboards many small merchants under its own master merchant account. A payment facilitator (PayFac) works the same way under a formal card network registration, and is often a software platform that onboards its own customers as sub-merchants.
- A merchant of record (MoR) is the legal seller of the transaction. It is usually responsible for sales tax, refunds and chargebacks, which is why some platforms take that role for the sellers they serve.
So the stack, from the checkout down, reads: orchestration layer (optional), then one or more gateways or PSPs, then processors and acquirers, then the card networks and issuing banks. A business with one PSP has no orchestration layer at all. A business with an orchestration layer still has PSPs and acquirers underneath it.
Where each layer sits
- CheckoutThe customer pays
- Orchestration layerRouting rules, failover, 1 set of reports
- Gateways and PSPsSeveral, picked per paymentPSP APSP BPSP C
- Processors and acquirersAuthorize and settle
- Card networksVisa, Mastercard and the rest
- Issuing bankApproves or declines
When is a payment gateway enough?
A single gateway, or a single PSP, is usually the right choice when:
- You sell mainly in one market, where one strong provider supports the cards and payment methods your customers use.
- Your team is small, and the time spent managing several providers, contracts and settlement files would cost more than it saves.
- Your volume is modest, so a few points of authorization rate or a short provider outage do not move your revenue much.
- Your provider’s rate is already competitive for your mix of domestic and cross-border cards.
In this situation, orchestration adds a layer to set up, pay for and run without solving a problem you have. A second PSP held as a manual backup is often enough insurance.
Orchestration also costs more than its fee. It needs staff with the skills to run it and changes to existing workflows, and it adds one more provider whose outage can affect every payment. Data protection rules such as GDPR apply alongside PCI DSS.
When do you need payment orchestration?
Orchestration starts to pay off when:
- You sell in many countries and want local acquiring in each, along with alternative payment methods (APMs) such as digital wallets, bank transfers and buy now, pay later (BNPL).
- Your volume is high enough that declines and outages show up in the numbers. Each lost authorization is a lost checkout, so a lower authorization rate pulls your conversion rate down with it.
- One provider has become a single point of failure, and one outage, risk review or contract change could stop your payments.
- You want to add or switch providers, or move volume between them on price, without rebuilding your checkout each time.
- You want card data in a vault you can take with you, rather than in tokens tied to one PSP.
If several of these apply, the next question is build vs buy. A few very large merchants build their own routing layer. Most compare platforms first. Our platform comparison lists card orchestration options as well as cross-border ones.
Where does cross-border payment orchestration fit?
Gateways and card orchestration both serve the same moment: a customer paying a business. Their job ends once the payment is captured and settled into the merchant account.
Many businesses also need to move money the other way, or across a border: paying sellers, suppliers and contractors abroad, collecting in one currency and delivering in another, or moving funds between their own accounts in different countries. Most of that money does not travel on card networks, although services such as Visa Direct can push some payouts to cards, bank accounts and wallets. It runs on bank rails such as SEPA, Faster Payments, ACH, Fedwire and SWIFT, and increasingly on stablecoin rails. Each corridor, a pair of countries and currencies, has its own rails, cutoffs and FX cost. Neither a gateway nor a card orchestration platform handles it.
That is the job of cross-border payment orchestration. It routes the money itself: where it comes from, which rail carries it, how the currency is converted, which compliance checks run and how it is delivered.
| Payment gateway | Card payment orchestration | Cross-border payment orchestration | |
|---|---|---|---|
| Moment it serves | A customer paying at checkout | A customer paying at checkout | Money moving between people, businesses or countries |
| What it routes | One card payment to one processor | One card payment across several providers | The money itself, across rails and currencies |
| Rails | Card networks | Card networks and local payment methods | Bank rails and stablecoin rails |
| Price | Processing fees, interchange and scheme fees | A platform fee on top of each provider’s processing fees | The FX spread plus rail and provider fees |
| Main outcome | The payment is authorized | More payments approved, at lower cost | The right amount arrives in the right account and currency |
Nodu works in the third column. Its API takes money in from a bank account through pay-ins, from a crypto wallet or from a balance held with Nodu, and delivers it to a bank account or wallet through payouts. Where the corridor needs it, the money crosses the border as stablecoin in minutes, without correspondent banks or pre-funded accounts, and on fiat-to-fiat routes both ends only see fiat. AML and sanctions screening run inside the payment, which pauses and resumes on its own. A quote locks the exchange rate and every fee for 15 minutes, so the amount shown is the amount that arrives, and a payment that does not match its quote is refused rather than repriced.
Nodu Digital SIA holds a payment institution license and a MiCA CASP license from Latvijas Banka, and Nodu Canada Inc. is registered with FINTRAC as a money services business. Nodu does not offer a gateway, a checkout or card acquiring, and it does not route card payments. A business that accepts cards keeps its gateway or orchestration platform for that, and uses Nodu for the money it sends across borders. The cross-border payment orchestration page shows the whole route, from quote to delivery.
Do you need orchestration?
- 01Do you accept cards or local methods through more than 1 PSP or acquirer?
- 02Do declines or provider outages cost you sales today?
- 03Do you send money across borders, for your customers or to suppliers?
- 04Do you need the price of a cross-border payment fixed before it moves?





