Skip to content

Platform modules

White Label Payment Orchestration for PSPs

Once a payment business works with more than one acquirer, someone has to decide where each payment goes. Doing that by hand, merchant by merchant, stops working at the second or third acquirer. Orchestration does it per transaction, by rules you set.

White label payment orchestration puts that layer under your own brand. You can run it for your own traffic, sell it to enterprise merchants as your product, or both. This page explains how the layer works, how rules and cascading behave, and what a PSP needs from an orchestration partner.

What a white label payment orchestration platform does

Think of it as a single layer that sits above your payment providers. It connects gateways, acquirers and alternative payment methods through one integration, decides which provider handles each transaction and retries failed payments through backup routes. It then pulls the reporting from every provider into one place.

Our orchestration platform works across a library of 700+ connectors plus any providers you already use. We don't process payments ourselves. The platform manages the providers that do, so your acquiring contracts and their pricing stay yours.

How a payment moves through the layer

Every payment follows the same short path, whichever merchant sends it. The difference between merchants lies in the rules applied at the second step.

  1. The payment arrives from the merchant's checkout, SDK or host-to-host call.
  2. Fraud filters and 3-D Secure rules screen it before it reaches any acquirer.
  3. Routing rules pick the provider most likely to approve it at the right cost.
  4. If the provider declines it, cascading can try another provider within the same payment attempt.
  5. The result goes back to the merchant, and the transaction lands in one report with every other provider's data.

Steps 3 and 4 are where orchestration earns its place. A payment that a second acquirer would have approved is revenue your merchant keeps.

Routing rules, with examples

Routing can use cost, region and card type, alone or together. The table shows the kind of rule PSPs set up first. The provider names are placeholders, not recommendations.

Rule Example Why you'd set it
By region Cards issued in the EU go to Acquirer A, others to Acquirer B Local acquiring often approves domestic cards more readily
By card type Amex goes to the provider with the Amex contract Only some providers can take every scheme
By cost Debit cards go to the cheaper provider for debit Spreads margin across your volume
By merchant One merchant's traffic uses its own acquirer setup Large merchants often negotiate their own terms
Failover A provider that goes down stops receiving traffic One outage doesn't take every merchant offline

Rules are set per merchant or merchant group, so a new merchant can start on a simple setup and move to finer rules as its volume grows.

Cascading without the pitfalls

Cascading retries a declined payment on another provider inside the same attempt, so the shopper never sees the first decline. Set it to retry declines another acquirer could reasonably approve, such as a technical error or an issuer timeout. A decline for a stolen card or a closed account should end the attempt, since retrying it only adds fees and risk.

Network tokenization helps here too. Stored cards are protected at the network level and stay usable when the issuer reissues the card, which keeps recurring payments from failing for reasons nobody can fix with routing.

One reconciliation across every provider

Each acquirer reports in its own format and on its own schedule. Without orchestration your finance team stitches those reports together every month.

The platform matches transactions across providers automatically and tracks settlement without manual work. Your team sees one set of figures for each merchant, whichever acquirers carried its payments.

Selling orchestration under your brand

Enterprise merchants with several PSPs want the same routing control you have. White label orchestration lets you sell it as your own product, with your brand on the dashboard and the payment page, and with your team as the merchant's contact.

That turns you into a white label orchestration partner for those merchants, not just one more acquirer on their list. Merchant onboarding, pricing and settlements for them run in the same merchant management system as the rest of your portfolio.

Deployment, regions and uptime

A white label payment hub has to stay up when individual providers don't. Ours runs on microservices spread over nodes in several geographic locations, with database replication, backups, automated monitoring and real-time alerts. SaaS comes with a 99.95% uptime SLA.

When data has to stay in a particular country, the hub can move into a cloud account you control with Google Cloud, Oracle Cloud, Azure or AWS, or onto dedicated servers. Cloud setup takes about 30 days and dedicated servers about 60. On SaaS with ready connectors, processing starts in about 5 business days on average.

Questions

What is the difference between a payment gateway and payment orchestration?

A gateway processes transactions. Orchestration manages several gateways and acquirers at once, deciding where each payment goes and retrying declines elsewhere.

Can I use orchestration with my existing acquirers?

Yes. You can connect the providers you already work with, use any of the 700+ ready connectors, and add a missing one in about 14 days.

Does orchestration move or hold the funds?

No. The platform manages the providers that process payments. Funds move between the acquirers, you and your merchants under your own contracts.

Can each merchant have its own routing?

Yes. Routing rules, fraud plans and payment methods are set per merchant or merchant group.

See your routing on a live platform

Bring two or three of your acquirers and a sample of your traffic mix, and we'll set up routing and cascading rules for it live.