New here? Start with the overview.
If you already deal directly with your payment providers — you negotiate the contracts, you own the pricing, the money settles to you — but running the technology behind those relationships has become a job in itself, the Cashier is built for you.

What is a payment Cashier?
Merchant → ModoGate Cashier → Multiple PSPs
You keep everything commercial. ModoGate runs the technology and operations layer.
What changes for your team
Before, your application carries a separate integration for every provider — plus its own routing, monitoring, reporting and the maintenance of all of it, forever. After, it talks to one operational layer instead of five moving targets.
Without Cashier
- PSP A, B, C, D integrations
- Your own routing engine
- Your own monitoring
- Your own reporting
- Integration maintenance – forever
With the Cashier
- One operational layer
- Rule-based routing, built in
- Monitoring & failover handled
- Reporting out of the box
- ModoGate maintains the connectors
Example — routing
Orchestration isn’t just “connecting PSPs.” It’s making your infrastructure behave according to business rules — without your engineers touching five different APIs:
- Domestic card → PSP A (best domestic approval rate)
- International card → PSP B (stronger cross-border)
- PSP A unavailable → fail over to PSP C
- High-risk transaction → apply an extra risk check first
Example — PSP performance you can trust
ModoGate can show performance based on aggregated traffic across the platform, not just your own limited sample.
| PSP | Approval | Response | Decline | Availability |
|---|---|---|---|---|
| PSP A | 91% | 1.2s | 9% | 99.90% |
| PSP B | 87% | 0.8s | 13% | 99.80% |
| PSP C | 93% | 1.8s | 7% | 99.95% |
Illustrative figures. You might see 91% on your own volume and assume it’s fine — aggregated data can reveal PSP A behaves very differently for a specific country or card type. That feeds routing, negotiations, and early detection of deterioration.
What you own vs. what ModoGate owns
You own
- PSP contracts & negotiations
- PSP pricing
- Settlement
- Business policies
- Which PSP you use
ModoGate owns
- Integrations & connectivity
- Orchestration & routing
- Operational tooling & monitoring
- Integration maintenance
- Optional risk layer & analytics
Build vs. Cashier: the economics
The honest comparison is ModoGate vs. the total cost of continuously operating equivalent infrastructure. Suppose you process ~90,000 transactions a month across several PSPs:
Running it in-house
- Payment / backend engineers (×2) €6,000–10,000
- DevOps / SRE €2,000–4,000
- QA €1,000–3,000
- Payment-optimisation specialist €1,000–2,000
- Servers & infrastructure €1,000–2,000
- PCI DSS audit (~€20k / yr) ~€1,700
- Per month ≈ €12,700–22,700
One developer can’t build new connectors and maintain the live ones and cover on-call — so this is a team, not a hire. And it’s before you add a risk/fraud analyst or build the routing engine, reporting and risk tooling.
With the Cashier — Advanced
€8,500 / month
Includes 100,000 transactions (then €0.09 each), €0 setup. Connectors, orchestration, monitoring, maintenance, analytics and PCI DSS L1 all operated for you.

Illustrative monthly figures.
Lower volume? Pay-As-You-Go is €0.13/txn with no setup or monthly fee.
Higher volume? Enterprise is €16,000/mo including 250,000 txns at €0.07.
Published prices exclude one-time integration/dev work (standard integration €2,500) and are subject to ModoGate’s terms.
What happens when something changes?
| Situation | In-house | With the Cashier |
|---|---|---|
| PSP changes its API | Your developers investigate and update | ModoGate maintains the connector |
| You need a new PSP | Build a new integration | Use an existing connector |
| A PSP’s performance drops | Analyze your own limited data | Surfaced in performance analytics |
| Fraud pattern shifts | Build / adjust rules | Configure the risk layer |
| Routing needs to change | Modify your infrastructure | Adjust orchestration rules |
