Skip to main content

Payments orchestration

Our payments orchestration layer lets you configure payment routing rules in your MONEI account.

With payments orchestration, you create rules that decide — per transaction — which handles the payment, which payment methods the customer sees, and whether to accept the payment at all. To route to an , you'll need a TPV Virtual from that bank. To route to Stripe, you only need your Stripe account — see Connect Stripe.

Once you've connected a processor, build your rules in MONEI Dashboard → Settings → Payments orchestration: set the conditions that decide when a rule applies, choose the action it takes, and click Save.

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, Apple Pay, Google Pay, and other local and alternative payment methods through MONEI. You manage everything from a single MONEI dashboard.

To connect Stripe:

  1. Open MONEI Dashboard → Settings → Payment methods → Card.
  2. Add Stripe as a card processor and paste your Stripe Secret Key.
  3. Click Save.

Unlike connecting an , connecting Stripe doesn't require a — 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​

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
  • Fraud Detector score — the transaction's Fraud Detector 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 — 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 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​

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​

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​

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.