Product

What SyncPay actually does.

A tour of the pipeline: ingest, normalise, match, resolve, report. Each stage designed for messy, real-world payment data.

Ingest

All your payment data, arriving on its own.

Connect processors and banks once; SyncPay keeps pulling settlements, payouts, fees, refunds and disputes on schedule. No more downloading CSVs from six dashboards.

API connections to major processors and bank feeds
Scheduled CSV / SFTP / email ingestion for everything else
Automatic deduplication and format normalisation
Every raw record retained and traceable

Data sources merging into a single ledger

Match

Matching that survives contact with reality.

Real payouts are batched, netted, delayed and occasionally just wrong. The matching engine is built around those cases, not around the happy path.

⧉

Batch unbundling

A single payout is split back into its component sales, fees, refunds and adjustments, each matched separately.

≈

Tolerant matching

Rounding differences, FX drift and date offsets are handled by configurable tolerances instead of failing the match.

☰

Your rules, learned

Confirm an edge case once and SyncPay proposes a rule. Approve it and the case never comes back.

Resolve & report

A short queue for humans, a clean feed for the books.

Whatever can't be matched with confidence lands in the exception queue with full context: the records involved, the amounts, the likely cause. One click documents the resolution.

Exception type	What SyncPay shows you	Typical resolution
Missing payout	Expected settlement vs. bank feed gap	Flag to processor with evidence attached
Amount mismatch	Fee/FX breakdown against the invoice	Accept tolerance or post adjustment
Duplicate charge	Both records, side by side	Mark duplicate; refund tracked to closure
Orphan refund	Refund with no linked sale	Link manually once; rule proposed

Everything resolved flows onward as clean, categorised entries — ready for your accounting tool or a plain export.