The short answer
An ISO finds and serves merchants for an acquirer; the acquirer signs each merchant. A payfac signs merchants itself, under its own relationship with the acquirer, and usually handles their money.
Visa describes ISOs as entities acquirers use for "seller account or transaction processing solicitation, sales, customer service, seller training activities" and the sale of POS terminals, and says they "operate as agents on behalf of acquirers". A payment facilitator, in Visa's definition, contracts with an acquirer to deposit transactions, receive settlement, or contract with the acquirer on behalf of sponsored merchants. The practical line: a classic ISO does not hold the merchant contract on the acquirer's behalf and does not receive or distribute settlement funds. A payfac does one or both.
Payfac vs ISO, side by side
The two models differ on who signs the merchant, who touches the money, who carries the liability, and what a buyer ends up owning.
| Question | ISO | Payfac |
|---|---|---|
| Who signs the merchant agreement? | The acquirer; the ISO sells and supports the account | The payfac signs sub-merchants under its own acquirer relationship |
| Who receives settlement? | The merchant, directly from the acquirer or processor | Usually the payfac, which pays it out; direct settlement is allowed at the acquirer's option |
| Who underwrites the merchant? | The acquirer, under Visa's due diligence rule; any ISO role is set by contract | The payfac, under Visa's due diligence rule, overseen by the acquirer |
| Who is liable for merchant losses? | Set by the ISO agreement; varies by contract | The payfac, for sub-merchant acts, disputes and each transaction |
| Card-brand status | Third Party Agent registered by its acquirer | Third Party Agent registered by its acquirer, with a unique payfac ID |
| How it earns | Residuals: the spread over its Schedule A or buy rate | Its own pricing to sub-merchants, less processing costs |
| Money transmission question | FinCEN's 2014 ruling found the ISO activity it reviewed was not money transmission | Depends on how funds flow and on state law |
| What a buyer usually buys | A residual stream, sometimes with merchant contracts, or the ISO company | An operating company or a carve-out of its sub-merchant book |
Visa treats both ISOs and payfacs as Third Party Agents. Before an acquirer contracts with one, a senior officer must review the documentation, background-check the principals and confirm financial responsibility.
Registration ties the two models down differently. Visa registration of a Third Party Agent is specific to each acquirer, and every payfac transaction carries the payfac's own ID. That makes the sponsor bank relationship part of what a payfac buyer is buying. An ISO buyer is mostly buying contract rights to a residual and the merchant relationships behind it.
How each one makes money
An ISO earns residuals, the spread between what its merchants pay and its costs under the processor's schedule. A payfac earns the margin on pricing it sets itself.
An ISO's economics live in its Schedule A, the cost schedule that typically sets out its revenue share, interchange pass-through, transaction fees, BIN sponsorship fees and authorization and settlement fees. Its residual is roughly what the merchant is charged minus those costs, times volume. If agents or sub-ISOs brought in the merchants, they take a split, and what is left is the net residual. Splits are contract-specific.
A payfac sets the price each sub-merchant pays and pays interchange, card-brand fees and its processor and sponsor bank fees underneath. It also pays for its own underwriting, fraud management, reserves and compliance.
How to tell which one you are
Your contracts decide it, not your marketing. Check who signed the merchant agreement and where settlement lands.
- If each merchant signed an agreement with the acquirer or processor, and funds go straight to the merchant, you are working as an ISO or agent.
- If merchants signed with your company or settlement comes to you first, you are acting as a payfac under Visa's description, even if you do only one of the two.
- If a provider's payfac ID is on your transactions and its account receives settlement, you are likely a customer of a managed payfac, and what you own depends on that agreement.
- If you work under an ISO and are paid a split of its residual, you are an agent or sub-ISO. Whether you own anything you can sell depends on your agreement, especially its vesting and portability terms. See who owns the residuals.
Some businesses run more than one model at once. Our explainer what is a payfac covers the payfac side in more detail.
Why the model changes value
ISO residual portfolios are usually priced as a multiple of net monthly residual. Payfacs and ISO companies are usually priced as operating businesses, on EBITDA or revenue. The two numbers are not comparable.
For an ISO book, what counts is the net residual the buyer will actually receive, and how long it lasts. Attrition, measured by both account count and revenue, is consistently named the biggest driver. Concentration, missing merchant contracts and weak portability rights all cut value. For a payfac, the same drivers apply, plus the cost and quality of the risk program, dispute history by sub-merchant, and owned technology. Public multiples vary widely with size, year and definition, so treat any single figure with caution. See selling merchant residuals for the ISO side.
Why the model changes diligence
ISO diligence is mostly about contract rights and residual reports. Payfac diligence adds the underwriting, funding and compliance program, because the buyer inherits liability for every sub-merchant.
ISO diligence
- Residual reports by merchant over time, with attrition by count and revenue
- Schedule A, buy rates, and agent and sub-ISO splits
- Ownership and portability of the merchants, vesting terms, and change-of-control and assignment clauses
- Signed merchant agreements, since missing contracts devalue a portfolio
Payfac diligence
- Underwriting policy and sample KYB files
- Chargeback, fraud and VAMP exposure by sub-merchant, and any MATCH or VMSS history
- Handling of sub-merchants above Visa's US$1 million direct-agreement threshold
- PCI DSS validation and the sub-merchant PCI program
- Reserves, negative balances and how settlement accounts are set up
Either way, sponsor bank, processor and ISO agreements frequently require consent on a sale. Read those clauses first. Our pages on selling a payments ISO and selling a payfac cover each path.
What to do next
Confirm which model your contracts describe, then gather the records a buyer for that model will ask for.
For an ISO book, that means residual reports and your processor agreement. For a payfac, add your sponsor bank agreement, dispute data by sub-merchant and PCI DSS documents. When you want a view on value, send ranges through the offer request form, and tell us which model you run. This guide is general information, not legal advice.
