The short answer
An ISO sells merchant accounts on behalf of a processor and sponsor bank, while a PayFac becomes the merchant of record and onboards businesses as sub merchants under its own account, owning underwriting, risk, and compliance. PayFacs suit software platforms that need instant embedded onboarding. ISOs suit sales organizations that want residual economics without liability.
The Core Difference
An ISO, or independent sales organization, is a company registered through a sponsor bank to market and sell payment processing, with the processor handling underwriting, settlement, and risk. A payment facilitator is a company that becomes a master merchant and boards other businesses as sub merchants under its own account, taking direct responsibility for onboarding, underwriting, risk monitoring, and funding.
The distinction is ownership of obligation. The ISO owns a sales relationship. The PayFac owns the regulatory and financial relationship, which is why it controls the experience and absorbs the losses. Card network rules formalize the distinction: payment facilitators register as such through acquirers and take on defined obligations for every sub merchant they board.
Why Software Platforms Choose the PayFac Model
Platforms want payments inside the product: signup in minutes, instant activation, unified reporting, and a share of every transaction. Sub merchant onboarding under a PayFac takes minutes against the days a traditional merchant account can require. That control comes at a price. Industry analyses put the cost of building a full payment facilitation operation at $1 million to $3 million and 12 to 18 months, plus permanent risk, compliance, and support staffing.
That is why the model concentrates among software companies with thousands of small accounts, where the economics of owning the stack repay the build. Managed facilitation platforms now offer a middle path, renting PayFac infrastructure for a share of the economics, which trims the upfront build but also trims the margin that justified the model. For platforms processing under roughly $50 million a year, most analyses favor renting over building.
Why Sales Organizations Choose the ISO Model
A sales organization has no product to embed payments into. Its asset is distribution: feet on the street, referral networks, and closed accounts. The ISO and agent model converts that distribution into residuals without underwriting liability, capital reserves, or a compliance department. Time to first revenue is weeks, not years, and the resulting portfolio is a salable asset trading at 20 to 45 times monthly residual, depending on attrition, merchant mix, and processing volume.
The model also fails gracefully. An agent who stops producing keeps vested residuals under a well built contract, while a PayFac that stops investing in risk management inherits fraud losses that can erase years of margin in a quarter.
Which Model Pays More
PayFacs earn more per transaction because they keep the full margin, but they buy that margin with capital, staff, and loss exposure. ISOs and their agents earn a split with almost no fixed cost. For a software platform at scale, PayFac usually wins. For a sales team, the ISO route wins in nearly every model. Neither choice is a verdict on ambition; the two models simply monetize different assets, code in one case and relationships in the other.
Sales organizations that want their own brand without network registration can operate through the Batch Group Sub ISO Program on Batch's ISO registration with full portfolio ownership.
How Do the PayFac and ISO Models Compare?
Both monetize payments; they carry radically different infrastructure.
| Payment facilitator | ISO / Sub ISO | |
|---|---|---|
| Entry cost | Commonly $50,000 plus to register, with Level 1 PCI programs alone often cited near $250,000, per payfac industry guides from Stax and Infinicept | Sub ISO: application and minimums. Registered ISO: about $10,000 first year plus $5,000 renewals per network, per published schedules |
| Timeline | Months of sponsor underwriting and compliance build | Sub ISO: weeks. Registered: a season |
| Merchant onboarding | Instant sub-merchant accounts under your master MID | Traditional per-merchant underwriting through the sponsor |
| Liability | Fraud, chargeback, and compliance risk sit on you | Sponsor and processor carry the heavy risk layers |
| Economics | The full processing margin, minus the infrastructure you now run | Buy-rate spread or splits, minus almost no fixed cost |
| Best fit | Software platforms embedding payments at scale | Sales organizations monetizing distribution |
What Do the Economics Look Like in Dollars?
A software platform processing $2 million a month that becomes a payfac and keeps a net 50 basis points earns roughly $10,000 a month, against the published entry costs above and the ongoing compliance, risk, and engineering payroll the model requires. The break-even sits years out unless volume scales fast.
A sales organization pushing the same $2 million through a sub ISO seat at a 30 to 40 basis point net spread earns $6,000 to $8,000 a month against effectively no fixed infrastructure, and the resulting portfolio is a salable asset commonly trading at 20 to 45 times monthly residual, depending on attrition, merchant mix, and processing volume.
That is the honest shape of the choice: the payfac buys margin with capital and liability; the ISO path buys slightly less margin with almost none of either.
When Is Becoming a PayFac the Right Choice?
The payfac model genuinely wins for software companies where payments are embedded in the product: instant onboarding is a feature, the sub-merchant base is captive, and volume compounds with the software's growth. At tens of millions in monthly volume, owning the full margin justifies the compliance payroll.
It is the wrong model for sales organizations. Distribution businesses have no product to embed payments into, no engineering team to run the stack, and no reason to carry fraud liability. The ISO and agent path converts the same relationships into residuals in weeks, which is why payment facilitation and merchant services sales remain different industries wearing the same industry name.
Which Model Fits Your Business?
The decision usually falls out of four questions.
- Do you own software your merchants live in? If not, the payfac case collapses
- Can you fund a compliance and risk function before revenue? Published entry costs start around $50,000 and climb
- Is instant onboarding a product feature or just a nice-to-have?
- Would your capital return more building distribution on a sub ISO seat instead?
Commonly Asked Questions
- Is a PayFac the same as a processor?
- No. A PayFac aggregates sub merchants under its own merchant account while still relying on a processor and sponsor bank behind it for settlement and network access.
- How much does it cost to become a PayFac?
- Industry estimates commonly run $1 million to $3 million in build and certification costs plus 12 to 18 months of work, followed by ongoing risk and compliance staffing.
- Can an ISO later become a PayFac?
- Yes. Many organizations start as ISOs to build volume and revenue, then evaluate facilitation once they have the scale to justify the fixed costs and liability.
- How much does it cost to become a payment facilitator?
- Industry guides from Stax and Infinicept commonly cite $50,000 plus just to register, with Level 1 PCI compliance programs often near $250,000 and meaningful annual compliance spend after that, before the engineering and risk payroll the model requires.
- Is Stripe a payfac? Is Square?
- Yes, both are payment facilitators: merchants onboard as sub-merchants under their master registration in minutes. That instant-onboarding experience is exactly what platforms buy when they take on the payfac model themselves.
- Can an ISO become a payfac later?
- Yes, and the staged path is common: build volume and margin on the ISO model first, then take the payfac plunge only when embedded volume justifies the fixed costs. The reverse migration is rare, which says something about how often the payfac math disappoints.
Keep reading