If your platform processes under roughly $10 million a year and lacks a dedicated payments team, start with an ISO or referral partnership. Once volume grows past that range and you need control over onboarding, funds flow, and merchant experience, a managed PayFac is usually the smarter step before pursuing full PayFac registration. The real trade-off is always the same: more control and better economics in exchange for more operational weight.

TL;DR:

  • Platforms processing over $10 million annually or with a high-risk vertical should consider transitioning to a managed PayFac for better control and higher margins.
  • Fully integrated PayFacs absorb portfolio risk and require ongoing monitoring, reserves, and compliance, increasing operational complexity compared to ISO models.
  • Most platforms reach the marginal benefit threshold of PayFac economics at volumes in the tens of millions of dollars per year, with smaller volumes typically better suited for ISO partnerships.
  • Moving between models takes three to six months, largely due to reboarding merchants, migrating data, and negotiating vault token portability.
  • The key to choosing the right model is understanding volume, risk profile, reserve requirements, and merchant experience control, not just branding or superficial features.

Table of Contents

PayFac vs. ISO: What Is a Payment Facilitator?

A payment facilitator, or PayFac, sits underneath its own master acquiring relationship and onboards businesses as sub-merchants rather than as fully independent merchant accounts. Stripe Connect and Shopify Payments are the two most recognizable examples: a seller signs up in minutes, but that speed comes from the PayFac absorbing the underwriting and portfolio risk that would otherwise sit with a traditional acquirer, Greensheet’s rundown of platform models notes.

The PayFac handles onboarding, KYC checks, underwriting, and ongoing portfolio monitoring itself instead of routing each application to a bank for approval, according to Stripe’s comparison of PayFac and ISO models. Funds typically flow through the PayFac before reaching the sub-merchant, which gives the PayFac visibility and control, but the sub-merchant is still legally responsible for its own product, refunds, and dispute conduct.

What a merchant experiences under a PayFac usually includes:

  • Fast, often instant, onboarding through an embedded application flow
  • A shared reserve pool or individual holds tied to risk scoring
  • Limited negotiating power on fees, since pricing is typically set by the platform
  • Faster access to features like split payouts, recurring billing, and embedded fraud tools
  • A dependency on the PayFac’s own risk appetite, which can mean sudden holds if the portfolio trips a threshold

PayFac vs. ISO: What Is an Independent Sales Organization?

An ISO is a sales and referral channel, not an acquirer. It signs merchants up for accounts, but the underlying processor or bank actually holds the merchant agreement and performs underwriting. That distinction matters more than most new platform operators realize: an ISO refers merchants to a processor and does not hold merchant accounts itself, with the processor or acquirer handling underwriting, settlement, and compliance, per Margin Labs’ breakdown of the ISO model.

The ISO earns residual income, typically a share of the processing spread measured in basis points, for the life of the merchant relationship. It’s a lightweight business model: no underwriting staff, no reserve liability, no compliance department. That’s exactly why it’s the fastest way to start earning from payments without building anything.

Working through an ISO comes with a familiar list of trade-offs:

  • Fast setup with minimal internal resources required
  • No underwriting burden or reserve capital tied up on your books
  • Lower economics, since residuals are a fraction of what a PayFac keeps
  • Little control over merchant experience, pricing flexibility, or onboarding speed
  • Limited say in how disputes, holds, or account terminations get handled

Key Differences: Contracts, Risk, Onboarding, and Tech

The fastest way to tell these models apart in practice is to ask three questions: who holds the merchant contract, who underwrites the account, and who executes settlement. If the answer to all three is the same entity, you’re in a PayFac relationship. If the acquirer or processor answers all three, you’re in an ISO arrangement, according to AcmeTicketing’s practical verification test.

Here’s how the two models diverge across the dimensions that actually drive a decision:

  1. Contract ownership. Under an ISO, the processor holds the merchant agreement. Under a PayFac, the platform (or its managed PayFac partner) holds it, with sub-merchants operating under that master agreement.
  2. Risk and liability. ISOs push chargeback and fraud liability to the processor. PayFacs absorb portfolio-level risk directly, which means a fraud spike from one bad sub-merchant can trigger reserve increases across the whole book.
  3. Onboarding speed. Traditional merchant accounts arranged through an ISO can take weeks to approve. PayFac onboarding often happens in minutes, a gap Greensheet calls one of the primary product advantages of the PayFac model for platforms and marketplaces.
  4. Funds flow and settlement timing. ISO merchants get funded directly by the processor on its standard schedule. PayFac sub-merchants get funded by the platform, which can offer faster or more flexible payout timing, but also introduces settlement risk if the PayFac’s own liquidity gets stretched.
  5. Technology and PCI scope. ISOs typically integrate with a processor’s existing gateway with limited customization. PayFacs build or license their own integration layer, taking on more PCI-DSS scope in exchange for owning the checkout and payout experience end to end.

Pro Tip: Before signing with any partner, ask directly whether vaulted card credentials are portable. If a provider won’t commit to exporting tokenized payment data on request, treat that as a warning sign, not a technicality.

Economics and Rules of Thumb: Residuals vs. Keeping the Spread

The dollar math is where this decision gets real. An ISO relationship pays you a residual, usually a small basis-point cut of processing volume, for referring merchants into someone else’s acquiring relationship. A PayFac keeps the full processing spread, the difference between what it charges merchants and what it pays its own acquiring bank, minus the cost of running underwriting, risk, and support internally.

Industry rules of thumb put the crossover point where PayFac economics start outperforming ISO residuals somewhere in the tens of millions of dollars in annual processed volume, often cited around a moderate high-volume threshold, according to FintekCafe’s analysis of merchant-of-record and PayFac risk models. Below that, the operational cost of running underwriting, reserves, and compliance usually eats more than the extra margin delivers.

A few numbers to sanity-check your own volume against:

  • Under a lower annual volume level generally considered small, ISO residuals often outperform PayFac economics once you account for staffing and compliance overhead.
  • At moderate volume levels, a managed PayFac (PayFac-as-a-service) frequently captures meaningfully more margin without requiring a full compliance build-out, a middle path described as a pragmatic option for platforms not ready to build their own risk organization.
  • At higher volumes, full PayFac registration typically starts to justify its fixed costs through the wider processing spread.

The volume threshold where PayFac math flips is the single most useful number in this whole decision, and it’s why platforms that guess at their own scale instead of modeling it tend to over-invest in infrastructure they don’t need yet.

Operational Implications: Underwriting, Reserves, and Support

Running payments changes what your team does every day, not just what you earn. A PayFac owns continuous KYC and AML monitoring, not just a one-time application review. Sub-merchants get re-screened as their volume or risk profile shifts, and that monitoring has to run indefinitely, not just at signup.

Reserve structures follow directly from that risk exposure. Rolling reserves hold back a percentage of each settlement for a fixed window; triggered holds freeze funds when a merchant’s chargeback ratio or refund pattern crosses a threshold. Either type ties up real cash, and platforms that underestimate reserve requirements often discover the liquidity hit only after their first fraud spike.

The operational checklist for running a PayFac (or evaluating a managed PayFac partner) typically includes:

  • A documented chargeback workflow with defined response-time SLAs
  • Fraud-scoring tools tuned to your specific merchant vertical, not generic ecommerce defaults
  • PCI-DSS compliance for however much of the transaction flow you touch directly
  • A dedicated support function for sub-merchant disputes and account holds
  • Clear internal escalation paths when a single sub-merchant’s fraud rate threatens the whole portfolio’s reserve terms

Solid guidance on the compliance side, including day-to-day controls most underwriting teams should have in place, is covered well in this payment processing compliance guide, and chargeback teams specifically benefit from a staged approach like the one outlined in this 30/90/180-day chargeback reduction playbook.

Pro Tip: Model your reserve requirements against your worst historical month, not your average month. Reserves exist precisely for the outlier, and platforms that size them against average volume routinely get caught short.

How to Choose: Checklist, Questions, and Contract Red Flags

Six factors should drive the decision: your current volume, merchant count, vertical risk profile, in-house operations capacity, how fast you need to launch, and how much control you actually need over the merchant experience. High-risk verticals like nutraceuticals or telehealth tend to push platforms toward a managed PayFac sooner, since generic ISOs are often reluctant to underwrite those categories at all.

Before signing with any partner, ask these questions directly:

  1. Who holds the merchant contract, and can you get that in writing?
  2. Who performs underwriting and ongoing monitoring, and how often does re-screening happen?
  3. Who holds settlement funds, and what’s the payout timeline?
  4. Are vaulted card credentials portable if you switch providers later?
  5. What’s the contractual SLA on settlement timing, and what happens if it’s missed?

Watch for a few specific red flags in any proposed agreement: non-portable vaulted credentials, vague or undefined reserve terms, escape clauses that only benefit the provider, and indefinite hold periods with no stated release condition.

Business stage Likely fit
Testing payments monetization, low volume ISO/referral
Scaling volume, need more margin, not ready to build compliance Managed PayFac
High volume, vertical expertise, control over UX and risk Full PayFac

The recommended path for most platforms is sequential: start with an ISO or referral to validate demand, move to a managed PayFac once volume and vertical risk justify it, and pursue full PayFac registration only when the economics and operational readiness both clearly support it.

Migration and Practical Next Steps

Moving from an ISO/referral setup to a managed PayFac, or from managed to full PayFac, typically takes three to six months. Most of that time goes into reboarding existing merchants under new underwriting criteria, migrating dispute histories, and reconciling settlement records against the old provider’s reporting.

Vaulted credential portability is the term that decides whether migration is smooth or painful. Losing access to tokenized card data means every subscription merchant has to re-collect payment information from customers, which is a fast way to lose recurring revenue during a transition.

Practical steps that reduce migration risk:

  • Negotiate vault export rights into the contract before you sign, not after you decide to leave
  • Communicate timeline and any temporary limitations to merchants well ahead of cutover
  • Reconcile open disputes and chargebacks before migrating settlement records
  • Budget for a churn buffer, since some merchant attrition during reboarding is normal even with a clean process

What Most Platforms Get Wrong About This Decision

Most platforms treat PayFac vs. ISO as a branding decision instead of a volume and risk decision. It isn’t. The math is fairly mechanical once you know your processed volume, your vertical’s risk profile, and your appetite for reserve liquidity, yet plenty of teams pick full PayFac status because it sounds more sophisticated, then discover the compliance overhead outpaces their revenue for a year or two.

Davincipay works specifically with high-risk and complex ecommerce businesses, including nutraceutical brands, telehealth providers, and subscription merchants, on exactly this kind of underwriting and acquiring complexity. That vantage point makes one pattern obvious: the platforms that struggle most are the ones that skip the managed PayFac stage entirely and try to jump straight from referral partner to full acquiring relationship without building the fraud, reserve, and support infrastructure first.

The bigger mistake isn’t picking the wrong model. It’s picking the right model at the wrong volume, then blaming the framework instead of the timing.

— Peter

Ready to Move Beyond ISO Limitations?

If your platform has outgrown what a standard ISO referral can offer, Davincipay gives you a faster path to PayFac-level control without building an underwriting department from scratch. Davincipay specializes in acquiring relationships, underwriting support, fraud prevention, and chargeback mitigation for high-risk and complex ecommerce categories, exactly the verticals where generic ISOs tend to say no.

Davincipay

Whether you’re running a nutraceutical subscription brand, a telehealth platform, or another regulated business that needs specialized payment infrastructure, Davincipay’s team can walk you through whether a managed PayFac setup fits your current volume or whether an ISO relationship still makes sense for now. If you’re processing enough volume to feel the limits of residual-based economics, apply now and get a straight answer on what your next step should look like.

Sources