Lumeo payments intelligence
Know what providers owe you. Know what you owe merchants. Know what you actually earned.
Continuous financial control for payment companies — built from reconciled transactions, not from spreadsheets.
- Provider
- Lumeo
- Controlled position
Diagnostic
Can you answer these questions right now?
How much money is currently unreconciled with your providers?
Which three merchants are destroying your margin today?
How much rolling reserve should be released today, this week and next month?
If your finance lead leaves tomorrow, who can explain the reconciliation model?
If the answer requires Excel, several people and a few hours —you do not have continuous financial control.
The problem
One payment. Multiple financial truths.
Between the transaction and the merchant balance, every step changes the number — and every system reports its own version.
- Transaction
- Provider
- Settlement report
- Bank / wallet
- Merchant balance
Finance rebuilds the truth manually — every day.
The Lumeo model
Four controls every PSP should have.
End-to-end reconciliation
Transaction → Provider settlement → Bank / Wallet → Merchant balance
Reconcile the exceptions, not the entire business.
Rolling reserve control
Held → Accrued → Due → Released
Per merchant: amount retained, rate and release date.
One controlled reserve ledger.
Merchant-level profitability
Revenue − provider fees − scheme costs − FX − chargebacks / refunds* = actual merchant margin
Know which merchants create volume — and which create profit.
*Cost components vary by PSP business model.
Fiat + stablecoin control
Fiat + USDT / stablecoins → one control model
One PSP control model across payment rails.
Inside the product
See how the controls work.
Short, unedited walkthroughs of the Lumeo product. Demo data only.
Any provider file. Mapped in seconds.
Every provider sends a different layout. Lumeo maps it to one financial model — without building a template for each new column order.
- Drop a file in any format — CSV, Excel or API feed.
- Similar fields connect automatically, even with different wording.
- Anything ambiguous waits for a person to confirm — nothing is guessed silently.
From upload to reconciled entries.
Imported transactions land in the ledger with their provider, status and currency — ready to be matched against settlement, bank and merchant data.
- System fields ↔ file columns, visible side by side.
- Import runs in the background; entries appear with status.
- Exceptions are routed with reason and owner, not buried in a sheet.
Merchant payouts, built from the ledger.
Know what you owe each merchant — and prove it. Lumeo calculates the payout act from reconciled ledger data, including reserve and fee components.
- Choose currency and counterparty — every payout act for the pair.
- Draft calculated from ledger data in seconds.
- Payout composition down to transaction level; export to Excel.
Every balance. Every currency. One view.
What you owe merchants and suppliers — and what customers and providers owe you — in each contract currency and in one base currency, including USDT.
- Balances sliced by counterparty and contract.
- Group by counterparty for totals; expand for each contract in its own currency.
- The same view for customers and suppliers, fiat and stablecoin.
The result
One controlled financial position.
Not another dashboard. A financial position built from reconciled transactions.
Provider receivables
How much each provider owes you.
Merchant payables
How much you owe each merchant.
Rolling reserve liability
What is held — and when it is released.
Confirmed cash
What actually arrived in banks and wallets.
Merchant margin
What you earned, by merchant.
Exceptions
What does not reconcile — and who owns it.
Exception-based finance
From manual reconciliation to exception-based finance.
Finance manually reconciles transactions.
Lumeo reconciles automatically. Finance investigates exceptions.
The goal is not to remove finance.The goal is to remove finance from repetitive matching.
Lumeo reconciliation flow of 10,000 transactions per day. Results depend on data quality, number of sources and scope.
How to start
Start with one payment flow.
You do not need to replace your finance stack to test Lumeo.
-
Baseline
One painful reconciliation flow.
-
Data
Provider, bank, wallet and merchant data.
-
Configure
Rules, fees, tolerances, exceptions.
-
Parallel run
Next to your current process.
-
Measure
Time, unmatched items, exceptions, effort.
- DecisionExpand or stop
Give us one difficult payment flow. We will show you what is currently invisible.
Architecture
Works above your existing stack.
No ERP replacement. A financial-control layer across existing systems.
Control layer
Enterprise deployment & data control
The customer controls the financial data.
Customer-controlled environment
Run Lumeo inside an environment your team controls.
Private cloud
Dedicated deployment for your organisation.
Role-based access
Access scoped by role, entity and function.
Audit trail
Every rule, match, override and approval is recorded.
Tenant isolation
Your data is logically separated from any other customer.
Data-location controls
Choose where financial data is stored and processed.
Availability of each option is confirmed per deployment. No certifications are claimed here.
Team
Built by a team that has done this before.
- 2012
- Banking
- Payments
- Processing
- Lumeo
transactions per day processed by systems the team has built and run before Lumeo.
Next step
Give us one difficult payment flow.
We will reconcile it next to your current process and show you unreconciled money, reserve exposure and merchant margin — measured, not promised.
or write to founders@lumeofin.com