Where unmatched transactions concentrate
Only the transactions left over after direct ID matching, bucketed by the fallback key. Shows which days / currencies / countries / types your unreconciled transactions pile up in.
How to read this table
- OnlySafe / EasierPay — how many leftover transactions each side has in this bucket.
- Matched here — how many got paired within the bucket. This is count-based only (the smaller of the two counts), so it's a diagnostic estimate, not a confirmed pairing like the ID matches.
- Extra OnlySafe — records you have that the provider has no charge for.
- Extra EasierPay — provider charges you have no record of.
- These leftovers are the same rows listed individually in the Unmatched tabs below — here they're aggregated so you can spot patterns.
| Group key | OnlySafe | EasierPay | Matched here | Extra OnlySafe | Extra EasierPay | Status |
|---|
Transactions recorded on OnlySafe with no EasierPay counterpart — money you expected but the provider has no matching charge for.
Charges on EasierPay with no OnlySafe counterpart — provider transactions your website has no record of.
Paired transactions whose amounts (or currencies) disagree — the same transaction recorded with different money on each side. Amounts shown in major units (OnlySafe cents ÷ 100).
Successfully paired transactions. ID = matched on provider_id; heuristic = matched on the fallback key.
Breakdown explorer
Slice matched vs unmatched by any field to find what the missing transactions have in common. A dimension with lots of unmatched and a low match rate is a discriminating factor worth investigating.
Daily trend
Transaction lookup
Search across every transaction — matched or not — by ID, provider ID, amount, date, country, platform… Matched rows show their counterpart's ID.