Residuals

Definition

Residuals are the leftover card-processing economics after interchange, network assessments, and the processor or payment facilitator take their contracted share. In the ISO and PayFac tradition, a residual is the ongoing split of merchant processing income, paid as volume continues, not as a one-time integration or SaaS fee. In vertical software, residuals usually mean the spread you keep over time between what merchants pay and what the acquiring program costs. That is not the same as an application fee attached to someone else’s rate card. This page does not print a residual percentage. Splits are contractual and vary by program.

This page is the leftover economics over time. Adjacent terms are Vertical Fintech’s. They are not this page. Interchange-plus (how the buy rate is shown), application fees (a platform cut on a charge), PayFac (who is registered), and sponsor-bank details sit next to this definition.

Why it matters

If you run vertical software, “we take a rate” can mean two different businesses. An application fee ships this quarter and dies when the processor changes pricing or you leave the stack. Residuals are the claim that the spread on your merchants keeps accruing to you as they process. Most teams on this directory should not pretend they own residuals on day one. The registered PayFac or processor still holds the merchant terms, the buy rate, and often the book if you churn. Ask whether the spread is assigned to you, whether it survives a processor or bank change, whether there is a buyout, and who the merchant agreement names. If the listing says residual economics you own are not the fit, believe it. Visible IC+ math is not ownership. A path to take the license later is a path, not residuals today.

Related on Vertical Fintech

• Payments: PayFac-as-a-service and platform payments. Take a rate on merchant volume without becoming a PayFac.
• Interchange-plus: The buy-rate shape. Visible plus is not the same as owning residuals.
• Application fee: A platform cut on a multiparty charge. Usually not a residual book you keep if you leave.
• Payment facilitator: Who is registered. Residuals are easier to argue when you are that party, or when the contract assigns the spread.
• Stripe Connect: Default start for payments revenue without becoming a PayFac. Not residual economics you own.
• Finix: PFaaS now, same API if you later take the license. The later path is how some teams get closer to residuals they own.
• Rainforest: Published IC+ buy rate and you set sell price. They stay on the merchant processing terms.

FAQ

If I take an application fee, do I own residuals?

Usually no. An application fee is a cut on charges while the processor keeps the license and the rate card. Residuals are an ongoing claim on the spread as merchants process, including what happens if you change stacks. Read the contract. Do not equate a fee field in an API with a residual book.

Do residuals survive if I change processors or banks?

Often no, unless the agreement assigns the merchant book and the spread to you and says they port. Many PFaaS programs keep merchant terms with the registered party. A documented path to become the PayFac is the usual way teams try to own economics later. Confirm buyout, assignment, and who the merchant agreement names.