Payment Service Providers
PSPs run on reconciliation. When it breaks, the merchant feels it first.
Every transaction generates settlement events across many systems. Scheme fees change quarterly. Chargeback lifecycles span 60–120 days across multiple systems. FX spreads are applied transaction-by-transaction. At PSP volume, basis-point variance is real money and merchant trust depends on getting it right at the line level, every time.
5–20 bps
Scheme fee variance per transaction
5–15%
Chargebacks won but never financially recovered
Quarterly
Scheme fee changes that invalidate fee engines
Structural failures in PSP finance & ops.
The structural problems that break manual reconciliation everywhere manifest at PSP scale with particular severity — because basis-point variance × billions in volume = real money, and merchant trust depends on every transaction settling correctly, every fee being justified, and every chargeback being followed end-to-end across systems.
Data Heterogeneity
Transaction logs, scheme reports, fee engine and bank statements all speak different languages
The transaction log holds the authorisation. The internal fee engine calculates expected fees per MCC and card type. Visa and Mastercard scheme reports arrive in their own formats with their own identifiers. Merchant agreements live as PDFs. Bank statements show net payouts. None of these systems share one identifier — and the reconciliation between expected and actual is always manual.
Every scheme fee, settlement and chargeback starts with manual cross-system mapping
Time Lag
Scheme fees change quarterly; chargeback lifecycles span months across systems
Visa and Mastercard publish interchange and assessment changes quarterly — manual fee engines lag by weeks. Chargeback lifecycles span 60–120 days across notification, representment, scheme arbitration and final financial recovery. By the time something is reconciled monthly, the scheme fee window has closed, the merchant statement is out, and the chargeback financial booking has drifted from the actual outcome.
Quarterly fee changes invalidate static fee engines; financial recovery breaks down
Header-Level Blindness
Batch settlement files hide per-transaction fee, FX and chargeback errors
A batch settlement file looks balanced at the header. But within: an interchange fee charged at the wrong tier, an FX spread applied above the contracted markup, a chargeback won in representment but never financially booked back to the merchant, a PCI fee increased without proper notice. At header level it all clears. At per-transaction level, 5–20 bps of overcharges and lost recoveries accumulate.
Basis-point variance compounds to real money at PSP volumes