Residuals

Residuals are the economic engine of the ISO and agent channel. When an ISO signs a merchant to a processor’s program, it does not earn a one-time commission; it earns a defined share of the ongoing processing margin on that merchant, month after month. A portfolio of residual-paying merchants behaves like an annuity, and portfolios are regularly bought and sold at multiples of monthly residuals.

How the math works

Residuals are calculated from the margin above cost. Suppose a merchant processes $100,000 a month priced at interchange plus 30 basis points plus $0.10 per transaction. The margin above interchange and network costs might come to roughly $400. Under a 60/40 split, the ISO’s residual is about $240 a month from that merchant. Multiply across a 300-merchant portfolio and residuals become a serious recurring business, which is why the accuracy of the residual statement matters so much. Splits cascade too: ISOs share residuals downstream with sub-agents and referral partners, each layer needing its own reporting.

The same concept applies to software platforms under PayFac-as-a-Service: the platform’s share of payment economics on its merchants is functionally a residual stream, whatever the contract calls it.

Why it matters

Residual disputes are among the most common sources of friction between ISOs and processors, almost always caused by opaque reporting: bundled cost lines, unexplained adjustments, statements delivered as PDFs that cannot be audited. When choosing a processing partner, ask to see an actual residual statement: line-item detail per merchant, costs separated from markup, and data accessible via export or API rather than locked in documents.

QorPay reports residuals through QorCommerce Reporting and Portfolio Tools, with portfolio- and channel-level detail designed for ISOs running multi-tier agent splits on the Channels module.