PayFac vs. ISO: Which Payment Model Fits Your Business?

Quick answer: The difference is who holds the merchant account. A payment facilitator (payfac) holds one master merchant account and onboards you as a sub-merchant underneath it, which means approval in minutes and simple flat-rate pricing. An ISO (Independent Sales Organization) is a reseller that places you into your own direct merchant account with an acquiring bank, which means slower underwriting but more control, better rates at volume, and a more stable account. Speed and simplicity point to a payfac. Volume, control, and negotiated pricing point to an ISO.

Both models exist to get businesses accepting card payments without dealing directly with an acquiring bank. They arrive at that goal from opposite directions, and the structural difference drives everything else: how fast you onboard, what you pay, who carries the risk, and how likely your account is to be shut off without warning.

This guide breaks down both models and covers who should choose which. For the underlying model, see our complete guide to what a payment facilitator is.

What is an ISO?

An Independent Sales Organization is a third party authorized to sell payment processing services on behalf of an acquiring bank. Think of it as a broker or reseller in the payments supply chain.

When you sign with an ISO, it takes your application to an acquirer, which underwrites you as an individual business and issues you your own merchant identification number (MID). The relationship is genuinely yours: your business is the merchant on record with the bank, and the ISO earns commission on the processing volume it brings in.

ISOs typically bundle in service: equipment, gateway setup, rate negotiation, and an account representative. Many operate regionally or specialize in particular industries, and a good one earns its margin through advocacy, especially when you need a rate review or a risk decision reversed.

What is a payfac?

A payment facilitator holds a single master merchant account with an acquirer and onboards businesses as sub-merchants beneath it. Rather than each business being underwritten by the bank, the payfac does its own KYC and risk assessment, then approves or declines in near real time.

Stripe, Square, PayPal, and Shopify Payments are the familiar examples. You don't get your own MID. You operate under the payfac's, which is precisely what makes onboarding take minutes instead of weeks.

The payfac absorbs the risk the bank offloaded. If a sub-merchant racks up chargebacks it can't cover, the payfac pays.

PayFac vs. ISO at a glance

Dimension	Payment Facilitator (PayFac)	ISO
Who holds the merchant account	The payfac (master account)	You (your own MID)
Your status	Sub-merchant	Merchant
Onboarding time	Minutes to hours	Days to weeks
Underwriting	Payfac's automated KYC	Bank's full underwriting
Pricing model	Flat blended rate (e.g. 2.9% + 30¢)	Interchange-plus or tiered, negotiable
Rate at high volume	Less competitive	More competitive
Who carries chargeback risk	Payfac, then you	You, with the bank exposed
Account stability	Lower, can be shut off quickly	Higher, contractual relationship
Support model	Self-serve, ticket-based	Account rep, relationship-based
Handles your sales tax / VAT	No	No
Best for	Small, fast-moving, low-volume	Established, higher-volume

Onboarding and underwriting

This is the clearest practical difference, and it cuts both ways.

Payfac onboarding is designed to be frictionless. Enter business details, connect a bank account, and process a payment the same day. The payfac accepts you into a pre-approved risk pool rather than underwriting you individually.

The cost of that speed shows up later. Because approval was fast and shallow, payfacs monitor aggressively afterward. Sudden volume changes, a chargeback spike, or a shift in what you sell can trigger a review, a funds hold, or account termination with little notice. Anyone who has read horror stories about frozen payment accounts is reading about this trade-off.

ISO onboarding is slower because a bank is genuinely underwriting your business: financials, processing history, industry risk, and sometimes personal guarantees. It takes days to weeks and you may be declined.

The payoff is stability. You have a contractual relationship with an acquirer that includes defined terms for termination and reserves. Accounts are far less likely to be switched off overnight, which matters enormously once payments are load-bearing for your business.

Pricing and economics

Payfacs publish simple blended rates. The familiar 2.9% + 30¢ is easy to understand and predict, and it's genuinely competitive at low volume because you're not paying for account management you don't need.

That simplicity costs you at scale. A blended rate has to cover the payfac's risk across its whole portfolio, so as your volume grows you're increasingly subsidizing riskier merchants.

ISOs typically offer interchange-plus pricing: actual interchange cost, plus a defined markup. It's less predictable month to month but more transparent, and usually cheaper once volume is meaningful. It's also negotiable, which a payfac's published rate generally isn't.

The rough crossover point is somewhere around $50,000 to $100,000 in monthly processing volume, though it depends heavily on your card mix and average transaction size. Below that, a payfac's simplicity usually wins on total cost once you account for the admin overhead of a direct account. Above it, an ISO relationship is often worth the friction.

Risk, liability, and control

With a payfac, the payfac is liable to the acquirer for your chargebacks, but it will recover from you where it can, including by holding your funds. You have limited visibility into risk decisions and limited recourse when one goes against you.

With an ISO, you carry your own chargeback liability directly and may need to fund a reserve. In exchange you get transparency into your own risk profile, direct contractual terms, and an account rep who can argue your case.

There's also a control dimension. Your own MID means portable processing history, the ability to negotiate, and the freedom to switch processors without rebuilding your customer payment relationships. Sub-merchant status under a payfac gives you none of that.

What neither model solves

Worth stating clearly, because it catches out a lot of software businesses: neither a payfac nor an ISO handles your sales tax or VAT.

Both arrangements leave you as the legal seller of your product. That means you're responsible for registering, calculating, collecting, filing, and remitting consumption taxes in every jurisdiction where you have obligations, whether that's US state sales tax under economic nexus rules or EU VAT on digital services.

Both also leave you holding product liability, consumer-protection obligations, and refund policy. They're payment-acceptance models, not liability-transfer models.

If you want those obligations genuinely off your books, you're looking at the merchant of record model, where a provider becomes the legal seller and takes on the tax and compliance burden with it. For software and digital sellers going global, that's usually the deciding factor rather than the payfac-vs-ISO question at all. (See Merchant of Record vs. Payment Facilitator.)

Which model should you choose?

Choose a payfac if you:

• Need to start accepting payments now, without an underwriting process
• Process modest volume where a flat rate is genuinely competitive
• Prefer predictable pricing over the lowest possible rate
• Are early-stage and testing whether the business works at all

Choose an ISO if you:

• Process meaningful volume, where interchange-plus beats a blended rate
• Want account stability and contractual protection against sudden termination
• Operate in an industry payfacs treat as high-risk
• Value having an account rep who advocates for you

Look at a merchant of record instead if you:

• Sell software, SaaS, or digital products internationally
• Face VAT, GST, or multi-state sales tax obligations that are growing faster than your finance capacity
• Want chargeback and compliance liability off your books, not just the payment plumbing solved
• Would rather have one relationship than a processor plus a tax engine plus a compliance function

The bottom line

PayFac vs. ISO comes down to a trade between speed and control. A payfac gets you processing today with simple pricing and shallow underwriting, at the cost of account stability and rate competitiveness as you grow. An ISO makes you wait for real underwriting, then gives you your own merchant account, negotiable pricing, and a relationship that doesn't disappear overnight.

For most businesses the honest answer is that you start on a payfac and graduate to an ISO relationship when volume justifies it.

But if you sell software or digital products across borders, both models leave the harder problem untouched. The tax, the compliance, and the legal-seller status stay with you. If you'd rather transfer those too, talk to the team at Comecero. We act as merchant of record for SaaS, AI, and high-ticket digital sellers, covering payments, global tax remittance, and chargeback liability in a single relationship.