Control what your payment providers actually charge you
Payment systems calculate their fees per transaction. This recalculates every one of them against your contract terms and reports the difference — so you find the discrepancies before they become the year’s margin.
| Provider | Txns | Contracted → charged | Variance |
|---|---|---|---|
| Card acquirer · EU | 128,442 | 1.40% + €0.25 | · |
| APM aggregatorapm_agg | 96,110 | 1.20% + €0.101.35% + €0.10 | · |
| Wallet provider | 54,908 | 0.90% | · |
| Card acquirer · LATAMacq_latam | 31,277 | 2.60% + $0.302.60% + $0.42 | · |
| Direct debit | 12,004 | €0.35 flat | · |
0 of 5 providers checked · 0 billing outside contract terms · illustrative output, not client data
Nobody checks the fees. There are too many of them.
A provider’s settlement file carries thousands of line items, each with a fee computed from a contract that has rates, fixed components, tiers, and terms that were renegotiated at least once. Checking them by hand means sampling — and sampling means the drift you didn’t sample stays in the provider’s favour, month after month.
The module checks all of them. Every transaction, every provider, against the terms as written.
The sample is the problem. Hand-checking reaches the ringed lines. Everything the sample missed is still billed, still wrong, and still invisible — and it repeats next month. Recalculation reads every dot.
The sample is the problem. Hand-checking reaches the ringed lines. Everything the sample missed is still billed, still wrong, and still invisible — and it repeats next month. Recalculation reads every dot.
How it works
Four steps. The first one is the reason finance agrees to it at all.
Your contract terms go in
Rates, fixed components, tiers and special conditions — entered through an interface your team already uses: Monday.com, SharePoint, or your own CRM. No new system, and no separate login for finance to learn.
Transaction data lands in the warehouse
Through Integration Gateway or SFTP, normalised into a consistent structure: provider, product, project, geography.
Every charge is recalculated
The fee the provider billed, against the fee your contract specifies — transaction by transaction, not sampled.
Differences surface as a report
By provider, product and geography: where the two disagree, and by how much. What you take back to the provider is your call.
Where the drift hides
A settlement file is not wrong in an obvious way. It is wrong in five quiet ways, and each one survives because nobody reads every line.
Rates that changed after a repricing — but only in the billing, not in your contract.
Fixed components applied where the contract specifies none — a per-transaction cent charge that was never agreed.
Volume tiers crossed without the discount arriving — you earned the lower rate; you were billed the higher one.
Charges on transactions that were declined or refunded — fees on money that never settled.
Fee lines that simply didn’t exist last quarter — new items appearing in a settlement file nobody reads line by line.
These are the categories the recalculation compares against. They describe what a line-by-line comparison can catch — not findings from any customer.
Architecture
A universal storage layer accepts data from any payment provider — whatever shape the settlement file arrives in. Internal optimisation tooling keeps processing fast at volume.
Source data is systematised into structures — providers, products, projects, geographies — that reporting and BI read directly. That normalisation is what makes a contract term and a billed charge comparable in the first place.
Deployed on-premise, on your SQL Server, inside your perimeter. This is a separate platform from the other Miraxtech products: you deploy it on its own, and it holds its own data.
Questions we get asked first
Why do contract terms go through Monday.com?
They don’t have to. The terms interface is whatever your team already uses — one production customer runs it on Monday, another on SharePoint. Any internal CRM works. The point is that finance never gets a new tool to learn.
What do we get out — a report, or something more?
A discrepancy report by provider, product and geography, on a warehouse your BI reads directly. What you take back to the provider is your call.
Where does our transaction data live?
In your own warehouse, inside your perimeter. Deployment is on-premise; Miraxtech holds no copy.
Ask what we’d find in your fee data
Send us the payment providers you work with and the contract terms you run them on. We’ll tell you what the recalculation would check against, and what it would take to stand it up on your side.