MyMercho / Settlement
The difference is found while it is still cheap to find.
Four stages between a day's trading and money in a merchant's account, each with somewhere for a mismatch to surface before it becomes a month of reconciliation.
Batch close
The terminal or the scheduler closes the batch. Totals are reconciled against stored transactions and any mismatch is reported before the batch is accepted.
Clearing
Cleared transactions are assembled into scheme clearing files and the core banking posting interface. Incoming files are ingested and matched.
Settlement
Positions are calculated per merchant, per institution and per currency, net of MDR and fees, and released to core banking and the accounting interface.
Reconciliation
Three-way reconciliation across terminal, switch and scheme records — which tells you not just that something is wrong, but which of the three is wrong.
Gross to net.
Reports the merchant can read
- Settlement and QR settlement reports per merchant, store, terminal, institution and currency
- Export and scheduling, so finance gets the same file every month without asking
- Operational dashboards by channel, merchant and terminal
- The scheduled report pack, delivered rather than downloaded
Figures illustrative.
A case, not an email thread.
| Stage | What happens | Merchant sees |
|---|---|---|
| Retrieval request | The issuer asks for evidence; the transaction and its lineage are assembled against the case. | A request, with what is needed |
| Chargeback | The debit is raised against the merchant and reflected in the settlement position at that stage. | The debit, on their statement |
| Representment | Evidence is submitted back within the scheme window; the case carries its own state and history. | The status, with the date |
| Write-off | Where the case is not defensible, the outcome is recorded and posted rather than left open. | The outcome, once |
Bring the spreadsheet. We will show you what replaces it.
Send us your merchant hierarchy, your MCC list and your fee plans. We come back with a migration shape, a roles and scoping model, and a delivery schedule.