One schema
for every
settlement report
Matchwright maintains open-source connectors to Baltic and CEE payment providers. Your engineers stop rewriting parsers, and month-end stops depending on who remembers how each report works.
| Line | Report, EUR | Ledger, EUR |
|---|---|---|
| Card payments (38) | 4 914,36 | 4 914,36 |
| Refunds (2) | −89,90 | −89,90 |
| Processing fees | −12,06 | missing |
| Payout to bank | 4 812,40 | 4 812,40 |
Each provider reports money its own way
Payouts arrive net of fees, and the fees sit in a separate report.
Matchwright splits every payout into gross, fees and net, so each part matches its own ledger line.
Refunds and chargebacks show up days later, in yet another file.
Late refunds and chargebacks are linked back to the original payment, whichever file they arrive in.
Timestamps follow the provider’s time zone, not your books.
Every record carries a UTC timestamp next to the provider’s original, so day boundaries line up with your books.
A column gets renamed without notice, and the parser breaks at month-end.
Each report is checked against its known format, so a changed file is caught before it reaches your ledger.
So every fintech writes and babysits its own connector for each provider. Matchwright does that work once, in the open, for everyone.
How it works
Connect a provider
Point a connector at the provider’s API or at the reports it exports, whatever the format or language.
Get one schema
Payments, fees, refunds, chargebacks and payouts come out as the same records, whichever provider sent them.
Reconcile in your own stack
Match the records against your ledger in your own database. The connectors run in your infrastructure, so transaction data stays with you.
Open source, with someone on call
Free and open
- A connector for each provider
- The shared record schema
- Sample reports to test against
Matchwright support
- We watch every provider for format changes
- Fixes ship as soon as a format changes
- A direct line to the people who maintain the connectors
A provider renames amount to gross_amount. What happens next?
On your own
- The report format changes
- Your parser skips the rows without an error
- The gap surfaces at month-end close
- An engineer drops everything to patch it
With Matchwright support
- The report format changes
- We spot the new format
- A connector update ships
- Your close runs as usual
Tell us which providers you reconcile
We’re choosing the first connectors now. Early partners decide which providers come first.
Request received
We’ll write to you once we pick the first connectors.