Pricing
A licence a month, and a price per payment.
Three levels. Each one carries a monthly licence with an allowance of payments included, and a price in cents for every payment above it. We never take a share of what you route.
The three levels
What each level costs.
The licence covers one company.
What changes between the levels is how many providers
you can connect and how many merchant accounts you can open.
| What you pay for | Route | Cascade | Estate |
|---|---|---|---|
| The licence, each month | €1,900 | €4,500 | €9,000 |
| Payments included in it | 50,000 a month | 250,000 a month | 1,000,000 a month |
| Every payment above that | €0.05 | €0.03 | €0.015 |
| Providers you can connect | Up to three | Up to ten | No limit |
| Merchant accounts | One account, your own business | Up to five merchant accounts | Every merchant account you open |
| Runs under your own name | No | Yes | Yes |
| The licence, per payment, if you use the whole allowance | €0.038 | €0.018 | €0.009 |
| The integration fee, charged once | €6,000 | €6,000 | €6,000 |
Nobody is billed per seat. Your finance team, your support team and your engineers all get a login at every level, because the price is set on the payments we route and not on the number of people who read the screen.
The two parts of the price
Why there is a licence and a price per payment.
The licence pays for a board that is there whether you route ten payments or ten
thousand.
The price per payment pays for the work each one actually causes.
THE LICENCE
What it costs us to be ready
The connections stay open, the reports run, the ledger stays correct and somebody answers when you write. None of that gets cheaper in a quiet month.
THE ALLOWANCE
Most months you pay the licence and nothing else
The allowance at each level is set above what a business at that level usually routes, so going over it is meant to be the exception rather than the plan.
THE CENTS
A busy month costs cents, not a percentage
A payment costs the same to route whether it is worth ten euro or ten thousand, so that is what we charge for it.
A good month should cost you cents, not a share of it.
What we count
What counts as one payment.
This rule decides your bill, so it is written down rather than left to the invoice.
A
retry after a decline is free, which is the whole point of the second level.
| What happens | What it counts as |
|---|---|
| Money arrives from a customer | One payment, counted once when it succeeds. |
| The first provider declines and we try the next one | Nothing. However many providers a cascade walks through, you are charged for the one payment that came out of it. |
| A payment fails everywhere and no money moves | Nothing. We do not charge for a payment you did not take. |
| You send a payout or release a withdrawal | One payment. |
| You refund a customer | One payment, because a refund moves money and has to be routed. |
| Somebody opens a screen, runs a report or downloads an export | Nothing, at any level, however often. |
| A dispute opens, is fought and is closed | Nothing. The dispute lifecycle is part of the licence, and a bad month for disputes is already expensive enough. |
The integration fee
€6,000, charged once.
The fee pays for the connection between your systems and OrchesPay, built with your
engineers.
It is the same figure at all three levels, and it is charged once in the
life of the account.
| What you add | What it costs | Why |
|---|---|---|
| The first connection | €6,000 | Your team and ours connect your checkout, your back office and your accounting to the board, and we test it with real money in a sandbox first. |
| A second or third provider we already support | Nothing | We have built that connection already, so switching it on is a setting rather than a project. |
| A provider we do not support yet | €2,500, once | Somebody has to write and certify that connector. At Estate, two of these are included every year. |
| Moving from one level to the next | Nothing | A level is a line in the agreement, not a different build, so there is nothing to reconnect. |
The three levels
What Route, Cascade and Estate actually mean.
Every level gets the whole board.
We do not hold a feature back in order to sell you
the level above it.
LEVEL ONE · ROUTE
One company, one way to market
Up to three providers and one account, which is your own business. We set the routing up with you and change it when you ask, so nobody on your side has to learn it first.
LEVEL TWO · CASCADE
Your team writes the fallback rules
Up to ten providers and five merchant accounts, running under your own name. When a provider declines a payment, your rules decide who gets it next, and you change them yourself.
LEVEL THREE · ESTATE
Every account you open, with nobody counting providers
No limit on providers or accounts, a named engineer here, and a response time written into the agreement. This is the level for a platform running payments for other businesses.
The names describe what you are doing with the money. Route is one way to market. Cascade is the word your payments team already uses for trying the next provider after a decline. Estate is everything you run once there is more than one of it. We considered calling the top level Treasury and did not, because OrchesPay routes your money and never holds it, and a level called Treasury would say the opposite.
The other model
We do not take a share of what you route.
Several vendors in this market price their orchestration as a percentage of the money that
passes through it.
That fee grows every time you have a good month, and ours does not.
| What you route in a month | A routing fee of 0.3% | This page |
|---|---|---|
| 50,000 payments, about €3,000,000 | €9,000 a month | €1,900 a month, at Route |
| 250,000 payments, about €15,000,000 | €45,000 a month | €4,500 a month, at Cascade |
| 1,000,000 payments, about €60,000,000 | €180,000 a month | €9,000 a month, at Estate |
Read this table as an illustration and not as a quote from anybody. It assumes an average payment of €60, which is a figure we chose to make the arithmetic visible. The 0.3% is the middle of the range that review sites publish for the vendors who charge this way, and not a price any of those vendors publishes itself. Your own average payment is the number that decides whether this comparison holds for you, and we will run it with your figures on a call.
Where these numbers come from
Almost nobody in this market publishes a price.
We checked ten payment orchestration vendors on 11 August 2026, and two of them put a figure of any kind on their own website. One publishes a vault product starting at 750 dollars a month and sends you to a salesperson for the orchestration itself. One is open source and free, and costs you only the servers you run it on. The other eight publish a shape and a sales form. That is why the prices above are ours rather than a competitor's, and it is also why we publish them.
Every euro on this page is our own list price.
Questions
What buyers ask about the price.
Where did these numbers come from
They are our own list prices, set against the little the market publishes. The two figures we could read at a vendor's own website are a vault product starting at 750 dollars a month, and an open source orchestrator that is free to license and costs between 100 and 1,500 dollars a month in servers. Those two numbers are the floor and the entry point of this market, and Route sits above both of them because it is a run product with people behind it.
One vendor publishes the shape of its tiers without any prices, at ten thousand, one hundred thousand and over one million transactions a month. Our allowances sit in the same places, at fifty thousand, two hundred and fifty thousand and one million, because that is where operators in this market actually change size.
Three figures we found did not survive being checked, and we dropped all three rather than repeat them. A search result put two monthly prices against a vendor whose own pricing page reads Custom in every cell. A competitor's comparison page stated another vendor's setup and monthly fees and admitted in the same paragraph that it was inferring them. A blog gave a setup fee and a monthly fee for a third vendor whose own FAQ says every fee is agreed individually.
Is the per payment fee charged on top of what my provider charges
Yes, and so is everyone else's. OrchesPay routes payments to the providers you already have agreements with, and those providers still charge you their own rate. We do not sit between you and them on the money, and we do not take a cut of their fee.
This is worth doing the arithmetic on before you buy. Orchestration is worth its price when it wins back more in approved payments and lower provider fees than it costs, and on small volumes it will not.
What happens when we go over the allowance
You pay the per payment price for the payments above it, on the same invoice, at the rate for your level. There is no penalty rate and no cut off, and the board keeps working.
If you go over in three months out of six we will tell you, because at that point the next level up is cheaper for you than the overage is.
Do you charge us for a payment that failed
No. We count a payment when money moves. A declined attempt costs nothing, and a cascade that walks through four providers before one accepts is charged as the single payment it produced.
We chose that rule deliberately. If we charged per attempt we would earn more from your declines, and then our interests and yours would point in opposite directions.
Can we start at Route and move up later
Yes. A level is a line in the agreement rather than a different piece of software, so moving up takes effect on your next invoice and there is nothing to rebuild or reconnect.
Moving back down works the same way. We ask for a month's notice so that the accounts above the new limit can be closed or moved in an orderly way.
Are these the prices we will actually be quoted
These are our list prices and we publish them so that you can plan against them without a call. A very large operation is a conversation, and we will say plainly on the call if your case sits outside the list rather than let you find out later.
OrchesPay is before launch and onboarding its first merchants, which is a fact you can use. The prices above are set below the ranges that established vendors in this market are reported to charge, and we would rather say that out loud than pretend to a maturity we have not earned yet.
Put your own volume through this.
Thirty minutes. Tell us how many payments you route in a month and what an average one is worth, and we will price it against what you pay today before the call ends.
hello@orchespay.com