# Payments orchestration

Our [payments orchestration](https://monei.com/features/payments-orchestration/) layer lets you configure payment routing rules in your MONEI account.

With payments orchestration, you create **rules** that decide — per transaction — which payment processor handles the payment, which payment methods the customer sees, and whether to accept the payment at all. To route to an acquiring bank, you'll need a [TPV Virtual](https://docs.monei.com/onboarding/connect-redsys-tpv-virtual/.md#set-up) from that bank. To route to Stripe, you only need your Stripe account — see [Connect Stripe](#connect-stripe).

Once you've connected a processor, build your rules in [MONEI Dashboard → Settings → Payments orchestration](https://dashboard.monei.com/settings/orchestration): set the **conditions** that decide when a rule applies, choose the **action** it takes, and click **Save**.

## Connect Stripe[​](#connect-stripe "Direct link to Connect Stripe")

If you already use Stripe, you don't have to leave it to switch to MONEI. Connect your existing Stripe account with your **Stripe Secret Key** and keep processing card payments through Stripe — while you add [Bizum](https://docs.monei.com/payment-methods/bizum/.md), [Apple Pay](https://docs.monei.com/payment-methods/apple-pay/.md), [Google Pay](https://docs.monei.com/payment-methods/google-pay/.md), and other [local and alternative payment methods](https://docs.monei.com/payment-methods/overview/.md) through MONEI. You manage everything from a single MONEI dashboard.

To connect Stripe:

1. Open [MONEI Dashboard → Settings → Payment methods → Card](https://dashboard.monei.com/settings/payment-methods/card).
2. Add **Stripe** as a card processor and paste your [Stripe Secret Key](https://stripe.com/docs/keys).
3. Click **Save**.

Unlike connecting an acquiring bank, connecting Stripe doesn't require a TPV Virtual — your Stripe account is the processor.

Once Stripe is connected, you can:

* **Load-balance** card traffic by sending a percentage of payments to Stripe and the rest to another processor — for example, a 50/50 split — to spread volume or compare performance.
* **Route by rules** — send specific transactions to Stripe based on amount, currency, payment method, or country, as described below.

## How routing rules work[​](#routing-rules "Direct link to How routing rules work")

Each rule has **conditions** that decide when it applies and an **action** that decides what happens.

<!-- -->

**Conditions** — match a transaction on one or more of:

* **Amount** — for example, treat high-value payments differently
* **Currency**
* **Payment method** — card, Bizum, and so on
* **Country**
* **Shop name** and **description**
* **Transaction type** — including whether the payment is recurring
* **Fraud Detector score** — the transaction's [Fraud Detector](https://docs.monei.com/fraud-prevention/fraud-detector-how-it-works-configuration-and-best-practices/.md) risk score, once it has been calculated. The score is known after the customer pays, so rules using it apply at that later point — not when the payment page is first shown.

Combine conditions with **AND** (all must match) or **OR** (any can match), and group them.

**Actions** — when a rule's conditions match, it can:

* **Route to a processor** — send the payment to a specific connected processor or acquirer.
* **Split traffic** — distribute payments across processors by percentage (for example, 70/30) to balance volume or compare performance. The split is consistent for a given payment.
* **Hide payment methods** — remove specific payment methods from the customer's options.
* **Block a processor** — stop a specific processor from being used for the payment.
* **Force 3D Secure** — require 3D Secure authentication for the payment, on top of MONEI's dynamic 3D Secure.
* **Skip the 3D Secure challenge** — skip the 3D Secure challenge for the payment — for example, for trusted, low-risk transactions.
* **Trigger a fraud check** — run MONEI's [Fraud Detector](https://docs.monei.com/fraud-prevention/fraud-detector-how-it-works-configuration-and-best-practices/.md) on the payment, even when it wouldn't be checked by default.
* **Decline the payment** — reject the transaction.

A matching rule's action falls into one of these groups:

<!-- -->

Rules are evaluated in priority order. For routing, the first matching rule commits the processor; hide and block rules accumulate. If no routing rule matches, the payment uses your default processor.

## When rules are evaluated[​](#when-evaluated "Direct link to When rules are evaluated")

Rules run at two points, because some conditions are known before the customer pays and others only after they enter their card:

1. **Before the payment page** — using what's known up front (amount, currency, country), MONEI decides which processors and payment methods to offer. Routing, hide, and block rules shape what the customer sees.
2. **After the card is entered** — once the payment method (and saved card, if any) is known, routing makes its final processor choice for that payment, and a percentage split commits to one processor. This is also where rules that need the full picture apply — forcing or skipping 3D Secure, acting on the Fraud Detector score, and declining a payment.

<!-- -->

## Coming soon[​](#coming-soon "Direct link to Coming soon")

We're expanding what a rule can do. This is on the roadmap and not available yet:

* **Route to stores and points of sale** — split or force payments across different stores or points of sale, the same way you route across processors today.

## Common questions[​](#common-questions "Direct link to Common questions")

### What do I need to route to a specific acquirer?[​](#need-tpv "Direct link to What do I need to route to a specific acquirer?")

You need a TPV Virtual from an acquiring bank. Once connected, you can set routing rules per payment method in your dashboard settings.