Most merchants do not pick their processing setup. They sign up with whichever option their software platform, sales rep, or accountant put in front of them. That choice quietly drives your pricing, your approval rates, your funding speed, and how much control you have when something goes wrong.
This guide compares the three structures merchants actually run on today: a payment facilitator (PayFac) submerchant account, an account through an ISO (Independent Sales Organization), and a direct merchant account with an acquiring bank. It also covers the hybrid setups that are increasingly common, and the signals that should push you from one model to another.
A payment facilitator is a registered entity that holds a master merchant account with an acquiring bank and onboards businesses underneath that master account as submerchants. Stripe, Square, PayPal, Adyen for Platforms, and most modern SaaS platforms that have "payments built in" operate as PayFacs or PayFac-adjacent.
From your perspective as a submerchant, the most visible features are:
PayFacs absorb risk in exchange for control. If your business model is straightforward and your transaction volume is below the PayFac's risk thresholds, you get fast setup and easy integration. If your volume grows or your model has any risk wrinkles (high ticket size, recurring billing, certain verticals), the PayFac will eventually push back.
An ISO is a registered seller of merchant accounts for one or more acquiring banks. The ISO does not hold the merchant funds itself - the merchant account is in your name with the acquiring bank, but the ISO handles sales, onboarding, support, and sometimes underwriting on the acquirer's behalf.
Key features:
The trade-off is that ISO setup is slower (a few days, sometimes longer for higher-risk verticals) and the experience varies widely by ISO. A good ISO is a partner that defends your account and negotiates on your behalf. A bad ISO is a price markup on top of an acquirer with no added value.
A direct merchant account is the traditional setup: you contract directly with an acquiring bank (or a sponsor bank), you go through full underwriting, and your account is in your business name on the acquirer's books. There is no PayFac or ISO sitting between you and the acquirer.
This is what large enterprise merchants and high-volume retailers run on. Setup is slower still, the contracts are more involved, and the pricing is usually the most aggressive of the three options. You also take on more of the operational burden: PCI scope, statement reconciliation, chargeback management, and ongoing compliance reporting.
The three models differ on speed, pricing, control, and risk tolerance.
| Dimension | PayFac (submerchant) | ISO merchant account | Direct merchant account |
|---|---|---|---|
| Onboarding time | Minutes to hours | 1 to 7 days | 1 to 4 weeks |
| Pricing model | Flat-rate (2.9% + 30c typical) | Interchange-plus or tiered | Interchange-plus, lowest markup |
| Underwriting depth | Light, automated, risk-model driven | Deeper, business-specific | Full enterprise underwriting |
| Funding speed | 1 to 2 days, sometimes instant | 1 to 2 days standard | Next-day standard |
| Account stability | Can be suspended quickly | Usually defended by the ISO | Most stable, contractual relationship |
| Suitable monthly volume | Up to ~$50k typical, more for low-risk | $25k to $1M+ | $100k+ |
| Customization | Minimal | Moderate | High (gateway, fraud rules, settlement) |
| Best for | Early stage, low-risk, SaaS embedded payments | Established SMB and mid-market | Enterprise, high-volume, complex risk |
The exact volume thresholds vary by acquirer and by industry, but the shape of the trade-off is consistent. PayFacs trade pricing power and stability for speed. Direct accounts trade speed for pricing power and stability. ISOs sit in the middle and let you pick which trade-offs matter most.
A few practical questions help narrow the choice.
If your ticket size is consistent, your volume is steady, and your refund and chargeback rates are low, almost any model works. The choice becomes about pricing.
If your ticket size varies (high-ticket coaching, consulting, custom B2B work), if you have seasonal spikes, or if your chargeback rate is above 0.5%, you should not be on a PayFac. PayFac risk models do not handle outliers well and you will spend a meaningful amount of time getting holds released or appealing terminations.
Below roughly $25,000 to $50,000 per month, PayFac flat-rate pricing is usually competitive with ISO interchange-plus, because the ISO has to cover underwriting and support costs that the PayFac amortizes across millions of submerchants. Our guide on reducing credit card processing fees walks through how to read your effective rate so you can compare like-for-like.
Above $50,000 per month, ISO interchange-plus typically saves real money. Above $250,000 per month, a direct merchant account is worth the slower setup.
PayFacs decide the gateway, the fraud rules, and which products you can accept. ISOs let you pick from a list of gateways and gives you visible control over many fraud settings. Direct accounts let you bring almost any compliant gateway and tune fraud and risk rules at the network level.
If you are running multi-channel retail (card-present plus card-not-present), or you have a sophisticated fraud stack, you will outgrow a PayFac quickly. Our explainer on the difference between a payment gateway and a merchant account covers why these are two separate pieces and why owning the gateway matters as you scale.
PayFacs are famous for sudden account freezes. If you wake up one Monday and your PayFac has locked your funds for a 90-day review, your business stops. ISOs and direct acquirers can also freeze accounts, but they are far less likely to do so without warning, and they are far more likely to work with you on a path forward.
If a 90-day freeze would close your business, do not stay on a PayFac as your primary processor once your monthly volume exceeds $25,000.
Many merchants now run two or three processing setups in parallel. The most common patterns:
The cost of running parallel processing is more operational complexity (reconciliation across systems, separate chargeback workflows), but the resilience is real. A processor outage or a sudden suspension stops being existential.
PCI compliance scope depends on how your business handles card data, not which model you are on, but the three structures change who carries which pieces of the work.
If you are unsure about your PCI scope, start with our PCI compliance guide for small business. The right answer is not always "the lowest SAQ I can claim". The right answer is the SAQ that actually matches how card data moves through your stack.
The most common migrations are:
Migrations are usually planned in two phases: getting the new account approved and connected, then shifting volume gradually over 2 to 4 weeks while you confirm the new setup handles your edge cases (refunds, recurring billing, currency conversion, settlement timing).
No. The structural difference is that the PayFac is the merchant of record for the funds it processes. An ISO sells the merchant account, but the merchant of record is the business itself, with the acquiring bank. That difference drives most of the downstream differences in pricing, control, and risk.
Yes, and some merchants do this deliberately for redundancy. Each PayFac will underwrite you independently, and you will manage settlement and reconciliation across both. The card brands generally do not restrict this, but be honest in each application about your processing relationships.
Most do, but several large PayFacs now offer interchange-plus pricing once you cross a volume threshold. Read the contract: the underlying acquirer and the actual settlement mechanics are usually unchanged, so the "interchange-plus" offer is real but the account is still a submerchant account, not a true MID.
Probably not, but it will change how chargebacks are handled. PayFacs typically dispute on your behalf with limited input. ISOs (and direct acquirers) give you control over representment and supporting documentation. If you have a chargeback problem, switching to an ISO usually means you can fight more of them, but the underlying customer experience issues still need to be fixed.
Not always. A direct merchant account is usually cheaper at very high volume, but at sub-$250k monthly volume the savings often do not cover the operational overhead of running a direct relationship. A well-priced ISO can match direct economics until you scale significantly past that threshold.
VC-backed and public companies typically end up with either an ISO that they have negotiated hard with, or a direct relationship with one or two acquirers. PayFac submerchant accounts get retired because the lack of contractual stability shows up in audits and risk reviews. Plan to migrate off PayFacs before you cross $5 million in annual processed volume if you are heading toward an institutional capital event.
If you are sub-$25k per month and your risk profile is clean, a PayFac is usually the right starter. If you are above $25k per month or you have any risk wrinkles, a well-priced ISO is the better default. If you are above $250k per month or you have multi-MID needs, evaluate a direct relationship.
You can apply for a merchant account through Easy Pay Direct or another processor that fits your model. Other options worth a look: