What is an orchestration?

An orchestration is a routing flow that decides which processor handles each payment. You can define different routes based on payment, customer, or card variables, and add alternative processors that kick in if the primary one fails.

To learn more about payment orchestration, you can read this Academy article.

Before creating an orchestration

• You can only orchestrate card processors. Other payment methods like PayPal or Klarna are not orchestrable.
• The processors you want to use must be added and active in Connections.
• The processor cannot be in redirect mode. When adding it in Connections, make sure it shows "No redirect".

The orchestrations list

Go to the Orchestrations section in the left side menu. You will see two tabs: Active and Deactivated.

You can filter by trigger type using the All triggers dropdown.

How to create an orchestration?

• Go to Orchestrations and click "Create orchestration".
• The canvas editor will open. Enter the orchestration name in the top field.
• Choose the trigger for this orchestration.
• Build the flow by adding blocks from the canvas.
• When done, click Publish for changes to take effect.

⚠️ When publishing, changes take effect immediately across all Checkouts using that orchestration.

The canvas: how it works

The orchestration editor is a visual canvas. You can navigate by dragging and zoom with the trackpad scroll.

In the editor header you will find:

• Orchestration activation toggle.
• Last updated date and time.
• Editable orchestration name (center).
• Usage counter: how many Checkouts are using this orchestration.
• Undo and redo buttons.
• Publish button.

Triggers

When creating an orchestration, you first choose the trigger. It defines what type of payment will activate it:

• First payment: payments initiated by the user at checkout.
• Recurring payment: recurring charges from authorizations or subscriptions.
• Physical payment: payments made at a physical terminal (POS).

Blocks

There are two types: utility blocks (organize the flow) and action blocks (execute something on the payment).

Utility blocks:

• Route: splits the flow into branches based on conditions (works like a switch/case).
• Split traffic: distributes traffic between branches at configurable percentages.

Action blocks:

• Complete payment: sends the payment to a processor for processing.
• Execute 3DS: launches 3D Secure authentication independently from the processor.
• Create Network Token: tokenizes the card with the network scheme before processing.

The Route block

The Route block is the most powerful in the editor. It works as a switch/case: each condition you add is an independent output branch with its own flow.

When you add a Route block you will see:

• Condition 1, Condition 2...: each is a branch. Add more with the "+ Add condition" button.
• All others: fallback branch that runs when no condition is met. Always present and cannot be removed.

Within each condition you define the variables the payment must meet to go through that branch. Multiple variables in the same condition all need to be met (AND logic).

Available variables (31 total)

Operation (10): Price, Currency, Type, Language, Authorize only, MOTO, Partial approval, POS, POS Terminal, Fraud score.

Customer (9): Custom variable, Device type, OS, Browser, IP country, IP region, Country, Region, Email.

Card (12): Brand, Type, Level, Issuing country, Issuing bank, Wallet used, BIN, Network Token, Network Token attempt, Cardholder name, Expiry month, Expiry year.

How to edit an orchestration?

• Go to Orchestrations, click the orchestration you want to edit.
• The canvas editor will open.
• Make the changes you need and click Publish.

How to enable or disable an orchestration?

From the canvas editor, use the activation toggle in the header.

Updated on: 03/05/2026