Skip to content
Lumino

Enterprise · Orchestration

Payment orchestration: more than one processor, managed as one

Payment orchestration is a layer that sits between a business and several payment processors and decides where each transaction goes. Lumino’s platform routes across processors by rule, so a merchant is not dependent on a single account, a declined payment can be retried elsewhere, and all activity still appears in one set of reports.

Summarize with

Who it’s for

Who needs payment orchestration?

  • High-volume e-commerce

    Stores for whom an hour of downtime or a point of approval rate is significant.

  • Merchants in reviewed categories

    Businesses that cannot rely on one processor’s continuing appetite for their industry.

  • Platforms and portfolios

    Operators placing many merchants and wanting the best fit for each.

What gets hard

What goes wrong with a single processor?

  • Single point of failure

    An outage, a review or a change in risk policy stops revenue.

  • Declines you cannot retry

    A soft decline at one processor might be approved at another, but only if there is another.

  • No comparison

    With one provider you have no data on whether another would cost less or approve more.

How we work

How does payment orchestration work?

  1. Connect processors

    Two or more merchant accounts are linked to the platform.

  2. Set the rules

    Route by card type, amount, region, MID balance or other criteria.

  3. Route and retry

    Each transaction follows the rules. Eligible declines can be sent to another processor.

  4. Measure

    Approvals, costs and disputes are reported per route so the rules can be tuned.

What’s included

What does Lumino’s orchestration include?

This page describes the approach in general terms. Specific routing features are confirmed during scoping.

  • Routing across processors

    Rules-based routing managed in the platform, without changes to your checkout.

  • Multi-MID management

    Volume balanced across merchant accounts, with ratios tracked per MID.

  • Unified reporting

    One view across every processor in Reporting & Analytics.

  • Risk built in

    Dispute and VAMP monitoring per route. See Risk & Disputes.

  • Scoping before setup

    The enterprise team reviews your volume, processors and current setup, then confirms which routing features apply to your business. Start with contact sales.

  • Planned implementation

    Linking merchant accounts to the platform and testing before launch are planned with professional services, with scope and owners agreed before anything changes.

In practice

When does payment orchestration make sense?

  • An online store on one processor

    A high-volume online store runs every sale through one merchant account, so a review or an outage at that processor stops revenue. With Lumino, a second merchant account is linked to the platform and rules decide where each transaction goes, while activity from both processors still appears in one set of reports.

  • A merchant in a reviewed category

    A subscription business in a category that processors review closely does not want to rely on one provider’s continuing appetite for its industry. It is transparent with each processor about what it sells, balances volume across more than one MID, and follows dispute and VAMP ratios per MID so that trouble shows early.

  • A platform placing many merchants

    A software platform boards merchants of different sizes and business models and wants each one placed with a processor that suits it. Placement is worked through with the enterprise team during scoping, merchants are underwritten through Lumino’s partners, and the platform follows the whole portfolio in one reporting view.

How we work with larger teams

Scoped with your team, and written down before anything moves.

  • Scoped, then proposed

    We map your volume, channels and entities first, then put a proposal against your current costs.

  • Responsibilities in writing

    Which party handles card data, underwriting and compliance is set out in the Trust Center and in your agreement.

  • Moved in stages

    Locations, brands or merchant groups move in an order you agree to, not all at once.

  • A direct line to the enterprise team

    Start with contact sales and tell us what you are moving. We reply with the next steps.

Good to know

Routing can improve resilience and give declined payments a second path, but approval rates and costs depend on your business, your processors and the card issuers. Lumino does not publish or guarantee an approval rate.

FAQ

Payment Orchestration: questions, answered

What is payment orchestration?

It is software that connects a business to multiple payment processors and methods through one integration and chooses, by rule, how each transaction is processed.

Is orchestration the same as having a backup processor?

A backup processor is the simplest form of it. Orchestration adds rules for sending transactions to each processor in normal operation, not only when one fails, and reports on the result.

Does routing across processors break card network rules?

Routing itself is a normal practice. What the networks prohibit is using multiple accounts to hide disputes or fraud, sometimes called load balancing to evade monitoring. A sound setup is transparent with each processor about the business.

How does an orchestration engagement start?

It starts with scoping. Tell the enterprise team your volume, current processors and setup through contact sales, along with any risk issues such as holds, reserves or elevated disputes. We look at where relying on a single account leaves you exposed and confirm what routing would involve for your business before anything is connected.

How is orchestration priced?

Pricing is scoped to your volume and setup, so there is no published figure for orchestration. Processing costs also differ between the merchant accounts you connect. The enterprise team sets both out in a proposal after scoping. See the pricing page for standard plans, and talk to sales about yours.

Do I have to leave my current processor?

Not necessarily. Orchestration is built on two or more merchant accounts, and which accounts are kept, added or moved is decided during scoping. Whether an existing account can remain as one of the routes depends on that processor and your setup. Any migration is planned through professional services, with dates set in the implementation plan.

Who is responsible for compliance and card data with several processors?

Responsibility stays shared, as it is with one processor. Processing, tokenization and card data handling are provided through Lumino’s processor and gateway partners, and each merchant account keeps its own agreement and its own obligations. Being open with every processor about the business is part of that. See compliance and PCI.

How does reporting work across processors?

All activity appears in one set of reports, whichever processor handled the transaction. Approvals, costs and disputes are reported per route, and dispute and VAMP ratios are tracked per MID, so routes can be compared and the rules tuned. The views sit in Reporting & Analytics.

Who is orchestration not for?

A small business with one location and steady volume rarely needs it. One well-matched account is simpler and enough.

How is orchestration different from a standard Lumino account?

A standard account matches a business with one processing setup. Orchestration is for larger merchants and platforms that hold two or more merchant accounts and want rules for how transactions move between them, so it is scoped with the enterprise team first. A business that needs one account should start with Online Payments.

Summarize with

Stop depending on a single processor.

Tell us your volume and setup and we’ll show how routing would work.