PSPs and PayFacs talk about acceptance rates, routing, and product breadth. Internally, many teams spend just as much time on something less glamorous: explaining where the money went. The reason is that payments businesses operate across multiple ledgers at once, and reconciliation is the system that keeps those ledgers from drifting apart.
In a PayFac model, the unit of complexity is not a transaction. It is a sub-merchant lifecycle. Every sub-merchant has pricing, reserves, payout schedules, disputes, refunds, and adjustments. The moment you scale beyond a small number of merchants, reconciliation stops being “accounting hygiene” and becomes the operating system for margin and risk.
Networks and platforms are explicit about how real these responsibilities are. Stripe’s PayFac guide highlights that PayFacs take on duties like sub-merchant payout handling, chargebacks, and reporting and reconciliation responsibilities. Visa’s materials for payment facilitators and marketplaces focus heavily on risk obligations and oversight expectations.
That operational reality comes with a few numerical facts that are easy to underestimate.
The numbers behind the complexity
First, disputes can come long after a transaction. Visa dispute rule documentation includes examples that reference “a 120-day dispute window for certain dispute conditions.” From an operator point of view, that means “final” is a fuzzy concept. You can have revenue today that becomes a liability later, and that liability must be tied back to the original event cleanly.
Second, ACH has return-rate thresholds that create compliance pressure for payouts or collections flows. Nacha’s guidance sets “an unauthorized return rate threshold of 0.5%” and defines the covered return reason codes. It also establishes an administrative return rate threshold of 3.0%. And it sets an overall return rate level of 15.0%, noting that this is far above a historical industry average of about 1.42% in 2013. Even if your business never gets close to those levels, the effect is the same: returns are monitored, and high exception rates have consequences.
Third, the finance world in general still spends significant time reconciling. A 2025 benchmark found that “27% of teams take more than 7 business days to close, and only 18% close in 1 to 3 business days.” For payments companies, the pain is sharper because you do not get to wait until month-end. Merchants care about payouts on schedule. Partners care about controls continuously.
What breaks most often inside PSP and PayFac operations
Net settlement variance
Gross volume is easy to tie out. Net is where the surprises live. Network fees, processor fees, pricing tiers, and adjustments create small differences that become meaningful at scale. Many teams reconcile net by sampling. That works until it does not — usually when margin dips and no one can explain why quickly.
Reserve accounting
Reserves are liabilities that move. If reserves are computed as formulas rather than tracked as ledger events, you can get into situations where balances look correct until a dispute spike reveals that the liability view was optimistic.
Lifecycle mismatches
Refunds, reversals, chargebacks, representment outcomes, and timing differences across reports. Visa’s dispute management guidelines exist because disputes are detailed and procedural, and because lifecycle discipline drives outcomes.
From matching to learning
The companies that scale do something deceptively simple. They stop treating reconciliation as a one-time matching job. They treat it as a learning system.
Matching is the start. Explanation is the point. A good reconciliation engine produces reason codes and categories that reduce repeats. If 40 mismatches are really one schema change or one merchant behavior pattern, you want the system to tell you that — not dump 40 rows on your team.
Over time, reconciliation becomes the control plane for everything that matters: margins you can defend, liabilities you can explain, and partner relationships you can sustain.
Methodology and Sources: This note synthesizes public network guidance, industry platform materials, and finance benchmark data. Sources include Stripe’s PayFac overview and responsibilities, Visa dispute guidance and dispute rule documentation, Nacha return rate thresholds and calculation guidance, and month-end close benchmark survey results.