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. You can route payments to MONEI, which needs no setup, or to your own processors. 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.

Add rule opens the rule form. Name the rule, set its priority, pick the action, then add one condition per Rule — or group several with Nested group and combine them with AND or OR. The rule below hides PayPal when the amount is under €20 — one way to keep a payment method off small baskets.

To see all your rules as one diagram, and to edit them there, use the payment flow builder.

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. Under Connect a processor, click the Stripe row and paste your Stripe Secret Key.
  3. Click Configure.

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 MONEI or to one of your own processors (see Processors you can route to).
  • 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.
  • Offer or don't offer MONEI Flex — choose which card payments are offered MONEI Flex installments (see MONEI Flex rules).
  • 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, MONEI picks one of your eligible processors at random. MONEI counts as one processor in this draw, so with MONEI and one own processor each gets half of the payments. Exception: when MONEI Flex is active, a payment that MONEI Flex can finance goes to MONEI, unless a Don't offer MONEI Flex rule matches it.

Processors you can route to​

A routing rule (route or split) and a block rule name one of your processors:

  • MONEI — the processing you get under your MONEI contract (in Andorra, Creand). MONEI is one target for all payment methods: on a card payment it means MONEI's card processing, and on a Bizum payment it means MONEI's Bizum. To send only some payment methods to MONEI, add a Payment method condition to the rule. MONEI chooses how to process each payment it receives, and this never changes where your rules send a payment.
  • Your own processors — each Redsys TPV Virtual, Stripe account or PayPal account you connected, by the name you gave it. See Manage your card processors.

Target warnings​

A processor accepts only some payment methods. For example, a Stripe account does not accept Bizum. When a rule can match a payment method that its processor does not accept, the rule form shows a warning such as:

Stripe does not accept Bizum. Bizum payments skip this rule and every routing rule after it, and go to a random processor.

You can still save the rule. To remove the warning, add a Payment method condition so that the rule matches only the methods its processor accepts.

Rules with a processor problem​

The rules list and the rule form flag a rule when one of its processors cannot take payments now:

  • Stripe EU is disabled (or MONEI is disabled for Bizum) — the processor is turned off. Turn it on again in the payment method settings.
  • Redsys BBVA is unavailable — the processor cannot take payments, for example because credentials are missing.
  • Redsys BBVA was deleted (or A processor this rule uses was deleted) — edit the rule to choose another processor.

The flag also shows when the change was not made in your dashboard. Until you fix the rule, the payments it would send to that processor skip it and every routing rule after it, and go to a random processor.

MONEI Flex rules​

When MONEI Flex is active on your account, MONEI offers installments on every card payment that can be financed. With a MONEI Flex rule you choose which payments are offered installments:

  • Offer — offer MONEI Flex on the payments that match the conditions.
  • Don't offer — do not offer MONEI Flex on the payments that match the conditions.

The first MONEI Flex rule that matches decides. To offer MONEI Flex only between €150 and €3,000, add an Offer rule with that amount range, then a Don't offer rule with no conditions after it.

Things to know:

  • MONEI Flex applies only to payments routed to MONEI. A payment your rules send to one of your own processors is never offered installments.
  • A rule cannot lower the minimum. MONEI Flex is never offered below the minimum amount, even when an Offer rule matches.
  • MONEI Flex rules apply when the processor is chosen. A condition on the Fraud Detector score does not apply to them, because the score is not known yet.

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.

Payment flow builder​

Beta

The payment flow builder is in beta. It edits the same rules as the table on the Payments orchestration page, so a change you apply in one shows in the other.

The payment flow builder shows your rules as a diagram of the path a payment takes: from the payment, through your checks and routing rules, to the processor that handles it. To open it, go to Settings → Payments orchestration and click Payment flow builder. The button does not show on small screens.

Read the diagram from left to right:

  • Payment: every payment starts here.
  • Checks: the rules that do not choose a processor. These rules decline a payment, hide payment methods, block a processor, force or skip 3D Secure, trigger a fraud check, or offer or don't offer MONEI Flex. A MONEI Flex rule shows Only for payments routed to MONEI. Each one applies at the point described in When rules are evaluated: hide and block rules before the payment page, the others once the card is entered. This group shows only when you have at least one of these rules.
  • Rules: your routing rules, in the order MONEI evaluates them. Each card shows the rule's action and its conditions, for example Amount is greater than 1000,00. A rule with no conditions shows Match all transactions.
  • Default: applies when no routing rule matches. MONEI then picks one of your eligible processors at random.
  • Route and Split: where each routing rule sends the payment. A split shows the share of traffic that goes to each processor. The width of each line matches its share.
  • The processors that receive the payments, on the right. MONEI is one box with the MONEI logo. Your own processors show their name, with the processor details under it. A processor that cannot take payments now is greyed out, with its status: Disabled, Unavailable or Pending activation.

A card shows a warning when its processor is not available on your account, or when an earlier rule blocks that processor.

Add and edit rules​

  • Add a rule: click Add rule at the end of a group, or click an action in the Rule library on the left. The new rule goes to the end of its group.
  • Edit a rule: click its card, or open the card's menu and click Edit. The rule opens in a panel on the right, with the same fields as the Add rule dialog. Click Done to keep your changes.
  • Change a split: type a new share in the split. The other shares change so that the total stays 100%. Click the check mark next to the shares to keep them.
  • Change the order: drag a card up or down in its group, or use Move up and Move down in the card's menu.
  • Turn a rule on or off: use the switch on its card.
  • Delete a rule: open the card's menu and click Delete.

You can move the groups and processors anywhere on the canvas. Positions are saved only in your browser, and Reset layout puts them back. Rules managed by MONEI show as read-only.

Review and apply your changes​

Your edits do not change your live payments at once. They stay on the canvas as unsaved changes, and your payments keep using the current rules. A bar in the bottom-right corner of the canvas shows how many rules you changed, for example 2 unsaved changes:

  • Discard removes all your unsaved changes. The dashboard asks you first.
  • Review & apply opens the Review your changes dialog.

The dialog lists your changes under New rules, Removed rules and Changed rules. A changed rule shows what changed, for example Order changed, Turned off or, for a split, Stripe: 30% → 50%.

Click Apply changes to make your changes live:

  1. MONEI reads your rules again before it sends anything. If someone changed or deleted a rule you edited after you started, the dialog shows Some rules changed somewhere else and you cannot apply. Click Discard changes and start again from the latest rules.
  2. MONEI applies your changes one at a time. Removed rules and rules you turned off go first, and new rules go last. Saving... shows in the page header while the changes are sent.
  3. When all changes are applied, the dialog closes and Your changes are live shows.

If a change fails, MONEI stops there. The dialog shows how many changes were applied, for example 1 of 3 changes were applied. The other changes stay unsaved. Click Try again to apply them.

Each change goes live when it is applied

There is no single save for all your changes. Each change applies to your live payments as soon as MONEI sends it. If a change fails, the changes applied before it stay live.

If you leave the page with unsaved changes, the dashboard asks you first.

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​

Does the payment flow builder change how my rules work?​

No. It is a different view of the same rules. MONEI evaluates them in the same way, whether you edit them in the builder or in the table.

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 for each payment method in Settings → Payments orchestration.