Payment Facilitator vs ISO vs Direct Processor: Which Relationship Are You Actually In?

TL;DR: If you process through Stripe, Square, or PayPal and haven't read your full Terms of Service, you're likely a sub-merchant under a payment facilitator's master account — and paying for it in flat-rate spread fees and unilateral hold terms. A dedicated merchant account doesn't eliminate hold risk, but it does give you negotiated terms instead of a standard clause applied across millions of merchants.

Your payment processing account is a contract. Most merchants agree to it, click confirm, and never read it again.

That contract determines what happens to your money when a risk flag appears. It determines who holds the direct relationship with the acquiring bank. It determines what you can negotiate and what is fixed.

Three structural models govern US payment processing: payment facilitators, Independent Sales Organizations (ISOs), and direct processors. Most merchants are in one without knowing which one. This guide identifies each model, shows you the actual contract language, and explains what the structure costs.

What is a payment facilitator, and are you in one?

A payment facilitator (PayFac) is a company registered with Visa and Mastercard under its own master merchant account. Mastercard's rules define a payment facilitator as "a service provider that is registered by an acquirer to facilitate transactions on behalf of submerchants" (Mastercard Rules, December 2025). When you sign up and start processing through a PayFac's platform, you become one of those sub-merchants.

Square is explicit about this. Section 1 of their Payment Terms reads: "Square is a payment facilitator that allows you to accept Cards from customers for the payment for goods and services."

Stripe does not use the phrase "payment facilitator" in its Services Agreement. The structure is equivalent regardless. One master account. Millions of sub-merchants under it.

As a sub-merchant, you remain the merchant of record for your own sales. You are responsible for your products, chargebacks, and compliance. What you are not is the party with a direct contractual relationship with the acquiring bank. That relationship belongs to the PayFac. The PayFac controls the master account, controls access to funds in transit, and sets the terms under which your sub-account can be restricted.

The test: if your entire processing relationship started with clicking "I Agree" to a Terms of Service — no separate merchant agreement, no underwriting file in your name — you are almost certainly a sub-merchant under a PayFac.

What is an ISO merchant account, and how does it differ?

An Independent Sales Organization (ISO) is a company registered directly with Visa and Mastercard as a reseller of payment processing services. Registration requires a sponsor bank, card network approval, background checks for all principals, and ongoing compliance obligations.

When you apply through an ISO and are approved, you receive your own Merchant Identification Number (MID). That MID is yours — tied to your business with the acquiring bank. Your processing history lives under it. Your underwriting was done on your business specifically: your industry, your volume, your chargeback history.

The structural differences from a PayFac sub-merchant account:

Your reserve terms are in your merchant agreement. Before you process a single transaction, the reserve amount, trigger conditions, and release timeline are negotiated and documented. You agreed to specific terms. Not an open clause permitting holds at the processor's discretion.

Underwriting reflects your file, not a risk pool. A PayFac approves you quickly by applying population-level risk rules. An ISO underwrites your specific account: your business type, your processing history, your projected volume. Established merchants with clean histories regularly get different outcomes on individual underwriting than they would pooled with every new platform signup.

Pricing is negotiated at application, not posted. No published rate applies to everyone. Your interchange-plus markup is specific to your account.

The rates section below shows what this structure difference produces in dollar terms on a real $363,000/month account.

What does a direct processor relationship mean?

A direct processor is a card association member bank holding its own acquiring license with Visa and Mastercard. Examples include Chase Merchant Services (JPMorgan Chase Bank, N.A.) and Elavon (U.S. Bancorp). No ISO intermediary. No PayFac structure. You negotiate directly with the institution holding your account.

These relationships require extensive underwriting: detailed financial statements, business documentation, and extended review periods. The tradeoff is that you are negotiating with the bank itself. Reserve terms, pricing, and account structure reflect a direct relationship, not a reseller's program.

For most merchants reading this: if your monthly volume hasn't reached high six figures, you are almost certainly either under a PayFac or through an ISO. The direct processor path is included here so the full structural map is clear — not because it is the likely next step for most merchants at this stage.

What does your processing relationship mean for your rates?

PayFacs publish flat rates. Stripe's current rate for card-not-present domestic transactions: 2.9% + 30¢ per transaction. In-person: 2.7% + 5¢ (Stripe pricing page, 2026).

Flat-rate pricing is simple and predictable. It also means the same rate applies to every card type. Debit card transactions — which carry significantly lower interchange costs for regulated issuers — process at the same 2.7% + 5¢ on Stripe as a premium rewards card. The gap between your actual interchange cost on lower-cost cards and the flat rate is spread the PayFac keeps.

ISO accounts use interchange-plus pricing. Your actual interchange rate (set by Visa and Mastercard, published quarterly) passes through at cost. On top of that, the processor adds a fixed markup negotiated at your application. A typical markup for an established, low-risk merchant runs in the range of 0.20%–0.40% plus a per-transaction fee.

At $10,000/month, flat-rate pricing and minimal setup friction often justify the spread. At $100,000/month, the math changes. A merchant whose card mix averages 2.0% in actual interchange costs pays roughly $900/month more on a 2.9% flat rate than on interchange-plus at 0.30% — approximately $10,800/year. This is illustrative; your actual gap depends on your card mix.

Here is what the math looks like on a real account.

In April 2026, we reviewed a statement from a Canadian B2B construction supply company processing approximately $363,000/month across Visa, Mastercard, and Amex. The merchant was on a direct acquiring relationship under interchange-plus pricing. We modeled a parallel proposal under a ClickWerxs interchange-plus account.

The current processor's monthly cost: $8,176 (2.25% effective rate). The ClickWerxs proposal: $7,432 — a saving of $744/month, or $8,928/year, on identical interchange costs.

The gap had almost nothing to do with interchange, which is set by Visa and Mastercard and is non-negotiable regardless of processor. It came from two line items most merchants never check.

Assessment fees. The current processor charged 0.25% as a "VISA CARD BRAND FEE" and "MC CARD BRAND FEE." Benchmarked against Visa Canada's published network assessment rate, the markup on those two lines alone was $570/month — presented as a network pass-through, priced above the published network schedule.

Transaction fees. A single "TRANSACTION FEES" line totaled $345 for 386 transactions — implying $0.89 per transaction. Market rate at this volume: $0.08–$0.15. At $0.10, the same 386 transactions cost $39. The difference: $306/month, buried in one line with no itemized breakdown.

(Canadian B2B construction supply company, April 2026. Merchant identity anonymized. Network rates sourced from published Visa Canada and Mastercard Canada schedules.)

Both gaps are common on direct acquiring statements. Neither is visible without reading the statement line by line against published network schedules. This is also why a PayFac's flat rate is not straightforwardly "more expensive" or "less expensive" than a direct or ISO account — it depends entirely on what the processor is charging inside their pricing structure, and most merchants have no visibility into that.

What does your processing relationship mean for account stability and hold risk?

Every payment processor can hold your funds. That applies to PayFac sub-merchant accounts, dedicated ISO merchant accounts, and direct processor relationships alike. Hold risk is a feature of the payment system. It is not a PayFac-specific problem.

The difference is not whether a hold can happen. The difference is where the terms live and who wrote them.

Under a PayFac, hold terms appear in a universal Terms of Service that covers every sub-merchant on the platform. Square's §12 states they may hold funds "temporarily or indefinitely." Square's §37 states: "Square may terminate your use of the Payment Services at any time for any reason." Stripe's §10.1 permits them to "close User's Stripe Account at any time." Stripe's §12 defines reserves held at Stripe's discretion with no stated release timeline.

These terms were drafted to manage risk across a population of millions of merchants in every industry. They were not written for your specific business, your volume, or your chargeback history.

Under a dedicated merchant account, your reserve and hold conditions are in your merchant agreement. The reserve percentage, trigger conditions, and release schedule are negotiated before you go live. A merchant with documented processing history and a chargeback ratio below 0.5% has that context on file before the first transaction. The hold terms they agreed to reflect their account.

A dedicated merchant account does not eliminate hold risk. If your chargeback ratio breaches card network thresholds — Visa's VAMP program, effective April 1, 2026, sets 1.5% as the excessive threshold — your processor can still act. What you have in a dedicated account is specific, pre-agreed terms that applied to you before any of that happened. Not a blanket clause applied when a platform decides it applies to you.

This is the real distinction: not "can you be held" (yes, in any structure), but "did you agree to defined conditions before your first transaction, or to open-ended language written for everyone?"

For more on what happens once a hold is placed and the exact 24-hour response sequence, see What to Do When Your Payment Processor Freezes Your Account.

What does negotiating your terms mean, and who can you actually do it with?

With a PayFac, standard pricing and reserve terms are not negotiable. You accept the posted rate or use a different platform. Some PayFacs offer custom pricing paths for high-volume merchants, but reaching that path requires the same underwriting review an ISO applies to every merchant by default.

With an ISO, negotiation is the starting point, not the exception. Your application opens a file. That file goes to an underwriting team. The result is a merchant agreement that reflects your specific business. A merchant with two years of processing history, a chargeback ratio below 0.3%, and consistent monthly volume has leverage in that conversation. A PayFac's standard ToS does not recognize that leverage. An underwriting process does.

With a direct processor, the negotiation is the most extensive and, for high-volume merchants, can produce the most favorable terms. The entry requirements are also the highest. But direct processor pricing can still contain hidden markup in the fee lines — the $570/month in assessment fee overcharges on the B2B electrical case above was on a direct acquiring account, not a PayFac or ISO.

For any established merchant with documented processing history: the underwriting conversation that comes with an ISO application is worth more than it looks. Clean history and consistent volume are assets. They do not appear anywhere on a PayFac's application.

How do you identify which relationship you're currently in?

Check three things.

Do you have a Merchant Identification Number that belongs to you? A dedicated merchant account comes with a MID tied to your business at the acquiring bank. It appears on your processing statement from the processor. A PayFac sub-merchant account has an account ID internal to the platform — a Stripe account ID, a Square merchant ID — but this is not a card-network MID registered to you directly.

Did you sign a merchant agreement, or click a checkbox? A dedicated merchant account requires a signed agreement that names you as the merchant, specifies your pricing, and outlines your reserve terms. If your processing relationship started entirely with "I Agree" online, you are almost certainly under a PayFac.

Who do you contact when something goes wrong? With a PayFac, you go to their support queue. With a dedicated merchant account through an ISO, you have a relationship manager who contacts the processor directly on your behalf. With a direct processor, you have a bank relationship manager. The support path differs at each level — and it matters when a hold arrives unexpectedly.

When does a PayFac make sense, and when does it work against you?

A PayFac makes sense when you need to accept payments immediately with minimal application friction. It also makes sense when your monthly volume is under $10,000 and the simplicity of flat-rate pricing is worth the spread. Same if you're testing a product or market and are not yet established enough for traditional underwriting.

A PayFac works against you once your volume has grown past $50,000/month and the flat-rate spread compounds into a real annual figure. It works against you if your industry carries elevated chargeback risk and you have already experienced a hold or restriction. If you need predictable settlement timing for cash flow management, a PayFac's payout queue is less controllable than a dedicated account with documented settlement terms.

The merchants who benefit most from a dedicated merchant account are also the ones most likely to qualify for good terms: established businesses with processing history and chargeback ratios below card network thresholds. These merchants are often the last to investigate, because their current processor has not yet given them a specific reason to.

Frequently Asked Questions

When a PayFac holds my funds, where exactly is the money?

During settlement, funds move from the cardholder's issuing bank through the card network, into the PayFac's master account at the acquiring bank, then out to you. While funds are in transit through the master account, they are under the PayFac's control. Once settled to your business bank account, they are yours. The reserve and hold mechanics operate in that transit window — before the final settlement clears to your account.

Can I run a PayFac account and a dedicated merchant account at the same time?

Yes. Merchants commonly keep a Stripe or Square integration for online transactions while running card-present or high-volume sales through a dedicated account. The two don't conflict. Comparing your effective rate across both monthly statements is a productive exercise, especially if your volume splits across both.

If I switch ISOs, do I lose my processing history?

Your processing history is tied to your MID, which is held by the acquiring bank via the processor — not by the ISO. If you switch to a processor that can accommodate your history, you may be able to transfer your MID or document your history for underwriting purposes. The ISO sponsored and services your account. They do not own it.

What triggers a hold on a dedicated account vs a PayFac account?

Common triggers are the same in both structures: a chargeback ratio exceeding card network thresholds, a fraud indicator, or a volume spike that wasn't in your application. The difference is documentation. On a PayFac, the trigger lives in a universal ToS clause. On a dedicated account, the conditions that trigger a hold or reserve are in your specific merchant agreement — agreed to before you went live. You consented to defined conditions, not an open-ended clause applied at scale.

Is Stripe a payment processor or a payment facilitator?

Both in practice. Stripe operates as a payment facilitator — they hold a master merchant account, and you transact as a sub-merchant under it. Stripe also operates its own processing infrastructure in many markets. These are related but distinct roles in the payment stack. When a merchant asks "who is my processor," the more useful question for account structure is: what type of merchant account do I have — sub-merchant under a PayFac, or a dedicated MID through an ISO or direct processor?

We reviewed a B2B merchant's statement line by line against published network schedules and found $744/month in fees that weren't justified by the network rates. The merchant had been on a direct acquiring relationship for two years and had never had the statement audited. The largest single gap was $570/month in assessment fees marked above the published rate — labeled as a network pass-through.

If you process more than $30,000/month and haven't run a statement audit, that's the starting point. ClickWerxs reviews merchant statements at no charge — we look at your effective rate, your interchange mix, and whether a dedicated account makes sense for your volume and risk profile. Request a statement review.

Disclaimer: This post provides general educational information about payment processing structures in the United States and Canada. It does not constitute legal or financial advice. Payment processing rates, terms, and eligibility vary by business type, processing history, and processor. Consult your processor's current Terms of Service and your own legal counsel for advice specific to your situation.

ClickWerxs is a registered ISO. We earn a share of processing revenue from merchants we onboard.

Kaleb Dickhaut — Founder, ClickWerxs. Kaleb reviews merchant statements, onboards accounts, and works directly with underwriting teams on behalf of ClickWerxs clients. linkedin.com/in/kalebdickhaut

Sources

1. Processing rates, fee ranges and effective-rate figures in this post are industry-typical ranges compiled from published network schedules and from accounts reviewed in the ClickWerxs ISO portfolio. They are not quoted rates. Interchange itself is set by Visa and Mastercard on published schedules that change twice yearly; your actual cost depends on card mix, MCC, ticket size and volume.
2. Federal Reserve Board, Regulation II debit card interchange fee standard — covered issuers may not receive more than $0.21 plus 0.05% of transaction value, plus a $0.01 fraud-prevention adjustment where eligible. federalreserve.gov
3. Competitor and platform pricing referenced in this post is taken from each company's published pricing or legal pages as of the date noted in text, and is subject to change without notice. ClickWerxs does not link to competitor websites; references are given in text so they remain verifiable. No affiliation is implied.
4. ClickWerxs ISO portfolio, aggregate observation — patterns described from merchant accounts under ClickWerxs management. Anonymized and reported in aggregate; individual account terms vary. Operator data.

ClickWerxs facilitates merchant account applications and provides ongoing account management as an authorized representative of our banking and processing partners. Approval, rates, and terms are determined by the issuing processor and acquiring bank — ClickWerxs does not guarantee approval for any merchant account application. Processing rates and fee structures cited in this post reflect publicly available industry data and general ranges; your actual rate depends on your industry, volume, and card mix. This post is not legal or financial advice. For a custom quote, see clickwerxs.com/payments/get-a-quote.