Methodology
How every number on this site is produced.
Every figure on this site comes from Reconora Research: a full-day run of Reconora’s engine on one anonymised merchant day. Each number has an internal source address, is stated with what it counts, and describes that day only — it is not an industry benchmark.
The data: one anonymised merchant day
One merchant day of payment traffic, anonymised at the merchant’s site before anything reached us. The merchant, its providers and the date are not named. On that day the engine read 1.5 million records from 96 payment providers and folded 790,948 events into 318,804 transactions.
Two scopes, named every time
| Scope | What it covers | Figures that use it |
|---|---|---|
| The full day | Every message the merchant exchanged with its providers | Message shapes, statuses, time formats, record balance, the Payment Chaos report |
| Reconciliation scope | The merchant’s deposit log (114,065 transactions) reconciled with notifications and statements | The four outcomes, shares of turnover, discrepancies, the spreadsheet comparison |
Shares of turnover are shares of the reconciliation scope. Counts of messages, rules and statuses describe the full day.
What one day can — and cannot — tell you
- It shows what happens, with exact counts: how many status values, formats and discrepancies one real day produced.
- It does not show how often across merchants, seasons or verticals. One day is one observation, not a distribution.
- Your day will differ. Your providers, currencies and statements set your own mix — which is why the pilot measures your own day.
- No money amounts are published. Percentages are shares of messages, rules or turnover in scope.
How a number gets onto a page
- Measured. The figure comes from the engine run, not from an estimate or a survey.
- Recorded once. Every figure lives in one file with its internal source address and the wording of its public source.
- Checked at every build. The site refuses to build if page text carries a number that is not in that file.
- Missing means missing. If a figure is not measured, its block is not shown — never as zero.
Open data
The structural figures are published as open data (JSON). Cite them as: Reconora Research (2026), one anonymised merchant day, reconora.com/payment-chaos.
Why some turnover is awaiting a statement
The awaiting share is turnover whose provider statement does not cover its hour yet. On one anonymised merchant day, 12.6% of turnover in the reconciliation scope was awaiting a statement. Statements arrive after the payments and follow each provider’s own period and time zone. Payments near midnight wait for the neighbouring day’s statement. Counting them as discrepancies would create false claims. Counting them as matched would hide money nobody has confirmed. We therefore report the awaiting share separately from the four outcomes. On a later run, the share shrinks as the next statements arrive. Payments with no final status are a separate count and are not part of this share. Why part of the day is always awaiting a statement
Editorial policy
Pages are written by Reconora Research and checked against the engine’s output before publication. We describe what the product does today; we do not present plans as features, and we do not claim certifications we do not hold. Weak spots are published with the rest — see how the anonymiser is tested.
Corrections
Found an error? Write to product@reconora.com. Corrections change the page’s “Updated” date.
Try it on one day of your data
One day of your data, reconciled, and the report stays with you whether or not you continue.
By Reconora Research · Updated